Wednesday, 31 December 2014
- [Bug 27718] New: Avoid removing anything harmless
- [Bug 21136] Define Home key and Back key of Android smartphone
Tuesday, 30 December 2014
Sunday, 28 December 2014
Saturday, 27 December 2014
Friday, 26 December 2014
Wednesday, 24 December 2014
Tuesday, 23 December 2014
- [Bug 27688] Odd comment in DOM spec about the new "Elements" class
- [Bug 27688] New: Odd comment in DOM spec about the new "Elements" class
- [Bug 23332] Support Binary Keys
- [Bug 23332] Support Binary Keys
- [Bug 22960] Document, XMLDocument, HTMLDocument, oh my
- [Bug 27684] Handling of .contentType is not interoperable
- [Bug 27684] Handling of .contentType is not interoperable
Monday, 22 December 2014
- [Bug 27359] [Shadow]: Need to define interaction with directionality
- [Bug 20713] Consider defining window.event and Event.srcElement
- [Bug 27359] [Shadow]: Need to define interaction with directionality
- [Bug 27684] New: Handling of .contentType is not interoperable
- [Bug 27674] requestFullscreen should return a promise
- [Bug 20713] Consider defining window.event and Event.srcElement
- [Bug 20713] Consider defining window.event and Event.srcElement
- [Bug 27359] [Shadow]: Need to define interaction with directionality
- [Bug 27222] [Shadow]: "title" attribute should inherit in shadow DOM
Sunday, 21 December 2014
- [Bug 20713] Consider defining window.event and Event.srcElement
- [Bug 19962] Add insertAdjacentText and insertAdjacentElement?
- [Bug 20713] Consider defining window.event and Event.srcElement
- [Bug 27674] requestFullscreen should return a promise
- [Bug 20713] Consider defining window.event and Event.srcElement
- [Bug 27674] requestFullscreen should return a promise
- [Bug 19962] Add insertAdjacentText and insertAdjacentElement?
- [Bug 20713] Consider defining window.event and Event.srcElement
Saturday, 20 December 2014
- [Bug 20713] Consider defining window.event and Event.srcElement
- [Bug 27222] [Shadow]: "title" attribute should inherit in shadow DOM
- [Bug 27359] [Shadow]: Need to define interaction with directionality
- [Bug 19962] Add insertAdjacentText and insertAdjacentElement?
- [Bug 20713] Consider defining window.event and Event.srcElement
- [Bug 26440] Allow fullscreenchange events to be synchronized with animation frames
- [Bug 27674] requestFullscreen should return a promise
- [Bug 27674] requestFullscreen should return a promise
Friday, 19 December 2014
- [Bug 19962] Add insertAdjacentText and insertAdjacentElement?
- [Bug 20713] Consider defining window.event and Event.srcElement
- [Bug 27674] requestFullscreen should return a promise
- [Bug 27674] requestFullscreen should return a promise
- [Bug 27674] requestFullscreen should return a promise
- [Bug 27359] [Shadow]: Need to define interaction with directionality
- [Bug 27674] requestFullscreen should return a promise
- [Bug 27674] New: requestFullscreen should return a promise
- [Bug 27010] allow beforepaste event listeners to inspect type of clipboard contents (?)
Thursday, 18 December 2014
- [Bug 27222] [Shadow]: "title" attribute should inherit in shadow DOM
- [Bug 27222] [Shadow]: "title" attribute should inherit in shadow DOM
- [Bug 27222] [Shadow]: "title" attribute should inherit in shadow DOM
- [Bug 27222] [Shadow]: "title" attribute should inherit in shadow DOM
- [Bug 21434] Need to spec liveness of Gamepad objects
- [Bug 21434] Need to spec liveness of Gamepad objects
- [Bug 26181] Spec should specify the presentation of the array returned by navigator.getGamepads() w.r.t "holes"
- [Bug 26181] Spec should specify the presentation of the array returned by navigator.getGamepads() w.r.t "holes"
- [Bug 26181] Spec should specify the presentation of the array returned by navigator.getGamepads() w.r.t "holes"
- [Bug 26181] Spec should specify the presentation of the array returned by navigator.getGamepads() w.r.t "holes"
- [Bug 26181] Spec should specify the presentation of the array returned by navigator.getGamepads() w.r.t "holes"
- [Bug 26181] Spec should specify the presentation of the array returned by navigator.getGamepads() w.r.t "holes"
- [Bug 26181] Spec should specify the presentation of the array returned by navigator.getGamepads() w.r.t "holes"
- [Bug 27222] [Shadow]: "title" attribute should inherit in shadow DOM
- [Bug 27637] [Shadow]: Explain the CSS inheritance in terms of Composed Tree
- [Bug 27650] Allow multiple nodes to be inserted to range
- [Bug 27650] Allow multiple nodes to be inserted to range
- [Bug 27650] Allow multiple nodes to be inserted to range
- [Bug 27650] Allow multiple nodes to be inserted to range
- [Bug 27650] New: Allow multiple nodes to be inserted to range
- [Bug 27637] [Shadow]: Explain the CSS inheritance in terms of Composed Tree
- [Bug 27222] [Shadow]: "title" attribute should inherit in shadow DOM
- [Bug 27222] [Shadow]: "title" attribute should inherit in shadow DOM
- [Bug 27222] [Shadow]: "title" attribute should inherit in shadow DOM
- [Bug 27222] [Shadow]: "title" attribute should inherit in shadow DOM
Wednesday, 17 December 2014
- [Bug 26181] Spec should specify the presentation of the array returned by navigator.getGamepads() w.r.t "holes"
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 27643] New: [Custom]: Section 10 prototype is not defined
- [Bug 27636] Markup typo "attributes moved from Node to Element."
- [Bug 27637] [Shadow]: Explain the CSS inheritance in terms of Composed Tree
- [Bug 27222] [Shadow]: "title" attribute should inherit in shadow DOM
- [Bug 27424] Node.isSameNode() has non-trivial usage
- [Bug 27424] Node.isSameNode() has non-trivial usage
- [Bug 27424] Node.isSameNode() has non-trivial usage
- [Bug 27637] [Shadow]: Explain the CSS inheritance in terms of Composed Tree
- [Bug 27637] New: [Shadow]: Explain the CSS inheritance in terms of ComposedTree
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 27636] New: Markup typo "attributes moved from Node to Element."
- [Bug 27424] Node.isSameNode() has non-trivial usage
- [Bug 27222] [Shadow]: "title" attribute should inherit in shadow DOM
- [Bug 27222] [Shadow]: "title" attribute should inherit in shadow DOM
- [Bug 27222] [Shadow]: "title" attribute should inherit in shadow DOM
Tuesday, 16 December 2014
- [Bug 27623] A node.index() method for the ChildNode interface?
- [Bug 22808] Throw if object is constructed without new
- [Bug 27623] A node.index() method for the ChildNode interface?
- [Bug 27623] A node.index() method for the ChildNode interface?
- [Bug 27623] A node.index() method for the ChildNode interface?
- [Bug 27623] A node.index() method for the ChildNode interface?
- [Bug 27623] A node.index() method for the ChildNode interface?
- [Bug 27623] New: A node.index() method for the ChildNode interface?
Monday, 15 December 2014
- [Bug 27605] [NewObject] and Promise
- [Bug 27544] [IndexedDB] "and and" typo
- [Bug 27611] [Custom]: SVG diagram accessibility
- [Bug 27611] [Custom]: SVG diagram accessibility
- [Bug 27611] New: [Custom]: SVG diagram accessibility
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 27597] [Shadow]: ShadowRoot is an interface (change section title)
- [Bug 27597] [Shadow]: ShadowRoot is an interface (change section title)
- [Bug 22080] [Shadow]: Node should expose their scope so that shared state can be scoped to components.
- [Bug 27544] [IndexedDB] "and and" typo
- [Bug 27605] [NewObject] and Promise
- [Bug 27605] [NewObject] and Promise
- [Bug 22716] [Shadow]: [Meta] Cleanup, refactoring, and polish
- [Bug 23620] [Shadow]: remove getElement* methods
- [Bug 27605] [NewObject] and Promise
Sunday, 14 December 2014
Saturday, 13 December 2014
- [Bug 27569] Move getElementsBy* to ParentNode?
- [Bug 27605] New: [NewObject] and Promise
- [Bug 23620] [Shadow]: remove getElement* methods
- [Bug 27557] Consider introducing a prose-friendly way to refer to enumerations
Friday, 12 December 2014
- [Bug 23620] [Shadow]: remove getElement* methods
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 27597] New: [Shadow]: ShadowRoot is an interface (change section title)
- [Bug 27569] Move getElementsBy* to ParentNode?
- [Bug 26440] Allow fullscreenchange events to be synchronized with animation frames
- [Bug 27569] Move getElementsBy* to ParentNode?
- [Bug 27557] Consider introducing a prose-friendly way to refer to enumerations
- [Bug 27557] Consider introducing a prose-friendly way to refer to enumerations
- [Bug 27593] Add some extended attributes to IDL
- [Bug 21066] Provide an event path API
- [Bug 27593] New: Add some extended attributes to IDL
- [Bug 23620] [Shadow]: remove getElement* methods
- [Bug 23620] [Shadow]: remove getElement* methods
- [Bug 27569] Move getElementsBy* to ParentNode?
- [Bug 21066] Provide an event path API
- [Bug 22716] [Shadow]: [Meta] Cleanup, refactoring, and polish
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 26365] [Shadow]: Need an equivalent definition of 'in a Document' for shadow trees
- [Bug 22080] [Shadow]: Node should expose their scope so that shared state can be scoped to components.
- [Bug 26365] [Shadow]: Need an equivalent definition of 'in a Document' for shadow trees
- [Bug 22715] [Shadow]: [Meta] New features and improvements
- [Bug 23636] [Shadow]: selectors in style elements in shadowRoots should match in sibling shadowRoots
Thursday, 11 December 2014
- [Bug 23620] [Shadow]: remove getElement* methods
- [Bug 23620] [Shadow]: remove getElement* methods
- [Bug 23620] [Shadow]: remove getElement* methods
- [Bug 23620] [Shadow]: remove getElement* methods
- [Bug 23620] [Shadow]: remove getElement* methods
- [Bug 27569] Move getElementsBy* to ParentNode?
- [Bug 27569] Move getElementsBy* to ParentNode?
- [Bug 27569] Move getElementsBy* to ParentNode?
- [Bug 27569] Move getElementsBy* to ParentNode?
- [Bug 27569] Move getElementsBy* to ParentNode?
- [Bug 27569] Move getElementsBy* to ParentNode?
- [Bug 27569] Move getElementsBy* to ParentNode?
- [Bug 27569] Move getElementsBy* to ParentNode?
- [Bug 27569] New: Move getElementsBy* to ParentNode?
- [Bug 27565] Step 15-1 in the clone range algorithm should specify a deep clone of the contained child.
- [Bug 27568] New: Requirement about DOMParser.parseFromString().location should not be normative
- [Bug 26365] [Shadow]: Need an equivalent definition of 'in a Document' for shadow trees
- [Bug 27565] New: Step 15-1 in the clone range algorithm should specify a deep clone of the contained child.
- [Bug 26181] Spec should specify the presentation of the array returned by navigator.getGamepads() w.r.t "holes"
- [Bug 27424] Node.isSameNode() has non-trivial usage
Wednesday, 10 December 2014
- [Bug 27424] Node.isSameNode() has non-trivial usage
- [Bug 27424] Node.isSameNode() has non-trivial usage
- [Bug 26181] Spec should specify the presentation of the array returned by navigator.getGamepads() w.r.t "holes"
- [Bug 27558] New: Specify MouseEvent.which
- [Bug 26181] Spec should specify the presentation of the array returned by navigator.getGamepads() w.r.t "holes"
- [Bug 26181] Spec should specify the presentation of the array returned by navigator.getGamepads() w.r.t "holes"
- [Bug 20683] [Imports]: Write HTML Imports spec
- [Bug 27550] [imports]: Content-Disposition header should be recognized
- [Bug 27553] Support Symbol
- [Bug 27553] Support Symbol
- [Bug 27553] Support Symbol
- [Bug 26181] Spec should specify the presentation of the array returned by navigator.getGamepads() w.r.t "holes"
- [Bug 26181] Spec should specify the presentation of the array returned by navigator.getGamepads() w.r.t "holes"
- [Bug 26181] Spec should specify the presentation of the array returned by navigator.getGamepads() w.r.t "holes"
- [Bug 27557] Consider introducing a prose-friendly way to refer to enumerations
- [Bug 26181] Spec should specify the presentation of the array returned by navigator.getGamepads() w.r.t "holes"
- [Bug 26181] Spec should specify the presentation of the array returned by navigator.getGamepads() w.r.t "holes"
- [Bug 27557] Consider introducing a prose-friendly way to refer to enumerations
- [Bug 27557] New: Consider introducing a prose-friendly way to refer to enumerations
- [Bug 26181] Spec should specify the presentation of the array returned by navigator.getGamepads() w.r.t "holes"
- [Bug 27553] New: Support Symbol
- [Bug 27424] Node.isSameNode() has non-trivial usage
Tuesday, 9 December 2014
- [Bug 27424] Node.isSameNode() has non-trivial usage
- [Bug 27317] Provide explicit guidance on enum value naming
- [Bug 27317] Provide explicit guidance on enum value naming
- [Bug 27317] Provide explicit guidance on enum value naming
- [Bug 27550] [imports]: Content-Disposition header should be recognized
- [Bug 20683] [Imports]: Write HTML Imports spec
- [Bug 27550] New: [imports]: Content-Disposition header should be recognized
- [Bug 27424] Node.isSameNode() has non-trivial usage
- [Bug 27424] Node.isSameNode() has non-trivial usage
- [Bug 27424] Node.isSameNode() has non-trivial usage
- [Bug 27549] Support holes or undefined values in the sequences as return values?
- [Bug 26181] Spec should specify the presentation of the array returned by navigator.getGamepads() w.r.t "holes"
- [Bug 27549] Support holes or undefined values in the sequences as return values?
- [Bug 27549] Support holes or undefined values in the sequences as return values?
- [Bug 27549] Support holes in the sequence return values?
- [Bug 27549] Support holes in the sequence return values?
- [Bug 27549] Support holes in the sequence return values?
- [Bug 27544] [IndexedDB] "and and" typo
- [Bug 27549] New: Support holes in the sequence return values?
- [Bug 27544] [IndexedDB] "and and" typo
- [Bug 26181] Spec should specify the presentation of the array returned by navigator.getGamepads() w.r.t "holes"
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 27545] [Custom]: Closing tag in example
- [Bug 27546] [Custom]: Update example markup
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 27546] New: [Custom]: Update example markup
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 27545] New: [Custom]: Closing tag in example
- [Bug 27488] Steps 14-5 and 17-5 of the DOM 4 Range cloning algorithm appear to be incorrect.
- [Bug 27544] New: [IndexedDB] "and and" typo
Monday, 8 December 2014
- [Bug 27488] Steps 14-5 and 17-5 of the DOM 4 Range cloning algorithm appear to be incorrect.
- [Bug 27538] [Custom]: Tone of note doesn't reflect severity
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 27538] New: [Custom]: Tone of note doesn't reflect severity
- [Bug 27534] Typo in "It is typically implemented as an JavaScript function"
- [Bug 27534] New: Typo in "It is typically implemented as an JavaScript function"
- [Bug 27488] Steps 14-5 and 17-5 of the DOM 4 Range cloning algorithm appear to be incorrect.
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 27511] [Shadow]: Six node trees in the diagram but description says "seven"
- [Bug 27466] https://dvcs.w3.org/hg/innerhtml/raw-file/tip/index.html#concept-serialize link is stale
Saturday, 6 December 2014
- [Bug 27488] Steps 14-5 and 17-5 of the DOM 4 Range cloning algorithm appear to be incorrect.
- [Bug 27488] Steps 14-5 and 17-5 of the DOM 4 Range cloning algorithm appear to be incorrect.
- [Bug 27466] https://dvcs.w3.org/hg/innerhtml/raw-file/tip/index.html#concept-serialize link is stale
Friday, 5 December 2014
- [Bug 26901] Stop using "octet"
- [Bug 26901] Stop using "octet"
- [Bug 26901] Stop using "octet"
- [Bug 26901] Stop using "octet"
- [Bug 26901] Stop using "octet"
Thursday, 4 December 2014
- [Bug 20567] Change [[Prototype]] for concept-node-adopt?
- [Bug 27521] Hook for changing prototype of an object to that of a specified global
- [Bug 20567] Change [[Prototype]] for concept-node-adopt?
- [Bug 27521] New: Hook for changing prototype of an object to that of a specified global
- [Bug 26901] Stop using "octet"
- [Bug 26901] Stop using "octet"
- [Bug 26901] Stop using "octet"
- [Bug 26901] Stop using "octet"
- [Bug 16070] uses MessageEvent but doesn't define or reference external definition
- [Bug 26850] [Shadow]: Style element should specify when to create and add style sheet in shadow DOM
- [Bug 26850] [Shadow]: Style element should specify when to create and add style sheet in shadow DOM
- [Bug 27511] [Shadow]: Six node trees in the diagram but description says "seven"
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 27511] New: [Shadow]: Six node trees in the diagram but description says "seven"
Wednesday, 3 December 2014
- [Bug 14949] [Meta]: Component Model needs an Explainer document
- [Bug 27496] New: [Explainer]: mispell on inherifance
- [Bug 26365] [Shadow]: Need an equivalent definition of 'in a Document' for shadow trees
- [Bug 26365] [Shadow]: Need an equivalent definition of 'in a Document' for shadow trees
- [Bug 20144] [Shadow]: Add "private" flag to createShadowRoot
- [Bug 27488] Steps 14-5 and 17-5 of the DOM 4 Range cloning algorithm appear to be incorrect.
- [Bug 27488] New: Steps 14-5 and 17-5 of the DOM 4 Range cloning algorithm appear to be incorrect.
Tuesday, 2 December 2014
- [Bug 27284] Should InvalidAccessError be discouraged?
- [Bug 27284] Should InvalidAccessError be discouraged?
- [Bug 27481] New: "The nodeType attribute must return the type of ..."
Monday, 1 December 2014
- [Bug 27466] https://dvcs.w3.org/hg/innerhtml/raw-file/tip/index.html#concept-serialize link is stale
- [Bug 22156] Allow trailing commas in Web IDL lists
- [Bug 11190] Make scripts created by createContextualFragment() executable
- [Bug 27386] Removing createCDATASection() unlikely to be successful
- [Bug 27386] Removing createCDATASection() unlikely to be successful