Friday, 31 August 2012
- [Bug 18461] Modifier key value for scroll lock is unclear
- [Bug 18461] Modifier key value for scroll lock is unclear
- [Bug 18429] [Shadow]: Specify imperative API for node distribution
- [Bug 18756] [Shadow]: Add "author-distributed" flag to shadow root machinery
- [Bug 18756] [Shadow]: Add "author-distributed" flag to shadow root machinery
- [Bug 18429] [Shadow]: Specify imperative API for node distribution
- [Bug 18757] [Shadow]: Refactor distribution/composition to be controllable by "manual" flag
- [Bug 18763] New: DOM4 does not conform with RFC 2119 keyword phrase erratum
- [Bug 18753] [Shadow]: Introduce HTMLContentElement projection API
- [Bug 18429] [Shadow]: Specify imperative API for node distribution
- [Bug 18757] New: [Shadow]: Refactor distribution/composition to be controllable by "manual" flag
- [Bug 18429] [Shadow]: Specify imperative API for node distribution
- [Bug 18756] New: [Shadow]: Add "manual-distribution" flag to shadow root machinery
- [Bug 18429] [Shadow]: Specify imperative API for node distribution
- [Bug 18755] New: [Shadow]: Introduce ShadowRoot distribution callback
- [Bug 18429] [Shadow]: Specify imperative API for node distribution
- [Bug 18753] New: [Shadow]: Introduce HTMLContentElement projection API
- [Bug 18429] [Shadow]: Specify imperative API for node distribution
- [Bug 18752] New: [Shadow]: Change default behavior for <content> element
- [Bug 18461] Modifier key value for scroll lock is unclear
- [Bug 18509] I find typo. in 4 The WebSocket interface attribute EventHandleronopen; -> attribute EventHandler onopen;
- [Bug 18749] Why removing exception throwing from binaryType
- [Bug 18461] Modifier key value for scroll lock is unclear
- [Bug 18749] Why removing exception throwing from binaryType
- [Bug 18749] Why removing exception throwing from binaryType
- [Bug 16682] Don't throw for ]]> with serializeAsCDATA
- [Bug 14347] Consider "createContextualFragment in detached contexts" thread
- [Bug 14694] innerHTML in DocumentFragment
- [Bug 15916] DOMParser Document origin
- [Bug 11190] Make scripts created by createContextualFragment() executable
- [Bug 12584] outerHTML should probably merge with adjacent text nodes if applicable. IE seems to do this to some extent, and WebKit just changed to do it: <https://bugs.webkit.org/show_bug.cgi?id=52686> This test shows behavior for outerText and outerHTML: <http://so
- [Bug 13410] XML serialisation incompletely defined.
- [Bug 14218] Check CharData when serializing Text
- [Bug 14842] Update createContextualFragment if detached flag is removed
- [Bug 15902] DOMParser created documents should use about:blank as URL
- [Bug 18749] Why removing exception throwing from binaryType
- [Bug 18749] New: Why removing exception throwing from binaryType
Thursday, 30 August 2012
- [Bug 18747] [Custom]: Specify invoking "created" callback
- [Bug 18747] [Custom]: Specify invoking "created" callback
- [Bug 18720] [Custom]: Specify imperative syntax for custom DOM elements
- [Bug 18747] [Custom]: Specify invoking "created" callback
- [Bug 18731] [Custom]: custom element instantiation does not provide for an initialization method (aka lifecycle.created)
- [Bug 18720] [Custom]: Specify imperative syntax for custom DOM elements
- [Bug 18748] New: [Custom]: Specify invoking "shadowRootCreated" callback
- [Bug 18720] [Custom]: Specify imperative syntax for custom DOM elements
- [Bug 18747] New: [Custom]: Specify invoking "created" callback
- [Bug 18732] [Custom]: element upgrade algorithm does not preserve attributes, event listeners, references
- [Bug 18613] [Templates]: Section 7 Parsing HTML Templates needs to be re-written
- [Bug 18732] [Custom]: element upgrade algorithm does not preserve attributes, event listeners, references
- [Bug 12584] outerHTML should probably merge with adjacent text nodes if applicable. IE seems to do this to some extent, and WebKit just changed to do it: <https://bugs.webkit.org/show_bug.cgi?id=52686> This test shows behavior for outerText and outerHTML: <http://so
- [Bug 18740] [Custom]: Specify semantics of handling document.register options
- [Bug 18732] [Custom]: element upgrade algorithm does not preserve attributes, event listeners, references
- [Bug 18738] [Custom]: Specify that type selectors match all derived types
- [Bug 12584] outerHTML should probably merge with adjacent text nodes if applicable. IE seems to do this to some extent, and WebKit just changed to do it: <https://bugs.webkit.org/show_bug.cgi?id=52686> This test shows behavior for outerText and outerHTML: <http://so
Wednesday, 29 August 2012
- [Bug 18669] Switch from is= to <tag if a decision has been reached among implementers
- [Bug 18731] [Custom]: custom element instantiation does not provide for an initialization method (aka lifecycle.created)
- [Bug 18720] [Custom]: Specify imperative syntax for custom DOM elements
- [Bug 18719] [Custom]: Specify declarative syntax for defining custom DOM elements
- [Bug 18595] [Custom]: Enumerate effects of hooking into parser
- [Bug 18731] [Custom]: custom element instantiation does not provide for an initialization method (aka lifecycle.created)
- [Bug 18720] [Custom]: Specify imperative syntax for custom DOM elements
- [Bug 18740] New: [Custom]: Specify semantics of handling document.register options
- [Bug 18732] [Custom]: element upgrade algorithm does not preserve attributes, event listeners, references
- [Bug 18720] [Custom]: Specify imperative syntax for custom DOM elements
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18738] [Custom]: Specify that type selectors match all derived types
- [Bug 18720] [Custom]: Specify imperative syntax for custom DOM elements
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18732] [Custom]: element upgrade algorithm does not preserve attributes, event listeners, references
- [Bug 18720] [Custom]: Specify imperative syntax for custom DOM elements
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18731] [Custom]: custom element instantiation does not provide for an initialization method (aka lifecycle.created)
- [Bug 18511] [Custom]: Things to Consider in the Future
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18721] [Custom]: Specify an event that fires when all known declarations loaded
- [Bug 18613] [Templates]: Section 7 Parsing HTML Templates needs to be re-written
- [Bug 18613] [Templates]: Section 7 Parsing HTML Templates needs to be re-written
- [Bug 18669] Switch from is= to <tag if a decision has been reached among implementers
- [Bug 18669] Switch from is= to <tag if a decision has been reached among implementers
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 18669] Switch from is= to <tag if a decision has been reached among implementers
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18738] New: [Custom]: Specify that type selectors match all derived types
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18729] [Custom]: instantiation algorithm omits creating shadow roots for custom base elements
- [Bug 18732] [Custom]: element upgrade algorithm does not preserve attributes, event listeners, references
- [Bug 18732] [Custom]: element upgrade algorithm does not preserve attributes, event listeners, references
- [Bug 18732] [Custom]: element upgrade algorithm does not preserve attributes, event listeners, references
- [Bug 18732] [Custom]: element upgrade algorithm does not preserve attributes, event listeners, references
- [Bug 18732] [Custom]: element upgrade algorithm does not preserve attributes, event listeners, references
- [Bug 18732] [Custom]: element upgrade algorithm does not preserve attributes, event listeners, references
- [Bug 18732] [Custom]: element upgrade algorithm does not preserve attributes, event listeners, references
- [Bug 18732] [Custom]: element upgrade algorithm does not preserve attributes, event listeners, references
- [Bug 18732] [Custom]: element upgrade algorithm does not preserve attributes, event listeners, references
- [Bug 18732] [Custom]: element upgrade algorithm does not preserve attributes, event listeners, references
- [Bug 18732] [Custom]: element upgrade algorithm does not preserve attributes, event listeners, references
- [Bug 18732] [Custom]: element upgrade algorithm does not preserve attributes, event listeners, references
- [Bug 18729] [Custom]: instantiation algorithm omits creating shadow roots for custom base elements
- [Bug 18729] [Custom]: instantiation algorithm omits creating shadow roots for custom base elements
- [Bug 18729] [Custom]: instantiation algorithm omits creating shadow roots for custom base elements
- [Bug 18732] [Custom]: element upgrade algorithm does not preserve attributes, event listeners, references
- [Bug 18732] [Custom]: element upgrade algorithm does not preserve attributes, event listeners, references
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 18736] New: [Shadow]: Specify what happens when a shadow root has multiple shadow insertion points
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 18735] New: [Templates]: Section 7 Parsing HTML Templates needs to be clear to be specific about ownerDocument WRT templates
- [Bug 18509] I find typo. in 4 The WebSocket interface attribute EventHandleronopen; -> attribute EventHandler onopen;
- [Bug 18732] [Custom]: element upgrade algorithm does not preserve attributes, event listeners, references
- [Bug 18732] [Custom]: element upgrade algorithm does not preserve attributes, event listeners, references
- [Bug 18623] Editorial issues: Clarify CLOSING, capitalize websocket, add anchor to reason attribute
- [Bug 18729] [Custom]: instantiation algorithm omits creating shadow roots for custom base elements
- [Bug 18623] Editorial issues: Clarify CLOSING, capitalize websocket, add anchor to reason attribute
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18733] [Custom]: Small correction in section 5 Declaring Custom DOM Elements
- [Bug 18730] [Custom]: typo in section 7 in TOC and in body: s/Pseudoclas/Pseudoclass
- [Bug 18730] [Custom]: typo in section 7 in TOC and in body: s/Pseudoclas/Pseudoclass
- [Bug 18729] [Custom]: instantiation algorithm omits creating shadow roots for custom base elements
- [Bug 18729] [Custom]: instantiation algorithm omits creating shadow roots for custom base elements
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18730] [Custom]: typo in section 7 in TOC and in body: s/Pseudoclas/Pseudoclass
- [Bug 18729] [Custom]: instantiation algorithm omits creating shadow roots for custom base elements
- [Bug 18732] [Custom]: element upgrade algorithm does not preserve attributes, event listeners, references
- [Bug 18732] [Custom]: element upgrade algorithm does not preserve attributes, event listeners, references
- [Bug 18732] [Custom]: element upgrade algorithm does not preserve attributes, event listeners, references
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18733] New: [Custom]: Small correction in section 5 Declaring Custom DOM Elements
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18732] New: [Custom]: element upgrade algorithm does not preserve attributes, event listeners, references
- [Bug 18731] [Custom]: custom element instantiation does not provide for an initialization method (aka lifecycle.created)
- [Bug 18731] [Custom]: custom element instantiation does not provide for an initialization method (aka lifecycle.created)
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18731] New: [Custom]: custom element instantiation omits does not provide a method to initialize shadow roots (i.e. lifecycle.created)
- [Bug 18729] New: [Custom]: instantiation algorithm omits creating shadow roots for custom base elements
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18730] New: [Custom]: typo in section 7 in TOC and in body: s/Pseudoclas/Pseudoclass
Tuesday, 28 August 2012
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 18613] [Templates]: Section 7 Parsing HTML Templates needs to be re-written
- [Bug 18720] [Custom]: Specify imperative syntax for custom DOM elements
- [Bug 18684] [Custom]: Specify what happens with elements that aren't in document tree
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 18669] Switch from is= to <tag if a decision has been reached among implementers
- [Bug 18719] [Custom]: Specify declarative syntax for defining custom DOM elements
- [Bug 18606] [Custom]: Constrain the "constructor" attribute value
- [Bug 18720] [Custom]: Specify imperative syntax for custom DOM elements
- [Bug 18719] [Custom]: Specify declarative syntax for defining custom DOM elements
- [Bug 18606] [Custom]: Constrain the "constructor" attribute value
- [Bug 18720] [Custom]: Specify imperative syntax for custom DOM elements
- [Bug 18585] [Custom]: Consider providing accessor from ELEMENT to UPGRADE
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 18725] New: [Templates]: <meta> tag needs to also not "determine the context element"
- [Bug 18534] [Custom]: Pseudo-class to mitigate FOUC
- [Bug 18720] [Custom]: Specify imperative syntax for custom DOM elements
- [Bug 18719] [Custom]: Specify declarative syntax for defining custom DOM elements
- [Bug 18723] New: [Custom]: Specify handling element re-definition
- [Bug 18719] [Custom]: Specify declarative syntax for defining custom DOM elements
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18722] [Custom]: Specify invalid definition state
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18722] New: [Custom]: Specify invalid definition state
- [Bug 18720] [Custom]: Specify imperative syntax for custom DOM elements
- [Bug 18511] [Custom]: Things to Consider in the Future
- [Bug 18552] [Custom]: Specify a way to define a default event listener
- [Bug 18533] [Custom]: When to fire upgrade events
- [Bug 18720] [Custom]: Specify imperative syntax for custom DOM elements
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18721] New: [Custom]: Specify an event that fires when all known declarations loaded
- [Bug 18533] [Custom]: When to fire upgrade events
- [Bug 18720] [Custom]: Specify imperative syntax for custom DOM elements
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 18684] [Custom]: Specify what happens with elements that aren't in document tree
- [Bug 18720] [Custom]: Specify imperative syntax for custom DOM elements
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 18606] [Custom]: Constrain the "constructor" attribute value
- [Bug 18585] [Custom]: Consider providing accessor from ELEMENT to UPGRADE
- [Bug 18720] [Custom]: Specify imperative syntax for custom DOM elements
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 18720] [Custom]: Specify imperative syntax for custom DOM elements
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 18552] [Custom]: Specify a way to define a default event listener
- [Bug 18720] [Custom]: Specify imperative syntax for custom DOM elements
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 18534] [Custom]: Pseudo-class to mitigate FOUC
- [Bug 18720] [Custom]: Specify imperative syntax for custom DOM elements
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 18533] [Custom]: When to fire upgrade events
- [Bug 18720] [Custom]: Specify imperative syntax for custom DOM elements
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 17313] [Custom]: Provide an example of how to create an element prototype
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 18719] [Custom]: Specify declarative syntax for defining custom DOM elements
- [Bug 18584] [Custom]: Specify how custom DOM elements are defined declaratively
- [Bug 18719] [Custom]: Specify declarative syntax for defining custom DOM elements
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 18718] [Custom]: Specify how a declaration turns into a definition
- [Bug 18719] [Custom]: Specify declarative syntax for defining custom DOM elements
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 18595] [Custom]: Enumerate effects of hooking into parser
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 18719] [Custom]: Specify declarative syntax for defining custom DOM elements
- [Bug 17113] [Custom]: What happens when you remove or change contents of <element>?
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18720] [Custom]: Specify imperative syntax for custom DOM elements
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18719] [Custom]: Specify declarative syntax for defining custom DOM elements
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18720] New: [Custom]: Specify imperative syntax for custom DOM elements
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18719] New: [Custom]: Specify declarative syntax for defining custom DOM elements
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18718] [Custom]: Specify how a declaration turns into a definition
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18718] New: [Custom]: Specify how a declaration turns into a definition
- [Bug 18513] [Shadow]: Consider re-projecting children in nested shadow DOM subtrees
- [Bug 18611] Blob should support Transferable
- [Bug 18611] Blob should support Transferable
Monday, 27 August 2012
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 18713] New: [Templates]: Stop at template when clearing the stack back to a table/tbody/row context
- [Bug 18289] Support 'column' here for consistency with window.onerror?
- [Bug 18289] Support 'column' here for consistency with window.onerror?
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 18710] New: [Templates]: Trigger parse errors when template content does not match the template context.
- [Bug 18623] Editorial issues: Clarify CLOSING, capitalize websocket, add anchor to reason attribute
- [Bug 18623] Editorial issues: Clarify CLOSING, capitalize websocket, add anchor to reason attribute
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 18704] New: [Shadow]: How reset-style-inheritance flag of insertion point works with multiple show roots
- [Bug 17570] Function declaration of Node::lookupPrefix and Node::lookupNamespaceURI do not allow 'null' return value
- [Bug 18701] New: FileSystem/FileWriter API needs a method to flush/sync
- [Bug 13999] [Awaiting ES6] DOMTokenList: allow to add/remove multiple tokens at once
- [Bug 18509] I find typo. in 4 The WebSocket interface attribute EventHandleronopen; -> attribute EventHandler onopen;
Saturday, 25 August 2012
Friday, 24 August 2012
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 17112] [Custom]: Specify behavior of <script> element when child of <element>
- [Bug 18611] Blob should support Transferable
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18684] [Custom]: Specify what happens with elements that aren't in document tree
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 18535] [Custom]: Scoping of element definitions in Shadow DOM
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18684] New: [Custom]: Specify what happens with elements that aren't in document tree
- [Bug 17765] APIs need to take a reference to blob data underlying object URLs
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 18613] [Templates]: Section 7 Parsing HTML Templates needs to be re-written
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 18598] [Templates]: Reference W3C copy of the HTML5 spec
- [Bug 18613] [Templates]: Section 7 Parsing HTML Templates needs to be re-written
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 18672] New: [Templates]: Define the behavior of cloneNode(deep) on template elements
Thursday, 23 August 2012
- [Bug 18668] Maybe restore support for Blob(ArrayBuffer)
- [Bug 17627] The order of mouseenter/leave events in a subtree should be defined
- [Bug 18341] Needs some guidelines for computing key and char values of KeyboardEvent when some modifier key is pressed and not causes text input
- [Bug 18461] Modifier key value for scroll lock is unclear
- [Bug 18327] Shouldn't "DeadDoubleacute" be "DeadDoubleAcute"?
- [Bug 18326] Is DeadEacute right name?
- [Bug 17756] IE9 users deifferent key names for "MediaTrackNext" and "MediaTrackPrevious"
- [Bug 18323] key names which are used by IE9 but not defined in D3E
- [Bug 17754] Key name "HistoryBack" and "HistoryForward" should be "BrowserBack" and "BrowserForward"
- [Bug 17755] IE9 uses different key names for "AudioMute", "AudioVolumeDown" and "AudioVolumeUp"
- [Bug 18323] key names which are used by IE9 but not defined in D3E
- [Bug 17715] Define that initEvent doesn't do anything when called during dispatch.
- [Bug 17714] Exceptions thrown from event handlers should not be propagated
- [Bug 17714] Exceptions thrown from event handlers should not be propagated
- [Bug 17628] delta attributes of WheelEvent should be double rather than float
- [Bug 17628] delta attributes of WheelEvent should be double rather than float
- [Bug 17628] delta attributes of WheelEvent should be double rather than float
- [Bug 17628] delta attributes of WheelEvent should be double rather than float
- [Bug 18669] New: Switch from is= to <tag if a decision has been reached among implementers
- [Bug 18668] New: Maybe restore support for Blob(ArrayBuffer)
- [Bug 18645] [Shadow]: HTMLSelectElement should have an insertion point
- [Bug 18645] [Shadow]: HTMLSelectElement should have an insertion point
- [Bug 18645] [Shadow]: HTMLSelectElement should have an insertion point
- [Bug 18558] [IndexedDB] Define error seen when key generator maximum value is reached
- [Bug 18645] [Shadow]: HTMLSelectElement should have an insertion point
- [Bug 18558] [IndexedDB] Define error seen when key generator maximum value is reached
- [Bug 18558] [IndexedDB] Define error seen when key generator maximum value is reached
- [Bug 18645] [Shadow]: HTMLSelectElement should have an insertion point
- [Bug 18645] [Shadow]: HTMLSelectElement should have an insertion point
- [Bug 18613] [Templates]: Section 7 Parsing HTML Templates needs to be re-written
- [Bug 12510] Specs split off from HTML5 (like WebSockets) need to have xrefs linked, otherwise they're ambiguous
Wednesday, 22 August 2012
- [Bug 18656] New: objectStore.delete should raise InvalidStateError if object store is deleted
- [Bug 18645] [Shadow]: HTMLSelectElement should have an insertion point
- [Bug 18653] New: wrong bug tracker link
- [Bug 18645] [Shadow]: HTMLSelectElement should have an insertion point
Tuesday, 21 August 2012
- [Bug 18242] Not clear what "script that invoked the method" means exactly. Should this be changed to "entry script" instead? If not, please specify what it means.
- [Bug 17570] Function declaration of Node::lookupPrefix and Node::lookupNamespaceURI do not allow 'null' return value
- [Bug 18001] Allow data: URL for new Worker(). Supported by Opera and Firefox.
- [Bug 18003] Change use of "relevant namespace object" term re workers
- [Bug 18188] "relevant namespace object" is not defined in WebIDL anymore.
- [Bug 18218] Within the workers text "list of active intervals" can be removed because it is the same as "list of active timers".
- [Bug 18080] "This specification introduces two related mechanisms, similar to HTTP session cookies, for storing structured data on the client side." - structured data is no longer supported
- [Bug 15994] origin attribute
- [Bug 18033] each MessageChannel acts as its own task source. This means that messages sent using this function are not guaranteed to execute in order, since the order task sources are processed isn't specified.
- [Bug 18045] Based on my experience and from reading many questions on the Web, this API is seriously flawed. It treats cross-domain iframes the same as same-domain iframes, except that almost every operation on contentWindow is an error.
- [Bug 18242] Not clear what "script that invoked the method" means exactly. Should this be changed to "entry script" instead? If not, please specify what it means.
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 18645] New: [Shadow]: HTMLSelectElement should have an insertion point
- [Bug 18637] New: iOS version
- [Bug 18611] Blob should support Transferable
Monday, 20 August 2012
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 18630] [Shadow]: It's unclear where a 'load' event is fired for replaced elements which has an author shadow root.
- [Bug 18630] [Shadow]: It's unclear where a 'load' event is fired for replaced elements which has an author shadow root.
- [Bug 18630] [Shadow]: It's unclear where a 'load' event is fired for replaced elements which has an author shadow root.
- [Bug 18630] [Shadow]: It's unclear where a 'load' event is fired for replaced elements which has an author shadow root.
- [Bug 18630] [Shadow]: It's unclear where a 'load' event is fired for replaced elements which has an author shadow root.
- [Bug 18630] [Shadow]: It's unclear where a 'load' event is fired for replaced elements which has an author shadow root.
- [Bug 18630] [Shadow]: It's unclear where a 'load' event is fired for replaced elements which has a author shadow root.
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 18630] New: [Shadow]: It's unclear where a 'load' event is fired for replaced elements where author shadow root is attached.
- [Bug 18513] [Shadow]: Consider re-projecting children in nested shadow DOM subtrees
- [Bug 18221] the word 'using' is repeated in the last line following 'Shared Blacklists' (This information can then be shared with other sites, using using visitors' IP)
- [Bug 10896] enable device independent access to event handlers
- [Bug 10896] enable device independent access to event handlers
- [Bug 18611] Blob should support Transferable
- [Bug 18611] Blob should support Transferable
- [Bug 18623] New: Editorial issues: Clarify CLOSING, capitalize websocket, add anchor to reason attribute
Saturday, 18 August 2012
- [Bug 18611] Blob should support Transferable
- [Bug 18611] Blob should support Transferable
- [Bug 18611] Blob should support Transferable
- [Bug 18614] [Templates]: Need to outline parser changes required to allow <template> to occur anywhere with <head> or <body>
Friday, 17 August 2012
- [Bug 18613] [Templates]: Section 7 Parsing HTML Templates needs to be re-written
- [Bug 18611] Blob should support Transferable
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 18614] New: [Templates]: Need to outline parser changes required to allow <template> to occur anywhere with <head> or <body>
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 18613] New: [Templates]: Section 7 Parsing HTML Templates needs to be re-written
- [Bug 18611] New: Blob should support Transferable
- [Bug 18610] New: Transferable should expose a close() method
- [Bug 17736] Get "dereference" Blob URI terminology more in keeping with HTML5
- [Bug 17762] lastModifiedDate should not be nullable
- [Bug 17757] Editorial: Add a note about why Blobs aren't Transferable
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 18608] [Templates] Specify that all template elements within a document have DF's that are owned by a shared browsing-context-less document
- [Bug 18608] New: [Templates] Specify that all template elements within a document have DF's that are owned by a shared browsing-context-less document
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 18607] [Templates]: Specify that the template element can occur as a child of any element within <body> or <head>
- [Bug 18607] New: [Templates]: Specify that the template element can occur as a child of any element within <body> or <head>
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 18606] New: [Custom]: Constrain the "constructor" attribute value
- [Bug 16952] Add a Blob.close()
- [Bug 18551] [IndexedDB] Ambiguity about operations preceding a failed createIndex.
- [Bug 17541] Carefully think through how Range.insertNode should behave when the node to be inserted is already at the beginning of the range
- [Bug 18596] [Custom]: Use a "has a" relationship instead of "is a" for custom types
Thursday, 16 August 2012
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 18597] [Templates]: Make <template> display:none by default
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 18594] [Custom]: It is not defined where elementupgrade event is dispatched
- [Bug 18597] [Templates]: Make <template> display:none by default
- [Bug 18598] New: [Templates]: Reference W3C copy of the HTML5 spec
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18596] [Custom]: Use a "has a" relationship instead of "is a" for custom types
- [Bug 16341] [Templates]: [Non-normative] Clarify that template contents cannot be matched against "selector" queries in their host documents.
- [Bug 16341] [Templates]: [Non-normative] Clarify that template contents cannot be matched against "selector" queries in their host documents.
- [Bug 16341] [Templates]: [Non-normative] Clarify that template contents cannot be matched against "selector" queries in their host documents.
- [Bug 16341] [Templates]: [Non-normative] Clarify that template contents cannot be matched against "selector" queries in their host documents.
- [Bug 17679] [Templates]: Latest editor's draft link incorrect
- [Bug 16341] [Templates]: [Non-normative] Clarify that template contents cannot be matched against "selector" queries in their host documents.
- [Bug 16787] [Templates]: Specify that XML parsing doesn't do anything special with <template>
- [Bug 16280] [Templates]: [Non-normative] Clarify the behavior of Node/Element mutation, traversal & serialize/deserialize APIs on <template>
- [Bug 16280] [Templates]: Non-normative: Clarify the behavior of Node/Element mutation, traversal & serialize/deserialize APIs on <template>
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 16280] [Templates]: Non-normative: Clarify the behavior of DOM traversal & serialize/deserialize APIS on template element
- [Bug 16788] [Templates]: Specify the behavior of adding and removing children from the template element
- [Bug 16341] [Templates]: [Non-normative] Clarify that template contents cannot be matched against "selector" queries in their host documents.
- [Bug 16788] [Templates]: Specify the behavior of adding and removing children from the template element
- [Bug 16341] [Templates]: [Non-normative] Clarify that template contents cannot be matched against "selector" queries in their host documents.
- [Bug 16340] [Templates]: Consider a more precise name for the created document fragments
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 18597] [Templates]: Make <template> display:none by default
- [Bug 18597] [Templates]: Make <template> display:none by default
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 18597] New: [Templates]: Make <template> display:none by default
- [Bug 16280] [Templates]: Non-normative: Clarify the behavior of DOM traversal & serialize/deserialize APIS on template element
- [Bug 16280] [Templates]: Non-normative: Clarify the behavior of DOM traversal & serialize/deserialize APIS on template element
- [Bug 16280] [Templates]: Non-normative: Clarify the behavior of DOM traversal & serialize/deserialize APIS on template element
- [Bug 18596] New: [Custom]: Use a "has a" relationship instead of "is a" for custom types
- [Bug 18595] New: [Custom]: Enumerate effects of hooking into parser
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 18594] New: [Custom]: It is not defined where elementupgrade event is dispatched
- [Bug 18535] [Custom]: Scoping of element definitions in Shadow DOM
Wednesday, 15 August 2012
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 18583] [Custom]: Define custom element template.
- [Bug 17112] [Custom]: Specify behavior of <script> element when child of <element>
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 18585] New: [Custom]: Consider providing accessor from ELEMENT to UPGRADE
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 17107] [Custom]: Specify stages of existence for custom DOM element
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 18584] New: [Custom]: Specify how custom DOM elements are defined declaratively
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 18583] New: [Custom]: Define custom element template.
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18552] [Custom]: Specify a way to define a default event listener
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18535] [Custom]: Scoping of element definitions in Shadow DOM
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18534] [Custom]: Pseudo-class to mitigate FOUC
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18533] [Custom]: When to fire upgrade events
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 15480] [Shadow]: Things to Consider in the Future
- [Bug 18435] [Shadow]: Needs consistent way to style the inner element of replaced elements.
- [Bug 18581] New: pre-insert and replace both check type of 'node' in too many places
- [Bug 18551] [IndexedDB] Ambiguity about operations preceding a failed createIndex.
Tuesday, 14 August 2012
- [Bug 18558] [IndexedDB] Define error seen when key generator maximum value is reached
- [Bug 18558] New: [IndexedDB] Define error seen when key generator maximum value is reached
- [Bug 18547] Add [ImplicitThis] to EventTarget?
- [Bug 18547] Add [ImplicitThis] to EventTarget?
- [Bug 18455] [Shadow]: Stop 'load' and 'error' events at shadow boundaries
- [Bug 18455] [Shadow]: Stop 'load' and 'error' events at shadow boundaries
Monday, 13 August 2012
- [Bug 18551] [IndexedDB] Ambiguity about operations preceding a failed createIndex.
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18552] New: [Custom]: Specify a way to define a default event listener
- [Bug 18534] [Custom]: Pseudo-class to mitigate FOUC
- [Bug 18551] New: [IndexedDB] Ambiguity about operations preceding a failed createIndex.
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 18455] [Shadow]: Stop 'load' and 'error' events at shadow boundaries
- [Bug 18548] New: Add a Content-Length header to Blob URI request-response semantics
- [Bug 18547] New: Add [ImplicitThis] to EventTarget?
- [Bug 18341] Needs some guidelines for computing key and char values of KeyboardEvent when some modifier key is pressed and not causes text input
- [Bug 18513] [Shadow]: Consider re-projecting children in nested shadow DOM subtrees
- [Bug 18535] [Custom]: Scoping of element definitions in Shadow DOM
- [Bug 18533] [Custom]: When to fire upgrade events
- [Bug 18455] [Shadow]: Stop 'load' and 'error' events at shadow boundaries
- [Bug 18455] [Shadow]: Stop 'load' and 'error' events at shadow boundaries
- [Bug 18455] [Shadow]: Stop 'load' and 'error' events at shadow boundaries
Sunday, 12 August 2012
- [Bug 18540] New: Proposal for a new acceptNode() return value for TreeWalker.
- [Bug 18529] Existence of separators in token should throw SyntaxError
- [Bug 18529] Existence of separators in token should throw SyntaxError
Saturday, 11 August 2012
- [Bug 18529] Existence of separators in token should throw SyntaxError
- [Bug 18529] Existence of separators in token should throw SyntaxError
Friday, 10 August 2012
- [Bug 18535] [Custom]: Scoping of element definitions in Shadow DOM
- [Bug 18533] [Custom]: When to fire upgrade events
- [Bug 18535] New: [Custom]: Scoping of element definitions in Shadow DOM
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18534] New: [Custom]: Pseudo-class to mitigate FOUC
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18533] New: [Custom]: When to fire upgrade events
- [Bug 18529] Existence of separators in token should throw SyntaxError
- [Bug 13999] [Awaiting ES6] DOMTokenList: allow to add/remove multiple tokens at once
- [Bug 18523] Spec is unclear about the restriction on LWS in the attribute/value in the ABNF for media-type
- [Bug 18521] Spec is unclear about lower-casing content types
- [Bug 18529] Existence of separators in token should throw SyntaxError
- [Bug 18529] Existence of separators in token should throw SyntaxError
- [Bug 18529] Existence of separators in token should throw SyntaxError
- [Bug 18529] New: Existence of separators in token should throw SyntaxError
- [Bug 13999] [Awaiting ES6] DOMTokenList: allow to add/remove multiple tokens at once
- [Bug 18528] New: Spec is unclear about the case sensitivity of parameter values
- [Bug 18523] New: Spec is unclear about the restriction on LWS in the attribute/value in the ABNF for media-type
- [Bug 18521] Spec is unclear about lower-casing content types
- [Bug 18521] New: Spec is unclear about lower-casing content types
Thursday, 9 August 2012
- [Bug 18513] [Shadow]: Consider re-projecting children in nested shadow DOM subtrees
- [Bug 18513] [Shadow]: Consider re-projecting children in nested shadow DOM subtrees
- [Bug 18513] [Shadow]: Consider re-projecting children in nested shadow DOM subtrees
- [Bug 18513] [Shadow]: Consider re-projecting children in nested shadow DOM subtrees
- [Bug 18511] [Custom]: Things to Consider in the Future
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 16152] [Custom Elements]: Consider replacing some (all?) lifecycle callbacks with mutation observers
- [Bug 18511] [Custom]: Things to Consider in the Future
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 15552] [Custom Elements]: Consider adding in-tree/out-of-tree callbacks to custom elements
- [Bug 18511] [Custom]: Things to Consider in the Future
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 15157] [Custom Elements]: maybe have a property to test if an element is 'upgraded' or not?
- [Bug 18511] [Custom]: Things to Consider in the Future
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 15052] One should be able to refer to existing templates in decorator and custom element definitions.
- [Bug 18511] [Custom]: Things to Consider in the Future
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 15019] [Custom Elements]: Specify a way to build UA HTML elements
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18511] [Custom]: Things to Consider in the Future
- [Bug 14967] [Custom Elements]: Find a way to avoid "x-" prefix because it's ugly
- [Bug 18513] [Shadow]: Consider re-projecting children in nested shadow DOM subtrees
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 18513] New: [Shadow]: Consider re-projecting children in nested shadow DOM subtrees
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18511] New: [Custom]: Things to Consider in the Future
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 17313] [Custom]: Provide an example of how to create an element prototype
- [Bug 17113] [Custom]: What happens when you remove or change contents of <element>?
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 17112] [Custom]: Behavior of <script> element is different when a child of <element>
Wednesday, 8 August 2012
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 17446] [Shadow]: Research and explain content fallback for HTML elements.
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 16009] [Shadow]: Specify how CSS behaves in shadow DOM subtrees
- [Bug 16009] [Shadow]: Specify how CSS behaves in shadow DOM subtrees
- [Bug 18483] [Shadow]: Shared stylesheets may make @host ambiguous
- [Bug 18455] [Shadow]: Stop 'load' and 'error' events at shadow boundaries
- [Bug 18502] New: [IndexedDB] Editorial: Wording around IDBFactory.open() with no version misleading
- [Bug 18455] [Shadow]: Stop 'load' and 'error' events at shadow boundaries
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 18455] [Shadow]: Stop 'load' and 'error' events at shadow boundaries
Tuesday, 7 August 2012
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 16810] [Templates]: Typo: "code" -> "content"
- [Bug 17446] [Shadow]: Research and explain content fallback for HTML elements.
- [Bug 16009] [Shadow]: Specify how CSS behaves in shadow DOM subtrees
- [Bug 18454] [Shadow]: Define how apply-author-styles affects sibling selectors
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 18455] [Shadow]: Stop 'load' and 'error' events at shadow boundaries
- [Bug 15495] Update EventSource model to do automatic reconnect even in the face of network errors
- [Bug 18320] Clarify how reconnection works after losing internet connectivity
- [Bug 15495] Update EventSource model to do automatic reconnect even in the face of network errors
- [Bug 18320] Clarify how reconnection works after losing internet connectivity
- [Bug 18483] [Shadow]: Shared stylesheets may make @host ambiguous
Monday, 6 August 2012
- [Bug 18483] [Shadow]: Shared stylesheets may make @host ambiguous
- [Bug 17627] The order of mouseenter/leave events in a subtree should be defined
- [Bug 18444] [Shadow]: @host @-rules vs rules in document tree
Friday, 3 August 2012
- [Bug 16009] [Shadow]: Specify how CSS behaves in shadow DOM subtrees
- [Bug 18444] [Shadow]: @host @-rules vs rules in document tree
- [Bug 16009] [Shadow]: Specify how CSS behaves in shadow DOM subtrees
- [Bug 18418] [Shadow]: Specify the order of stylesheets in Shadow DOM for the purpose of the cascade
- [Bug 16009] [Shadow]: Specify how CSS behaves in shadow DOM subtrees
- [Bug 18345] [Shadow]: @host in a shadow DOM subtree that is not rendered
- [Bug 16009] [Shadow]: Specify how CSS behaves in shadow DOM subtrees
- [Bug 17674] [Shadow]: /select/ combinator not included in rule applicability algorithm
- [Bug 18483] [Shadow]: Shared stylesheets may make @host ambiguous
- [Bug 18461] Modifier key value for scroll lock is unclear
- [Bug 18341] Needs some guidelines for computing key and char values of KeyboardEvent when some modifier key is pressed and not causes text input
- [Bug 18483] [Shadow]: Shared stylesheets may make @host ambiguous
- [Bug 18327] Shouldn't "DeadDoubleacute" be "DeadDoubleAcute"?
- [Bug 18326] Is DeadEacute right name?
- [Bug 18323] key names which are used by IE9 but not defined in D3E
- [Bug 17756] IE9 users deifferent key names for "MediaTrackNext" and "MediaTrackPrevious"
- [Bug 17755] IE9 uses different key names for "AudioMute", "AudioVolumeDown" and "AudioVolumeUp"
- [Bug 17754] Key name "HistoryBack" and "HistoryForward" should be "BrowserBack" and "BrowserForward"
- [Bug 17715] Define that initEvent doesn't do anything when called during dispatch.
- [Bug 17714] Exceptions thrown from event handlers should not be propagated
- [Bug 16009] [Shadow]: Specify how CSS behaves in shadow DOM subtrees
- [Bug 17515] [Shadow]: @host and shadow insertion point
- [Bug 18444] [Shadow]: @host @-rules vs rules in document tree
- [Bug 16009] [Shadow]: Specify how CSS behaves in shadow DOM subtrees
- [Bug 15480] [Shadow]: Things to Consider in the Future
- [Bug 17515] [Shadow]: @host and shadow insertion point
- [Bug 16009] [Shadow]: Specify how CSS behaves in shadow DOM subtrees
- [Bug 17515] [Shadow]: @host and shadow insertion point
- [Bug 18345] [Shadow]: @host in a shadow DOM subtree that is not rendered
- [Bug 18382] [Shadow]: ShadowRoot needs the flag to control @host @-rules in a similar way to the apply-author-styles flag.
- [Bug 16009] [Shadow]: Specify how CSS behaves in shadow DOM subtrees
- [Bug 18483] New: [Shadow]: Shared stylesheets may make @host ambiguous
- [Bug 17515] [Shadow]: @host and shadow insertion point
- [Bug 17515] [Shadow]: @host and shadow insertion point
- [Bug 16009] [Shadow]: Specify how CSS behaves in shadow DOM subtrees
- [Bug 18444] [Shadow]: @host @-rules vs rules in document tree
- [Bug 11329] Browsers must generate resize event during a zoom.
- [Bug 13711] Alternative style sheet handling undefined
- [Bug 15181] Override of non-recognised media type appears unsupported in xml-stylesheet processing
- [Bug 10533] [scroll] Remove the scrollIntoView() section in favour of the CSSOM spec
- [Bug 14197] CSSOMVIEW - inconsistent naming convention - media_query_list
- [Bug 14072] [CSSOMVIEW] Screen.alphaDepth missing
- [Bug 14071] [CSSOMVIEW] Screen.{color,pixel}Depth not sufficiently distinguished
- [Bug 11328] Canvas authors needs to be able to assess pixel resolution to rescale canvas elements
- [Bug 11329] HTML 5 supporting browsers must generate resize event during a zoom.
- [Bug 10533] [scroll] Remove the scrollIntoView() section in favour of the CSSOM spec
- [Bug 14072] [CSSOMVIEW] Screen.alphaDepth missing
- [Bug 14207] ElementCSSInlineStyle needs binding to Element
- [Bug 14197] CSSOMVIEW - inconsistent naming convention - media_query_list
- [Bug 14203] JavaScript API to access unsupported CSS properties
- [Bug 13711] [html5] Alternative style sheet handling undefined
- [Bug 14071] [CSSOMVIEW] Screen.{color,pixel}Depth not sufficiently distinguished
- [Bug 15181] CSSOM: Override of non-recognised media type appears unsupported
- [Bug 17681] [IndexedDB] Operations that raise multiple exceptions types should define order
- [Bug 18427] [IndexedDB] Spec text requires index names be unique within database
Thursday, 2 August 2012
- [Bug 17681] [IndexedDB] Operations that raise multiple exceptions types should define order
- [Bug 18329] [IndexedDB] [supertrivial] Use more understandable example for indeces
- [Bug 18427] [IndexedDB] Spec text requires index names be unique within database
- [Bug 16009] [Shadow]: Specify how CSS behaves in shadow DOM subtrees
- [Bug 17472] [Shadow]: Specify resetStyleInheritance on <content>/<shadow>
- [Bug 15480] [Shadow]: Things to Consider in the Future
- [Bug 16009] [Shadow]: Specify how CSS behaves in shadow DOM subtrees
- [Bug 15222] [Shadow]: Specify physics of apply-shadow-styles
- [Bug 16009] [Shadow]: Specify how CSS behaves in shadow DOM subtrees
- [Bug 15480] [Shadow]: Things to Consider in the Future
- [Bug 17143] [Shadow]: Consider explicitly exporting CSS Variables across a shadow boundary
- [Bug 16009] [Shadow]: Specify how CSS behaves in shadow DOM subtrees
- [Bug 15480] [Shadow]: Things to Consider in the Future
- [Bug 16294] [Shadow]: Should ShadowRoot have style?
- [Bug 16009] [Shadow]: Specify how CSS behaves in shadow DOM subtrees
- [Bug 15818] [Shadow]: Consider a notion of shared stylesheet
- [Bug 18437] XML serialization of text node does no escaping
Wednesday, 1 August 2012
- [Bug 18463] New: DOMTokenList enable
- [Bug 15818] [Shadow]: Consider a notion of shared stylesheet
- [Bug 16009] [Shadow]: Specify how CSS behaves in shadow DOM subtrees
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 18444] [Shadow]: @host @-rules vs rules in document tree
- [Bug 18461] New: Modifier key value for scroll lock is unclear
- [Bug 17627] The order of mouseenter/leave events in a subtree should be defined
- [Bug 15818] [Shadow]: Consider a notion of shared stylesheet
- [Bug 16009] [Shadow]: Specify how CSS behaves in shadow DOM subtrees
- [Bug 18454] [Shadow]: Define how apply-author-styles affects sibling selectors
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 18455] [Shadow]: Stop 'load' and 'error' events at shadow boundaries