esrille / escudo Goto Github PK

cf. http://lists.fedoraproject.org/pipermail/announce/2013-May/003161.html

• Fedora-19-Beta-x86_64 (6800297)
• Fedora-19-RC3-x86_64 (6800297)

Note event handler content attributes are handled at #4.

Otherwise, file descriptor offsets can be changed unexpectedly. For instance, CSS @import rule is not handled properly since 739eaac.

cf. http://dom.spec.whatwg.org/#dom-element-tagname

and also,

https://developer.mozilla.org/ja/docs/Updating_extensions_for_Firefox_3.6

cf. b860795

cf. http://www.w3.org/TR/DOM-Level-3-Events/#event-type-mouseover

cf. https://developers.google.com/v8/embed#contexts

It turns out supporting XBL binding documents is very hard in the current activation model with the V8 API.

cf. http://www.w3.org/TR/html5/dom.html#dom-document-lastmodified

It must be redesigned to support multiple contexts.

Items needed to be refined:

• window . frameElement; 983d9d2
• window . name; cae4e52
• window . open; 1d9dde7

cf. http://www.w3.org/TR/html5/dom.html#dom-style

The 11th box has a red square inside of it:

http://test.csswg.org/suites/css3-color/nightly-unstable/html4/t32-opacity-zorder-c.htm

The 'text-align' property of an absolutely positioned box should be applied to its child 'inline-block' elements.

test-case: https://github.com/esrille/escort/blob/b5c184ac9a309be6ae2089135220a2f1842b2c78/testdata/css-001.html

• JSAPI 3d6af19
• V8 API 3cd5caf

cf. https://github.com/esrille/escort/blob/master/testdata/html-019.html

Missing fonts, building Escort in OSX is available but executing is not.

I suggest discoverying fonts by code.
For example,
https://gist.github.com/Constellation/4946675
works and lists available font pathes on OSX.

But since this code touches CoreText framework directly, code becomes a little complicated.
So I also suggest adding backend-specific code directory such as src/font/mac and enabling Objective-C++ building support to Makefile.am.

Switch out eval() for new handleMutation() method if possible.

cf. http://domparsing.spec.whatwg.org/

Implement HTML features that are used in testharness.js sooner than later.
cf. https://github.com/w3c/testharness.js

Items to be supported:

• [DOM] Support Element.innerHTML setter #19
• [DOM] Support document.createElementNS 44801fe
• [selectors-api] Support Selectors API Level 1 #21 199d49c
• [js-bridge] Make hasOwnProperty() work with indexed properties #22
• [CSS] Reflect the dynamic creation/removal of a style element to the layout #45 739eaac

HTMLElementImp::eval() has been used to perform additional operations for each element inserted into the DOM tree. Most of them can be processed by mutation callbacks and fixed in issue #12.

Note even though the spec says,
"DOM mutation events must not fire for changes caused by the UA parsing the document. This includes the parsing of any content inserted using document.write() and document.writeln() calls." - http://www.whatwg.org/specs/web-apps/current-work/multipage/tree-construction.html#tree-construction
we still need to fire DOM mutation events from the parser for DEFAULT_PHASE (not for other phases). As we'll switching over to Mutation observers, this might be changed as well.

The remaining elements that still use eval() are the link and object elements.

As for the link element, resources can be obtained later rather than just after the element is parsed:
"User agents may opt to only try to obtain such resources when they are needed, instead of pro-actively fetching all the external resources that are not applied." - http://www.w3.org/TR/html5/document-metadata.html#concept-link-obtain

As for the object element, the conditions to execute steps similar to eval() are listed in the paragraph starting with "Whenever one of the following conditions occur:" in,
http://www.w3.org/TR/html5/embedded-content-0.html#the-object-element

cf. http://dev.w3.org/csswg/selectors4/#attribute-case

Note attribute case-sensitivity flags are used in HTML5.

cf.
http://www.w3.org/TR/html5/browsers.html#event-hashchange
http://www.w3.org/TR/html5/browsers.html#scroll-to-fragid
http://www.w3.org/TR/html5/browsers.html#traverse-the-history

Currently, in OSX, escort crashes when page load happens.

Crash is caused at BoxGL.cpp void deleteImage(uint8_t* image)'s glDeleteTextures.

Investigating it, I've found that gs register based mov code in glDeleteTextures returns unexpected value ($0). I remember that gs is the register related to thread local value.

I think that the crash is caused since glDeleteTextures is called from the different thread from generating texture thread.

