Tuesday, 31 March 2015
Monday, 30 March 2015
Thursday, 26 March 2015
Sunday, 29 March 2015
- Re: File Save As
- Re: File Save As
- Re: File Save As
- charter template for Community Group used by a large Working Group
Friday, 27 March 2015
- [Bug 28211] [Shadow]: A syntax for loading/parsing shadow trees directly from HTML
- [Bug 26238] [new feature] Add follow redirects back
- Re: CfC: publish Proposed Recommendation of Web Messaging; deadline March 28
- [Bug 28353] New: [Shadow]: Use a parent/child relationship in the composed tree for some elements, i.e. <ol>/<li>
- Re: [Shadow] Q: Removable shadows (and an idea for lightweight shadows)?
- Re: [Shadow] Q: Removable shadows (and an idea for lightweight shadows)?
Thursday, 26 March 2015
- Re: [Shadow] Q: Removable shadows (and an idea for lightweight shadows)?
- Re: [Shadow] Q: Removable shadows (and an idea for lightweight shadows)?
- Re: [Shadow] Q: Removable shadows (and an idea for lightweight shadows)?
- RE: CfC: publish Proposed Recommendation of Web Messaging; deadline March 28
- RE: [Shadow] Q: Removable shadows (and an idea for lightweight shadows)?
- Re: [websockets] Test results available
- Re: [Shadow] Q: Removable shadows (and an idea for lightweight shadows)?
- Re: [Shadow] Q: Removable shadows (and an idea for lightweight shadows)?
- RE: [Shadow] Q: Removable shadows (and an idea for lightweight shadows)?
- Re: [Shadow] Q: Removable shadows (and an idea for lightweight shadows)?
- RE: [Shadow] Q: Removable shadows (and an idea for lightweight shadows)?
- Re: [Shadow] Q: Removable shadows (and an idea for lightweight shadows)?
- RE: [Shadow] URL-based shadows?
- [Shadow] Q: Removable shadows (and an idea for lightweight shadows)?
- Re: [websockets] Test results available
- Re: [websockets] Test results available
- Re: [websockets] Test results available
- Re: [websockets] Test results available
- Re: [Shadow] URL-based shadows?
- Re: [websockets] Test results available
- [websockets] Test results available
- [Screen Orientation] nit for the case when the screen width and height are equal
Wednesday, 25 March 2015
- [Bug 28332] Remove any border and padding from fullscreen iframes
- Re: CfC: publish Proposed Recommendation of Web Messaging; deadline March 28
- Re: I18N comments on "Manifest for Web applications"
- [Bug 28332] New: Remove any border and padding from fullscreen iframes
- Re: CfC: publish Proposed Recommendation of Web Messaging; deadline March 28
Tuesday, 24 March 2015
- Re: CfC: publish Proposed Recommendation of Web Messaging; deadline March 28
- Re: CfC: publish Proposed Recommendation of Web Messaging; deadline March 28
- Re: I18N comments on "Manifest for Web applications"
- Re: I18N comments on "Manifest for Web applications"
- Re: I18N comments on "Manifest for Web applications"
- Re: [XHR] UTF-16 - do content sniffing or not?
Monday, 23 March 2015
- [Bug 27552] Make execCommand("InsertImage", false, "") insert an img element with no src attribute
- [gamepad]-Demo
- [Bug 27552] Make execCommand("InsertImage", false, "") insert an img element with no src attribute
- Re: [XHR] UTF-16 - do content sniffing or not?
- Re: [XHR] UTF-16 - do content sniffing or not?
- Re: [XHR] UTF-16 - do content sniffing or not?
Sunday, 22 March 2015
- [XHR] UTF-16 - do content sniffing or not?
- Re: Proposal for a Permissions API
- Re: Proposal for a Permissions API
- Re: Proposal for a Permissions API
- Re: [Shadow] URL-based shadows?
Saturday, 21 March 2015
- Re: Proposal for a Permissions API
- Re: CfC: publish Proposed Recommendation of Web Messaging; deadline March 28
- [Bug 27558] Specify MouseEvent.which
- [Bug 27337] For synthetic activation, should the original event still be dispatched?
- [Bug 25927] Specify the Event Loop integration for various non-deprecated events, incl. hit testing
- [Bug 26218] When .getModifierState("OS") should be true?
- [Bug 25844] Clarify or change the use of "default action" to avoid confusion
- [Bug 25967] Testing DOM L3 Events
- [Bug 27129] [D3E-key]: Separator
- [Bug 25485] D3E and corelation with DOM4(W3C)/DOM(WHATWAG) and DOM3 Core
- [Bug 26141] [D3E-Key] Needs more explicit explanation of "MediaSelect", "LaunchMediaPlayer" and "MediaApps"
- [Bug 28119] Reference to createEvent("FocusEvent")
- [Bug 27827] Need to remove input/beforeinput event info from D3E and point to input event spec
- [Bug 26227] Define that click doesn't fire on disabled elements
- [Bug 25968] Needs clearer definition of virtual keyboard's KeyboardEvent.code value if it doesn't emulate physical key event completely
- [Bug 27333] Most user agents (Chrome, Firefox) seem to distinguish between space and enter. Enter submits the form, even for radio buttons, space selects the checkbox.
- [Bug 28029] Mouse coordinates represented in CSS pixels do not account for retina displays with window.devicePixelRatio > 1.
- [Bug 25928] Converge with CSSOM-View
- [Bug 26611] [Proposal] Add "Zoom" event
- [Bug 27825] DOM Level 3 KeyboardEvent key Values specification does not include core key values
- [Bug 27996] [D3E-code] KeyboardEvent code spec should have featurephone section
- CfC: publish Proposed Recommendation of Web Messaging; deadline March 28
Friday, 20 March 2015
- RE: [Shadow] URL-based shadows?
- Re: [Shadow] URL-based shadows?
- RE: I18N comments on "Manifest for Web applications"
- RE: I18N comments on "Manifest for Web applications"
- RE: I18N comments on "Manifest for Web applications"
- RE: [appmanifest] No direction metadata for 'name' (etc.) [I18N-ISSUE-416]
- [Bug 28246] New: [Shadow]: Disable event capturing through a ShadowRoot
Thursday, 19 March 2015
- [appmanifest] appropriate use of ACI [I18N-ISSUE-417]
- [appmanifest] No direction metadata for 'name' (etc.) [I18N-ISSUE-416]
- [appmanifest] No language metadata for 'name' [I18N-ISSUE-415]
- [appmanifest] No means of obtaining correctly localized manifest [I18N-ISSUE-414]
- [appmanifest] No localized examples [I18N-ISSUE-413]
- [appmanifest] No localization model [I18N-ISSUE-412]
- I18N comments on "Manifest for Web applications"
- Re: [Shadow] URL-based shadows?
- Re: [Shadow] URL-based shadows?
- Re: [Shadow] URL-based shadows?
Wednesday, 18 March 2015
- RE: [Shadow] URL-based shadows?
- Re: [Shadow] URL-based shadows?
- Minuts IndieUI Teleconference 18 March 2015
- RE: [Shadow] URL-based shadows?
- Re: template namespace attribute proposal
- Re: [Shadow] URL-based shadows?
- Re: template namespace attribute proposal
- Re: template namespace attribute proposal
- [Bug 27222] [Shadow]: Define how attributes are handled in shadow DOM
Tuesday, 17 March 2015
- IndieUI Teleconference Agenda; 18 March at 21:00Z
- RE: Access to localhost to be outlawed?
- [Bug 27931] Override 'flex' and 'transform' styling
- Access to localhost to be outlawed?
- Re: template namespace attribute proposal
Monday, 16 March 2015
- Re: template namespace attribute proposal
- Re: template namespace attribute proposal
- Re: [Shadow] URL-based shadows?
- Re: [Shadow] URL-based shadows?
Sunday, 15 March 2015
Saturday, 14 March 2015
Friday, 13 March 2015
- Re: template namespace attribute proposal
- Re: template namespace attribute proposal
- Re: template namespace attribute proposal
- Re: template namespace attribute proposal
- Re: template namespace attribute proposal
- Re: [Shadow] URL-based shadows?
- [Bug 28211] New: [Shadow]: A syntax for loading/parsing shadow trees directly from HTML
- Re: template namespace attribute proposal
- Re: template namespace attribute proposal
- Re: template namespace attribute proposal
- Re: [Shadow] URL-based shadows?
- Re: [Shadow] URL-based shadows?
- Re: [Shadow] URL-based shadows?
- [Shadow] URL-based shadows?
Thursday, 12 March 2015
- Re: template namespace attribute proposal
- Re: template namespace attribute proposal
- Re: template namespace attribute proposal
- RE: template namespace attribute proposal
- Re: template namespace attribute proposal
- Re: template namespace attribute proposal
- Re: template namespace attribute proposal
- Re: template namespace attribute proposal
- Re: template namespace attribute proposal
- Re: template namespace attribute proposal
- Re: CfC: publish WG Note of UI Events; deadline November 14
- Re: template namespace attribute proposal
- Re: template namespace attribute proposal
- template namespace attribute proposal
Wednesday, 11 March 2015
- FYI: IETF Token Binding Working Group formed (tokbind)
- Re: Extending HTMLCanvasElement in Custom Element issue
- Re: IndieUI Teleconference Agenda; 18 March at 21:00Z
- RE: IndieUI Teleconference Agenda; 18 March at 21:00Z
- Extending HTMLCanvasElement in Custom Element issue
Tuesday, 10 March 2015
Wednesday, 11 March 2015
Tuesday, 10 March 2015
- Re: IndieUI Teleconference Agenda; 18 March at 21:00Z
- Re: IndieUI Teleconference Agenda; 18 March at 21:00Z
- Standardizing autocapitalize
- IndieUI Teleconference Agenda; 18 March at 21:00Z
- [Bug 28069] [Shadow]: Should Text.getDestinationInsertionPoints() be specified?
- [Bug 28185] [Shadow]: TextNode should have getDestinationInsertionPoints()
- [Bug 28185] New: [Shadow]: TextNode should have getDestinationInsertionPoints()
Monday, 9 March 2015
Saturday, 7 March 2015
- [Bug 28158] New: [Custom]: inflexible extends as fixed element type
- [Bug 28157] New: [Shadow]: Link to CSS Scoping module spec?
Friday, 6 March 2015
- Re: [manifest] RE: Manifest for web application; review deadline March 5
- RE: [manifest] RE: Manifest for web application; review deadline March 5
- RE: [manifest] RE: Manifest for web application; review deadline March 5
- RE: [manifest] RE: Manifest for web application; review deadline March 5
- Re: [manifest] RE: Manifest for web application; review deadline March 5
- Manifest for web application privacy review
- Re: CORS performance
Thursday, 5 March 2015
Wednesday, 4 March 2015
Tuesday, 3 March 2015
Sunday, 1 March 2015
Friday, 27 February 2015
Thursday, 26 February 2015
Wednesday, 25 February 2015
Tuesday, 24 February 2015
- [admin] Registration for April 24 2015 Web Components f2f meeting; deadline April 10
- Re: CORS performance
- Re: Custom elements: synchronous constructors and cloning
- [Bug 28092] New: [Custom]: Clarify in informative note that cloning/importing also enqueues created callback
- Re: Custom elements: synchronous constructors and cloning
- Re: Custom elements: synchronous constructors and cloning
- Re: Custom elements: synchronous constructors and cloning
- Re: CORS performance
- Re: Custom elements: synchronous constructors and cloning
Monday, 23 February 2015
- [Bug 28086] New: [Shadow] (assuming iframes should work inside shadow DOM) Should the contentWindow objects of iframes in shadow DOM show up in window.frames?
- Re: Custom elements: synchronous constructors and cloning
- Re: CORS performance
- Re: CORS performance
- Re: CORS performance proposal
- Re: CORS performance proposal
- Re: CORS performance
- Re: CORS performance
- Re: Custom elements: synchronous constructors and cloning
- Custom elements: synchronous constructors and cloning
- [Bug 28079] New: [Shadow]: inappropriate reference to CSS3-UI nav-index spec in focus navigation order
Sunday, 22 February 2015
Saturday, 21 February 2015
- [Bug 28069] New: [Shadow]: Should Text.getDestinationInsertionPoints() be specified?
- [Bug 28067] New: DOMStringList has been removed from DOM
- Re: Standardising canvas-driven background images
- Re: CORS performance proposal
- Re: CORS performance proposal
Friday, 20 February 2015
- Re: Standardising canvas-driven background images
- Re: Standardising canvas-driven background images
- Re: Web Components F2F in April 2015
- Re: Web Components F2F in April 2015
- Re: CORS performance proposal
- Re: Standardising canvas-driven background images
- Re: Standardising canvas-driven background images
- Standardising canvas-driven background images
- Re: CORS performance proposal
- Re: CORS performance proposal
- Re: CORS performance proposal
Thursday, 19 February 2015
- Re: CORS performance
- Re: The futile war between Native and Web
- Re: CORS performance proposal
- Re: CORS performance proposal
- Re: CORS explained simply
- Re: CORS performance
- Re: [WebCrypto.Next] Any ideas on how to proceed?
- Re: The futile war between Native and Web
- Re: CORS performance
- CORS explained simply
- Re: The futile war between Native and Web
- Re: CORS performance
- Re: CORS performance proposal
- Re: The futile war between Native and Web
- Re: CORS performance
- Re: CORS performance proposal
- Re: CORS performance
- Re: CORS performance
- Re: The futile war between Native and Web
- Re: The futile war between Native and Web
- Re: The futile war between Native and Web
- Re: The futile war between Native and Web
- Re: The futile war between Native and Web
- Re: Web Components F2F in April 2015
- Re: Staying on Topic [Was: Re: WebPortable/PlatformProprietary - An Established Concept]
- Re: Staying on Topic [Was: Re: WebPortable/PlatformProprietary - An Established Concept]
- Staying on Topic [Was: Re: WebPortable/PlatformProprietary - An Established Concept]
- WebPortable/PlatformProprietary - An Established Concept
- Re: CORS performance proposal
- Re: CORS performance
- Re: CORS performance
- Re: CORS performance
- Re: CORS performance
- CORS performance proposal
- Re: Web Components F2F in April 2015
- Re: CORS performance
- Re: CORS performance
- Re: CORS performance
- Re: CORS performance
- Re: CORS performance
- Re: CORS performance
- Re: CORS performance
- Re: CORS performance
- Re: CORS performance
- Re: Better focus support for Shadow DOM
- Re: CORS performance
- Re: CORS performance
- Re: CORS performance
- Re: Better focus support for Shadow DOM
- [Bug 28054] New: Focus on shadow host should slide to its inner focusable node
Wednesday, 18 February 2015
- Mozilla on Privileged Hosted Apps
- Web Components F2F in April 2015
- [Bug 28051] [imports]: showing <dialog> from import
- Re: Showing <dialog> from HTML import
- Re: Showing <dialog> from HTML import
- Showing <dialog> from HTML import
- Re: [WebCrypto.Next] Any ideas on how to proceed?
- Re: [WebCrypto.Next] Any ideas on how to proceed?
- [WebCrypto.Next] Any ideas on how to proceed?
- Re: CORS performance
Tuesday, 17 February 2015
- Re: CORS performance
- Re: CORS performance
- Re: CORS performance
- Re: CORS performance
- Re: CORS performance
- Updated: Running trusted code in the untrusted web
- CORS performance
Saturday, 14 February 2015
Tuesday, 17 February 2015
Monday, 16 February 2015
- Re: The futile war between Native and Web
- Re: The futile war between Native and Web
- Re: The futile war between Native and Web
- Re: The futile war between Native and Web
- Re: The futile war between Native and Web
- Re: The futile war between Native and Web
- Re: The futile war between Native and Web
- Re: The futile war between Native and Web
- Re: The futile war between Native and Web
- Re: The futile war between Native and Web
- Re: The futile war between Native and Web
- Re: The futile war between Native and Web
- Re: The futile war between Native and Web
- Re: The futile war between Native and Web
- Re: The futile war between Native and Web
- Re: The futile war between Native and Web
- Re: Base Template (Was Re: Minimum viable custom elements)
- [Bug 28031] Does the destination insertion points include Shadow IP without older trees?
- [Bug 28031] New: Does the destination insertion points include Shadow IP without older trees?
Sunday, 15 February 2015
- Re: The futile war between Native and Web
- The futile war between Native and Web
- Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest
Friday, 13 February 2015
- Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest
- RE: [clipboard API] platform integration stuff - in spec or out of scope?
- RE: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest
- Re: Base Template (Was Re: Minimum viable custom elements)
- Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest
- Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest
- [Bug 28008] New: [Shadow] Should "Events that are Always Stopped" include destination insertion points?
- RfC: Manifest for web application; review deadline March 5
Thursday, 12 February 2015
- Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest
- Re: Base Template (Was Re: Minimum viable custom elements)
- Base Template (Was Re: Minimum viable custom elements)
Wednesday, 11 February 2015
Thursday, 12 February 2015
- Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest
- Re: Minimum viable custom elements
- Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest
- Re: Minimum viable custom elements
- Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest
- Re: Minimum viable custom elements
- Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest
- Re: [clipboard API] platform integration stuff - in spec or out of scope?
- Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest
- Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest
- Re: [clipboard] Feature detect Clipboard API support?
Wednesday, 11 February 2015
- Re: [clipboard API] platform integration stuff - in spec or out of scope?
- Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest
- Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest
- Re: [Unbearable] IETF seeking feedback on proposed "Token Binding" Working Group
- Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest
- Re: [clipboard] Feature detect Clipboard API support?
- [clipboard] Feature detect Clipboard API support?
- Re: [clipboard API] platform integration stuff - in spec or out of scope?
- Re: IETF seeking feedback on proposed "Token Binding" Working Group
- IETF seeking feedback on proposed "Token Binding" Working Group
- Re: do not deprecate synchronous XMLHttpRequest
- Re: do not deprecate synchronous XMLHttpRequest
- Re: do not deprecate synchronous XMLHttpRequest
- Re: do not deprecate synchronous XMLHttpRequest
- Re: do not deprecate synchronous XMLHttpRequest
- [DOM3Events/UIEvents] Minutes from 10 Feb 2015 teleconference
- Re: do not deprecate synchronous XMLHttpRequest
Tuesday, 10 February 2015
- Re: do not deprecate synchronous XMLHttpRequest
- Re: do not deprecate synchronous XMLHttpRequest
- Re: do not deprecate synchronous XMLHttpRequest
- Re: do not deprecate synchronous XMLHttpRequest
- Standards wonks and developers working together [Was: Re: do not deprecate synchronous XMLHttpRequest]
- Re: do not deprecate synchronous XMLHttpRequest
- Staying on topic [Was: Re: do not deprecate synchronous XMLHttpRequest]
- Re: do not deprecate synchronous XMLHttpRequest
- Re: do not deprecate synchronous XMLHttpRequest
- Re: do not deprecate synchronous XMLHttpRequest
- Re: do not deprecate synchronous XMLHttpRequest
- Re: do not deprecate synchronous XMLHttpRequest
- Re: do not deprecate synchronous XMLHttpRequest
- Re: do not deprecate synchronous XMLHttpRequest
- Re: do not deprecate synchronous XMLHttpRequest
- Re: do not deprecate synchronous XMLHttpRequest
- Re: do not deprecate synchronous XMLHttpRequest
- Re: do not deprecate synchronous XMLHttpRequest
- Re: do not deprecate synchronous XMLHttpRequest
- Re: do not deprecate synchronous XMLHttpRequest
- Re: do not deprecate synchronous XMLHttpRequest
- Re: do not deprecate synchronous XMLHttpRequest
- [Bug 27994] New: [Shadow]: Distribution result usage examples
- Re: do not deprecate synchronous XMLHttpRequest
- Re: [webcomponents]: Let's reach consensus on Shadow DOM
- Re: do not deprecate synchronous XMLHttpRequest
Monday, 9 February 2015
- Re: do not deprecate synchronous XMLHttpRequest
- Re: Violation of mail list policy [Was: Fwd: Re: do not deprecate synchronous XMLHttpRequest]
- Violation of mail list policy [Was: Fwd: Re: do not deprecate synchronous XMLHttpRequest]
- RE: Minimum viable custom elements
- [Bug 27986] New: Specify exact length of array returned by Navigator.getGamepads()
Sunday, 8 February 2015
- Re: [webcomponents]: Let's reach consensus on Shadow DOM
- Re: [webcomponents]: Let's reach consensus on Shadow DOM
Saturday, 7 February 2015
- [Bug 27978] New: [Custom]: attachedCallback has no protocol for indicating that the custom tag is not applicable in this context
- [Bug 27977] New: [Custom]: mixin pattern: custom elements should be able to extend any base tag with is=
- [Bug 27976] New: [Custom]: type extensions should be available as custom tags, not only through <baseTag is="...">
- [Bug 27975] New: [Custom]: No way to unregister a component
- Re: Are web components *seriously* not namespaced?
- Re: Are web components *seriously* not namespaced?
Friday, 6 February 2015
- [webcomponents]: Let's reach consensus on Shadow DOM
- Re: Are web components *seriously* not namespaced?
- Re: Are web components *seriously* not namespaced?
- Re: do not deprecate synchronous XMLHttpRequest
- Re: do not deprecate synchronous XMLHttpRequest
- Re: do not deprecate synchronous XMLHttpRequest
- Re: do not deprecate synchronous XMLHttpRequest
- Re: do not deprecate synchronous XMLHttpRequest
- Re: do not deprecate synchronous XMLHttpRequest
- Re: do not deprecate synchronous XMLHttpRequest
- Re: do not deprecate synchronous XMLHttpRequest
- Re: Are web components *seriously* not namespaced?
- Re: do not deprecate synchronous XMLHttpRequest
- Re: do not deprecate synchronous XMLHttpRequest
- Re: do not deprecate synchronous XMLHttpRequest
- Mail list Etiquette [Was: Re: Shadow tree style isolation primitive]
- Re: Are web components *seriously* not namespaced?
- Re: Are web components *seriously* not namespaced?
- Re: Allow custom headers (Websocket API)
Thursday, 5 February 2015
Friday, 6 February 2015
- Re: Shadow tree style isolation primitive
- Re: [IndexedDB] When is an error event dispatched at a transcation?
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
Thursday, 5 February 2015
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
- Re: Are web components *seriously* not namespaced?
- Re: Are web components *seriously* not namespaced?
- Re: Are web components *seriously* not namespaced?
- Re: Minimum viable custom elements
- Re: Shadow tree style isolation primitive
- Re: Minimum viable custom elements
- Re: Shadow tree style isolation primitive
- Re: [IndexedDB] When is an error event dispatched at a transcation?
- Re: Shadow tree style isolation primitive
- Re: Minimum viable custom elements
- Re: Are web components *seriously* not namespaced?
- Re: Are web components *seriously* not namespaced?
- Re: Allow custom headers (Websocket API)
- Re: Allow custom headers (Websocket API)
- Re: Allow custom headers (Websocket API)
- Re: Allow custom headers (Websocket API)
- Re: Allow custom headers (Websocket API)
- Re: Allow custom headers (Websocket API)
- Re: Are web components *seriously* not namespaced?
- Re: Allow custom headers (Websocket API)
- Re: Shadow tree style isolation primitive
- Re: Allow custom headers (Websocket API)
- Re: Allow custom headers (Websocket API)
- Re: Allow custom headers (Websocket API)
- Re: Allow custom headers (Websocket API)
- Re: Allow custom headers (Websocket API)
- Re: Allow custom headers (Websocket API)
- Re: Allow custom headers (Websocket API)
- Re: Allow custom headers (Websocket API)
- Re: Allow custom headers (Websocket API)
- Re: Allow custom headers (Websocket API)
- Re: Shadow tree style isolation primitive
- Re: Allow custom headers (Websocket API)
- Re: Allow custom headers (Websocket API)
- [IndexedDB] When is an error event dispatched at a transcation?
- Re: Are web components *seriously* not namespaced?
- Re: Are web components *seriously* not namespaced?
- Re: Allow custom headers (Websocket API)
- Re: Allow custom headers (Websocket API)
- Re: Allow custom headers (Websocket API)
- Re: Allow custom headers (Websocket API)
- Re: Allow custom headers (Websocket API)
- Re: Allow custom headers (Websocket API)
- Allow custom headers (Websocket API)
- Re: Are web components *seriously* not namespaced?
- [Bug 27965] New: [Shadow]: Shadow host with tabindex=-1, all descendent tree should be ignored for tab navigation
- Re: Are web components *seriously* not namespaced?
- Re: Are web components *seriously* not namespaced?
- Re: Are web components *seriously* not namespaced?
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
Wednesday, 4 February 2015
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
- Re: Are web components *seriously* not namespaced?
- Re: Are web components *seriously* not namespaced?
- Re: Are web components *seriously* not namespaced?
- Re: Are web components *seriously* not namespaced?
- Re: Are web components *seriously* not namespaced?
- Re: Are web components *seriously* not namespaced?
- Are web components *seriously* not namespaced?
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Shadow tree style isolation primitive
- RE: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Shadow tree style isolation primitive
- Re: Minimum viable custom elements
- Re: Shadow tree style isolation primitive
- Re: [IndexedDB] link to Editor's draft is a 404
- Re: Shadow tree style isolation primitive
Tuesday, 3 February 2015
Wednesday, 4 February 2015
Tuesday, 3 February 2015
- Re: Minimum viable custom elements
- Re: Shadow tree style isolation primitive
- Re: Minimum viable custom elements
- Re: Shadow tree style isolation primitive
- PSA: publishing new WD of Service Workers on February 5
- RE: IndieUI Teleconference Agenda; 4 February at 22:00Z for 60 minutes
- Re: Shadow tree style isolation primitive
- IndieUI Teleconference Agenda; 4 February at 22:00Z for 60 minutes
- Re: Minimum viable custom elements
Monday, 2 February 2015
- Re: Shadow tree style isolation primitive
- Re: Toward more productive f2f meetings [Was:Re: Feedback needed for April 2015 face-to-face location by *January 27, 2015*]
- Re: Toward more productive f2f meetings [Was:Re: Feedback needed for April 2015 face-to-face location by *January 27, 2015*]
- Re: Minimum viable custom elements
Saturday, 31 January 2015
Friday, 30 January 2015
Monday, 2 February 2015
- Toward more productive f2f meetings [Was:Re: Feedback needed for April 2015 face-to-face location by *January 27, 2015*]
- Re: [IndexedDB] link to Editor's draft is a 404
- [IndexedDB] link to Editor's draft is a 404
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
Saturday, 31 January 2015
- Re: [clipboard API] platform integration stuff - in spec or out of scope?
- Re: [clipboard API] platform integration stuff - in spec or out of scope?
- Re: Minimum viable custom elements
- Re: [clipboard API] platform integration stuff - in spec or out of scope?
- [clipboard API] platform integration stuff - in spec or out of scope?
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
Friday, 30 January 2015
- Re: Security use cases for packaging
- Re: Security use cases for packaging
- Re: Minimum viable custom elements
- [Bug 27931] New: Override 'flex' and 'transform' styling
- Re: Minimum viable custom elements
- Re: =[xhr]
- Re: Minimum viable custom elements
Thursday, 29 January 2015
Friday, 30 January 2015
- Re: Security use cases for packaging
- Re: Security use cases for packaging
- Re: Security use cases for packaging
- Re: Security use cases for packaging
- Re: Security use cases for packaging
- Re: Security use cases for packaging
Thursday, 29 January 2015
- Re: Security use cases for packaging
- Re: Security use cases for packaging
- Re: Security use cases for packaging
- Re: Security use cases for packaging
- Re: Security use cases for packaging
- Security use cases for packaging
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- CfC: publish Wide Review Draft of Manifest for web application; deadline Feb 5
- Custom elements and the HTML parser
Wednesday, 28 January 2015
- Re: [Selection] Support of Multiple Selection (was: Should selection.getRangeAt return a clone or a reference?)
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
- [Bug 27915] New: Clients of WebSockets are not NTP synced (and there is no NTP-alike spec)
- Re: Custom element design with ES6 classes and Element constructors
- RE: Custom element design with ES6 classes and Element constructors
- Re: Custom element design with ES6 classes and Element constructors
- RE: Custom element design with ES6 classes and Element constructors
- Re: Custom element design with ES6 classes and Element constructors
- Re: Custom element design with ES6 classes and Element constructors
- [DOM3Events/UIEvents] Minutes from 27 Jan 2015 teleconference
- [Bug 27914] New: [Custom]: Typo instantation ---> instantiation
Tuesday, 27 January 2015
- Re: oldNode.replaceWith(...collection) edge case
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
- Re: [Selection] Support of Multiple Selection (was: Should selection.getRangeAt return a clone or a reference?)
- Re: oldNode.replaceWith(...collection) edge case
- Re: oldNode.replaceWith(...collection) edge case
Monday, 26 January 2015
Sunday, 25 January 2015
Monday, 26 January 2015
Sunday, 25 January 2015
- [admin] Important: Feedback needed for April 2015 face-to-face location by *January 27, 2015*
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
- Re: [Selection] Support of Multiple Selection (was: Should selection.getRangeAt return a clone or a reference?)
Saturday, 24 January 2015
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
- Re: [Selection] Support of Multiple Selection (was: Should selection.getRangeAt return a clone or a reference?)
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
- Re: [Selection] Support of Multiple Selection (was: Should selection.getRangeAt return a clone or a reference?)
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
Friday, 23 January 2015
- FYI: Change in my affiliation
- Re: <webview> API common subset
- Re: <webview> API common subset
- <webview> API common subset
- [Bug 27876] [Shadow] It is not defined what event.path actually should return
Thursday, 22 January 2015
- [Bug 26181] Spec should specify the presentation of the array returned by navigator.getGamepads() w.r.t "holes"
- Re: oldNode.replaceWith(...collection) edge case
- Re: oldNode.replaceWith(...collection) edge case
Wednesday, 21 January 2015
- RE: Better focus support for Shadow DOM
- [Bug 27876] New: [Shadow] It is not defined what event.path actually should return
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
- Re: oldNode.replaceWith(...collection) edge case
- Re: oldNode.replaceWith(...collection) edge case
- Re: oldNode.replaceWith(...collection) edge case
- Re: Better focus support for Shadow DOM
- Re: oldNode.replaceWith(...collection) edge case
- Re: Feedback needed for April 2015 face-to-face location by *January 27, 2015*
- [D3E/UIEvents] Transferring related Bugzilla bugs to github issues
Tuesday, 20 January 2015
- Re: oldNode.replaceWith(...collection) edge case
- IndieUI Teleconference Agenda; 21 January at 22:00Z for 60 minutes
- Re: Feedback needed for April 2015 face-to-face location by *January 27, 2015*
- Re: Feedback needed for April 2015 face-to-face location by *January 27, 2015*
- Feedback needed for April 2015 face-to-face location by *January 27, 2015*
- Re: oldNode.replaceWith(...collection) edge case
- Re: oldNode.replaceWith(...collection) edge case
- Re: oldNode.replaceWith(...collection) edge case
- Re: oldNode.replaceWith(...collection) edge case
- [Bug 27865] New: Interaction issues between fullscreen and <dialog>
- Re: oldNode.replaceWith(...collection) edge case
- [Bug 27863] New: Not need to specify moving element in top layer and fullscreen stack
Monday, 19 January 2015
- Re: Minimum viable custom elements
- Re: Defining a constructor for Element and friends
- Re: Defining a constructor for Element and friends
- [Bug 27844] [Shadow]: Element.createShadowRoot() throws an exception for some elements
Thursday, 15 January 2015
Sunday, 18 January 2015
Saturday, 17 January 2015
- Re: [Selection] Support of Multiple Selection (was: Should selection.getRangeAt return a clone or a reference?)
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
- Re: [Selection] Support of Multiple Selection (was: Should selection.getRangeAt return a clone or a reference?)
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
Friday, 16 January 2015
- Re: Minimum viable custom elements
- RE: Defining a constructor for Element and friends
- RE: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- RfC: Manifest for web application
- Re: oldNode.replaceWith(...collection) edge case
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Defining a constructor for Element and friends
- Re: Custom element design with ES6 classes and Element constructors
- [Bug 27844] New: [Shadow]: Element.createShadowRoot() throws an exception for some elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Better focus support for Shadow DOM
- Re: oldNode.replaceWith(...collection) edge case
- Re: oldNode.replaceWith(...collection) edge case
- Re: oldNode.replaceWith(...collection) edge case
- oldNode.replaceWith(...collection) edge case
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
Thursday, 15 January 2015
- RE: Minimum viable custom elements
- RE: Defining a constructor for Element and friends
- Re: Minimum viable custom elements
- RE: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: CfC: publish FPWD of Packaging on the Web; deadline November 3
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- RE: Minimum viable custom elements
- Re: Custom element design with ES6 classes and Element constructors
- Re: Minimum viable custom elements
- Re: Custom element design with ES6 classes and Element constructors
- Re: Minimum viable custom elements
- RE: Custom element design with ES6 classes and Element constructors
- Re: Custom element design with ES6 classes and Element constructors
- Re: Custom element design with ES6 classes and Element constructors
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Custom element design with ES6 classes and Element constructors
- Re: Minimum viable custom elements
- Re: Custom element design with ES6 classes and Element constructors
- Re: Custom element design with ES6 classes and Element constructors
- Re: Custom element design with ES6 classes and Element constructors
- [Bug 27836] New: Scripts in HTML Imports should be scoped to the import (treat imports as script modules)
Wednesday, 14 January 2015
- RE: Custom element design with ES6 classes and Element constructors
- [Bug 27835] New: registerElement() should be scoped to modules
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- RE: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- Re: Minimum viable custom elements
- RE: Minimum viable custom elements
- Re: Custom element design with ES6 classes and Element constructors
- Re: Minimum viable custom elements
- RE: Minimum viable custom elements
- Re: Minimum viable custom elements
- RE: Minimum viable custom elements
- Re: Custom element design with ES6 classes and Element constructors
- Re: Minimum viable custom elements
- Re: Custom element design with ES6 classes and Element constructors
- Re: Minimum viable custom elements
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
- RE: Adopting a Custom Element into Another Document
- Re: Minimum viable custom elements
- Re: Custom element design with ES6 classes and Element constructors
- Re: Minimum viable custom elements
- IME API…
- Minimum viable custom elements
- Re: Custom element design with ES6 classes and Element constructors
- [Bug 27823] We should consider dropping [NoInterfaceObject] from XMLHttpRequestEventTarget
- Re: Custom element design with ES6 classes and Element constructors
- Re: Custom element design with ES6 classes and Element constructors
- Re: Defining a constructor for Element and friends
- Re: Shadow tree style isolation primitive
- Re: Better focus support for Shadow DOM
- Re: Better focus support for Shadow DOM
- Re: Better focus support for Shadow DOM
- Re: Adopting a Custom Element into Another Document
- Re: Adopting a Custom Element into Another Document
- Re: Defining a constructor for Element and friends
- Better focus support for Shadow DOM
- [Bug 27829] New: [Shadow]: Update ShadowRoot to have elementsFromPoint and caretPositionFromPoint
- Re: Defining a constructor for Element and friends
- RE: Defining a constructor for Element and friends
- Re: Defining a constructor for Element and friends
- Re: Adopting a Custom Element into Another Document
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
Tuesday, 13 January 2015
- [Bug 25223] IDB exposes GC behavior
- [Bug 27712] IndexedDB: Array comparison algorithm doesn't handle empty arrays
- Re: Shadow tree style isolation primitive
- Re: [Selection] Support of Multiple Selection (was: Should selection.getRangeAt return a clone or a reference?)
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
- Re: [Selection] Support of Multiple Selection (was: Should selection.getRangeAt return a clone or a reference?)
- Re: [Selection] Support of Multiple Selection (was: Should selection.getRangeAt return a clone or a reference?)
- Re: Custom element design with ES6 classes and Element constructors
- [Bug 27823] New: We should consider dropping [NoInterfaceObject] from XMLHttpRequestEventTarget
- Re: Adopting a Custom Element into Another Document
- RE: Adopting a Custom Element into Another Document
- Re: Defining a constructor for Element and friends
- Re: Adopting a Custom Element into Another Document
- Re: Defining a constructor for Element and friends
- Re: Adopting a Custom Element into Another Document
- Re: Adopting a Custom Element into Another Document
- Re: Shadow tree style isolation primitive
- Re: Defining a constructor for Element and friends
- RE: Defining a constructor for Element and friends
- Re: Defining a constructor for Element and friends
- RE: Defining a constructor for Element and friends
- Re: Defining a constructor for Element and friends
- Re: Defining a constructor for Element and friends
- Re: Defining a constructor for Element and friends
- Re: Custom element design with ES6 classes and Element constructors
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
- RE: Custom element design with ES6 classes and Element constructors
- [Bug 27709] Dictionary MouseEventInit uses keyword attribute for its members
- Re: [Bug 27709] New: Dictionary MouseEventInit uses keyword attribute for its members
- Re: [Bug 27709] New: Dictionary MouseEventInit uses keyword attribute for its members
- RE: Defining a constructor for Element and friends
- Re: Custom element design with ES6 classes and Element constructors
- Re: Custom element design with ES6 classes and Element constructors
- RE: Custom element design with ES6 classes and Element constructors
- Re: Defining a constructor for Element and friends
- RE: Custom element design with ES6 classes and Element constructors
- Re: Custom element design with ES6 classes and Element constructors
- RE: Defining a constructor for Element and friends
- Re: Adopting a Custom Element into Another Document
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
- Re: Shadow tree style isolation primitive
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
- Re: Defining a constructor for Element and friends
- Re: element.onresize
- Re: Custom element design with ES6 classes and Element constructors
- Adopting a Custom Element into Another Document
- Re: Custom element design with ES6 classes and Element constructors
- Re: Custom element design with ES6 classes and Element constructors
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
- Re: Custom element design with ES6 classes and Element constructors
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
- RE: Custom element design with ES6 classes and Element constructors
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
- Re: Custom element design with ES6 classes and Element constructors
- Re: Shadow tree style isolation primitive
- RE: Custom element design with ES6 classes and Element constructors
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
Monday, 12 January 2015
- Re: Custom element design with ES6 classes and Element constructors
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
- RE: Custom element design with ES6 classes and Element constructors
- RE: Custom element design with ES6 classes and Element constructors
- RE: Shadow tree style isolation primitive
- Re: Custom element design with ES6 classes and Element constructors
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
- Re: Custom element design with ES6 classes and Element constructors
- [Selection] Support of Multiple Selection (was: Should selection.getRangeAt return a clone or a reference?)
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
- RE: Custom element design with ES6 classes and Element constructors
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
- Re: Custom element design with ES6 classes and Element constructors
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
- Re: Custom element design with ES6 classes and Element constructors
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
- Re: Spring meeting in Paris?
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
Sunday, 11 January 2015
- RE: Custom element design with ES6 classes and Element constructors
- Custom element design with ES6 classes and Element constructors
- RE: Defining a constructor for Element and friends
- [Bug 27727] Remove DOMError from IDB
Saturday, 10 January 2015
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
- Re: Defining a constructor for Element and friends
- RE: Defining a constructor for Element and friends
Friday, 9 January 2015
- Re: [Pointer Lock] Comments
- [Bug 26904] Introduce typedef for IDBKeyPath, use it
- Re: Shadow tree style isolation primitive
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
- Re: Shadow tree style isolation primitive
- RE: Custom element lifecycle callbacks
- Re: Shadow tree style isolation primitive
- Re: Custom element lifecycle callbacks
- Re: Custom element lifecycle callbacks
- Re: Custom element lifecycle callbacks
- Re: Custom element lifecycle callbacks
- Shadow tree style isolation primitive
- Re: Custom element lifecycle callbacks
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
- Re: Custom element lifecycle callbacks
- Re: Custom element lifecycle callbacks
- Re: Custom element lifecycle callbacks
- Re: Custom element lifecycle callbacks
- [Bug 27785] [Shadow]: broken link in draft spec section 9.3
- Re: Custom element lifecycle callbacks
- Re: PSA: Indexed Database API is a W3C Recommendation
Thursday, 8 January 2015
- PSA: Indexed Database API is a W3C Recommendation
- Re: Custom element lifecycle callbacks
- Re: Custom element lifecycle callbacks
- Custom element lifecycle callbacks
- [Manifest] Navigation Scope is unclear
- [Bug 27785] New: [Shadow]: broken link in draft spec section 9.3
Wednesday, 7 January 2015
- [Bug 27727] Remove DOMError from IDB
- Re: Defining a constructor for Element and friends
- [Bug 27780] New: [Custom]: "All Algorithms in One Diagram"
- Re: Defining a constructor for Element and friends
- Re: Defining a constructor for Element and friends
- FYI: Deep linking
- RE: ES6 and upgrading custom elements
- Defining a constructor for Element and friends
- Re: ES6 and upgrading custom elements
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
- RE: ES6 and upgrading custom elements
- [Bug 27775] New: [Shadow]: Define the behavior of *closed* shadow trees.
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
Tuesday, 6 January 2015
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
- Re: [Selection] Should selection.getRangeAt return a clone or a reference?
- RE: [Selection] Should selection.getRangeAt return a clone or a reference?
- [Selection] Should selection.getRangeAt return a clone or a reference?
- IndieUI Teleconference Agenda; 7 January at 22:00Z for 60 minutes
- Re: Spring meeting in Paris?
- Re: ES6 and upgrading custom elements
- Re: ES6 and upgrading custom elements
- Re: ES6 and upgrading custom elements
- Re: ES6 and upgrading custom elements
- Re: ES6 and upgrading custom elements
- Re: ES6 and upgrading custom elements
- [Bug 27770] New: [Custom]: Improve the wording in element upgrade algorithm
- Re: pull request on custom elements spec
- Re: ES6 and upgrading custom elements
- [Bug 27769] New: [Custom]: ES6 section needs to be updated
- [Bug 27768] New: [Custom]: "Parsing Custom Elements"
- [Bug 27544] [IndexedDB] "and and" typo
- ES6 and upgrading custom elements
- [Bug 27762] New: [Custom]: what happens with Unresolved Elements when removed from the tree?
- pull request on custom elements spec
Monday, 5 January 2015
- [Bug 27757] New: [Shadow]: how is the autofocus attribute supposed to be handled?
- [Bug 27751] New: [Custom]: suggest note on requirements
- Re: custom elements without the dash
- Re: custom elements without the dash
- Re: custom elements without the dash
- Re: custom elements without the dash
- Re: custom elements without the dash
- Re: custom elements without the dash
- custom elements without the dash
- [Bug 25813] [Custom]: Throw Exception when EXTENDS and PROTOTYPE have a mismatch