Sunday, 31 March 2013
- [Bug 21430] [Templates]: <template><table>Foo should result in <template> being the foster parent for "Foo"
- [Bug 5851] Consider adding .toArray() on NodeList and HTMLCollection
- [Bug 21444] FutureResolver's resolve algorithm uses wrong resolver in new handlers
- [Bug 21433] "AlreadyResolved" error name is not listed
Saturday, 30 March 2013
- [Bug 21444] FutureResolver's resolve algorithm uses wrong resolver in new handlers
- [Bug 21444] New: FutureResolver's resolve algorithm uses wrong resolver in new handlers
Friday, 29 March 2013
- [Bug 21404] [Shadow]: 5.5 Event Dispatch references incorrect steps of event dispatching algorithm
- [Bug 21434] Need to spec liveness of Gamepad objects
- [Bug 17309] It is not defined what the value of Gamepad.index should be after disconnecting the gamepad
- [Bug 17309] It is not defined what the value of Gamepad.index should be after disconnecting the gamepad
- [Bug 21434] New: Need to spec liveness of Gamepad objects
- [Bug 21433] "AlreadyResolved" error name is not listed
- [Bug 21433] "AlreadyResolved" error name is not listed
- [Bug 21433] New: "AlreadyResolved" error name is not listed
Thursday, 28 March 2013
- [Bug 21430] [Templates]: <template><table>Foo should result in <template> being the foster parent for "Foo"
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 21430] New: [Templates]: <template><table>Foo should result in <template> being the foster parent for "Foo"
- [Bug 21226] [Components]: Components fetching should always use CORS.
- [Bug 21427] Futures: use thenable
- [Bug 21427] Futures: use thenable
- [Bug 21427] New: Futures: use thenable
- [Bug 21424] Futures: rename `catch`
- [Bug 21424] Futures: rename `catch`
- [Bug 21424] Futures: rename `catch`
- [Bug 21424] Futures: rename `catch`
- [Bug 21424] Futures: rename `catch`
- [Bug 21424] New: Futures: rename `catch`
- [Bug 21422] New: Futures
- [Bug 21229] [Components]: would like to be able to load external scripts too
- [Bug 21229] [Components]: would like to be able to load external scripts too
Wednesday, 27 March 2013
- [Bug 20600] [Shadow]: Custom Pseudo-Elements should follow the same convention as custom element names.
- [Bug 20600] [Shadow]: Custom Pseudo-Elements should follow the same convention as custom element names.
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 21409] New: [Custom]: The upgrade algorithm should invoke lifecycle callback
- [Bug 21408] [Custom]: should createElement('x-foo') work when called synchronously after document.register('x-foo', ...)
- [Bug 21408] [Custom]: should createElement('x-foo') work when called synchronously after document.register('x-foo', ...)
- [Bug 21408] [Custom]: does createElement('x-foo') work when called synchronously after document.register('x-foo', ...)
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 21408] New: [Custom]: can I use createElement synchronously after calling document.register
- [Bug 21407] New: [Custom]: Loading resources is inconvenient
- [Bug 14968] [Meta]: Specify how custom elements work
Tuesday, 26 March 2013
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 21404] New: [Shadow]: 5.5 Event Dispatch references incorrect steps of event dispatching algorithm
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 21400] New: [Shadow]: 5.4 Events that are Always Stopped needs clarification
- [Bug 21399] New: [Components]:
- [Bug 20683] [Components]: Specify how Custom Elements are included as external resources
- [Bug 21387] Need to spec better support for control mapping
- [Bug 20713] Consider defining window.event and Event.srcElement
- [Bug 21389] [Shadow]: ::distributed should allow the :root pseudo selector
- [Bug 21389] [Shadow]: ::distributed should allow the :root pseudo selector
- [Bug 21389] [Shadow]: ::distributed should allow the :root pseudo selector
- [Bug 21392] FileReader does not specify behavior on invalid input
Monday, 25 March 2013
- [Bug 21392] FileReader does not specify behavior on invalid input
- [Bug 21392] New: FileReader does not specify behavior on invalid input
- [Bug 21391] New: [Shadow]: allow @host rules to match nodes in the host scope not just the host node
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 21390] New: [Shadow]: add support for styling shadowDOM contents based on host element
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 21389] New: [Shadow]: ::distributed should allow the :root pseudo selector
- [Bug 21338] Gut check on when to clear transient registered mutation observers
- [Bug 21338] Gut check on when to clear transient registered mutation observers
- [Bug 17201] HTMLCollection.prototype.namedItem behavior not defined for HTMLPropertiesCollection
- [Bug 21387] Need to spec better support for control mapping
- [Bug 20713] Consider defining window.event and Event.srcElement
- [Bug 21388] New: handling of analog vs. digital buttons
- [Bug 21387] New: Need to spec better support for control mapping
- [Bug 21386] New: Should specify how to present d-pads/triggers as buttons
- [Bug 21270] Introduce syntax for getters that keep returning the same object
- [Bug 17201] HTMLCollection.prototype.namedItem behavior not defined for HTMLPropertiesCollection
- [Bug 17311] The dictionary for GamepadEvent's ctor isn't defined
Friday, 22 March 2013
- [Bug 17310] The target of gamepad(dis)connected events is not defined
- [Bug 17311] The dictionary for GamepadEvent's ctor isn't defined
- [Bug 21321] Add event constructor and *EventInit dictionary for GamePadEvent
- [Bug 17681] [IndexedDB] Operations that raise multiple exceptions types should define order
- [Bug 21255] [Components]: Components should load as DocumentFragments
- [Bug 17309] It is not defined what the value of Gamepad.index should be after disconnecting the gamepad
- [Bug 17309] It is not defined what the value of Gamepad.index should be after disconnecting the gamepad
- [Bug 17309] It is not defined what the value of Gamepad.index should be after disconnecting the gamepad
- [Bug 17309] It is not defined what the value of Gamepad.index should be after disconnecting the gamepad
- [Bug 17310] The target of gamepad(dis)connected events is not defined
- [Bug 21320] The spec doesn't define where the events should be dispatched
- [Bug 17306] The initial value of timestamp is not defined
- [Bug 21322] The definition of timestamp is unclear
- [Bug 21323] Gamepad should have a connected attribute
- [Bug 21067] [Shadow]: Provide an api to insertionParent
- [Bug 21067] [Shadow]: Provide an api to getDistributedParent
- [Bug 21067] [Shadow]: Provide an api to getDistributedParent
- [Bug 21067] [Shadow]: Provide an api to getDistributedParent
- [Bug 21067] [Shadow]: Provide an api to getDistributedParent
- [Bug 21067] [Shadow]: Provide an api to getDistributedParent
- [Bug 21067] [Shadow]: Provide an api to getDistributedParent
- [Bug 21067] [Shadow]: Provide an api to getDistributedParent
- [Bug 21067] [Shadow]: Provide an api to getDistributedParent
Thursday, 21 March 2013
- [Bug 18289] Support 'column' here for consistency with window.onerror?
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 21366] New: [Shadow]: "Assigned" term should be explained and linkified
- [Bug 19297] May user agents apply additional restrictions on entering pointer lock?
- [Bug 20720] Define HTMLSelectElement.remove() (without argument) to do the same as ChildNode.remove()
- [Bug 21067] [Shadow]: Provide an api to getDistributedParent
- [Bug 21354] [Explainer]: Web Components explainer actually explaining Custom Elements spec
Wednesday, 20 March 2013
- [Bug 21066] [Shadow]: Provide an event path api
- [Bug 20720] Define HTMLSelectElement.remove() (without argument) to do the same as ChildNode.remove()
- [Bug 21354] [Explainer]: Web Components explainer actually explaining Custom Elements spec
- [Bug 14949] [Meta]: Component Model needs an Explainer document
- [Bug 21354] New: [Explainer]:
Tuesday, 19 March 2013
- [Bug 21067] [Shadow]: Provide an api to getDistributedParent
- [Bug 21067] [Shadow]: Provide an api to getDistributedParent
- [Bug 21067] [Shadow]: Provide an api to getDistributedParent
- [Bug 21067] [Shadow]: Provide an api to getDistributedParent
- [Bug 21338] Gut check on when to clear transient registered mutation observers
- [Bug 21338] Gut check on when to clear transient registered mutation observers
- [Bug 21305] [Shadow] Add explanatory rationale for the set of content selectors, and possibly update the spec with selectors from CSS4 Selectors
- [Bug 21338] New: Gut check on when to clear transient registered mutation observers
- [Bug 21318] anon flag should be anonymous
- [Bug 21305] [Shadow] Add explanatory rationale for the set of content selectors, and possibly update the spec with selectors from CSS4 Selectors
- [Bug 21305] [Shadow]: :visited selectors are dangerous
- [Bug 21305] [Shadow]: :visited selectors are dangerous
Monday, 18 March 2013
- [Bug 5851] Consider adding .toArray() on NodeList and HTMLCollection
- [Bug 21305] [Shadow]: :visited selectors are dangerous
- [Bug 21271] Node.childNodes and Element.attributes need to return the same object each time
- [Bug 21271] Node.childList and Element.attributes need to return the same object each time
- [Bug 21323] New: Gamepad should have a connected attribute
- [Bug 21322] New: The definition of timestamp is unclear
- [Bug 21321] New: Add event constructor and *EventInit dictionary for GamePadEvent
- [Bug 21320] New: The spec doesn't define where the events should be dispatched
- [Bug 21305] [Shadow]: :visited selectors are dangerous
- [Bug 21318] New: anon flag should be anonymous
- [Bug 21318] anon flag should be anonymous
Saturday, 16 March 2013
Friday, 15 March 2013
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 21305] New: [Shadow]: :visited selectors are dangerous
- [Bug 21066] [Shadow]: Provide an event path api
- [Bug 21295] overload resolution: are DOMString and sequence<T> distinguishable now?
Thursday, 14 March 2013
- [Bug 21295] New: overload resolution: are DOMString and sequence<T> distinguishable now?
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 21293] New: [Templates]: EOF processing fails if a <template> in a non-html namespace is on the stack of open elements
Wednesday, 13 March 2013
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 20924] [Templates]: processing an EOF token deep within a template which was opened in <head> may fail to run after-head work
- [Bug 21269] [Shadow]: Should Non-bubbling events in ShadowRoot children trigger listeners on Host?
- [Bug 20683] [Components]: Specify how Custom Elements are included as external resources
- [Bug 21275] New: [Components]: Force utf-8
- [Bug 21269] [Shadow]: Should Non-bubbling events in ShadowRoot children trigger listeners on Host?
- [Bug 16834] FileList in input.files (multiple attribute)
- [Bug 17125] Add a FileList.drop(index) method
- [Bug 21270] Introduce syntax for getters that keep returning the same object
- [Bug 21269] [Shadow]: Should Non-bubbling events in ShadowRoot children trigger listeners on Host?
- [Bug 21270] Introduce syntax for getters that keep returning the same object
- [Bug 21270] Introduce syntax for getters that keep returning the same object
- [Bug 21271] New: Node.childList and Element.attributes need to return the same object each time
- [Bug 21270] New: Introduce syntax for getters that keep returning the same object
- [Bug 21269] New: [Shadow]: Should Non-bubbling events in ShadowRoot children trigger listeners on Host?
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 18511] [Custom]: Things to Consider in the Future
- [Bug 18669] Switch from is= to <tag if a decision has been reached among implementers
- [Bug 14967] [Custom Elements]: Find a way to avoid "x-" prefix because it's ugly
- [Bug 21264] New: referrer source is wrong
Tuesday, 12 March 2013
- [Bug 21218] [Components]: Specify that loading components blocks script
- [Bug 20683] [Components]: Specify how Custom Elements are included as external resources
- [Bug 17749] [WebIDL] Nit: "unrestricted double type" defined as 32-bit
- [Bug 21251] Typos: unrestricted double describing 32-bit float (copy/paste error)
- [Bug 21258] [Explainer]: this spec seems extremely dev-oriented, rather than HTML-writing-people oriented
- [Bug 21258] [Explainer]: this spec seems extremely dev-oriented, rather than HTML-writing-people oriented
- [Bug 21258] [Explainer]: this spec seems extremely dev-oriented, rather than HTML-writing-people oriented
- [Bug 21258] New: [Explainer]: this spec seems extremely dev-oriented, rather than HTML-writing-people oriented
- [Bug 14949] [Meta]: Component Model needs an Explainer document
- [Bug 18540] Proposal for a new acceptNode() return value for TreeWalker.
- [Bug 18867] Web developers cannot know whether a key event will cause text input actually
Monday, 11 March 2013
- [Bug 20683] [Components]: Specify how Custom Elements are included as external resources
- [Bug 21255] New: [Components]: Components should load as DocumentFragments
- [Bug 21217] [Components]: Add willchan and simonjam as contributors
- [Bug 20683] [Components]: Specify how Custom Elements are included as external resources
- [Bug 21253] [Components]: Consider changing component location to component identifier
- [Bug 21242] [Shadow]: 6.3 @host @-rule should extend the CSS 2.1 grammar 'stylesheet' production
- [Bug 21242] [Shadow]: 6.3 @host @-rule should extend the CSS 2.1 grammar 'stylesheet' production
- [Bug 20683] [Components]: Specify how Custom Elements are included as external resources
- [Bug 21253] New: [Components]: Consider adding an optional name attribute and using it in the loading algorithm
- [Bug 21251] Typos: unrestricted double describing 32-bit float (copy/paste error)
- [Bug 21251] New: Typos: double/unrestricted double describing "float" (copy/paste error)
- [Bug 21242] [Shadow]: 6.3 @host @-rule should extend the CSS 2.1 grammar 'stylesheet' production
- [Bug 16834] FileList in input.files (multiple attribute)
- [Bug 18540] Proposal for a new acceptNode() return value for TreeWalker.
- [Bug 16834] FileList in input.files (multiple attribute)
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 21242] New: [Shadow]: 6.3 @host @-rule should extend the CSS 2.1 grammar 'stylesheet' production
Saturday, 9 March 2013
- [Bug 21229] [Components]: would like to be able to load external scripts too
- [Bug 20683] [Components]: Specify how Custom Elements are included as external resources
- [Bug 21229] New: [Components]: would like to be able to load external scripts too
Friday, 8 March 2013
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 21228] [Templates]: </template> handling for "in head" should check for "template element in html scope"
- [Bug 21228] New: [Templates]: </template> handling for "in head" should check for "template element in html scope"
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 18540] Proposal for a new acceptNode() return value for TreeWalker.
- [Bug 20683] [Components]: Specify how Custom Elements are included as external resources
- [Bug 21226] New: [Components]: Components fetching should always use CORS.
- [Bug 20683] [Components]: Specify how Custom Elements are included as external resources
- [Bug 21225] New: [Components]: Component interface is not necessary
- [Bug 17201] HTMLCollection.prototype.namedItem behavior not defined for HTMLPropertiesCollection
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 21220] New: [Custom]: document.register() should not allow custom element name duplication
- [Bug 21219] New: [Custom]: document.register() should allow aliases of same prototype object.
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 20683] [Components]: Specify how Custom Elements are included as external resources
- [Bug 21218] New: [Components]: Specify that loading components blocks script
- [Bug 20683] [Components]: Specify how Custom Elements are included as external resources
- [Bug 21217] New: [Components]: Add willchan and simonjam as contributors
Thursday, 7 March 2013
- [Bug 21169] [Components]: Write introduction section
- [Bug 20683] [Components]: Specify how Custom Elements are included as external resources
- [Bug 21215] New: [Components]: Specify how the <element> elements are processed
- [Bug 20683] [Components]: Specify how Custom Elements are included as external resources
- [Bug 21214] New: [Components]: Write example for imperative API
- [Bug 20683] [Components]: Specify how Custom Elements are included as external resources
- [Bug 20468] [Components]: specify link rel="components"
- [Bug 20683] [Components]: Specify how Custom Elements are included as external resources
- [Bug 21168] [Components]: Write the spec
- [Bug 19870] [Components]: Ensure component resources are loaded relative to location of component definition
- [Bug 20683] [Components]: Specify how Custom Elements are included as external resources
- [Bug 19870] [Components]: Ensure component resources are loaded relative to location of component definition
- [Bug 17201] HTMLCollection.prototype.namedItem behavior not defined for HTMLPropertiesCollection
- [Bug 17201] HTMLCollection.prototype.namedItem behavior not defined for HTMLPropertiesCollection
- [Bug 20463] The otherwise clause for Document objects can point to the DOM standard instead. See bug 20390 for more details.
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 21209] New: [Custom]: 4 Instantiating Custom Elements: parameters on createElement() doesn't need to be optional
- [Bug 21137] Define key names for game controller of Android
- [Bug 21204] [Custom]: "Custom tag wins" policy can be inconsistent.
- [Bug 21137] Define key names for game controller of Android
- [Bug 14968] [Meta]: Specify how custom elements work
Wednesday, 6 March 2013
- [Bug 20463] The otherwise clause for Document objects can point to the DOM standard instead. See bug 20390 for more details.
- [Bug 20463] The otherwise clause for Document objects can point to the DOM standard instead. See bug 20390 for more details.
- [Bug 21204] New: [Custom]: "Custom tag wins" policy can be inconsistent.
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 21202] [Shadow]: Clarify how @host rules interact with the 'scoped' attribute in a <style> in a shadow tree
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 21202] New: [Shadow]:
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 21201] New: [Shadow]: The spec should not mention select reference combinators when it means ::distributed
Tuesday, 5 March 2013
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 21200] New: [Custom]: Case sensitivity of custom element names?
- [Bug 21137] Define key names for game controller of Android
- [Bug 21137] Define key names for game controller of Android
- [Bug 21137] Define key names for game controller of Android
- [Bug 21137] Define key names for game controller of Android
- [Bug 21137] Define key names for game controller of Android
Monday, 4 March 2013
- [Bug 21147] WebSocket API could provide a method to get the HTTP response code when it's not 101
- [Bug 21168] [Components]: Write the spec
- [Bug 20468] [Components]: specify link rel="components"
- [Bug 19870] [Components]: Ensure component resources are loaded relative to location of component definition
- [Bug 20683] [Components]: Specify how Custom Elements are included as external resources
- [Bug 19297] May user agents apply additional restrictions on entering pointer lock?
- [Bug 20683] [Components]: Specify Custom Elements are included as external resources
- [Bug 21147] WebSocket API could provide a method to get the HTTP response code when it's not 101
- [Bug 21147] WebSocket API could provide a method to get the HTTP response code when it's not 101
- [Bug 21147] WebSocket API could provide a method to get the HTTP response code when it's not 101
- [Bug 21147] WebSocket API could provide a method to get the HTTP response code when it's not 101
Saturday, 2 March 2013
- [Bug 20683] [Packages]: Specify how Web Components are packaged
- [Bug 21169] New: [Packages]: Write introduction section
Friday, 1 March 2013
- [Bug 20683] [Packages]: Specify how Web Components are packaged
- [Bug 21168] New: [Packages]: Write the spec
- [Bug 20468] [Packages]: specify link rel="components"
- [Bug 19870] [Packages]: Ensure component resources are loaded relative to location of component definition
- [Bug 20683] [Packages]: Specify how Web Components are packaged
- [Bug 17649] Address WebIDL comments from Kyle Huey and Ms2ger
- [Bug 17649] Address WebIDL comments from Kyle Huey and Ms2ger
- [Bug 20260] [Shadow]: ShadowRoot should have shadowRoot attribute to get older shadow tree.
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 20260] [Shadow]: ShadowRoot should have shadowRoot attribute to get older shadow tree.
- [Bug 21166] [Shadow]: The olderShadowRoot property should be defined on ShadowRoot
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 21166] New: [Shadow]: The olderShadowRoot property should be defined on ShadowRoot
- [Bug 18809] Some examples in the index section (3.3.4) have errors
- [Bug 18502] [IndexedDB] Editorial: Wording around IDBFactory.open() with no version misleading
- [Bug 20394] [IndexedDB] Spec should use WebIDL concepts such as sequence<T> rather than Array
- [Bug 16653] IndexedDB: Define overloads for IDBDatabase.transaction()
- [Bug 20394] [IndexedDB] Spec should use WebIDL concepts such as sequence<T> rather than Array
- [Bug 20582] Definitions of "valid key" and key comparison are underdefined and not compatible with WebIDL
- [Bug 17649] Address WebIDL comments from Kyle Huey and Ms2ger
- [Bug 17649] Address WebIDL comments from Kyle Huey and Ms2ger
- [Bug 17649] Address WebIDL comments from Kyle Huey and Ms2ger
- [Bug 20684] [Custom]: Unblock Mozilla's implementation of document.register
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 21064] [Custom]: Update serializing and parsing to include custom tags and type extensions.
- [Bug 17649] Address WebIDL comments from Kyle Huey and Ms2ger
- [Bug 17649] Address WebIDL comments from Kyle Huey and Ms2ger
- [Bug 19450] [IndexedDB] Key path segments should permit reserved words
- [Bug 16653] IndexedDB: Define overloads for IDBDatabase.transaction()
- [Bug 20394] [IndexedDB] Spec should use WebIDL concepts such as sequence<T> rather than Array
- [Bug 20582] Definitions of "valid key" and key comparison are underdefined and not compatible with WebIDL
- [Bug 17649] Address WebIDL comments from Kyle Huey and Ms2ger
- [Bug 17649] Address WebIDL comments from Kyle Huey and Ms2ger
- [Bug 17649] Address WebIDL comments from Kyle Huey and Ms2ger
- [Bug 20260] [Shadow]: ShadowRoot should have shadowRoot attribute to get older shadow tree.
- [Bug 17649] Address WebIDL comments from Kyle Huey and Ms2ger
- [Bug 17649] Address WebIDL comments from Kyle Huey and Ms2ger