Since 739eaac, a DOMCharacterDataModified event is triggered for each character which is just parsed and inserted to a DOM node. It should be just one event at the end of a sequence of characters within a node.

In practice, what we'd need is a single DOMNodeInserted event for a Text node instead of a DOMNodeInserted event followed by a sequence of DOMCharacterDataModified events.

At this time, we should test css3-color [1] in addition to css2.1.

[1] http://test.csswg.org/suites/css3-color/

cf. wg/cssom-view/#widl-Document-elementFromPoint-Element-float-x-float-y

cf. http://www.w3.org/TR/css3-color/#currentcolor

Acid2 fails since 04cd719.

The following style seems to be not applied:

<link rel="appendix stylesheet" href="data:text/css,.picture%20%7B%20background%3A%20none%3B%20%7D"> <!-- this stylesheet should be applied by default -->

escort 0.3.1 cannot be built on 13.04

• Makefile.am 2081ee5
• debian/control 0b8a959

Let's move non-CSS presentational hints to a stylesheet as much as possible. Currently presentational hints are processed by the code. It would be nice if those are processed via an ordinary CSS stylesheet.

cf. http://www.w3.org/TR/CSS21/cascade.html#preshint
cf. http://www.w3.org/TR/html5/rendering.html#the-css-user-agent-style-sheet-and-presentational-hints
cf. http://dbaron.org/css/test/noncss2

The 'display' property of the tr element doesn't seem to be processed properly.

cf. 7ca3bb4

cf. http://www.w3.org/TR/css3-color/

• the ‘opacity’ property
• RGBA color values; ee15227, 2d833d7
• HSL and HSLA color values; 0046a42
• ‘currentColor’ color keyword ➡️ #58

s.3.2.a should read:
Since an element with opacity less than 1 is composited from a single offscreen image, content outside of it cannot be layered in z-order between pieces of content inside of it. For the same reason, implementations must create a new stacking context for any element with opacity less than 1. If an element with opacity less than 1 is not positioned, then it is painted on the same layer, within its parent stacking context, as positioned elements with stack level 0. If an element with opacity less than 1 is positioned, the ‘z-index’ property applies as described in [CSS21], except that if the used value is ‘auto’ then the element behaves exactly as if it were ‘0’.
cf. http://www.w3.org/Style/2011/REC-css3-color-20110607-errata.html

cf. CSS3 Color Conformance Test Suite
http://test.csswg.org/suites/css3-color/

cf. http://www.w3.org/TR/2012/CR-html5-20121217/sections.html#the-body-element

Note HTMLBodyElementImp::setOnload() does this already.
Do the same with HTMLFrameSetElement.

cf. http://www.w3.org/TR/2012/CR-html5-20121217/webappapis.html#event-handler-attributes

Something like this:

events::EventHandlerNonNull HTMLElementImp::getOnclick()
{
    events::EventListener listener = getEventHandlerListener(u"click");
    return listener.getHandler();
}

void HTMLElementImp::setOnclick(events::EventHandlerNonNull onclick)
{
    events::EventListener listener = getEventHandlerListener(u"click");
    listener.setHandler(onclick));
}

It has been broken since 87ea0a9.

cf. https://github.com/esrille/escort/blob/master/testdata/partial-reflow-list-004.html

After deleting an absolutely positioned element, the corresponding, unused stacking context is not removed in testdata/partial-reflow-remove-003.html.

Note when an element is removed, the following functions are called in this order:

1. ViewCSSImp::handleMutation
2. ViewCSSImp::removeComputedStyle
3. CSSStyleDeclarationImp::revert

cf. http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html#global-attributes

cf. 9c44e71

cf. http://www.w3.org/TR/2012/CR-html5-20121217/infrastructure.html#reflecting-content-attributes-in-idl-attributes

Initial content attributes are set to each element in HTMLParser::insertHtmlElement(), which is the right timing to reflect the them in IDL attributes.

cf. http://www.w3.org/TR/selectors-api/

cf. http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#linkTypes

Platforms to be checked:

• Fedora 17
• Fedora 18 (escort.x86_64 c9e843d, escort.i686 98e3552)
• Ubuntu 12.10 (i386 and amd64 04042e5)
• Mac OS X Lion/Mountain Lion (lion 04042e5)

testharness.js dynamically creates/removes a style element to control the layout.

cf. https://github.com/w3c/testharness.js/blob/36b2f766393b1550cb1f3adf7939d9fd98758908/testharness.js#L1651-L1669