[Bug 26033] Make distribution algorithm forward compatible with <shadow> as function call.
[Bug 25313] Improve and add examples
[Bug 23887] [Shadow] Put only the final destination insertion point to the event path
[Bug 23887] [Shadow] Put only the final destination insertion point to the event path
[Bug 23887] [Shadow] Put only the final destination insertion point to the event path
[Bug 23887] [Shadow] Put only the final destination insertion point to the event path
[Bug 23887] [Shadow] Put only the final destination insertion point to the event path
[Bug 23887] [Shadow] Put only the final destination insertion point to the event path
[Bug 26183] make it easier to define an iterator on an interface that iterates over a set of values
[Bug 26183] make it easier to define an iterator on an interface that iterates over a set of values
[Bug 20683] [Imports]: Write HTML Imports spec
[Bug 26682] New: [imports]: The relationship between import and browsing context should be stated more clearly
[Bug 26681] New: [imports]: Script execution order should be stated more clearly
[Bug 20683] [Imports]: Write HTML Imports spec
[Bug 23278] [imports]: Things to Consider in the Future
[Bug 20683] [Imports]: Write HTML Imports spec
[Bug 23170] [imports]: Why not have imported documents share their importing document's defaultView?
[Bug 25473] [Custom]: Add support for focus navigation similar to input type=date
[Bug 26677] New: Clarify when :fullscreen applies
[Bug 26676] New: Non-fullscreen documents can end up with non-empty fullscreen element stacks
[Bug 26303] Add a way to have required dictionary entries
[Bug 26673] New: Append topDoc to exitDocs?
[Bug 26672] New: Slightly confused definition of descendantDocs
- [Bug 26672] Slightly confused definition of descendantDocs
- [Bug 26672] Slightly confused definition of descendantDocs
- [Bug 26672] Slightly confused definition of descendantDocs
- [Bug 26672] Slightly confused definition of descendantDocs
[Bug 26671] New: Always-true "If error is false" in requestFullscreen()
[Bug 25587] Be more clear that progress events are about bytes being transferred
[Bug 23887] [Shadow] Put only the final destination insertion point to the event path
[Bug 26656] New: Figure out how form owner should work in shadow dom
[Bug 23887] [Shadow] Put only the final destination insertion point to the event path
[Bug 25412] Allow some recursion in NodeIterator/TreeWalker
[Bug 20480] Say something about keys
[Bug 22141] [Shadow]: Need mechanism to tell if an element in a ShadowRoot has been inserted into the Document
[Bug 22141] [Shadow]: Need mechanism to tell if an element in a ShadowRoot has been inserted into the Document
[Bug 22141] [Shadow]: Need mechanism to tell if an element in a ShadowRoot has been inserted into the Document
[Bug 25412] Allow some recursion in NodeIterator/TreeWalker
[Bug 22141] [Shadow]: Need mechanism to tell if an element in a ShadowRoot has been inserted into the Document
[Bug 23887] [Shadow] Put only the final destination insertion point to the event path
[Bug 25412] Allow some recursion in NodeIterator/TreeWalker
[Bug 25412] Allow some recursion in NodeIterator/TreeWalker
[Bug 25412] Allow some recursion in NodeIterator/TreeWalker
[Bug 25412] Allow some recursion in NodeIterator/TreeWalker
[Bug 25412] Allow some recursion in NodeIterator/TreeWalker
[Bug 25587] Be more clear that progress events are about bytes being transferred
[Bug 26303] Add a way to have required dictionary entries
[Bug 26303] Add a way to have required dictionary entries
[Bug 26643] New: Figure out how "If a reflecting IDL attribute has the type HTMLElement, or an interface that descends from HTMLElement" should work in the context of shadow dom.
- [Bug 26643] Figure out how "If a reflecting IDL attribute has the type HTMLElement, or an interface that descends from HTMLElement" should work in the context of shadow dom.
- [Bug 26643] Figure out how "If a reflecting IDL attribute has the type HTMLElement, or an interface that descends from HTMLElement" should work in the context of shadow dom.
- [Bug 26643] Figure out how "If a reflecting IDL attribute has the type HTMLElement, or an interface that descends from HTMLElement" should work in the context of shadow dom.
- [Bug 26643] Figure out how "If a reflecting IDL attribute has the type HTMLElement, or an interface that descends from HTMLElement" should work in the context of shadow dom.
- [Bug 26643] Figure out how "If a reflecting IDL attribute has the type HTMLElement, or an interface that descends from HTMLElement" should work in the context of shadow dom.
- [Bug 26643] Figure out how "If a reflecting IDL attribute has the type HTMLElement, or an interface that descends from HTMLElement" should work in the context of shadow dom.
- [Bug 26643] Figure out how "If a reflecting IDL attribute has the type HTMLElement, or an interface that descends from HTMLElement" should work in the context of shadow dom.
- [Bug 26643] Figure out how "If a reflecting IDL attribute has the type HTMLElement, or an interface that descends from HTMLElement" should work in the context of shadow dom.
[Bug 26642] New: [Shadow] Remove deepContains
[Bug 26638] New: [Custom]: sorted element queue definition is not in sync with Imports
[Bug 26033] Make distribution algorithm forward compatible with <shadow> as function call.
[Bug 26626] New: Populate the full list of event targets before firing any events
- [Bug 26626] Populate the full list of event targets before firing any events
- [Bug 26626] Populate the full list of event targets before firing any events
- [Bug 26626] Populate the full list of event targets before firing any events
[Bug 26615] New: Is topLevelViewport needed?
- [Bug 26615] Is topLevelViewport needed?
- [Bug 26615] Is topLevelViewport needed?
- [Bug 26615] Is topLevelViewport needed?
[Bug 25015] "asynchromous"
[Bug 26612] New: D3E defines input event should be fired immediately after the DOM as been updated but it shouldn't be so if the editor value is changed by setting value attribute
- [Bug 26612] D3E defines input event should be fired immediately after the DOM as been updated but it shouldn't be so if the editor value is changed by setting value attribute
- [Bug 26612] D3E defines input event should be fired immediately after the DOM as been updated but it shouldn't be so if the editor value is changed by setting value attribute
- [Bug 26612] D3E defines input event should be fired immediately after the DOM as been updated but it shouldn't be so if the editor value is changed by setting value attribute
- [Bug 26612] D3E defines input event should be fired immediately after the DOM as been updated but it shouldn't be so if the editor value is changed by setting value attribute
[Bug 26611] New: [Proposal] Add "Zoom" event
- [Bug 26611] [Proposal] Add "Zoom" event
- [Bug 26611] [Proposal] Add "Zoom" event
- [Bug 26611] [Proposal] Add "Zoom" event
- [Bug 26611] [Proposal] Add "Zoom" event
- [Bug 26611] [Proposal] Add "Zoom" event
- [Bug 26611] [Proposal] Add "Zoom" event
[Bug 26609] New: AttrExodus: investigate child nodes of attributes and attributes being nodes
- [Bug 26609] AttrExodus: investigate child nodes of attributes and attributes being nodes
- [Bug 26609] AttrExodus: investigate child nodes of attributes and attributes being nodes
- [Bug 26609] AttrExodus: investigate child nodes of attributes and attributes being nodes
[Bug 25016] AttrExodus: Element.getAttributeNode
[Bug 14978] [Meta]: Specify how shadow DOM works
[Bug 26602] New: Cross-process damage control in requestFullscreen() and exitFullscreen()?
- [Bug 26602] Cross-process damage control in requestFullscreen() and exitFullscreen()?
- [Bug 26602] Cross-process damage control in requestFullscreen() and exitFullscreen()?
- [Bug 26602] Cross-process damage control in requestFullscreen() and exitFullscreen()?
[Bug 26601] New: Populate fullscreenElements later in requestFullscreen()
- [Bug 26601] Populate fullscreenElements later in requestFullscreen()
- [Bug 26601] Populate fullscreenElements later in requestFullscreen()
[Bug 25016] AttrExodus: Element.getAttributeNode
[Bug 25016] AttrExodus: Element.getAttributeNode
[Bug 26599] New: Define abstract algorithm that performs NS validation and extraction
[Bug 26598] New: The parentDocs set should stop at documents with > 1 element on the fullscreen element stack
- [Bug 26598] The parentDocs set should stop at documents with > 1 element on the fullscreen element stack
- [Bug 26598] The parentDocs set should stop at documents with > 1 element on the fullscreen element stack
[Bug 25016] AttrExodus: Element.getAttributeNode
[Bug 25370] AttrExodus: Specify document.createAttributeNS
[Bug 25370] AttrExodus: Specify document.createAttributeNS
[Bug 25086] AttrExodus: Attr should retain ownerElement property
[Bug 21522] AttrExodus: Restore hasAttributes()
[Bug 21522] AttrExodus: Restore hasAttributes()
[Bug 25016] AttrExodus: Element.getAttributeNode
[Bug 26596] New: Attr.value cannot be readonly
- [Bug 26596] Attr.value cannot be readonly
- [Bug 26596] Attr.value cannot be readonly
- [Bug 26596] Attr.value cannot be readonly
- [Bug 26596] Attr.value cannot be readonly
- [Bug 26596] Attr.value cannot be readonly
[Bug 21522] AttrExodus: Restore hasAttributes()
[Bug 25016] AttrExodus: Element.getAttributeNode
[Bug 25093] AttrExodus: "Setting the value attribute must change value t..."
[Bug 21986] AttrExodus: Element.attributes needs to have a named getter
[Bug 25016] AttrExodus: Element.getAttributeNode
[Bug 14978] [Meta]: Specify how shadow DOM works
[Bug 26595] New: [Shadow]: A shadow host will receives an event, which must be *stopped*, if a node in a older shadow tree is distributed into a shadow insertion point in the younger tree
- [Bug 26595] [Shadow]: A shadow host will receive an event, which must be *stopped*, if a node in a older shadow tree is distributed into a shadow insertion point in the younger tree
- [Bug 26595] [Shadow]: A shadow host will receive an event, which must be *stopped*, if a node in a older shadow tree is distributed into a shadow insertion point in the younger tree
- [Bug 26595] [Shadow]: A shadow host will receive an event, which must be *stopped*, if a node in a older shadow tree is distributed into a shadow insertion point in the younger tree
- [Bug 26595] [Shadow]: A shadow host will receive an event, which must be *stopped*, if a node in a older shadow tree is distributed into a shadow insertion point in the younger tree
- [Bug 26595] [Shadow]: A shadow host will receive an event, which must be *stopped*, if a node in a older shadow tree is distributed into a shadow insertion point in the younger tree
- [Bug 26595] [Shadow]: A shadow host will receive an event, which must be *stopped*, if a node in a older shadow tree is distributed into a shadow insertion point in the younger tree
[Bug 20480] Say something about keys
[Bug 26587] New: Element removal order is undefined in "fully exit fullscreen"
- [Bug 26587] Element removal order is undefined in "fully exit fullscreen"
- [Bug 26587] Element removal order is undefined in "fully exit fullscreen"
[Bug 20976] Define base URLs in DOM
[Bug 25869] DOMClassList.toggle 'force' parameter is "wonky API design"
[Bug 24653] Planning on changing mutation hooks
[Bug 25430] NodeIterator mutation algorithm is totally broken
[Bug 23268] Cannot describe NodeIterator in terms of "node is removed"
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 26583] New: [Custom]: Add the possibility to extend the custom element
- [Bug 26583] [Custom]: Add the possibility to extend the custom element
- [Bug 26583] [Custom]: Add the possibility to extend the custom element
[Bug 26580] New: Not enough "element" in "for an element"
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 26576] New: [Custom]: Add informative text about importNode
[Bug 26568] New: Nothing stopping mis-nested fullscreen in iframes?
- [Bug 26568] Nothing stopping mis-nested fullscreen in iframes?
- [Bug 26568] Nothing stopping mis-nested fullscreen in iframes?
- [Bug 26568] Nothing stopping mis-nested fullscreen in iframes?
- [Bug 26568] Nothing stopping mis-nested fullscreen in iframes?
- [Bug 26568] Nothing stopping mis-nested fullscreen in iframes?
- [Bug 26568] Nothing stopping mis-nested fullscreen in iframes?
- [Bug 26568] Nothing stopping mis-nested fullscreen in iframes?
- [Bug 26568] Nothing stopping mis-nested fullscreen in iframes?
- [Bug 26568] Nothing stopping mis-nested fullscreen in iframes?
- [Bug 26568] Nothing stopping mis-nested fullscreen in iframes?
- [Bug 26568] Nothing stopping mis-nested fullscreen in iframes?
- [Bug 26568] Nothing stopping mis-nested fullscreen in iframes?
- [Bug 26568] Nothing stopping mis-nested fullscreen in iframes?
- [Bug 26568] Nothing stopping mis-nested fullscreen in iframes?
- [Bug 26568] Nothing stopping mis-nested fullscreen in iframes?
- [Bug 26568] Nothing stopping mis-nested fullscreen in iframes?
- [Bug 26568] Nothing stopping mis-nested fullscreen in iframes?
[Bug 26567] New: Infinite loop in "fully exit fullscreen"
[Bug 24872] [Shadow]: Consider adding back at least :first-of-type to valid matching criteria
[Bug 26563] New: Typo in "element's node document fullscreen element stack"
[Bug 25587] Be more clear that progress events are about bytes being transferred
[Bug 25587] Be more clear that progress events are about bytes being transferred
[Bug 24756] [imports]: Cascading order for stylesheets of imported documents should be stated more clearly
[Bug 26552] New: [Shadow]: consider supporting :first-child, nth-child() in content select
- [Bug 26552] [Shadow]: consider supporting :first-child, nth-child() in content select
- [Bug 26552] [Shadow]: consider supporting :first-child, nth-child() in content select
[Bug 22141] [Shadow]: Need mechanism to tell if an element in a ShadowRoot has been inserted into the Document
[Bug 22141] [Shadow]: Need mechanism to tell if an element in a ShadowRoot has been inserted into the Document
[Bug 22141] [Shadow]: Need mechanism to tell if an element in a ShadowRoot has been inserted into the Document
[Bug 24756] [imports]: Cascading order for stylesheets of imported documents should be stated more clearly
[Bug 24756] [imports]: Cascading order for stylesheets of imported documents should be stated more clearly
[Bug 22141] [Shadow]: Need mechanism to tell if an element in a ShadowRoot has been inserted into the Document
[Bug 22141] [Shadow]: Need mechanism to tell if an element in a ShadowRoot has been inserted into the Document
[Bug 25715] [imports]: Unify loading and dependency resolution model with ES6 modules
[Bug 25715] [imports]: Unify loading and dependency resolution model with ES6 modules
[Bug 25715] [imports]: Unify loading and dependency resolution model with ES6 modules
[Bug 26005] Selection.extend behavior when there is no range needs to be clarified
[Bug 26005] Selection.extend behavior when there is no range needs to be clarified
[Bug 25831] Specify selection.setBaseAndExtent
[Bug 26524] New: replace [SameObject] with [Cached]?
[Bug 16904] [Shadow]: Consider better aligning with or just plain moving ShadowRoot interface to DOM spec
[Bug 24570] [Custom]: Callback for cloneNode/importNode
[Bug 24756] [imports]: Cascading order for stylesheets of imported documents should be stated more clearly
[Bug 26490] Prevent freezing/sealing objects by having [[PreventExtensions]] return false
[Bug 26521] New: [[GetOwnProperty]] behavior for named properties is not web-compatible
[Bug 24570] [Custom]: Callback for cloneNode/importNode
[Bug 26517] New: Methods that return promises are unable to throw exceptions
- [Bug 26517] Methods that return promises are unable to throw exceptions
- [Bug 26517] Methods that return promises are unable to throw exceptions
- [Bug 26517] Methods that return promises are unable to throw exceptions
- [Bug 26517] Methods that return promises are unable to throw exceptions
- [Bug 26517] Methods that return promises are unable to throw exceptions
- [Bug 26517] Methods that return promises are unable to throw exceptions
- [Bug 26517] Methods that return promises are unable to throw exceptions
- [Bug 26517] Methods that return promises are unable to throw exceptions
- [Bug 26517] Methods that return promises are unable to throw exceptions
- [Bug 26517] Methods that return promises are unable to throw exceptions
- [Bug 26517] Methods that return promises are unable to throw exceptions
- [Bug 26517] Methods that return promises are unable to throw exceptions
- [Bug 26517] Methods that return promises are unable to throw exceptions
- [Bug 26517] Methods that return promises are unable to throw exceptions
- [Bug 26517] Methods that return promises are unable to throw exceptions
- [Bug 26517] Methods that return promises are unable to throw exceptions
- [Bug 26517] Methods that return promises are unable to throw exceptions
- [Bug 26517] Methods that return promises are unable to throw exceptions
- [Bug 26517] Methods that return promises are unable to throw exceptions
[Bug 26440] Allow fullscreenchange events to be synchronized with animation frames
[Bug 26396] innerHTML depends on node document; doesn't look at element context
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 26514] New: [Custom]: Custom elements spec lists the wrong lifecycle callbacks
- [Bug 26514] [Custom]: Custom elements spec lists the wrong lifecycle callbacks
- [Bug 26514] [Custom]: Custom elements spec lists the wrong lifecycle callbacks
- [Bug 26514] [Custom]: Custom elements spec lists the wrong lifecycle callbacks