Thursday, 28 February 2013
- [Bug 17649] Address WebIDL comments from Kyle Huey and Ms2ger
- [Bug 16513] Use WebIDL enum for IDBDatabase.transaction's mode argument
- [Bug 20924] [Templates]: processing an EOF token deep within a template which was opened in <head> may fail to run after-head work
- [Bug 21149] [Shadow]: Shadow DOM-based components could benefit from a way to detect when light DOM contents change
- [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 21149] New: [Shadow]: Shadow DOM-based components could benefit from a way to detect when light DOM contents change
- [Bug 14978] [Meta]: Specify how shadow DOM works
Wednesday, 27 February 2013
- [Bug 21143] New: Define command key names for multimedia keyboard
- [Bug 21134] Define key names which launches specific application
- [Bug 21120] Define TV or A/V remote controller's keys
- [Bug 21137] Define key names for game controller of Android
- [Bug 21134] Define key names which launches specific application
- [Bug 21121] Define mobile phone related keys
- [Bug 21083] Proposal key names for Android
- [Bug 21136] Define Home key and Back key of Android smartphone
- [Bug 21120] Define TV or A/V remote controller's keys
- [Bug 21119] Define 'ZoomIn' key and 'ZoomOut' key
- [Bug 21135] Define 'Symbol' modifier
- [Bug 21083] Proposal key names for Android
- [Bug 21118] Define power management related keys like 'Power'
- [Bug 21117] Define 'Break' and 'SysReq' key names
- [Bug 21140] New: Define key names for keyboard layout change keys
- [Bug 21116] Define 'SingleCandidate' key in the key name list
- [Bug 21083] Proposal key names for Android
- [Bug 19827] map event.key to character values of a normal QUERTY (en-US) layout
- [Bug 19771] Need way to determine what keys are supported on device.
- [Bug 21114] Dead key names are not enough for Linux
- [Bug 21113] Should KeyboardEvent.char really be set control characters? E.g., Cancel, Esc, Backspace and Del
- [Bug 18931] D3E should define when compositionupdate event is fired
- [Bug 21115] Define 'Redo' key in the key name list
- [Bug 18867] Web developers cannot know whether a key event will cause text input actually
- [Bug 18851] necessary compositionupdate event isn't written in the examples in 6.2.3
- [Bug 18850] necessary compositionupdate event isn't written in the examples in 6.2.4
- [Bug 21139] New: Define key name for Hankaku-Zenkaku key and Katakana-Hiragana key
- [Bug 21083] Proposal key names for Android
- [Bug 21083] Proposal key names for Android
- [Bug 21137] Define key names for game controller of Android
- [Bug 21137] Define key names for game controller of Android
- [Bug 21134] Define key names which launches specific application
- [Bug 21083] Proposal key names for Android
- [Bug 21137] New: Define key names for game controller of Android
- [Bug 21083] Proposal key names for Android
- [Bug 21136] New: Define Home key and Back key of Android smartphone
- [Bug 21083] Proposal key names for Android
- [Bug 21083] Proposal key names for Android
- [Bug 21135] New: Define 'Symbol' modifier
- [Bug 21083] Proposal key names for Android
- [Bug 21134] New: Define key names which launches specific application
- [Bug 21120] Define TV or A/V remote controller's keys
- [Bug 21083] Proposal key names for Android
- [Bug 21121] Define mobile phone related keys
- [Bug 21119] Define 'ZoomIn' key and 'ZoomOut' key
- [Bug 21118] Define power management related keys like 'Power'
- [Bug 20684] [Custom]: Unblock Mozilla's implementation of document.register
- [Bug 21064] [Custom]: Update serializing and parsing to include custom tags and type extensions.
Tuesday, 26 February 2013
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 20684] [Custom]: Unblock Mozilla's implementation of document.register
- [Bug 20684] [Custom]: Unblock Mozilla's implementation of document.register
- [Bug 21064] [Custom]: Update serializing and parsing to include custom tags and type extensions.
- [Bug 21064] [Custom]: Update serializing and parsing to include custom tags and type extensions.
- [Bug 21063] [Custom]: Element upgrade algorithm needs to be rewritten
- [Bug 20684] [Custom]: Unblock Mozilla's implementation of document.register
- [Bug 21063] [Custom]: Element upgrade algorithm needs to be rewritten
- [Bug 21129] Custom element registration behavior with HTMLElement prototype from a different window.
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 21129] New: Custom element registration behavior with HTMLElement prototype from a different window.
- [Bug 21111] response property should return incremental data for ArrayBuffer and Blob
- [Bug 21083] Proposal key names for Android
- [Bug 21121] New: Define mobile phone related keys
- [Bug 21083] Proposal key names for Android
- [Bug 21120] New: Define TV or A/V remote controller's keys
- [Bug 21083] Proposal key names for Android
- [Bug 21119] New: Define 'ZoomIn' key and 'ZoomOut' key
- [Bug 21118] New: Define power management related keys like 'Power'
- [Bug 21117] New: Define 'Break' and 'SysReq' key names
- [Bug 21116] New: Define 'SingleCandidate' key in the key name list
- [Bug 21115] New: Define 'Redo' key in the key name list
- [Bug 21114] New: Dead key names are not enough for Linux
- [Bug 21113] New: Should KeyboardEvent.char really be set control characters? E.g., Cancel, Esc, Backspace and Del
- [Bug 21083] Proposal key names for Android
- [Bug 21083] Proposal key names for Android
- [Bug 21111] response property should return incremental data for ArrayBuffer and Blob
Monday, 25 February 2013
- [Bug 21111] response property should return incremental data for ArrayBuffer and Blob
- [Bug 21111] New: response property should return incremental data for ArrayBuffer and Blob
Saturday, 23 February 2013
Friday, 22 February 2013
- [Bug 20913] [Custom]: What does inheriting from existing HTML element really mean?
- [Bug 20684] [Custom]: Unblock Mozilla's implementation of document.register
- [Bug 20913] [Custom]: What does inheriting from existing HTML element really mean?
- [Bug 20913] [Custom]: What does inheriting from existing HTML element really mean?
- [Bug 20913] [Custom]: What does inheriting from existing HTML element really mean?
- [Bug 21066] [Shadow]: Provide an event path api
- [Bug 21066] [Shadow]: Provide an event path api
- [Bug 21066] [Shadow]: Provide an event path api
- [Bug 21078] EventInit should have default values for bubbles and cancelable
- [Bug 21066] [Shadow]: Provide an event path api
- [Bug 21078] EventInit should have default values for bubbles and cancelable
- [Bug 21083] Proposal key names for Android
- [Bug 21083] New: Proposal key names for Android
Thursday, 21 February 2013
- [Bug 20913] [Custom]: What does inheriting from existing HTML element really mean?
- [Bug 21017] [Templates]: handle white space inside templates in a way that allows templates to be more human readable
- [Bug 21078] New: EventInit should have default values for bubbles and cancelable
- [Bug 21076] Remove _-escape mechanism for identifiers
- [Bug 21076] New: Remove _-escape mechanism for identifiers
- [Bug 21066] [Shadow]: Provide an event path api
- [Bug 21073] merge [Unforgeable] and readonly into unforgeable
- [Bug 21073] merge [Unforgeable] and readonly into unforgeable
- [Bug 21073] merge [Unforgeable] and readonly into unforgeable
- [Bug 21073] merge [Unforgeable] and readonly into unforgeable
- [Bug 21073] New: merge [Unforgeable] and readonly into unforgeable
- [Bug 21069] [Unforgeable] attributes as data property
- [Bug 21069] [Unforgeable] attributes as data property
- [Bug 21069] [Unforgeable] attributes as data property
- [Bug 21069] [Unforgeable] attributes as data property
- [Bug 21069] [Unforgeable] attributes as data property
- [Bug 21069] [Unforgeable] attributes as data property
- [Bug 21069] [Unforgeable] attributes as data property
- [Bug 21069] New: [Unforgeable] attributes as data property
- [Bug 21068] event.isTrusted should be [Unforgeable]
- [Bug 21066] [Shadow]: Provide an event path api
- [Bug 21068] New: event.isTrusted should be [Unforgeable]
- [Bug 18483] [Shadow]: Shared stylesheets may make @host ambiguous
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 21067] New: [Shadow]: Provide an api to getDistributedParent
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 21066] New: [Shadow]: Provide an event path api
Wednesday, 20 February 2013
- [Bug 18540] Proposal for a new acceptNode() return value for TreeWalker.
- [Bug 20684] [Custom]: Unblock Mozilla's implementation of document.register
- [Bug 20686] [Custom]: Enumerate exact requirements for an element prototype
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 20684] [Custom]: Unblock Mozilla's implementation of document.register
- [Bug 20685] [Custom]: Provide a thorough description of the custom elements, goals, objectives, approach.
- [Bug 20913] [Custom]: What does inheriting from existing HTML element really mean?
- [Bug 20684] [Custom]: Unblock Mozilla's implementation of document.register
- [Bug 21064] New: [Custom]: Update serializing and parsing to include custom tags and type extensions.
- [Bug 20684] [Custom]: Unblock Mozilla's implementation of document.register
- [Bug 18669] Switch from is= to <tag if a decision has been reached among implementers
- [Bug 20684] [Custom]: Unblock Mozilla's implementation of document.register
- [Bug 20490] [Custom]: Things that mutate the DOM tree should queue observer records
- [Bug 21063] [Custom]: Element upgrade algorithm needs to be rewritten
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 21063] [Custom]: Element upgrade algorithm needs to be rewritten
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 20684] [Custom]: Unblock Mozilla's implementation of document.register
- [Bug 20489] [Custom]: Nothing ever defines what the "custom element name" of a random element is
- [Bug 20684] [Custom]: Unblock Mozilla's implementation of document.register
- [Bug 21063] New: [Custom]: Element upgrade algorithm needs to be rewritten
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 20831] [Custom]: Make document.register work with ES6 classes and @@create
- [Bug 20684] [Custom]: Unblock Mozilla's implementation of document.register
- [Bug 18780] Fix event dispatching for shadow DOM and <iframe seamless>
- [Bug 19470] Event firing sequence on abort() after send()
- [Bug 19470] Event firing sequence on abort() after send()
- [Bug 18780] Fix event dispatching for shadow DOM and <iframe seamless>
- [Bug 18780] Fix event dispatching for shadow DOM and <iframe seamless>
- [Bug 19470] Event firing sequence on abort() after send()
- [Bug 19470] Event firing sequence on abort() after send()
- [Bug 19470] Event firing sequence on abort() after send()
- [Bug 20833] Incomplete sentence in draft WD-IndexedDB-20120524
- [Bug 18656] objectStore.delete should raise InvalidStateError if object store is deleted
- [Bug 18558] [IndexedDB] Define error seen when key generator maximum value is reached
Tuesday, 19 February 2013
- [Bug 18502] [IndexedDB] Editorial: Wording around IDBFactory.open() with no version misleading
- [Bug 21048] Broken Links to ES6 Draft
- [Bug 20913] [Custom]: What does inheriting from existing HTML element really mean?
- [Bug 19470] Event firing sequence on abort() after send()
- [Bug 19470] Event firing sequence on abort() after send()
- [Bug 21048] New: Broken Links to ES6 Draft
- [Bug 12607] Let authors control redirect behavior
- [Bug 17046] Implement redirect audit functionality for XHR
- [Bug 19470] Event firing sequence on abort() after send()
- [Bug 19470] Event firing sequence on abort() after send()
Monday, 18 February 2013
- [Bug 19470] Event firing sequence on abort() after send()
- [Bug 20913] [Custom]: What does inheriting from existing HTML element really mean?
- [Bug 15653] [Templates]: Specify "liveness" of the elements
- [Bug 20913] [Custom]: What does inheriting from existing HTML element really mean?
Sunday, 17 February 2013
Saturday, 16 February 2013
- [Bug 16491] Add simpler and better event registration system
- [Bug 20913] [Custom]: What does inheriting from existing HTML element really mean?
- [Bug 16491] Add simpler and better event registration system
- [Bug 16491] Add simpler and better event registration system
- [Bug 16491] Add simpler and better event registration system
Friday, 15 February 2013
- [Bug 16491] Add simpler and better event registration system
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 21017] [Templates]: handle white space inside templates in a way that allows templates to be more human readable
- [Bug 21017] [Templates]: handle white space inside templates in a way that allows templates to be more human readable
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 21017] New: [Templates]: handle white space inside templates in a way that allows templates to be more human readable
- [Bug 16491] Add simpler and better event registration system
- [Bug 16491] Add simpler and better event registration system
- [Bug 20913] [Custom]: What does inheriting from existing HTML element really mean?
- [Bug 16491] Add simpler and better event registration system
Thursday, 14 February 2013
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 20686] [Custom]: Enumerate exact requirements for an element prototype
- [Bug 20801] [Custom]: Custom element generation algorithm should be careful about its argument
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 20970] [Custom]: typo
- [Bug 20913] [Custom]: What does inheriting from existing HTML element really mean?
- [Bug 20913] [Custom]: What does inheriting from existing HTML element really mean?
- [Bug 20972] Use https for "file a bug" utility
- [Bug 15013] [Meta] Provide simple bug-filing facilities for the deliverables.
- [Bug 20972] Use https for "file a bug" utility
- [Bug 15013] [Meta] Provide simple bug-filing facilities for the deliverables.
- [Bug 16491] Add simpler and better event registration system
Tuesday, 12 February 2013
- [Bug 20972] Use https for "file a bug" utility
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 20973] [Custom]: Restrict custom elements to NCName
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 20831] [Custom]: Make document.register work with ES6 classes and @@create
- [Bug 20913] [Custom]: What does inheriting from existing HTML element really mean?
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 20982] New: [Shadow]: Event retargeting algorithm optimization/clarification
- [Bug 20913] [Custom]: What does inheriting from existing HTML element really mean?
- [Bug 20971] [Custom]: Use a normal callback
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 20971] [Custom]: Use a normal callback
- [Bug 20971] [Custom]: Use a normal callback
- [Bug 20913] [Custom]: What does inheriting from existing HTML element really mean?
- [Bug 20913] [Custom]: What does inheriting from existing HTML element really mean?
- [Bug 20913] [Custom]: Meaning of prototype in document.register is underspecified
- [Bug 20913] [Custom]: Meaning of prototype in document.register is underspecified
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 20973] New: [Custom]: Restrict custom elements to NCName
- [Bug 20972] New: [Custom]: Use https for "file a bug" utility
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 20971] New: [Custom]: Use a normal callback
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 20970] New: [Custom]: typo
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 20913] [Custom]: Meaning of prototype in document.register is underspecified
- [Bug 20913] [Custom]: Meaning of prototype in document.register is underspecified
- [Bug 20913] [Custom]: Meaning of prototype in document.register is underspecified
- [Bug 20913] [Custom]: Meaning of prototype in document.register is underspecified
- [Bug 20913] [Custom]: Meaning of prototype in document.register is underspecified
- [Bug 20913] [Custom]: Meaning of prototype in document.register is underspecified
- [Bug 20924] [Templates]: processing an EOF token deep within a template which was opened in <head> may fail to run after-head work
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 20958] New: [Shadow]: Consider dropping resetStyleInheritance in favor of a CSS property
- [Bug 14978] [Meta]: Specify how shadow DOM works
- [Bug 20957] New: [Shadow]: Styling elements in shadow trees based on host element
Monday, 11 February 2013
- [Bug 16294] [Shadow]: Should ShadowRoot have style or be an Element?
- [Bug 20924] [Templates]: processing an EOF token deep within a template which was opened in <head> may fail to run after-head work
- [Bug 20913] [Custom]: Meaning of prototype in document.register is underspecified
- [Bug 20913] [Custom]: Meaning of prototype in document.register is underspecified
- [Bug 16487] EventTarget constructor
- [Bug 14141] Introduce a constructor for Range
- [Bug 20045] data: URLs, HTTP, and parsing
- [Bug 16491] Add simpler and better event registration system
Sunday, 10 February 2013
- [Bug 20913] [Custom]: Meaning of prototype in document.register is underspecified
- [Bug 20941] Treewalker previousNode algorithm seems wrong
- [Bug 20913] [Custom]: Meaning of prototype in document.register is underspecified
- [Bug 20913] [Custom]: Meaning of prototype in document.register is underspecified
- [Bug 20941] New: Treewalker previousNode algorithm seems wrong
Saturday, 9 February 2013
- [Bug 20924] [Templates]: processing an EOF token deep within a template which was opened in <head> may fail to run after-head 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 15476] [Templates]: Specify how templates work
- [Bug 20924] New: [Templates]: processing an EOF token deep within a template which was opened in <head> may fail to run after-head work
- [Bug 20913] [Custom]: Meaning of prototype in document.register is underspecified
Friday, 8 February 2013
- [Bug 20684] [Custom]: Unblock Mozilla's implementation of document.register
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 20485] [Custom]: Creation of custom elements via constructor function is underdefined
- [Bug 20684] [Custom]: Unblock Mozilla's implementation of document.register
- [Bug 20487] [Custom]: Creation of custom elements via createElement is underdefined
- [Bug 20913] [Custom]: Meaning of prototype in document.register is underspecified
- [Bug 20684] [Custom]: Unblock Mozilla's implementation of document.register
- [Bug 20913] [Custom]: Meaning of prototype in document.register is underspecified
- [Bug 20486] [Custom]: Prototype don't inherit from interfaces
- [Bug 20913] [Custom]: Meaning of prototype in document.register is underspecified
- [Bug 20913] [Custom]: Meaning of prototype in document.register is underspecified
- [Bug 20913] [Custom]: Meaning of prototype in document.register is underspecified
- [Bug 20486] [Custom]: Prototype don't inherit from interfaces
- [Bug 20486] [Custom]: Prototype don't inherit from interfaces
- [Bug 20913] [Custom]: Meaning of prototype in document.register is underspecified
- [Bug 20486] [Custom]: Prototype don't inherit from interfaces
- [Bug 20913] [Custom]: Meaning of prototype in document.register is underspecified
- [Bug 20486] [Custom]: Prototype don't inherit from interfaces
- [Bug 20913] [Custom]: Meaning of prototype in document.register is underspecified
- [Bug 20913] [Custom]: Meaning of prototype in document.register is underspecified
- [Bug 20486] [Custom]: Prototype don't inherit from interfaces
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 20684] [Custom]: Unblock Mozilla's implementation of document.register
- [Bug 20486] [Custom]: Prototype don't inherit from interfaces
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 20913] [Custom]: Meaning of prototype in document.register is underspecified
- [Bug 20487] [Custom]: Creation of custom elements via createElement is underdefined
- [Bug 17103] [Custom]: Write first draft of the Custom DOM elements spec
- [Bug 20487] [Custom]: Creation of custom elements via createElement is underdefined
- [Bug 20913] [Custom]: Meaning of prototype in document.register is underspecified
- [Bug 20127] [Templates]: Template needs to disallow DOM hierarchy cycles which can result from template.contents
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 20913] New: [Custom]: Meaning of prototype in document.register is underspecified
- [Bug 20487] [Custom]: Creation of custom elements via createElement is underdefined
- [Bug 20127] [Templates]: Template needs to disallow DOM hierarchy cycles which can result from template.contents
- [Bug 17681] [IndexedDB] Operations that raise multiple exceptions types should define order
- [Bug 20801] [Custom]: Custom element generation algorithm should be careful about its argument
Thursday, 7 February 2013
- [Bug 20487] [Custom]: Creation of custom elements via createElement is underdefined
- [Bug 17681] [IndexedDB] Operations that raise multiple exceptions types should define order
- [Bug 20801] [Custom]: Custom element generation algorithm should be careful about its argument
- [Bug 14968] [Meta]: Specify how custom elements work
- [Bug 20684] [Custom]: Unblock Mozilla's implementation of document.register
- [Bug 20831] [Custom]: Make document.register work with ES6 classes and @@create
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 20127] [Templates]: Template needs to disallow DOM hierarchy cycles which can result from template.contents
- [Bug 17681] [IndexedDB] Operations that raise multiple exceptions types should define order
- [Bug 20831] [Custom]: Make document.register work with ES6 classes and @@create
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 20892] [Templates]: Where should hrefs link to for specific spec dependencies
- [Bug 20487] [Custom]: Creation of custom elements via createElement is underdefined
- [Bug 20892] [Templates]: Where should hrefs link to for specific spec dependencies
- [Bug 20127] [Templates]: Template needs to disallow DOM hierarchy cycles which can result from template.contents
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 20892] New: [Templates]: Where should hrefs link to for specific spec dependencies
- [Bug 20801] [Custom]: Section 4, custom element constructor generation algorithm, Step 5
Wednesday, 6 February 2013
- [Bug 20127] [Templates]: Template needs to disallow DOM hierarchy cycles which can result from template.contents
- [Bug 20849] [Templates]: Should non-template end tags be ignored in template contents insertion mode?
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 20849] [Templates]: Should non-template end tags be ignored in template contents insertion mode?
- [Bug 20849] [Templates]: Should non-template end tags be ignored in template contents insertion mode?
- [Bug 20127] [Templates]: Template needs to disallow DOM hierarchy cycles which can result from template.contents
- [Bug 20887] New: Add a File constructor
Tuesday, 5 February 2013
Monday, 4 February 2013
- [Bug 14053] Need a spec for WheelEvent constructor
- [Bug 14053] Need a spec for WheelEvent constructor
- [Bug 14053] Need a spec for WheelEvent constructor
- [Bug 14053] Need a spec for WheelEvent constructor
Friday, 1 February 2013
- [Bug 20487] [Custom]: Creation of custom elements via createElement is underdefined
- [Bug 17645] Define more precisely what the "origin" of the IDBEnvironment is
- [Bug 20797] [Templates]: Additions to the "in column group" section duplicated.
- [Bug 20849] [Templates]: Should non-template end tags be ignored in template contents insertion mode?
- [Bug 20849] [Templates]: Should non-template end tags be ignored in template contents insertion mode?
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 20849] New: [Templates]: Should non-template end tags be ignore in template contents insertion mode?
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 19488] [Templates]: Consider explanatory examples which motivate the various parser changes
- [Bug 19488] [Templates]: Consider explanatory examples which motivate the various parser changes
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 20797] [Templates]: Additions to the "in column group" section duplicated.
- [Bug 20797] [Templates]: Additions to the "in column group" section duplicated.
- [Bug 20797] [Templates]: Additions to the "in column group" section duplicated.
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 20848] [Templates]: processing any other start tag in template contents mode needs to push "in body" on the stack of template insertion modes
- [Bug 20848] [Templates]: processing any other start tag in template contents mode needs to push "in body" on the stack of template insertion modes
- [Bug 15476] [Templates]: Specify how templates work
- [Bug 20848] New: [Templates]: processing any other start tag in template contents mode needs to push "in body" on the stack of template insertion modes
- [Bug 18483] [Shadow]: Shared stylesheets may make @host ambiguous
- [Bug 18483] [Shadow]: Shared stylesheets may make @host ambiguous
- [Bug 20150] [Shadow]: "Nested tree" is defined, but "nesting tree" is only implied
- [Bug 18428] [Shadow]: Next Working Draft Iteration
- [Bug 20150] [Shadow]: "Nested tree" is defined, but "nesting tree" is only implied
- [Bug 20836] What happens when a dictionary references itself?