Friday, 31 May 2013
- [Bug 22228] Clarification of timeout attribute late overrides
- [Bug 22228] Clarification of timeout attribute late overrides
- [Bug 22228] New: Clarification of timeout attribute late overrides
- [Bug 15145] [Explainer]: Integrate samples into the explainer
- [Bug 14949] [Meta]: Component Model needs an Explainer document
- [Bug 19911] [Explainer]: Mention Custom Pseudo-Elements in Explainer
- [Bug 14949] [Meta]: Component Model needs an Explainer document
- [Bug 19911] [Explainer]: Mention Custom Pseudo-Elements in Explainer
- [Bug 15145] [Explainer]: Integrate samples into the explainer
- [Bug 22203] [Shadow]: Define relationships between trees using terms of {child, parent, descendant, ancestor}.
- [Bug 22203] [Shadow]: Define relationships between trees using terms of {child, parent, descendant, ancestor}.
- [Bug 22203] [Shadow]: It would be nice to have a general term which can specify either a document tree or a shadow tree.
- [Bug 21066] Provide an event path API
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 22224] New: [Shadow]: Typo: distrubted => distributed
- [Bug 20746] [Shadow]: Touch.target should be retargeted
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 20746] [Shadow]: Touch.target should be retargeted
Thursday, 30 May 2013
- [Bug 21833] Under read* chaining during load event loadends should be suppressed
- [Bug 18720] [Custom]: Specify imperative API for custom DOM elements
- [Bug 21958] [Custom]: Should element registration be associated with a browsing context, not document?
- [Bug 18720] [Custom]: Specify imperative API for custom DOM elements
- [Bug 21200] [Custom]: Case sensitivity of custom element names?
- [Bug 21958] [Custom]: Should element registration be associated with a browsing context, not document?
- [Bug 18720] [Custom]: Specify imperative API for custom DOM elements
- [Bug 21886] [Custom]: Define or link to what it means for a local name to be associated with an interface
- [Bug 22203] [Shadow]: It would be nice to have a general term which can specify either a document tree or a shadow tree.
- [Bug 19911] [Explainer]: Mention Custom Pseudo-Elements in Explainer
- [Bug 14949] [Meta]: Component Model needs an Explainer document
- [Bug 19997] [Explainer]: Update examples with spec changes (:host -> @host, remove <style scoped>)
- [Bug 14949] [Meta]: Component Model needs an Explainer document
- [Bug 19912] [Explainer]: Appendices A and B. interfaces out of sync
- [Bug 14949] [Meta]: Component Model needs an Explainer document
- [Bug 22199] [Explainer]: Zap the link to samples, since the samples had grown stale
- [Bug 14949] [Meta]: Component Model needs an Explainer document
- [Bug 20613] [Explainer]: Remove ShadowRoot constructor
- [Bug 15145] [Explainer]: Integrate samples into the explainer
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 22203] New: [Shadow]: It would be nice to have a general term which can specify either a document tree or a shadow tree.
- [Bug 15145] [Explainer]: Integrate samples into the explainer
- [Bug 21986] Element.attributes needs to have a named getter
- [Bug 14949] [Meta]: Component Model needs an Explainer document
- [Bug 21354] [Explainer]: Web Components explainer actually explaining Custom Elements spec
- [Bug 14949] [Meta]: Component Model needs an Explainer document
- [Bug 22200] [Explainer]: Are custom elements still called components?
- [Bug 21886] [Custom]: Define or link to what it means for a local name to be associated with an interface
Wednesday, 29 May 2013
- [Bug 21886] [Custom]: Define or link to what it means for a local name to be associated with an interface
- [Bug 21886] [Custom]: Define or link to what it means for a local name to be associated with an interface
- [Bug 18720] [Custom]: Specify imperative API for custom DOM elements
- [Bug 22055] [Custom]: It is weird to throw InvalidCharacterError for names like annotation-xml which don't contain invalid characters
- [Bug 22192] [Custom]: Perhaps element's last completion value should not be from an exceptional termination?
- [Bug 18719] [Custom]: Specify declarative syntax for defining custom DOM elements
- [Bug 18719] [Custom]: Specify declarative syntax for defining custom DOM elements
- [Bug 22077] [Custom]: How to process "constructor name" of element declaration?
- [Bug 18511] [Custom]: Things to Consider in the Future
- [Bug 20482] [Custom]: specify default <element extends>
- [Bug 18511] [Custom]: Things to Consider in the Future
- [Bug 19763] [Custom]: Consider copying event listeners when upgrading elements
- [Bug 20189] [Custom]: Provide an event that signals when all custom elements in static source are ready/upgraded
- [Bug 18511] [Custom]: Things to Consider in the Future
- [Bug 18721] [Custom]: Specify an event that fires when all known declarations loaded
- [Bug 18511] [Custom]: Things to Consider in the Future
- [Bug 18596] [Custom]: Use a "has a" relationship instead of "is a" for custom types
- [Bug 16152] [Custom Elements]: Consider replacing some (all?) lifecycle callbacks with mutation observers
- [Bug 18511] [Custom]: Things to Consider in the Future
- [Bug 15157] [Custom Elements]: Add an example testing an element for the right prototype
- [Bug 18511] [Custom]: Things to Consider in the Future
- [Bug 19870] [Components]: Ensure component resources are loaded relative to location of component definition
- [Bug 21407] [Custom]: Loading resources is inconvenient
- [Bug 19870] [Components]: Ensure component resources are loaded relative to location of component definition
- [Bug 19870] [Components]: Ensure component resources are loaded relative to location of component definition
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 22201] New: [Shadow]: <shadow> should be used in an example
- [Bug 18719] [Custom]: Specify declarative syntax for defining custom DOM elements
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 22192] [Custom]: Perhaps element's last completion value should not be from an exceptional termination?
- [Bug 14949] [Meta]: Component Model needs an Explainer document
- [Bug 22200] New: [Explainer]: Are custom elements still called components?
- [Bug 14949] [Meta]: Component Model needs an Explainer document
- [Bug 22199] New: [Explainer]: Zap the link to samples, since the samples had grown stale
- [Bug 14949] [Meta]: Component Model needs an Explainer document
- [Bug 16873] [Explainer]: Template inertness is not described sufficiently
- [Bug 16811] [Explainer]: document.createElement seems to create a custom element
- [Bug 14949] [Meta]: Component Model needs an Explainer document
- [Bug 22018] Consider adding getCompositionAlternatives() in InputMethodContext
- [Bug 14949] [Meta]: Component Model needs an Explainer document
- [Bug 21258] [Explainer]: this spec seems extremely dev-oriented, rather than HTML-writing-people oriented
- [Bug 22196] New: Clarification of InputMethodContext behavior when an element losts focus.
- [Bug 22194] New: Clarificaiton of 'enabled' property behavior
- [Bug 22192] New: [Custom]: Perhaps element's last completion value should not be from an exceptional termination?
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 22126] [Custom]: Should <element> support declaring SVG elements?
- [Bug 21993] Change .getInputContext() to .inputMethodContext
- [Bug 21022] [Explainer]: Typo
- [Bug 14949] [Meta]: Component Model needs an Explainer document
- [Bug 19289] [Explainer]: Typo
- [Bug 15425] [Explainer]: Poem example should not use markup to describe rendered output
- [Bug 15150] [Explainer]: Rendered markup in poem example does not have the classname
- [Bug 18453] [Explainer]: Typo
- [Bug 14949] [Meta]: Component Model needs an Explainer document
- [Bug 21992] Consider adding getInputContext() to SVGElement
- [Bug 14949] [Meta]: Component Model needs an Explainer document
- [Bug 15536] [Explainer]: Clarify more how isolation will work
- [Bug 19870] [Components]: Ensure component resources are loaded relative to location of component definition
Tuesday, 28 May 2013
- [Bug 22094] Add 'target' in InputMethodContext
- [Bug 22093] Consider adding candidatewindowshow/update/hide events and getCandidateWindowClientRect()
- [Bug 22057] Clarify InputMethodContext's scope in the spec
- [Bug 22028] Consider adding hasComposition() in InputMethodContext
- [Bug 22018] Consider adding getCompositionAlternatives() in InputMethodContext
- [Bug 21993] Change .getInputContext() to .inputMethodContext
- [Bug 21992] Consider adding getInputContext() to SVGElement
- [Bug 18719] [Custom]: Specify declarative syntax for defining custom DOM elements
- [Bug 22079] [Custom]: How to transfer callbacks when declarations are being processed by parser?
- [Bug 20683] [Imports]: Write HTML Imports spec
- [Bug 19870] [Components]: Ensure component resources are loaded relative to location of component definition
- [Bug 20683] [Imports]: Write HTML Imports spec
- [Bug 22168] An attribute cannot be a dictionary type
- [Bug 15536] [Explainer]: Clarify more how isolation will work
- [Bug 22168] An attribute cannot be a dictionary type
- [Bug 15181] Override of non-recognised media type appears unsupported in xml-stylesheet processing
- [Bug 14203] JavaScript API to access unsupported CSS properties
- [Bug 15536] [Explainer]: Clarify more how isolation will work
- [Bug 21959] [Shadow]: @host rules should be overridden by selectors in document
- [Bug 21959] [Shadow]: @host rules should be overridden by selectors in document
- [Bug 14949] [Meta]: Component Model needs an Explainer document
- [Bug 19092] [Explainer]: Typo "inherifance"
- [Bug 21022] [Explainer]: Typo
- [Bug 14949] [Meta]: Component Model needs an Explainer document
- [Bug 19657] [Explainer]: Typo "reset-style-inherifance"
- [Bug 14949] [Meta]: Component Model needs an Explainer document
- [Bug 19909] [Explainer]: Typos in 7 November 2012 draft
- [Bug 20294] [Explainer]: Misleading claim around CSS resets
- [Bug 14949] [Meta]: Component Model needs an Explainer document
Monday, 27 May 2013
- [Bug 14949] [Meta]: Component Model needs an Explainer document
- [Bug 21022] [Explainer]: Typo
- [Bug 21067] [Shadow]: Provide an api to insertionParent
- [Bug 22174] [Shadow]: reprojection context node is not defined in the parent calculation algorithm.
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 21591] String constant on NavigatorID is invalid per WebIDL
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 22174] New: [Shadow]: reprojection context node is not defined in the parent calculation algorithm.
- [Bug 22169] New: [Shadow]: Nit: Update StyleSheetList definition link
- [Bug 14978] [Meta]: Specify how shadow DOM works
Sunday, 26 May 2013
- [Bug 22168] An attribute cannot be a dictionary type
- [Bug 22168] New: An attribute cannot be a dictionary type
Friday, 24 May 2013
- [Bug 21589] SelectionMode enum should not have a trailing comma
- [Bug 21589] SelectionMode enum should not have a trailing comma
- [Bug 21589] SelectionMode enum should not have a trailing comma
- [Bug 17508] Let enum lists end with a comma
- [Bug 22156] Allow trailing commas in Web IDL lists
- [Bug 21589] SelectionMode enum should not have a trailing comma
- [Bug 22156] New: Allow trailing commas in Web IDL lists
- [Bug 19778] Wrong regex for integer
- [Bug 19778] Wrong regex for integer
Thursday, 23 May 2013
- [Bug 22080] [Shadow]: Node should expose there scope so that shared state can be scoped to components.
- [Bug 22153] New: DOMError name
- [Bug 21066] Provide an event path API
- [Bug 19831] Investigate overrideMimeType()
- [Bug 21066] Provide an event path API
- [Bug 21067] [Shadow]: Provide an api to insertionParent
Wednesday, 22 May 2013
- [Bug 22055] [Custom]: It is weird to throw InvalidCharacterError for names like annotation-xml which don't contain invalid characters
- [Bug 22145] [Shadow]: Grammatically incorrect sentence in "::distributed() pseudo-element" section
- [Bug 21958] [Custom]: Should element registration be associated with a browsing context, not document?
- [Bug 21886] [Custom]: Define or link to what it means for a local name to be associated with an interface
- [Bug 21886] [Custom]: Define or link to what it means for a local name to be associated with an interface
- [Bug 21886] [Custom]: Define or link to what it means for a local name to be associated with an interface
- [Bug 22145] [Shadow]: Grammatically incorrect sentence in "::distributed() pseudo-element" section
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 22079] [Custom]: How to transfer callbacks when declarations are being processed by parser?
- [Bug 18720] [Custom]: Specify imperative API for custom DOM elements
- [Bug 21962] [Custom]: Running lifecycle callbacks should be integrated with microtask processing
- [Bug 21962] [Custom]: Running lifecycle callbacks should be integrated with microtask processing
- [Bug 22145] [Shadow]: Grammatically incorrect sentence in "::distributed() pseudo-element" section
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 22145] New: [Shadow]: Grammatically incorrect sentence in "::distributed() pseudo-element" section
- [Bug 21962] [Custom]: Running lifecycle callbacks should be integrated with microtask processing
- [Bug 21958] [Custom]: Should element registration be associated with a browsing context, not document?
- [Bug 21958] [Custom]: Should element registration be associated with a browsing context, not document?
- [Bug 22055] [Custom]: It is weird to throw InvalidCharacterError for names like annotation-xml which don't contain invalid characters
- [Bug 18720] [Custom]: Specify imperative API for custom DOM elements
- [Bug 22054] [Custom]: A couple of comments on document.register
- [Bug 20189] [Custom]: Provide an event that signals when all custom elements in static source are ready/upgraded
- [Bug 18720] [Custom]: Specify imperative API for custom DOM elements
- [Bug 21956] [Custom]: Add a note about garbage-collection
- [Bug 21886] [Custom]: Define or link to what it means for a local name to be associated with an interface
- [Bug 21886] [Custom]: Define or link to what it means for a local name to be associated with an interface
- [Bug 20189] [Custom]: Provide an event that signals when all custom elements in static source are ready/upgraded
- [Bug 20189] [Custom]: Provide an event that signals when all custom elements in static source are ready/upgraded
- [Bug 22142] New: [imports]: typos: "a import"
- [Bug 20683] [Imports]: Specify how Custom Elements are included as external resources
- [Bug 22141] New: [Shadow]: Need mechanism to tell if an element in a ShadowRoot has been inserted into the Document
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 21067] [Shadow]: Provide an api to insertionParent
- [Bug 20683] [Imports]: Specify how Custom Elements are included as external resources
- [Bug 22132] New: [imports]: 6 Loading Imports: It is not clear how PARSER and FRAGMENT relate each otehr
- [Bug 16000] Trailers
- [Bug 21067] [Shadow]: Provide an api to insertionParent
- [Bug 20189] [Custom]: Provide an event that signals when all custom elements in static source are ready/upgraded
- [Bug 22130] Modification for IDBObjectStore's clear and delete method
- [Bug 22126] [Custom]: Should <element> support declaring SVG elements?
- [Bug 22130] New: Modification for clear and delete method
- [Bug 21886] [Custom]: Define or link to what it means for a local name to be associated with an interface
Tuesday, 21 May 2013
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 22128] New: [Shadow]: Define what "inserted into document" means for elements in shadow tree
- [Bug 18720] [Custom]: Specify imperative API for custom DOM elements
- [Bug 21952] [Custom]: Being "In document" definition does not include shadow trees.
- [Bug 21888] [Custom]: #dfn-custom-element-definition should be defined, and maybe registering a type extension of a custom tag should become an error?
- [Bug 18720] [Custom]: Specify imperative API for custom DOM elements
- [Bug 18720] [Custom]: Specify imperative API for custom DOM elements
- [Bug 21887] [Custom]: Add a note about using TYPE and NAMESPACE to identify definitions despite NAMESPACE being redundant
- [Bug 21886] [Custom]: Define or link to what it means for a local name to be associated with an interface
- [Bug 21825] [Custom]: Specify or comment on node adoption--does element initialization happen?
- [Bug 20488] [Custom]: Need to define what happens when nodes are adopted into or out of documents that have custom element definitions
- [Bug 20189] [Custom]: Provide an event that signals when all custom elements in static source are ready/upgraded
- [Bug 18719] [Custom]: Specify declarative syntax for defining custom DOM elements
- [Bug 22126] New: [Custom]: Should <element> support declaring SVG elements?
- [Bug 18914] [Custom]: Provide exact description of when declaration is processed
- [Bug 18719] [Custom]: Specify declarative syntax for defining custom DOM elements
- [Bug 14207] ElementCSSInlineStyle needs binding to Element
- [Bug 16000] Trailers
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 22108] New: [Shadow]: Some editorial issues
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 22107] New: [Shadow]: <content> usage in a place where non-flow content is expected
- [Bug 15200] HTMLCollection string methods should return multiple matches
- [Bug 20660] DOMTokenList list of tokens isn't properly initialised
- [Bug 22080] [Shadow]: Node should expose there scope so that shared state can be scoped to components.
Monday, 20 May 2013
- [Bug 22094] Add 'target' in InputMethodContext
- [Bug 18511] [Custom]: Things to Consider in the Future
- [Bug 15552] [Custom Elements]: Consider adding in-tree/out-of-tree callbacks to custom elements
- [Bug 22094] Add 'target' in InputMethodContext
- [Bug 22080] [Shadow]: Node should expose there scope so that shared state can be scoped to components.
- [Bug 22080] [Shadow]: Node should expose there scope so that shared state can be scoped to components.
- [Bug 21390] [Shadow]: add support for styling shadowDOM contents based on host element
- [Bug 22094] Add 'target' in InputMethodContext
- [Bug 22093] Consider adding candidatewindowshow/update/hide events and getCandidateWindowClientRect()
- [Bug 21390] [Shadow]: add support for styling shadowDOM contents based on host element
- [Bug 22051] DOMTokenList clarifications
- [Bug 22051] DOMTokenList clarifications
- [Bug 21067] [Shadow]: Provide an api to insertionParent
- [Bug 22094] Add 'target' in InputMethodContext
- [Bug 22094] New: Add 'target' in InputMethodContext
- [Bug 22093] Consider adding candidatewindowshow/update/hide events and getCandidateWindowClientRect()
- [Bug 22093] Consider adding candidatewindowshow/update/hide events and getCandidateWindowClientRect()
- [Bug 22093] New: Consider adding candidatewindowshow/update/hide events and getCandidateWindowClientRect()
- [Bug 22051] DOMTokenList clarifications
Saturday, 18 May 2013
- [Bug 22084] New: Consistent key names in D3E spec
- [Bug 22083] New: Break D3E Key Value table into smaller chunks of related keys
- [Bug 22082] New: Review and cleanup examples in D3E spec
- [Bug 22081] Needs to be clearer definition of "Spacebar" whether it should be used when non-ASCII space (U+20) is inputted or physical space key is pressed
- [Bug 22081] Needs to be clearer definition of "Spacebar" whether it should be used when non-ASCII space (U+20) is inputted or physical space key is pressed
- [Bug 22071] Remove 'char' from KeyboardEvent in DOM3
- [Bug 18867] Web developers cannot know whether a key event will cause text input actually
- [Bug 22073] 'Meta' key is the same as the 'OS' or 'Win' key
- [Bug 22072] "current click count" deserves its own attribute
- [Bug 21067] [Shadow]: Provide an api to insertionParent
- [Bug 22070] Add input/beforeinput events to D3E [was "Revive textInput"]
- [Bug 18867] Web developers cannot know whether a key event will cause text input actually
- [Bug 21834] Dead keys--should they just use the composition event model?
- [Bug 21981] Key name definition about "foo[0-9]+"
- [Bug 22070] Add input/beforeinput events to D3E [was "Revive textInput"]
- [Bug 22073] 'Meta' key is the same as the 'OS' or 'Win' key
- [Bug 22070] Add input/beforeinput events to D3E [was "Revive textInput"]
- [Bug 22070] Add input/beforeinput events to D3E [was "Revive textInput"]
- [Bug 22070] Add input/beforeinput events to D3E [was "Revive textInput"]
- [Bug 22073] 'Meta' key is the same as the 'OS' or 'Win' key
- [Bug 17625] Shouldn't ExSel key value be Exsel?
- [Bug 22073] 'Meta' key is the same as the 'OS' or 'Win' key
- [Bug 22081] Needs to be clearer definition of "Spacebar" whether it should be used when non-ASCII space (U+20) is inputted or physical space key is pressed
- [Bug 22081] New: Needs to be clear whether "Spacebar" key value should be used when non-ASCII space (U+20) is inputted
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 22080] New: [Shadow]: Node should expose there scope so that shared state can be scoped to components.
- [Bug 17625] Shouldn't ExSel key value be Exsel?
Friday, 17 May 2013
- [Bug 22070] Add input/beforeinput events to D3E [was "Revive textInput"]
- [Bug 22071] Remove 'char' from KeyboardEvent in DOM3
- [Bug 22069] Names for media keys should be organized
- [Bug 22070] Add input/beforeinput events to D3E [was "Revive textInput"]
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 22078] [Custom]:
- [Bug 18719] [Custom]: Specify declarative syntax for defining custom DOM elements
- [Bug 22079] New: [Custom]: How to transfer callbacks when declarations are being processed by parser?
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 22078] New: [Custom]:
- [Bug 22073] 'Meta' key is the same as the 'OS' or 'Win' key
- [Bug 21390] [Shadow]: add support for styling shadowDOM contents based on host element
- [Bug 18719] [Custom]: Specify declarative syntax for defining custom DOM elements
- [Bug 22077] New: [Custom]: How to process "constructor name" of element declaration?
- [Bug 18914] [Custom]: Provide exact description of when declaration is processed
- [Bug 18723] [Custom]: Specify handling element re-definition
- [Bug 18719] [Custom]: Specify declarative syntax for defining custom DOM elements
- [Bug 18723] [Custom]: Specify handling element re-definition
- [Bug 18719] [Custom]: Specify declarative syntax for defining custom DOM elements
- [Bug 18722] [Custom]: Specify invalid definition state
- [Bug 18719] [Custom]: Specify declarative syntax for defining custom DOM elements
- [Bug 18718] [Custom]: Specify how a declaration turns into a definition
- [Bug 17113] [Custom]: What happens when you remove or change contents of <element>?
- [Bug 18719] [Custom]: Specify declarative syntax for defining custom DOM elements
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 22056] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters?
- [Bug 18720] [Custom]: Specify imperative API for custom DOM elements
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 22055] [Custom]: It is weird to throw InvalidCharacterError for names like annotation-xml which don't contain invalid characters
- [Bug 18720] [Custom]: Specify imperative API for custom DOM elements
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 22054] [Custom]: A couple of comments on document.register
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18720] [Custom]: Specify imperative API for custom DOM elements
- [Bug 21969] [Custom]: add attributeChangedCallback to the set of prototype callbacks
- [Bug 21886] [Custom]: Define or link to what it means for a local name to be associated with an interface
- [Bug 22070] Add input/beforeinput events to D3E [was "Revive textInput"]
- [Bug 22070] Add input/beforeinput events to D3E [was "Revive textInput"]
- [Bug 21830] KeyboardEvent.locale is too general.
- [Bug 22070] Add input/beforeinput events to D3E [was "Revive textInput"]
- [Bug 22070] Add input/beforeinput events to D3E [was "Revive textInput"]
- [Bug 22072] "current click count" deserves its own attribute
- [Bug 22070] Revive textInput in DOM3
- [Bug 22069] Names for media keys should be organized
- [Bug 22070] Revive textInput in DOM3
- [Bug 21067] [Shadow]: Provide an api to insertionParent
- [Bug 22070] Revive textInput in DOM3
- [Bug 22070] Revive textInput in DOM3
- [Bug 21067] [Shadow]: Provide an api to insertionParent
- [Bug 22071] Remove 'char' from KeyboardEvent in DOM3
- [Bug 19771] Need way to determine what keys are supported on device.
- [Bug 21067] [Shadow]: Provide an api to insertionParent
- [Bug 22073] New: 'Meta' key is the same as the 'OS' or 'Win' key
- [Bug 22072] "current click count" deserves its own attribute
- [Bug 22072] New: "current click count" deserves its own attribute
- [Bug 22070] Revive textInput in DOM3
- [Bug 22071] Remove 'char' from KeyboardEvent in DOM3
- [Bug 22071] New: Remove 'char' from KeyboardEvent in DOM3
- [Bug 22070] New: Revive textInput in DOM3
- [Bug 22069] New: Names for media keys should be organized
- [Bug 22068] [DOM3] Remove Appendix A and replace with references to UI Events spec
- [Bug 22068] New: Remove Appendix A and replace with references to UI Events spec
- [Bug 17625] Shouldn't ExSel key value be Exsel?
- [Bug 21067] [Shadow]: Provide an api to insertionParent
- [Bug 21886] [Custom]: Define or link to what it means for a local name to be associated with an interface
Thursday, 16 May 2013
- [Bug 21886] [Custom]: Define or link to what it means for a local name to be associated with an interface
- [Bug 21275] [Imports]: Force utf-8
- [Bug 16000] Trailers
- [Bug 16000] Trailers
- [Bug 16000] Trailers
- [Bug 16000] Trailers
- [Bug 16000] Trailers
- [Bug 15418] sort out HTTP auth
- [Bug 16000] Trailers
- [Bug 15417] Redirects and the base URL
- [Bug 16304] DONE != DONE
- [Bug 15417] Redirects and the base URL
- [Bug 22058] "error" event should fire before final readystatechange event
- [Bug 16304] DONE != DONE
- [Bug 22058] "error" event should fire before final readystatechange event
- [Bug 22059] Composition dictionary should be changed
- [Bug 22059] New: Composition dictionary should be changed
- [Bug 22058] New: "error" event should fire before final readystatechange event
- [Bug 22057] Clarify InputMethodContext's scope in the spec
- [Bug 15417] Redirects and the base URL
- [Bug 22057] New: Clarify InputMethodContext's scope in the spec
- [Bug 22056] New: [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters?
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 22055] New: [Custom]: It is weird to throw InvalidCharacterError for names like annotation-xml which don't contain invalid characters
- [Bug 22054] [Custom]: A couple of comments on document.register
Wednesday, 15 May 2013
- [Bug 22054] New: [Custom]: A couple of comments on document.register
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 16595] Ability to get non-sequential records from various operations
- [Bug 21490] [Custom]: Some attributes of HTMLElementElement should be read-only
- [Bug 21490] [Custom]: Some attributes of HTMLElementElement should be read-only
- [Bug 18719] [Custom]: Specify declarative syntax for defining custom DOM elements
- [Bug 21490] [Custom]: Some attributes of HTMLElementElement should be read-only
- [Bug 22051] New: DOMTokenList clarifications
- [Bug 21391] [Shadow]: allow @host rules to match nodes in the host scope not just the host node
- [Bug 21391] [Shadow]: allow @host rules to match nodes in the host scope not just the host node
- [Bug 20683] [Imports]: Specify how Custom Elements are included as external resources
- [Bug 22038] New: [imports]: Dynamic update on <link> attribute should be considered
- [Bug 21390] [Shadow]: add support for styling shadowDOM contents based on host element
Tuesday, 14 May 2013
- [Bug 21275] [Imports]: Force utf-8
- [Bug 20683] [Imports]: Specify how Custom Elements are included as external resources
- [Bug 21225] [Imports]: Component interface is not necessary
- [Bug 20683] [Imports]: Specify how Custom Elements are included as external resources
- [Bug 21255] [Imports]: Components should load as DocumentFragments
- [Bug 21391] [Shadow]: allow @host rules to match nodes in the host scope not just the host node
- [Bug 19684] [Shadow]: shadow reference combinator should be css function.
- [Bug 15480] [Shadow]: Things to Consider in the Future
- [Bug 11329] Browsers must generate resize event during a zoom.
- [Bug 22018] Consider adding getCompositionAlternatives() in InputMethodContext
- [Bug 22028] Consider adding hasComposition() in InputMethodContext
- [Bug 22028] New: Consider adding hasComposition() in InputMethodContext
- [Bug 21066] Provide an event path API
Monday, 13 May 2013
- [Bug 22018] Consider adding getCompositionAlternatives() in InputMethodContext
- [Bug 22018] Consider adding getCompositionAlternatives() in InputMethodContext
- [Bug 22018] New: Consider adding getCompositionAlternatives() in InputMethodContext
Sunday, 12 May 2013
- [Bug 22014] New: newly created exception objects should have the exception prototype interface object as their [[Prototype]]
- [Bug 22014] newly created exception objects should have the exception prototype interface object as their [[Prototype]]
- [Bug 22013] property enumeration section should mention named property visibility
- [Bug 22013] New: property enumeration section should mention named property visibility
Saturday, 11 May 2013
- [Bug 22006] need to define that the .length of a stringifier's Function object is 0
- [Bug 22006] New: need to define that the .length of a stringifier's Function object is 0
Friday, 10 May 2013
- [Bug 21993] Change .getInputContext() to .inputMethodContext
- [Bug 21992] Consider adding getInputContext() to SVGElement
- [Bug 21993] New: Change .getInputContext() to .inputMethodContext
- [Bug 21992] New: Consider adding getInputContext() to SVGElement
- [Bug 21924] [Shadow]: Remove pseudo-classes/elements from selector fragments
Thursday, 9 May 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 18428] [Shadow]: Next Working Draft Iteration
- [Bug 20982] [Shadow]: Event retargeting algorithm optimization/clarification
- [Bug 21924] [Shadow]: Remove pseudo-classes/elements from selector fragments
- [Bug 20600] [Shadow]: Custom Pseudo-Elements should follow the same convention as custom element names.
- [Bug 21986] New: Element.attributes needs to have a named getter
- [Bug 21555] Use of IDL arrays for keyPath values is underdefined
- [Bug 21981] New: Key name definition about "foo[0-9]+"
- [Bug 21966] D3E spec should prohibit browser vendors name original key name
- [Bug 20600] [Shadow]: Custom Pseudo-Elements should follow the same convention as custom element names.
Wednesday, 8 May 2013
- [Bug 21225] [Imports]: Component interface is not necessary
- [Bug 21976] [imports]: Preventing DOM hierarchy cycles
- [Bug 21225] [Imports]: Component interface is not necessary
- [Bug 20683] [Imports]: Specify how Custom Elements are included as external resources
- [Bug 21979] [imports]: Node -> Element
- [Bug 21225] [Imports]: Component interface is not necessary
- [Bug 21924] [Shadow]: Remove pseudo-classes/elements from selector fragments
- [Bug 20683] [Imports]: Specify how Custom Elements are included as external resources
- [Bug 21979] New: [imports]: Node -> Element
- [Bug 21924] [Shadow]: Remove pseudo-classes/elements from selector fragments
- [Bug 21976] New: [imports]: Preventing DOM hierarchy cycles
- [Bug 20683] [Imports]: Specify how Custom Elements are included as external resources
- [Bug 21924] [Shadow]: Remove pseudo-classes/elements from selector fragments
- [Bug 21924] [Shadow]: Remove pseudo-classes/elements from selector fragments
- [Bug 21969] [Custom]: add attributeChangedCallback to the set of prototype callbacks
- [Bug 21962] [Custom]: Running lifecycle callbacks should be integrated with microtask processing
- [Bug 21422] Futures
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 21201] [Shadow]: The spec should not mention select reference combinators when it means ::distributed
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 21269] [Shadow]: Should Non-bubbling events in ShadowRoot children trigger listeners on Host?
- [Bug 20247] [Shadow]: Update constraints around stopping events
- [Bug 20247] [Shadow]: Update constraints around stopping events
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 20247] [Shadow]: Update constraints around stopping events
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 21366] [Shadow]: "Assigned" term should be explained and linkified
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 21242] [Shadow]: 6.3 @host @-rule should extend the CSS 2.1 grammar 'stylesheet' production
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 21959] [Shadow]: @host rules should be overridden by selectors in document
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 21486] [Shadow]: ::distributed should support scope-relative selectors.
- [Bug 21067] [Shadow]: Provide an api to insertionParent
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 21390] [Shadow]: add support for styling shadowDOM contents based on host element
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 21391] [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 18428] [Shadow]: Next Working Draft Iteration
- [Bug 21390] [Shadow]: add support for styling shadowDOM contents based on host element
- [Bug 21067] [Shadow]: Provide an api to insertionParent
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 20139] [Shadow]: Scoping constraints should be informative
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 21924] [Shadow]: Remove pseudo-classes/elements from selector fragments
- [Bug 21969] [Custom]: add attributeChangedCallback to the set of prototype callbacks
- [Bug 21923] [Shadow]: Remove addStylesheet/removeStylesheet APIs
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 21923] [Shadow]: Remove addStylesheet/removeStylesheet APIs
- [Bug 21969] [Custom]: add attributeChangedCallback to the set of prototype callbacks
- [Bug 21969] [Custom]: add attributeChangedCallback to the set of prototype callbacks
- [Bug 21969] [Custom]: add attributeChangedCallback to the set of prototype callbacks
- [Bug 21969] [Custom]: add attributeChangedCallback to the set of prototype callbacks
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 21969] New: [Custom]: add attributeChangedCallback to the set of prototype callbacks
- [Bug 18720] [Custom]: Specify imperative API for custom DOM elements
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 21962] [Custom]: Running lifecycle callbacks should be integrated with microtask processing
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 21962] [Custom]: Running lifecycle callbacks should be integrated with microtask processing
- [Bug 18511] [Custom]: Things to Consider in the Future
- [Bug 21660] [Custom]: Specify "insertedCallback" and "removedCallback"
- [Bug 20438] [Custom]: consider adding "inserted" and "removed" lifecycle methods
- [Bug 21945] Does responseXML ever return an XMLDocument
- [Bug 11328] Canvas authors needs to be able to assess pixel resolution to rescale canvas elements
- [Bug 21966] New: D3E spec should prohibit browser vendors name original key name
- [Bug 21121] Define mobile phone related keys
- [Bug 21962] [Custom]: Running lifecycle callbacks should be integrated with microtask processing
- [Bug 21962] [Custom]: Running lifecycle callbacks should be integrated with microtask processing
- [Bug 21962] [Custom]: Running lifecycle callbacks should be integrated with microtask processing
- [Bug 21962] [Custom]: Running lifecycle callbacks should be integrated with microtask processing
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 21962] New: [Custom]: Running lifecycle callbacks should be integrated with microtask processing
- [Bug 21945] Does responseXML ever return an XMLDocument
- [Bug 21886] [Custom]: Define or link to what it means for a local name to be associated with an interface
- [Bug 21958] [Custom]: Should element registration be associated with a browsing context, not document?
- [Bug 21956] [Custom]: Add a note about garbage-collection
- [Bug 21888] [Custom]: #dfn-custom-element-definition should be defined, and maybe registering a type extension of a custom tag should become an error?
Tuesday, 7 May 2013
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 20693] [Shadow]: Incorrect specification for ShadowRoot.olderShadowRoot attribute
- [Bug 20693] [Shadow]: Incorrect specification for ShadowRoot.olderShadowRoot attribute
- [Bug 20693] [Shadow]: Incorrect specification for ShadowRoot.olderShadowRoot attribute
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 20303] [Shadow]: ShadowAware
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 20839] [Shadow]: Typo, "shadow" needs to be capitalized in the first sentence of Navigation section
- [Bug 20600] [Shadow]: Custom Pseudo-Elements should follow the same convention as custom element names.
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 21959] [Shadow]: @host rules should be overridden by selectors in document
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 21924] [Shadow]: Remove pseudo-classes/elements from selector fragments
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 21923] [Shadow]: Remove addStylesheet/removeStylesheet APIs
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 20296] [Shadow]: Attributes should not have dashes
- [Bug 21958] [Custom]: Should element registration be associated with a browsing context, not document?
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 21959] New: [Shadow]: @host rules should be overridden by selectors in document
- [Bug 18720] [Custom]: Specify imperative API for custom DOM elements
- [Bug 21958] New: [Custom]: Should element registration be associated with a browsing context, not document?
- [Bug 21499] [Meta]: Web Developers Feedback/Hotlist
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 21404] [Shadow]: 5.5 Event Dispatch references incorrect steps of event dispatching algorithm
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 21600] [Shadow]: misspelled word, ::distrbuted should be ::distributed
- [Bug 21956] New: [Custom]: Add a note about garbage-collection
- [Bug 18720] [Custom]: Specify imperative API for custom DOM elements
- [Bug 21888] [Custom]: #dfn-custom-element-definition should be defined, and maybe registering a type extension of a custom tag should become an error?
- [Bug 21888] [Custom]: #dfn-custom-element-definition should be defined, and maybe registering a type extension of a custom tag should become an error?
- [Bug 21886] [Custom]: Define or link to what it means for a local name to be associated with an interface
- [Bug 18720] [Custom]: Specify imperative API for custom DOM elements
- [Bug 21200] [Custom]: Case sensitivity of custom element names?
- [Bug 21945] Does responseXML ever return an XMLDocument
- [Bug 21200] [Custom]: Case sensitivity of custom element names?
- [Bug 21889] [Custom]: Consider making all names/types lowercase
- [Bug 18720] [Custom]: Specify imperative API for custom DOM elements
- [Bug 18720] [Custom]: Specify imperative API for custom DOM elements
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 21952] [Custom]: Being "In document" definition does not include shadow trees.
- [Bug 18720] [Custom]: Specify imperative API for custom DOM elements
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 21889] [Custom]: Consider making all names/types lowercase
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 21888] [Custom]: #dfn-custom-element-definition should be defined, and maybe registering a type extension of a custom tag should become an error?
- [Bug 18720] [Custom]: Specify imperative API for custom DOM elements
- [Bug 18720] [Custom]: Specify imperative API for custom DOM elements
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 21887] [Custom]: Add a note about using TYPE and NAMESPACE to identify definitions despite NAMESPACE being redundant
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 18720] [Custom]: Specify imperative API for custom DOM elements
- [Bug 21886] [Custom]: Define or link to what it means for a local name to be associated with an interface
- [Bug 21952] New: [Custom]: Being "In document" definition does not include shadow trees.
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 21945] Does responseXML ever return an XMLDocument
- [Bug 21945] Does responseXML ever return an XMLDocument
- [Bug 21945] Does responseXML ever return an XMLDocument
- [Bug 21945] Does responseXML ever return an XMLDocument
- [Bug 21945] Does responseXML ever return an XMLDocument
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 21947] [Custom]: Clarify registering HTMLElement.prototype as a prototype multiple times
- [Bug 21947] [Custom]: Clarify registering HTMLElement.prototype as a prototype multiple times
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 21947] New: [Custom]: Clarify registering HTMLElement.prototype as a prototype multiple times
Monday, 6 May 2013
- [Bug 21945] Does responseXML ever return an XMLDocument
- [Bug 21945] Does responseXML ever return an XMLDocument
- [Bug 21945] Does responseXML ever return an XMLDocument
- [Bug 21945] Does responseXML ever return an XMLDocument
- [Bug 21945] Does responseXML ever return an XMLDocument
- [Bug 21945] New: Does responseXML ever return an XMLDocument
- [Bug 15418] sort out HTTP auth
- [Bug 15418] sort out HTTP auth
Sunday, 5 May 2013
Friday, 3 May 2013
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 21924] New: [Shadow]: Remove pseudo-classes/elements from selector fragments
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 21923] New: [Shadow]: Remove addStylesheet/removeStylesheet APIs
- [Bug 15418] sort out HTTP auth
Thursday, 2 May 2013
- [Bug 21914] bug-assist should include a URL in the bug description
- [Bug 15013] [Meta] Provide simple bug-filing facilities for the deliverables.
- [Bug 21916] bug-assist should use data-* attributes instead of <meta name>
- [Bug 21916] New: bug-assist should use data-* attributes instead of <meta name>
- [Bug 15013] [Meta] Provide simple bug-filing facilities for the deliverables.
- [Bug 21915] bug-assist should set z-index
- [Bug 21915] New: bug-assist should set z-index
- [Bug 15013] [Meta] Provide simple bug-filing facilities for the deliverables.
- [Bug 21914] bug-assist should include a URL in the bug description
- [Bug 21914] New: bug-assist should include a URL in the bug description
- [Bug 15013] [Meta] Provide simple bug-filing facilities for the deliverables.
- [Bug 21913] bug-assist doesn't support selection in Opera (Presto)
- [Bug 21913] New: bug-assist doesn't support selection in Opera (Presto)
- [Bug 15418] sort out HTTP auth
- [Bug 15418] sort out HTTP auth
- [Bug 21318] anon flag should be anonymous
- [Bug 21264] referrer source is wrong
Wednesday, 1 May 2013
- [Bug 21555] Use of IDL arrays for keyPath values is underdefined
- [Bug 21555] Use of IDL arrays for keyPath values is underdefined
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 21889] New: [Custom]: Consider making all names/types lowercase
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 21888] New: [Custom]: #dfn-custom-element-definition should be defined, and maybe registering a type extension of a custom tag should become an error?
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 21887] New: [Custom]: Add a note about using TYPE and NAMESPACE to identify definitions despite NAMESPACE being redundant
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 21886] New: [Custom]: Define or link to what it means for a local name to be associated with an interface