public-webapps@w3.org from January to March 2015 by date

Tuesday, 31 March 2015

• Re: Pointer lock spec Vincent Scheib
• IndieUI Teleconference Agenda; 1 April at 21:00Z Janina Sajka

Monday, 30 March 2015

• [Bug 28373] New: FilePropertyBag can inherit from BlobPropertyBag bugzilla@jessica.w3.org

Thursday, 26 March 2015

• Obsolete Document Gulfaraz Yasin

Sunday, 29 March 2015

• Re: File Save As Florian Bösch
• Re: File Save As Jonas Sicking
• Re: File Save As Florian Bösch
• charter template for Community Group used by a large Working Group Wayne Carr

Friday, 27 March 2015

• [Bug 28211] [Shadow]: A syntax for loading/parsing shadow trees directly from HTML bugzilla@jessica.w3.org
• [Bug 26238] [new feature] Add follow redirects back bugzilla@jessica.w3.org
• Re: CfC: publish Proposed Recommendation of Web Messaging; deadline March 28 Simon Pieters
• [Bug 28353] New: [Shadow]: Use a parent/child relationship in the composed tree for some elements, i.e. <ol>/<li> bugzilla@jessica.w3.org
• Re: [Shadow] Q: Removable shadows (and an idea for lightweight shadows)? Dominic Cooney
• Re: [Shadow] Q: Removable shadows (and an idea for lightweight shadows)? Hayato Ito

Thursday, 26 March 2015

• Re: [Shadow] Q: Removable shadows (and an idea for lightweight shadows)? Elliott Sprehn
• Re: [Shadow] Q: Removable shadows (and an idea for lightweight shadows)? Ryosuke Niwa
• Re: [Shadow] Q: Removable shadows (and an idea for lightweight shadows)? Justin Fagnani
• RE: CfC: publish Proposed Recommendation of Web Messaging; deadline March 28 Travis Leithead
• RE: [Shadow] Q: Removable shadows (and an idea for lightweight shadows)? Travis Leithead
• Re: [websockets] Test results available Arthur Barstow
• Re: [Shadow] Q: Removable shadows (and an idea for lightweight shadows)? Elliott Sprehn
• Re: [Shadow] Q: Removable shadows (and an idea for lightweight shadows)? Ryosuke Niwa
• RE: [Shadow] Q: Removable shadows (and an idea for lightweight shadows)? Travis Leithead
• Re: [Shadow] Q: Removable shadows (and an idea for lightweight shadows)? Daniel Freedman
• RE: [Shadow] Q: Removable shadows (and an idea for lightweight shadows)? Travis Leithead
• Re: [Shadow] Q: Removable shadows (and an idea for lightweight shadows)? Justin Fagnani
• RE: [Shadow] URL-based shadows? Travis Leithead
• [Shadow] Q: Removable shadows (and an idea for lightweight shadows)? Travis Leithead
• Re: [websockets] Test results available Boris Zbarsky
• Re: [websockets] Test results available James Graham
• Re: [websockets] Test results available Boris Zbarsky
• Re: [websockets] Test results available Boris Zbarsky
• Re: [Shadow] URL-based shadows? Anne van Kesteren
• Re: [websockets] Test results available Olli Pettay
• [websockets] Test results available Arthur Barstow
• [Screen Orientation] nit for the case when the screen width and height are equal Kang-Hao (Kenny) Lu（吕康豪）

Wednesday, 25 March 2015

• [Bug 28332] Remove any border and padding from fullscreen iframes bugzilla@jessica.w3.org
• Re: CfC: publish Proposed Recommendation of Web Messaging; deadline March 28 Xiaoqian Wu
• Re: I18N comments on "Manifest for Web applications" Arthur Barstow
• [Bug 28332] New: Remove any border and padding from fullscreen iframes bugzilla@jessica.w3.org
• Re: CfC: publish Proposed Recommendation of Web Messaging; deadline March 28 Arthur Barstow

Tuesday, 24 March 2015

• Re: CfC: publish Proposed Recommendation of Web Messaging; deadline March 28 Sigbjorn Finne
• Re: CfC: publish Proposed Recommendation of Web Messaging; deadline March 28 Arthur Barstow
• Re: I18N comments on "Manifest for Web applications" Arthur Barstow
• Re: I18N comments on "Manifest for Web applications" Kenneth Rohde Christiansen
• Re: I18N comments on "Manifest for Web applications" Richard Ishida
• Re: [XHR] UTF-16 - do content sniffing or not? Hallvord Reiar Michaelsen Steen

Monday, 23 March 2015

• [Bug 27552] Make execCommand("InsertImage", false, "") insert an img element with no src attribute bugzilla@jessica.w3.org
• [gamepad]-Demo 个人
• [Bug 27552] Make execCommand("InsertImage", false, "") insert an img element with no src attribute bugzilla@jessica.w3.org
• Re: [XHR] UTF-16 - do content sniffing or not? Simon Pieters
• Re: [XHR] UTF-16 - do content sniffing or not? Hallvord Reiar Michaelsen Steen
• Re: [XHR] UTF-16 - do content sniffing or not? Simon Pieters

Sunday, 22 March 2015

• [XHR] UTF-16 - do content sniffing or not? Hallvord Reiar Michaelsen Steen
• Re: Proposal for a Permissions API Jeffrey Yasskin
• Re: Proposal for a Permissions API Florian Bösch
• Re: Proposal for a Permissions API Anders Rundgren
• Re: [Shadow] URL-based shadows? Ryosuke Niwa

Saturday, 21 March 2015

• Re: Proposal for a Permissions API Florian Bösch
• Re: CfC: publish Proposed Recommendation of Web Messaging; deadline March 28 Jonas Sicking
• [Bug 27558] Specify MouseEvent.which bugzilla@jessica.w3.org
• [Bug 27337] For synthetic activation, should the original event still be dispatched? bugzilla@jessica.w3.org
• [Bug 25927] Specify the Event Loop integration for various non-deprecated events, incl. hit testing bugzilla@jessica.w3.org
• [Bug 26218] When .getModifierState("OS") should be true? bugzilla@jessica.w3.org
• [Bug 25844] Clarify or change the use of "default action" to avoid confusion bugzilla@jessica.w3.org
• [Bug 25967] Testing DOM L3 Events bugzilla@jessica.w3.org
• [Bug 27129] [D3E-key]: Separator bugzilla@jessica.w3.org
• [Bug 25485] D3E and corelation with DOM4(W3C)/DOM(WHATWAG) and DOM3 Core bugzilla@jessica.w3.org
• [Bug 26141] [D3E-Key] Needs more explicit explanation of "MediaSelect", "LaunchMediaPlayer" and "MediaApps" bugzilla@jessica.w3.org
• [Bug 28119] Reference to createEvent("FocusEvent") bugzilla@jessica.w3.org
• [Bug 27827] Need to remove input/beforeinput event info from D3E and point to input event spec bugzilla@jessica.w3.org
• [Bug 26227] Define that click doesn't fire on disabled elements bugzilla@jessica.w3.org
• [Bug 25968] Needs clearer definition of virtual keyboard's KeyboardEvent.code value if it doesn't emulate physical key event completely bugzilla@jessica.w3.org
• [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. bugzilla@jessica.w3.org
• [Bug 28029] Mouse coordinates represented in CSS pixels do not account for retina displays with window.devicePixelRatio > 1. bugzilla@jessica.w3.org
• [Bug 25928] Converge with CSSOM-View bugzilla@jessica.w3.org
• [Bug 26611] [Proposal] Add "Zoom" event bugzilla@jessica.w3.org
• [Bug 27825] DOM Level 3 KeyboardEvent key Values specification does not include core key values bugzilla@jessica.w3.org
• [Bug 27996] [D3E-code] KeyboardEvent code spec should have featurephone section bugzilla@jessica.w3.org
• CfC: publish Proposed Recommendation of Web Messaging; deadline March 28 Arthur Barstow

Friday, 20 March 2015

• RE: [Shadow] URL-based shadows? Travis Leithead
• Re: [Shadow] URL-based shadows? Travis Leithead
• RE: I18N comments on "Manifest for Web applications" Christiansen, Kenneth R
• RE: I18N comments on "Manifest for Web applications" Phillips, Addison
• RE: I18N comments on "Manifest for Web applications" Christiansen, Kenneth R
• RE: [appmanifest] No direction metadata for 'name' (etc.) [I18N-ISSUE-416] Christiansen, Kenneth R
• [Bug 28246] New: [Shadow]: Disable event capturing through a ShadowRoot bugzilla@jessica.w3.org

Thursday, 19 March 2015

• [appmanifest] appropriate use of ACI [I18N-ISSUE-417] Phillips, Addison
• [appmanifest] No direction metadata for 'name' (etc.) [I18N-ISSUE-416] Phillips, Addison
• [appmanifest] No language metadata for 'name' [I18N-ISSUE-415] Phillips, Addison
• [appmanifest] No means of obtaining correctly localized manifest [I18N-ISSUE-414] Phillips, Addison
• [appmanifest] No localized examples [I18N-ISSUE-413] Phillips, Addison
• [appmanifest] No localization model [I18N-ISSUE-412] Phillips, Addison
• I18N comments on "Manifest for Web applications" Phillips, Addison
• Re: [Shadow] URL-based shadows? Anne van Kesteren
• Re: [Shadow] URL-based shadows? Anne van Kesteren
• Re: [Shadow] URL-based shadows? Ryosuke Niwa

Wednesday, 18 March 2015

• RE: [Shadow] URL-based shadows? Travis Leithead
• Re: [Shadow] URL-based shadows? Dimitri Glazkov
• Minuts IndieUI Teleconference 18 March 2015 Michael Cooper
• RE: [Shadow] URL-based shadows? Travis Leithead
• Re: template namespace attribute proposal Ryosuke Niwa
• Re: [Shadow] URL-based shadows? Ryosuke Niwa
• Re: template namespace attribute proposal Tab Atkins Jr.
• Re: template namespace attribute proposal Ryosuke Niwa
• [Bug 27222] [Shadow]: Define how attributes are handled in shadow DOM bugzilla@jessica.w3.org

Tuesday, 17 March 2015

• IndieUI Teleconference Agenda; 18 March at 21:00Z Janina Sajka
• RE: Access to localhost to be outlawed? SULLIVAN, BRYAN L
• [Bug 27931] Override 'flex' and 'transform' styling bugzilla@jessica.w3.org
• Access to localhost to be outlawed? Anders Rundgren
• Re: template namespace attribute proposal Brian Birtles

Monday, 16 March 2015

• Re: template namespace attribute proposal Tab Atkins Jr.
• Re: template namespace attribute proposal Benjamin Lesh
• Re: [Shadow] URL-based shadows? Dimitri Glazkov
• Re: [Shadow] URL-based shadows? Anne van Kesteren

Sunday, 15 March 2015

• Re: template namespace attribute proposal Austin William Wright

Saturday, 14 March 2015

• Re: template namespace attribute proposal Karl Dubost

Friday, 13 March 2015

• Re: template namespace attribute proposal Jonas Sicking
• Re: template namespace attribute proposal Tab Atkins Jr.
• Re: template namespace attribute proposal Jonas Sicking
• Re: template namespace attribute proposal Tab Atkins Jr.
• Re: template namespace attribute proposal Jonas Sicking
• Re: [Shadow] URL-based shadows? Dimitri Glazkov
• [Bug 28211] New: [Shadow]: A syntax for loading/parsing shadow trees directly from HTML bugzilla@jessica.w3.org
• Re: template namespace attribute proposal Tab Atkins Jr.
• Re: template namespace attribute proposal Benjamin Lesh
• Re: template namespace attribute proposal Tab Atkins Jr.
• Re: [Shadow] URL-based shadows? Travis Leithead
• Re: [Shadow] URL-based shadows? Dimitri Glazkov
• Re: [Shadow] URL-based shadows? Dimitri Glazkov
• [Shadow] URL-based shadows? Travis Leithead

Thursday, 12 March 2015

• Re: template namespace attribute proposal Benjamin Lesh
• Re: template namespace attribute proposal Anne van Kesteren
• Re: template namespace attribute proposal Adam Klein
• RE: template namespace attribute proposal Travis Leithead
• Re: template namespace attribute proposal Anne van Kesteren
• Re: template namespace attribute proposal Adam Klein
• Re: template namespace attribute proposal Benjamin Lesh
• Re: template namespace attribute proposal Anne van Kesteren
• Re: template namespace attribute proposal Ryosuke Niwa
• Re: template namespace attribute proposal Dimitri Glazkov
• Re: CfC: publish WG Note of UI Events; deadline November 14 Arthur Barstow
• Re: template namespace attribute proposal Robin Berjon
• Re: template namespace attribute proposal Anne van Kesteren
• template namespace attribute proposal Benjamin Lesh

Wednesday, 11 March 2015

• FYI: IETF Token Binding Working Group formed (tokbind) Arthur Barstow
• Re: Extending HTMLCanvasElement in Custom Element issue Dimitri Glazkov
• Re: IndieUI Teleconference Agenda; 18 March at 21:00Z Andy Heath
• RE: IndieUI Teleconference Agenda; 18 March at 21:00Z Katie Haritos-Shea GMAIL
• Extending HTMLCanvasElement in Custom Element issue Халитов Кирилл

Tuesday, 10 March 2015

• Re: IndieUI Teleconference Agenda; 18 March at 21:00Z Andy Heath

Wednesday, 11 March 2015

• [UIEvents] telecon minutes 10 March 2015 Travis Leithead

Tuesday, 10 March 2015

• Re: IndieUI Teleconference Agenda; 18 March at 21:00Z White, Jason J
• Re: IndieUI Teleconference Agenda; 18 March at 21:00Z Janina Sajka
• Standardizing autocapitalize Mounir Lamouri
• IndieUI Teleconference Agenda; 18 March at 21:00Z Janina Sajka
• [Bug 28069] [Shadow]: Should Text.getDestinationInsertionPoints() be specified? bugzilla@jessica.w3.org
• [Bug 28185] [Shadow]: TextNode should have getDestinationInsertionPoints() bugzilla@jessica.w3.org
• [Bug 28185] New: [Shadow]: TextNode should have getDestinationInsertionPoints() bugzilla@jessica.w3.org

Monday, 9 March 2015

• [Bug 28157] [Shadow]: Link to CSS Scoping module spec? bugzilla@jessica.w3.org

Saturday, 7 March 2015

• [Bug 28158] New: [Custom]: inflexible extends as fixed element type bugzilla@jessica.w3.org
• [Bug 28157] New: [Shadow]: Link to CSS Scoping module spec? bugzilla@jessica.w3.org

Friday, 6 March 2015

• Re: [manifest] RE: Manifest for web application; review deadline March 5 Anders Rundgren
• RE: [manifest] RE: Manifest for web application; review deadline March 5 Nilsson, Claes1
• RE: [manifest] RE: Manifest for web application; review deadline March 5 Christiansen, Kenneth R
• RE: [manifest] RE: Manifest for web application; review deadline March 5 Nilsson, Claes1
• Re: [manifest] RE: Manifest for web application; review deadline March 5 Kenneth Rohde Christiansen
• Manifest for web application privacy review Nick Doty
• Re: CORS performance Austin William Wright

Thursday, 5 March 2015

• [manifest] RE: Manifest for web application; review deadline March 5 Nilsson, Claes1

Wednesday, 4 March 2015

• Re: [manifest] I18N review in progress Mounir Lamouri

Tuesday, 3 March 2015

• [Bug 28008] [Shadow] Should "Events that are Always Stopped" include destination insertion points? bugzilla@jessica.w3.org

Sunday, 1 March 2015

• [Bug 28117] New: Clarify timeout in case Preflighted CORS requests bugzilla@jessica.w3.org

Friday, 27 February 2015

• Re: Pointer lock spec Florian Bösch

Thursday, 26 February 2015

• Re: Pointer lock spec Vincent Scheib
• [manifest] I18N review in progress Phillips, Addison
• Re: Better focus support for Shadow DOM 河内 隆仁

Wednesday, 25 February 2015

• Re: CORS performance Anne van Kesteren

Tuesday, 24 February 2015

• [admin] Registration for April 24 2015 Web Components f2f meeting; deadline April 10 Arthur Barstow
• Re: CORS performance Jonas Sicking
• Re: Custom elements: synchronous constructors and cloning Dimitri Glazkov
• [Bug 28092] New: [Custom]: Clarify in informative note that cloning/importing also enqueues created callback bugzilla@jessica.w3.org
• Re: Custom elements: synchronous constructors and cloning Dimitri Glazkov
• Re: Custom elements: synchronous constructors and cloning Anne van Kesteren
• Re: Custom elements: synchronous constructors and cloning Dimitri Glazkov
• Re: CORS performance Anne van Kesteren
• Re: Custom elements: synchronous constructors and cloning Anne van Kesteren

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? bugzilla@jessica.w3.org
• Re: Custom elements: synchronous constructors and cloning Ryosuke Niwa
• Re: CORS performance Jonas Sicking
• Re: CORS performance Anne van Kesteren
• Re: CORS performance proposal Jonas Sicking
• Re: CORS performance proposal Jonas Sicking
• Re: CORS performance Jonas Sicking
• Re: CORS performance Henri Sivonen
• Re: Custom elements: synchronous constructors and cloning Boris Zbarsky
• Custom elements: synchronous constructors and cloning Anne van Kesteren
• [Bug 28079] New: [Shadow]: inappropriate reference to CSS3-UI nav-index spec in focus navigation order bugzilla@jessica.w3.org

Sunday, 22 February 2015

• Re: CORS performance proposal Anne van Kesteren

Saturday, 21 February 2015

• [Bug 28069] New: [Shadow]: Should Text.getDestinationInsertionPoints() be specified? bugzilla@jessica.w3.org
• [Bug 28067] New: DOMStringList has been removed from DOM bugzilla@jessica.w3.org
• Re: Standardising canvas-driven background images Elliott Sprehn
• Re: CORS performance proposal Martin Thomson
• Re: CORS performance proposal Anne van Kesteren

Friday, 20 February 2015

• Re: Standardising canvas-driven background images Tab Atkins Jr.
• Re: Standardising canvas-driven background images Matthew Robb
• Re: Web Components F2F in April 2015 Dimitri Glazkov
• Re: Web Components F2F in April 2015 Dimitri Glazkov
• Re: CORS performance proposal Jonas Sicking
• Re: Standardising canvas-driven background images Tab Atkins Jr.
• Re: Standardising canvas-driven background images Matthew Robb
• Standardising canvas-driven background images Ashley Gullen
• Re: CORS performance proposal Anne van Kesteren
• Re: CORS performance proposal Bjoern Hoehrmann
• Re: CORS performance proposal Martin Thomson

Thursday, 19 February 2015

• Re: CORS performance Jonas Sicking
• Re: The futile war between Native and Web Jeffrey Walton
• Re: CORS performance proposal Bjoern Hoehrmann
• Re: CORS performance proposal Brian Smith
• Re: CORS explained simply Arthur Barstow
• Re: CORS performance Bjoern Hoehrmann
• Re: [WebCrypto.Next] Any ideas on how to proceed? Harry Halpin
• Re: The futile war between Native and Web Anne van Kesteren
• Re: CORS performance henry.story@bblfish.net
• CORS explained simply henry.story@bblfish.net
• Re: The futile war between Native and Web Jeffrey Walton
• Re: CORS performance Martin Thomson
• Re: CORS performance proposal Martin Thomson
• Re: The futile war between Native and Web Michaela Merz
• Re: CORS performance Brad Hill
• Re: CORS performance proposal Jonas Sicking
• Re: CORS performance Jonas Sicking
• Re: CORS performance Jonas Sicking
• Re: The futile war between Native and Web Jeffrey Walton
• Re: The futile war between Native and Web Bjoern Hoehrmann
• Re: The futile war between Native and Web Jeffrey Walton
• Re: The futile war between Native and Web Anne van Kesteren
• Re: The futile war between Native and Web Jeffrey Walton
• Re: Web Components F2F in April 2015 Dimitri Glazkov
• Re: Staying on Topic [Was: Re: WebPortable/PlatformProprietary - An Established Concept] Arthur Barstow
• Re: Staying on Topic [Was: Re: WebPortable/PlatformProprietary - An Established Concept] Anders Rundgren
• Staying on Topic [Was: Re: WebPortable/PlatformProprietary - An Established Concept] Arthur Barstow
• WebPortable/PlatformProprietary - An Established Concept Anders Rundgren
• Re: CORS performance proposal Dale Harvey
• Re: CORS performance James M Snell
• Re: CORS performance Brian Smith
• Re: CORS performance Dale Harvey
• Re: CORS performance Dale Harvey
• CORS performance proposal Anne van Kesteren
• Re: Web Components F2F in April 2015 Arthur Barstow
• Re: CORS performance Brian Smith
• Re: CORS performance Dale Harvey
• Re: CORS performance Brian Smith
• Re: CORS performance Dale Harvey
• Re: CORS performance Brian Smith
• Re: CORS performance Anne van Kesteren
• Re: CORS performance Dale Harvey
• Re: CORS performance Brian Smith
• Re: CORS performance Anne van Kesteren
• Re: Better focus support for Shadow DOM chaals@yandex-team.ru
• Re: CORS performance Anne van Kesteren
• Re: CORS performance Brian Smith
• Re: CORS performance Mike West
• Re: Better focus support for Shadow DOM 河内 隆仁
• [Bug 28054] New: Focus on shadow host should slide to its inner focusable node bugzilla@jessica.w3.org

Wednesday, 18 February 2015

• Mozilla on Privileged Hosted Apps Anders Rundgren
• Web Components F2F in April 2015 Dimitri Glazkov
• [Bug 28051] [imports]: showing <dialog> from import bugzilla@jessica.w3.org
• Re: Showing <dialog> from HTML import Ashley Gullen
• Re: Showing <dialog> from HTML import Dimitri Glazkov
• Showing <dialog> from HTML import Ashley Gullen
• Re: [WebCrypto.Next] Any ideas on how to proceed? Anders Rundgren
• Re: [WebCrypto.Next] Any ideas on how to proceed? David Leon Gil
• [WebCrypto.Next] Any ideas on how to proceed? Anders Rundgren
• Re: CORS performance Eric Mill

Tuesday, 17 February 2015

• Re: CORS performance Bjoern Hoehrmann
• Re: CORS performance Devdatta Akhawe
• Re: CORS performance Brad Hill
• Re: CORS performance Anne van Kesteren
• Re: CORS performance Bjoern Hoehrmann
• Updated: Running trusted code in the untrusted web Anders Rundgren
• CORS performance Anne van Kesteren

Saturday, 14 February 2015

• Is clearUndo() in UndoManager the wrong way round? Simon

Tuesday, 17 February 2015

• Running trusted code in the untrusted web - A writeup Anders Rundgren

Monday, 16 February 2015

• Re: The futile war between Native and Web Anders Rundgren
• Re: The futile war between Native and Web Anne van Kesteren
• Re: The futile war between Native and Web Anders Rundgren
• Re: The futile war between Native and Web Jeffrey Walton
• Re: The futile war between Native and Web Michaela Merz
• Re: The futile war between Native and Web Anders Rundgren
• Re: The futile war between Native and Web Michaela Merz
• Re: The futile war between Native and Web Anders Rundgren
• Re: The futile war between Native and Web Anne van Kesteren
• Re: The futile war between Native and Web Jeffrey Walton
• Re: The futile war between Native and Web Florian Bösch
• Re: The futile war between Native and Web Jeffrey Walton
• Re: The futile war between Native and Web Jeffrey Walton
• Re: The futile war between Native and Web Florian Bösch
• Re: The futile war between Native and Web Anders Rundgren
• Re: The futile war between Native and Web Florian Bösch
• Re: Base Template (Was Re: Minimum viable custom elements) Hayato Ito
• [Bug 28031] Does the destination insertion points include Shadow IP without older trees? bugzilla@jessica.w3.org
• [Bug 28031] New: Does the destination insertion points include Shadow IP without older trees? bugzilla@jessica.w3.org

Sunday, 15 February 2015

• Re: The futile war between Native and Web Jeffrey Walton
• The futile war between Native and Web Anders Rundgren
• Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest Brendan Eich

Friday, 13 February 2015

• Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest Marc Fawzi
• RE: [clipboard API] platform integration stuff - in spec or out of scope? Ben Peters
• RE: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest Travis Leithead
• Re: Base Template (Was Re: Minimum viable custom elements) Jan Miksovsky
• Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest Brendan Eich
• Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest Brendan Eich
• [Bug 28008] New: [Shadow] Should "Events that are Always Stopped" include destination insertion points? bugzilla@jessica.w3.org
• RfC: Manifest for web application; review deadline March 5 Arthur Barstow

Thursday, 12 February 2015

• Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest Brendan Eich
• Re: Base Template (Was Re: Minimum viable custom elements) Dimitri Glazkov
• Base Template (Was Re: Minimum viable custom elements) Ryosuke Niwa

Wednesday, 11 February 2015

• RE: [Unbearable] IETF seeking feedback on proposed "Token Binding" Working Group Andrei Popov

Thursday, 12 February 2015

• Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest Marc Fawzi
• Re: Minimum viable custom elements Steve Faulkner
• Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest Aryeh Gregor
• Re: Minimum viable custom elements Anne van Kesteren
• Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest David Rajchenbach-Teller
• Re: Minimum viable custom elements Steve Faulkner
• Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest Boris Zbarsky
• Re: [clipboard API] platform integration stuff - in spec or out of scope? James M. Greene
• Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest Tab Atkins Jr.
• Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest Marc Fawzi
• Re: [clipboard] Feature detect Clipboard API support? Glenn Maynard

Wednesday, 11 February 2015

• Re: [clipboard API] platform integration stuff - in spec or out of scope? Hallvord Reiar Michaelsen Steen
• Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest Boris Zbarsky
• Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest Brendan Eich
• Re: [Unbearable] IETF seeking feedback on proposed "Token Binding" Working Group Anne van Kesteren
• Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest Marc Fawzi
• Re: [clipboard] Feature detect Clipboard API support? Michaela Merz
• [clipboard] Feature detect Clipboard API support? James M. Greene
• Re: [clipboard API] platform integration stuff - in spec or out of scope? James M. Greene
• Re: IETF seeking feedback on proposed "Token Binding" Working Group Anne van Kesteren
• IETF seeking feedback on proposed "Token Binding" Working Group Arthur Barstow
• Re: do not deprecate synchronous XMLHttpRequest Brendan Eich
• Re: do not deprecate synchronous XMLHttpRequest Marc Fawzi
• Re: do not deprecate synchronous XMLHttpRequest Brendan Eich
• Re: do not deprecate synchronous XMLHttpRequest Marc Fawzi
• Re: do not deprecate synchronous XMLHttpRequest Marc Fawzi
• [DOM3Events/UIEvents] Minutes from 10 Feb 2015 teleconference Travis Leithead
• Re: do not deprecate synchronous XMLHttpRequest Brendan Eich

Tuesday, 10 February 2015

• Re: do not deprecate synchronous XMLHttpRequest Marc Fawzi
• Re: do not deprecate synchronous XMLHttpRequest Marc Fawzi
• Re: do not deprecate synchronous XMLHttpRequest Michaela Merz
• Re: do not deprecate synchronous XMLHttpRequest Jonas Sicking
• Standards wonks and developers working together [Was: Re: do not deprecate synchronous XMLHttpRequest] Arthur Barstow
• Re: do not deprecate synchronous XMLHttpRequest Jonas Sicking
• Staying on topic [Was: Re: do not deprecate synchronous XMLHttpRequest] Arthur Barstow
• Re: do not deprecate synchronous XMLHttpRequest Marc Fawzi
• Re: do not deprecate synchronous XMLHttpRequest Michaela Merz
• Re: do not deprecate synchronous XMLHttpRequest Marc Fawzi
• Re: do not deprecate synchronous XMLHttpRequest Michaela Merz
• Re: do not deprecate synchronous XMLHttpRequest Florian Bösch
• Re: do not deprecate synchronous XMLHttpRequest Elliott Sprehn
• Re: do not deprecate synchronous XMLHttpRequest Marc Fawzi
• Re: do not deprecate synchronous XMLHttpRequest Marc Fawzi
• Re: do not deprecate synchronous XMLHttpRequest Elliott Sprehn
• Re: do not deprecate synchronous XMLHttpRequest Boris Zbarsky
• Re: do not deprecate synchronous XMLHttpRequest Marc Fawzi
• Re: do not deprecate synchronous XMLHttpRequest Michaela Merz
• Re: do not deprecate synchronous XMLHttpRequest Marc Fawzi
• Re: do not deprecate synchronous XMLHttpRequest George Calvert
• Re: do not deprecate synchronous XMLHttpRequest Michaela Merz
• [Bug 27994] New: [Shadow]: Distribution result usage examples bugzilla@jessica.w3.org
• Re: do not deprecate synchronous XMLHttpRequest Glenn Adams
• Re: [webcomponents]: Let's reach consensus on Shadow DOM Anne van Kesteren
• Re: do not deprecate synchronous XMLHttpRequest Ashley Gullen

Monday, 9 February 2015

• Re: do not deprecate synchronous XMLHttpRequest George Calvert
• Re: Violation of mail list policy [Was: Fwd: Re: do not deprecate synchronous XMLHttpRequest] Michaela Merz
• Violation of mail list policy [Was: Fwd: Re: do not deprecate synchronous XMLHttpRequest] Arthur Barstow
• RE: Minimum viable custom elements Jonathan Bond-Caron
• [Bug 27986] New: Specify exact length of array returned by Navigator.getGamepads() bugzilla@jessica.w3.org

Sunday, 8 February 2015

• Re: [webcomponents]: Let's reach consensus on Shadow DOM Ryosuke Niwa
• Re: [webcomponents]: Let's reach consensus on Shadow DOM Ryosuke Niwa

Saturday, 7 February 2015

• [Bug 27978] New: [Custom]: attachedCallback has no protocol for indicating that the custom tag is not applicable in this context bugzilla@jessica.w3.org
• [Bug 27977] New: [Custom]: mixin pattern: custom elements should be able to extend any base tag with is= bugzilla@jessica.w3.org
• [Bug 27976] New: [Custom]: type extensions should be available as custom tags, not only through <baseTag is="..."> bugzilla@jessica.w3.org
• [Bug 27975] New: [Custom]: No way to unregister a component bugzilla@jessica.w3.org
• Re: Are web components *seriously* not namespaced? Melvin Carvalho
• Re: Are web components *seriously* not namespaced? Kurt Cagle

Friday, 6 February 2015

• [webcomponents]: Let's reach consensus on Shadow DOM Dimitri Glazkov
• Re: Are web components *seriously* not namespaced? Austin William Wright
• Re: Are web components *seriously* not namespaced? Kurt Cagle
• Re: do not deprecate synchronous XMLHttpRequest Marc Fawzi
• Re: do not deprecate synchronous XMLHttpRequest Michaela Merz
• Re: do not deprecate synchronous XMLHttpRequest Michaela Merz
• Re: do not deprecate synchronous XMLHttpRequest Florian Bösch
• Re: do not deprecate synchronous XMLHttpRequest Michaela Merz
• Re: do not deprecate synchronous XMLHttpRequest Ryosuke Niwa
• Re: do not deprecate synchronous XMLHttpRequest Marc Fawzi
• Re: do not deprecate synchronous XMLHttpRequest Michaela Merz
• Re: Are web components *seriously* not namespaced? Dimitri Glazkov
• Re: do not deprecate synchronous XMLHttpRequest James M. Greene
• Re: do not deprecate synchronous XMLHttpRequest Florian Bösch
• Re: do not deprecate synchronous XMLHttpRequest Michaela Merz
• Mail list Etiquette [Was: Re: Shadow tree style isolation primitive] Arthur Barstow
• Re: Are web components *seriously* not namespaced? Arthur Barstow
• Re: Are web components *seriously* not namespaced? Glen
• Re: Allow custom headers (Websocket API) Takeshi Yoshino

Thursday, 5 February 2015

• do not deprecate synchronous XMLHttpRequest Gregg Tracton

Friday, 6 February 2015

• Re: Shadow tree style isolation primitive Dimitri Glazkov
• Re: [IndexedDB] When is an error event dispatched at a transcation? Glen Huang
• Re: Shadow tree style isolation primitive Ryosuke Niwa
• Re: Shadow tree style isolation primitive Maciej Stachowiak

Thursday, 5 February 2015

• Re: Shadow tree style isolation primitive Dimitri Glazkov
• Re: Shadow tree style isolation primitive Bjoern Hoehrmann
• Re: Shadow tree style isolation primitive Ryosuke Niwa
• Re: Shadow tree style isolation primitive Dimitri Glazkov
• Re: Are web components *seriously* not namespaced? Tab Atkins Jr.
• Re: Are web components *seriously* not namespaced? Kurt Cagle
• Re: Are web components *seriously* not namespaced? Tab Atkins Jr.
• Re: Minimum viable custom elements Tab Atkins Jr.
• Re: Shadow tree style isolation primitive Marc Fawzi
• Re: Minimum viable custom elements Erik Bryn
• Re: Shadow tree style isolation primitive Dimitri Glazkov
• Re: [IndexedDB] When is an error event dispatched at a transcation? Joshua Bell
• Re: Shadow tree style isolation primitive Dimitri Glazkov
• Re: Minimum viable custom elements Chris Bateman
• Re: Are web components *seriously* not namespaced? Glen
• Re: Are web components *seriously* not namespaced? Melvin Carvalho
• Re: Allow custom headers (Websocket API) Bjoern Hoehrmann
• Re: Allow custom headers (Websocket API) Michiel De Mey
• Re: Allow custom headers (Websocket API) Takeshi Yoshino
• Re: Allow custom headers (Websocket API) Anne van Kesteren
• Re: Allow custom headers (Websocket API) Takeshi Yoshino
• Re: Allow custom headers (Websocket API) Florian Bösch
• Re: Are web components *seriously* not namespaced? Glen
• Re: Allow custom headers (Websocket API) Bjoern Hoehrmann
• Re: Shadow tree style isolation primitive Olli Pettay
• Re: Allow custom headers (Websocket API) Florian Bösch
• Re: Allow custom headers (Websocket API) Takeshi Yoshino
• Re: Allow custom headers (Websocket API) Anne van Kesteren
• Re: Allow custom headers (Websocket API) Florian Bösch
• Re: Allow custom headers (Websocket API) Takeshi Yoshino
• Re: Allow custom headers (Websocket API) Florian Bösch
• Re: Allow custom headers (Websocket API) Anne van Kesteren
• Re: Allow custom headers (Websocket API) Florian Bösch
• Re: Allow custom headers (Websocket API) Bjoern Hoehrmann
• Re: Allow custom headers (Websocket API) Anne van Kesteren
• Re: Shadow tree style isolation primitive Anne van Kesteren
• Re: Allow custom headers (Websocket API) Florian Bösch
• Re: Allow custom headers (Websocket API) Anne van Kesteren
• [IndexedDB] When is an error event dispatched at a transcation? Glen Huang
• Re: Are web components *seriously* not namespaced? Tab Atkins Jr.
• Re: Are web components *seriously* not namespaced? Tab Atkins Jr.
• Re: Allow custom headers (Websocket API) Florian Bösch
• Re: Allow custom headers (Websocket API) Anne van Kesteren
• Re: Allow custom headers (Websocket API) Florian Bösch
• Re: Allow custom headers (Websocket API) Anne van Kesteren
• Re: Allow custom headers (Websocket API) Michiel De Mey
• Re: Allow custom headers (Websocket API) Anne van Kesteren
• Allow custom headers (Websocket API) Michiel De Mey
• Re: Are web components *seriously* not namespaced? Anne van Kesteren
• [Bug 27965] New: [Shadow]: Shadow host with tabindex=-1, all descendent tree should be ignored for tab navigation bugzilla@jessica.w3.org
• Re: Are web components *seriously* not namespaced? Benjamin Goering
• Re: Are web components *seriously* not namespaced? Tab Atkins Jr.
• Re: Are web components *seriously* not namespaced? Kurt Cagle
• Re: Shadow tree style isolation primitive Tab Atkins Jr.
• Re: Shadow tree style isolation primitive Tab Atkins Jr.
• Re: Shadow tree style isolation primitive Dimitri Glazkov
• Re: Shadow tree style isolation primitive Olli Pettay

Wednesday, 4 February 2015

• Re: Shadow tree style isolation primitive Ryosuke Niwa
• Re: Shadow tree style isolation primitive Tab Atkins Jr.
• Re: Shadow tree style isolation primitive Tab Atkins Jr.
• Re: Are web components *seriously* not namespaced? Tab Atkins Jr.
• Re: Are web components *seriously* not namespaced? Glen
• Re: Are web components *seriously* not namespaced? William Edney
• Re: Are web components *seriously* not namespaced? Glen
• Re: Are web components *seriously* not namespaced? Dimitri Glazkov
• Re: Are web components *seriously* not namespaced? Glenn Adams
• Are web components *seriously* not namespaced? Glen
• Re: Minimum viable custom elements Ryosuke Niwa
• Re: Minimum viable custom elements Steve Faulkner
• Re: Minimum viable custom elements Alice Boxhall
• Re: Minimum viable custom elements Ryosuke Niwa
• Re: Minimum viable custom elements Ryosuke Niwa
• Re: Minimum viable custom elements Chris Bateman
• Re: Minimum viable custom elements Ryosuke Niwa
• Re: Minimum viable custom elements Alice Boxhall
• Re: Minimum viable custom elements Brian Kardell
• Re: Minimum viable custom elements Alice Boxhall
• Re: Minimum viable custom elements Ryosuke Niwa
• Re: Minimum viable custom elements Ryosuke Niwa
• Re: Minimum viable custom elements Brian Kardell
• Re: Minimum viable custom elements Chris Bateman
• Re: Minimum viable custom elements Steve Faulkner
• Re: Minimum viable custom elements Ryosuke Niwa
• Re: Minimum viable custom elements Ryosuke Niwa
• Re: Shadow tree style isolation primitive Ryosuke Niwa
• RE: Minimum viable custom elements Domenic Denicola
• Re: Minimum viable custom elements Anne van Kesteren
• Re: Shadow tree style isolation primitive Brian Kardell
• Re: Minimum viable custom elements Chris Bateman
• Re: Shadow tree style isolation primitive Olli Pettay
• Re: [IndexedDB] link to Editor's draft is a 404 Tobie Langel
• Re: Shadow tree style isolation primitive Olli Pettay

Tuesday, 3 February 2015

• Ted Dinklocker Introduction Ted Dinklocker

Wednesday, 4 February 2015

• Re: [IndexedDB] link to Editor's draft is a 404 Tobie Langel
• Re: [IndexedDB] link to Editor's draft is a 404 Michael[tm] Smith

Tuesday, 3 February 2015

• Re: Minimum viable custom elements Ryosuke Niwa
• Re: Shadow tree style isolation primitive Dimitri Glazkov
• Re: Minimum viable custom elements Chris Bateman
• Re: Shadow tree style isolation primitive Brian Kardell
• PSA: publishing new WD of Service Workers on February 5 Arthur Barstow
• RE: IndieUI Teleconference Agenda; 4 February at 22:00Z for 60 minutes Katie Haritos-Shea GMAIL
• Re: Shadow tree style isolation primitive Olli Pettay
• IndieUI Teleconference Agenda; 4 February at 22:00Z for 60 minutes Janina Sajka
• Re: Minimum viable custom elements Ryosuke Niwa

Monday, 2 February 2015

• Re: Shadow tree style isolation primitive Dimitri Glazkov
• Re: Toward more productive f2f meetings [Was:Re: Feedback needed for April 2015 face-to-face location by *January 27, 2015*] Dimitri Glazkov
• Re: Toward more productive f2f meetings [Was:Re: Feedback needed for April 2015 face-to-face location by *January 27, 2015*] Anne van Kesteren
• Re: Minimum viable custom elements Chris Bateman

Saturday, 31 January 2015

• Re: Minimum viable custom elements Chris Bateman

Friday, 30 January 2015

• Re: Minimum viable custom elements Alice Boxhall
• Re: Minimum viable custom elements Alice Boxhall

Monday, 2 February 2015

• Toward more productive f2f meetings [Was:Re: Feedback needed for April 2015 face-to-face location by *January 27, 2015*] Arthur Barstow
• Re: [IndexedDB] link to Editor's draft is a 404 Arthur Barstow
• [IndexedDB] link to Editor's draft is a 404 Tobie Langel
• Re: Minimum viable custom elements Anne van Kesteren
• Re: Minimum viable custom elements Anne van Kesteren

Saturday, 31 January 2015

• Re: [clipboard API] platform integration stuff - in spec or out of scope? Hallvord Reiar Michaelsen Steen
• Re: [clipboard API] platform integration stuff - in spec or out of scope? Paul Libbrecht
• Re: Minimum viable custom elements Elliott Sprehn
• Re: [clipboard API] platform integration stuff - in spec or out of scope? Anne van Kesteren
• [clipboard API] platform integration stuff - in spec or out of scope? Hallvord Reiar Michaelsen Steen
• Re: Minimum viable custom elements Anne van Kesteren
• Re: Minimum viable custom elements Anne van Kesteren
• Re: Minimum viable custom elements Anne van Kesteren
• Re: Minimum viable custom elements Tantek Çelik
• Re: Minimum viable custom elements fantasai
• Re: Minimum viable custom elements Ryosuke Niwa
• Re: Minimum viable custom elements Ryosuke Niwa

Friday, 30 January 2015

• Re: Security use cases for packaging Chris Palmer
• Re: Security use cases for packaging Daniel Kahn Gillmor
• Re: Minimum viable custom elements Anne van Kesteren
• [Bug 27931] New: Override 'flex' and 'transform' styling bugzilla@jessica.w3.org
• Re: Minimum viable custom elements Steve Faulkner
• Re: =[xhr] Frederik Braun
• Re: Minimum viable custom elements Bruce Lawson

Thursday, 29 January 2015

• =[xhr] LOUIFI, Bruno

Friday, 30 January 2015

• Re: Security use cases for packaging Yan Zhu
• Re: Security use cases for packaging Yan Zhu
• Re: Security use cases for packaging Michaela Merz
• Re: Security use cases for packaging Daniel Kahn Gillmor
• Re: Security use cases for packaging Yan Zhu
• Re: Security use cases for packaging Deian Stefan

Thursday, 29 January 2015

• Re: Security use cases for packaging Ilya Grigorik
• Re: Security use cases for packaging Devdatta Akhawe
• Re: Security use cases for packaging Brad Hill
• Re: Security use cases for packaging Yan Zhu
• Re: Security use cases for packaging Chris Palmer
• Security use cases for packaging Yan Zhu
• Re: Minimum viable custom elements Brian Kardell
• Re: Minimum viable custom elements Ryosuke Niwa
• Re: Minimum viable custom elements Bruce Lawson
• Re: Minimum viable custom elements Brian Kardell
• Re: Minimum viable custom elements Elliott Sprehn
• Re: Minimum viable custom elements Brian Kardell
• Re: Minimum viable custom elements Steve Faulkner
• Re: Minimum viable custom elements Dimitri Glazkov
• Re: Minimum viable custom elements Anne van Kesteren
• Re: Minimum viable custom elements Bruce Lawson
• Re: Minimum viable custom elements Steve Faulkner
• CfC: publish Wide Review Draft of Manifest for web application; deadline Feb 5 Arthur Barstow
• Custom elements and the HTML parser Anne van Kesteren

Wednesday, 28 January 2015

• Re: [Selection] Support of Multiple Selection (was: Should selection.getRangeAt return a clone or a reference?) Aryeh Gregor
• Re: [Selection] Should selection.getRangeAt return a clone or a reference? Aryeh Gregor
• [Bug 27915] New: Clients of WebSockets are not NTP synced (and there is no NTP-alike spec) bugzilla@jessica.w3.org
• Re: Custom element design with ES6 classes and Element constructors Yehuda Katz
• RE: Custom element design with ES6 classes and Element constructors Domenic Denicola
• Re: Custom element design with ES6 classes and Element constructors Elliott Sprehn
• RE: Custom element design with ES6 classes and Element constructors Domenic Denicola
• Re: Custom element design with ES6 classes and Element constructors Elliott Sprehn
• Re: Custom element design with ES6 classes and Element constructors Goktug Gokdogan
• [DOM3Events/UIEvents] Minutes from 27 Jan 2015 teleconference Travis Leithead
• [Bug 27914] New: [Custom]: Typo instantation ---> instantiation bugzilla@jessica.w3.org

Tuesday, 27 January 2015

• Re: oldNode.replaceWith(...collection) edge case Jonas Sicking
• Re: [Selection] Should selection.getRangeAt return a clone or a reference? Koji Ishii
• Re: [Selection] Support of Multiple Selection (was: Should selection.getRangeAt return a clone or a reference?) Koji Ishii
• Re: oldNode.replaceWith(...collection) edge case Glen Huang
• Re: oldNode.replaceWith(...collection) edge case Anne van Kesteren

Monday, 26 January 2015

• Fwd: Getting to Zaragoza (may be harder) chaals@yandex-team.ru

Sunday, 25 January 2015

• [WebSocket API]: Missing request header fields option Martin Altenstedt

Monday, 26 January 2015

• Re: <webview> API common subset 陳侃如

Sunday, 25 January 2015

• [admin] Important: Feedback needed for April 2015 face-to-face location by *January 27, 2015* Arthur Barstow
• Re: [Selection] Should selection.getRangeAt return a clone or a reference? Aryeh Gregor
• Re: [Selection] Support of Multiple Selection (was: Should selection.getRangeAt return a clone or a reference?) Aryeh Gregor

Saturday, 24 January 2015

• Re: [Selection] Should selection.getRangeAt return a clone or a reference? Mats Palmgren
• Re: [Selection] Support of Multiple Selection (was: Should selection.getRangeAt return a clone or a reference?) Tab Atkins Jr.
• Re: [Selection] Should selection.getRangeAt return a clone or a reference? Aryeh Gregor
• Re: [Selection] Should selection.getRangeAt return a clone or a reference? Aryeh Gregor
• Re: [Selection] Support of Multiple Selection (was: Should selection.getRangeAt return a clone or a reference?) Aryeh Gregor
• Re: [Selection] Should selection.getRangeAt return a clone or a reference? Koji Ishii
• Re: [Selection] Should selection.getRangeAt return a clone or a reference? Olli Pettay
• Re: [Selection] Should selection.getRangeAt return a clone or a reference? Koji Ishii

Friday, 23 January 2015

• FYI: Change in my affiliation Arthur Barstow
• Re: <webview> API common subset Olli Pettay
• Re: <webview> API common subset Arthur Barstow
• <webview> API common subset 陳侃如
• [Bug 27876] [Shadow] It is not defined what event.path actually should return bugzilla@jessica.w3.org

Thursday, 22 January 2015

• [Bug 26181] Spec should specify the presentation of the array returned by navigator.getGamepads() w.r.t "holes" bugzilla@jessica.w3.org
• Re: oldNode.replaceWith(...collection) edge case Jonas Sicking
• Re: oldNode.replaceWith(...collection) edge case Glen Huang

Wednesday, 21 January 2015

• RE: Better focus support for Shadow DOM Domenic Denicola
• [Bug 27876] New: [Shadow] It is not defined what event.path actually should return bugzilla@jessica.w3.org
• Re: [Selection] Should selection.getRangeAt return a clone or a reference? Mats Palmgren
• Re: oldNode.replaceWith(...collection) edge case Boris Zbarsky
• Re: oldNode.replaceWith(...collection) edge case Glen Huang
• Re: oldNode.replaceWith(...collection) edge case Simon Pieters
• Re: Better focus support for Shadow DOM 河内 隆仁
• Re: oldNode.replaceWith(...collection) edge case Boris Zbarsky
• Re: Feedback needed for April 2015 face-to-face location by *January 27, 2015* chaals@yandex-team.ru
• [D3E/UIEvents] Transferring related Bugzilla bugs to github issues Travis Leithead

Tuesday, 20 January 2015

• Re: oldNode.replaceWith(...collection) edge case Glen Huang
• IndieUI Teleconference Agenda; 21 January at 22:00Z for 60 minutes Janina Sajka
• Re: Feedback needed for April 2015 face-to-face location by *January 27, 2015* Philippe Le Hegaret
• Re: Feedback needed for April 2015 face-to-face location by *January 27, 2015* chaals@yandex-team.ru
• Feedback needed for April 2015 face-to-face location by *January 27, 2015* Philippe Le Hegaret
• Re: oldNode.replaceWith(...collection) edge case Simon Pieters
• Re: oldNode.replaceWith(...collection) edge case Glen Huang
• Re: oldNode.replaceWith(...collection) edge case Anne van Kesteren
• Re: oldNode.replaceWith(...collection) edge case Glen Huang
• [Bug 27865] New: Interaction issues between fullscreen and <dialog> bugzilla@jessica.w3.org
• Re: oldNode.replaceWith(...collection) edge case Anne van Kesteren
• [Bug 27863] New: Not need to specify moving element in top layer and fullscreen stack bugzilla@jessica.w3.org

Monday, 19 January 2015

• Re: Minimum viable custom elements Anne van Kesteren
• Re: Defining a constructor for Element and friends Anne van Kesteren
• Re: Defining a constructor for Element and friends Simon Pieters
• [Bug 27844] [Shadow]: Element.createShadowRoot() throws an exception for some elements bugzilla@jessica.w3.org

Thursday, 15 January 2015

• Range.getClientRanges()? Justin Fagnani

Sunday, 18 January 2015

• Re: oldNode.replaceWith(...collection) edge case Glen Huang
• Re: oldNode.replaceWith(...collection) edge case Glen Huang

Saturday, 17 January 2015

• Re: [Selection] Support of Multiple Selection (was: Should selection.getRangeAt return a clone or a reference?) Olivier Forget
• Re: [Selection] Should selection.getRangeAt return a clone or a reference? Aryeh Gregor
• Re: [Selection] Support of Multiple Selection (was: Should selection.getRangeAt return a clone or a reference?) Aryeh Gregor
• Re: Minimum viable custom elements Ryosuke Niwa
• Re: Minimum viable custom elements Dimitri Glazkov

Friday, 16 January 2015

• Re: Minimum viable custom elements Ryosuke Niwa
• RE: Defining a constructor for Element and friends Domenic Denicola
• RE: Minimum viable custom elements Domenic Denicola
• Re: Minimum viable custom elements Ryosuke Niwa
• Re: Minimum viable custom elements Ryosuke Niwa
• Re: Minimum viable custom elements Anne van Kesteren
• Re: Minimum viable custom elements Steve Faulkner
• Re: Minimum viable custom elements Anne van Kesteren
• Re: Minimum viable custom elements Steve Faulkner
• RfC: Manifest for web application Arthur Barstow
• Re: oldNode.replaceWith(...collection) edge case Glen Huang
• Re: Minimum viable custom elements Anne van Kesteren
• Re: Minimum viable custom elements Anne van Kesteren
• Re: Defining a constructor for Element and friends Anne van Kesteren
• Re: Custom element design with ES6 classes and Element constructors Anne van Kesteren
• [Bug 27844] New: [Shadow]: Element.createShadowRoot() throws an exception for some elements bugzilla@jessica.w3.org
• Re: Minimum viable custom elements Steve Faulkner
• Re: Minimum viable custom elements Steve Faulkner
• Re: Better focus support for Shadow DOM 河内 隆仁
• Re: oldNode.replaceWith(...collection) edge case Glen Huang
• Re: oldNode.replaceWith(...collection) edge case Anne van Kesteren
• Re: oldNode.replaceWith(...collection) edge case Glen Huang
• oldNode.replaceWith(...collection) edge case Glen Huang
• Re: Minimum viable custom elements Dimitri Glazkov
• Re: Minimum viable custom elements Ryosuke Niwa
• Re: Minimum viable custom elements Dimitri Glazkov
• Re: Minimum viable custom elements Ryosuke Niwa
• Re: Minimum viable custom elements Brian Kardell

Thursday, 15 January 2015

• RE: Minimum viable custom elements Domenic Denicola
• RE: Defining a constructor for Element and friends Domenic Denicola
• Re: Minimum viable custom elements Edward O'Connor
• RE: Minimum viable custom elements Domenic Denicola
• Re: Minimum viable custom elements Ryosuke Niwa
• Re: Minimum viable custom elements Tab Atkins Jr.
• Re: CfC: publish FPWD of Packaging on the Web; deadline November 3 Arthur Barstow
• Re: Minimum viable custom elements Ryosuke Niwa
• Re: Minimum viable custom elements Brian Kardell
• RE: Minimum viable custom elements Domenic Denicola
• Re: Custom element design with ES6 classes and Element constructors Dimitri Glazkov
• Re: Minimum viable custom elements Dimitri Glazkov
• Re: Custom element design with ES6 classes and Element constructors Dimitri Glazkov
• Re: Minimum viable custom elements Dimitri Glazkov
• RE: Custom element design with ES6 classes and Element constructors Domenic Denicola
• Re: Custom element design with ES6 classes and Element constructors Yehuda Katz
• Re: Custom element design with ES6 classes and Element constructors Dimitri Glazkov
• Re: Minimum viable custom elements Kenneth Rohde Christiansen
• Re: Minimum viable custom elements Anne van Kesteren
• Re: Minimum viable custom elements Kenneth Rohde Christiansen
• Re: Minimum viable custom elements Anne van Kesteren
• Re: Custom element design with ES6 classes and Element constructors Erik Arvidsson
• Re: Minimum viable custom elements Anne van Kesteren
• Re: Custom element design with ES6 classes and Element constructors Anne van Kesteren
• Re: Custom element design with ES6 classes and Element constructors Dmitry Lomov
• Re: Custom element design with ES6 classes and Element constructors Yehuda Katz
• [Bug 27836] New: Scripts in HTML Imports should be scoped to the import (treat imports as script modules) bugzilla@jessica.w3.org

Wednesday, 14 January 2015

• RE: Custom element design with ES6 classes and Element constructors Domenic Denicola
• [Bug 27835] New: registerElement() should be scoped to modules bugzilla@jessica.w3.org
• Re: Minimum viable custom elements Dimitri Glazkov
• Re: Minimum viable custom elements Ryosuke Niwa
• RE: Minimum viable custom elements Domenic Denicola
• Re: Minimum viable custom elements Ryosuke Niwa
• Re: Minimum viable custom elements Ryosuke Niwa
• Re: Minimum viable custom elements Dimitri Glazkov
• RE: Minimum viable custom elements Domenic Denicola
• Re: Custom element design with ES6 classes and Element constructors Dimitri Glazkov
• Re: Minimum viable custom elements Erik Arvidsson
• RE: Minimum viable custom elements Domenic Denicola
• Re: Minimum viable custom elements Ryosuke Niwa
• RE: Minimum viable custom elements Domenic Denicola
• Re: Custom element design with ES6 classes and Element constructors Boris Zbarsky
• Re: Minimum viable custom elements Anne van Kesteren
• Re: Custom element design with ES6 classes and Element constructors Dimitri Glazkov
• Re: Minimum viable custom elements Steve Faulkner
• Re: [Selection] Should selection.getRangeAt return a clone or a reference? Mats Palmgren
• RE: Adopting a Custom Element into Another Document Domenic Denicola
• Re: Minimum viable custom elements Erik Arvidsson
• Re: Custom element design with ES6 classes and Element constructors Boris Zbarsky
• Re: Minimum viable custom elements Boris Zbarsky
• IME API… chaals@yandex-team.ru
• Minimum viable custom elements Anne van Kesteren
• Re: Custom element design with ES6 classes and Element constructors Anne van Kesteren
• [Bug 27823] We should consider dropping [NoInterfaceObject] from XMLHttpRequestEventTarget bugzilla@jessica.w3.org
• Re: Custom element design with ES6 classes and Element constructors Boris Zbarsky
• Re: Custom element design with ES6 classes and Element constructors Anne van Kesteren
• Re: Defining a constructor for Element and friends Anne van Kesteren
• Re: Shadow tree style isolation primitive Anne van Kesteren
• Re: Better focus support for Shadow DOM chaals@yandex-team.ru
• Re: Better focus support for Shadow DOM 河内 隆仁
• Re: Better focus support for Shadow DOM chaals@yandex-team.ru
• Re: Adopting a Custom Element into Another Document Anne van Kesteren
• Re: Adopting a Custom Element into Another Document Anne van Kesteren
• Re: Defining a constructor for Element and friends Ryosuke Niwa
• Better focus support for Shadow DOM 河内 隆仁
• [Bug 27829] New: [Shadow]: Update ShadowRoot to have elementsFromPoint and caretPositionFromPoint bugzilla@jessica.w3.org
• Re: Defining a constructor for Element and friends Bjoern Hoehrmann
• RE: Defining a constructor for Element and friends Domenic Denicola
• Re: Defining a constructor for Element and friends Bjoern Hoehrmann
• Re: Adopting a Custom Element into Another Document Ryosuke Niwa
• Re: Shadow tree style isolation primitive Brian Kardell
• Re: Shadow tree style isolation primitive Ryosuke Niwa

Tuesday, 13 January 2015

• [Bug 25223] IDB exposes GC behavior bugzilla@jessica.w3.org
• [Bug 27712] IndexedDB: Array comparison algorithm doesn't handle empty arrays bugzilla@jessica.w3.org
• Re: Shadow tree style isolation primitive Brian Kardell
• Re: [Selection] Support of Multiple Selection (was: Should selection.getRangeAt return a clone or a reference?) Ryosuke Niwa
• Re: [Selection] Should selection.getRangeAt return a clone or a reference? Ryosuke Niwa
• Re: [Selection] Support of Multiple Selection (was: Should selection.getRangeAt return a clone or a reference?) Tab Atkins Jr.
• Re: [Selection] Support of Multiple Selection (was: Should selection.getRangeAt return a clone or a reference?) Mats Palmgren
• Re: Custom element design with ES6 classes and Element constructors Yehuda Katz
• [Bug 27823] New: We should consider dropping [NoInterfaceObject] from XMLHttpRequestEventTarget bugzilla@jessica.w3.org
• Re: Adopting a Custom Element into Another Document Boris Zbarsky
• RE: Adopting a Custom Element into Another Document Domenic Denicola
• Re: Defining a constructor for Element and friends Ryosuke Niwa
• Re: Adopting a Custom Element into Another Document Ryosuke Niwa
• Re: Defining a constructor for Element and friends Boris Zbarsky
• Re: Adopting a Custom Element into Another Document Anne van Kesteren
• Re: Adopting a Custom Element into Another Document Ryosuke Niwa
• Re: Shadow tree style isolation primitive Ryosuke Niwa
• Re: Defining a constructor for Element and friends Ryosuke Niwa
• RE: Defining a constructor for Element and friends Domenic Denicola
• Re: Defining a constructor for Element and friends Ryosuke Niwa
• RE: Defining a constructor for Element and friends Domenic Denicola
• Re: Defining a constructor for Element and friends Ryosuke Niwa
• Re: Defining a constructor for Element and friends Boris Zbarsky
• Re: Defining a constructor for Element and friends Ryosuke Niwa
• Re: Custom element design with ES6 classes and Element constructors Boris Zbarsky
• Re: [Selection] Should selection.getRangeAt return a clone or a reference? Ryosuke Niwa
• RE: Custom element design with ES6 classes and Element constructors Domenic Denicola
• [Bug 27709] Dictionary MouseEventInit uses keyword attribute for its members bugzilla@jessica.w3.org
• Re: [Bug 27709] New: Dictionary MouseEventInit uses keyword attribute for its members Ms2ger
• Re: [Bug 27709] New: Dictionary MouseEventInit uses keyword attribute for its members Vincent Scheib
• RE: Defining a constructor for Element and friends Domenic Denicola
• Re: Custom element design with ES6 classes and Element constructors Boris Zbarsky
• Re: Custom element design with ES6 classes and Element constructors Boris Zbarsky
• RE: Custom element design with ES6 classes and Element constructors Domenic Denicola
• Re: Defining a constructor for Element and friends Boris Zbarsky
• RE: Custom element design with ES6 classes and Element constructors Domenic Denicola
• Re: Custom element design with ES6 classes and Element constructors Gabor Krizsanits
• RE: Defining a constructor for Element and friends Domenic Denicola
• Re: Adopting a Custom Element into Another Document Anne van Kesteren
• Re: [Selection] Should selection.getRangeAt return a clone or a reference? Arthur Barstow
• Re: Shadow tree style isolation primitive chaals@yandex-team.ru
• Re: [Selection] Should selection.getRangeAt return a clone or a reference? Koji Ishii
• Re: [Selection] Should selection.getRangeAt return a clone or a reference? chaals@yandex-team.ru
• Re: Defining a constructor for Element and friends Boris Zbarsky
• Re: element.onresize Spirit
• Re: Custom element design with ES6 classes and Element constructors Boris Zbarsky
• Adopting a Custom Element into Another Document Ryosuke Niwa
• Re: Custom element design with ES6 classes and Element constructors Boris Zbarsky
• Re: Custom element design with ES6 classes and Element constructors Boris Zbarsky
• Re: Shadow tree style isolation primitive Hayato Ito
• Re: Shadow tree style isolation primitive Marc Fawzi
• Re: [Selection] Should selection.getRangeAt return a clone or a reference? Boris Zbarsky
• Re: Shadow tree style isolation primitive Ryosuke Niwa
• Re: Shadow tree style isolation primitive Tab Atkins Jr.
• Re: Shadow tree style isolation primitive Ryosuke Niwa
• Re: Shadow tree style isolation primitive Tab Atkins Jr.
• Re: Custom element design with ES6 classes and Element constructors Ryosuke Niwa
• Re: Shadow tree style isolation primitive Ryosuke Niwa
• Re: Shadow tree style isolation primitive Tab Atkins Jr.
• RE: Custom element design with ES6 classes and Element constructors Domenic Denicola
• Re: Shadow tree style isolation primitive Tab Atkins Jr.
• Re: Shadow tree style isolation primitive Brian Kardell
• Re: Shadow tree style isolation primitive Ryosuke Niwa
• Re: Custom element design with ES6 classes and Element constructors Ryosuke Niwa
• Re: Shadow tree style isolation primitive Brian Kardell
• RE: Custom element design with ES6 classes and Element constructors Domenic Denicola
• Re: Shadow tree style isolation primitive Ryosuke Niwa
• Re: Shadow tree style isolation primitive Ryosuke Niwa
• Re: Shadow tree style isolation primitive Brian Kardell
• Re: Shadow tree style isolation primitive Tab Atkins Jr.

Monday, 12 January 2015

• Re: Custom element design with ES6 classes and Element constructors Ryosuke Niwa
• Re: Shadow tree style isolation primitive Ryosuke Niwa
• Re: Shadow tree style isolation primitive Ryosuke Niwa
• Re: Shadow tree style isolation primitive Ryosuke Niwa
• RE: Custom element design with ES6 classes and Element constructors Domenic Denicola
• RE: Custom element design with ES6 classes and Element constructors Domenic Denicola
• RE: Shadow tree style isolation primitive François REMY
• Re: Custom element design with ES6 classes and Element constructors Ryosuke Niwa
• Re: Shadow tree style isolation primitive Tab Atkins Jr.
• Re: Shadow tree style isolation primitive Brian Kardell
• Re: Shadow tree style isolation primitive Ryosuke Niwa
• Re: Shadow tree style isolation primitive Ryosuke Niwa
• Re: Shadow tree style isolation primitive Brian Kardell
• Re: Shadow tree style isolation primitive Ryosuke Niwa
• Re: Shadow tree style isolation primitive Tab Atkins Jr.
• Re: [Selection] Should selection.getRangeAt return a clone or a reference? Olli Pettay
• Re: Custom element design with ES6 classes and Element constructors Erik Arvidsson
• [Selection] Support of Multiple Selection (was: Should selection.getRangeAt return a clone or a reference?) Ben Peters
• Re: [Selection] Should selection.getRangeAt return a clone or a reference? Olivier Forget
• RE: Custom element design with ES6 classes and Element constructors Domenic Denicola
• Re: Shadow tree style isolation primitive Marc Fawzi
• Re: Shadow tree style isolation primitive Brian Kardell
• Re: Custom element design with ES6 classes and Element constructors Tab Atkins Jr.
• Re: Shadow tree style isolation primitive Anne van Kesteren
• Re: Shadow tree style isolation primitive Brian Kardell
• Re: Custom element design with ES6 classes and Element constructors Anne van Kesteren
• Re: Shadow tree style isolation primitive chaals@yandex-team.ru
• Re: Shadow tree style isolation primitive Anne van Kesteren
• Re: [Selection] Should selection.getRangeAt return a clone or a reference? Aryeh Gregor
• Re: Spring meeting in Paris? Michael[tm] Smith
• Re: [Selection] Should selection.getRangeAt return a clone or a reference? Karl Dubost

Sunday, 11 January 2015

• RE: Custom element design with ES6 classes and Element constructors Domenic Denicola
• Custom element design with ES6 classes and Element constructors Domenic Denicola
• RE: Defining a constructor for Element and friends Domenic Denicola
• [Bug 27727] Remove DOMError from IDB bugzilla@jessica.w3.org

Saturday, 10 January 2015

• Re: [Selection] Should selection.getRangeAt return a clone or a reference? Aryeh Gregor
• Re: Defining a constructor for Element and friends Boris Zbarsky
• RE: Defining a constructor for Element and friends Domenic Denicola

Friday, 9 January 2015

• Re: [Pointer Lock] Comments Vincent Scheib
• [Bug 26904] Introduce typedef for IDBKeyPath, use it bugzilla@jessica.w3.org
• Re: Shadow tree style isolation primitive Tab Atkins Jr.
• Re: [Selection] Should selection.getRangeAt return a clone or a reference? Olivier Forget
• Re: [Selection] Should selection.getRangeAt return a clone or a reference? Mats Palmgren
• Re: [Selection] Should selection.getRangeAt return a clone or a reference? Koji Ishii
• Re: Shadow tree style isolation primitive Dimitri Glazkov
• Re: Shadow tree style isolation primitive Brian Kardell
• Re: Shadow tree style isolation primitive Dimitri Glazkov
• Re: Shadow tree style isolation primitive Anne van Kesteren
• RE: Custom element lifecycle callbacks Domenic Denicola
• Re: Shadow tree style isolation primitive Brian Kardell
• Re: Custom element lifecycle callbacks Boris Zbarsky
• Re: Custom element lifecycle callbacks Anne van Kesteren
• Re: Custom element lifecycle callbacks Boris Zbarsky
• Re: Custom element lifecycle callbacks Anne van Kesteren
• Shadow tree style isolation primitive Anne van Kesteren
• Re: Custom element lifecycle callbacks Boris Zbarsky
• Re: [Selection] Should selection.getRangeAt return a clone or a reference? Aryeh Gregor
• Re: Custom element lifecycle callbacks Anne van Kesteren
• Re: Custom element lifecycle callbacks Boris Zbarsky
• Re: Custom element lifecycle callbacks Anne van Kesteren
• Re: Custom element lifecycle callbacks Anne van Kesteren
• [Bug 27785] [Shadow]: broken link in draft spec section 9.3 bugzilla@jessica.w3.org
• Re: Custom element lifecycle callbacks Adam Klein
• Re: PSA: Indexed Database API is a W3C Recommendation Jonas Sicking

Thursday, 8 January 2015

• PSA: Indexed Database API is a W3C Recommendation Arthur Barstow
• Re: Custom element lifecycle callbacks Boris Zbarsky
• Re: Custom element lifecycle callbacks Dimitri Glazkov
• Custom element lifecycle callbacks Anne van Kesteren
• [Manifest] Navigation Scope is unclear chaals@yandex-team.ru
• [Bug 27785] New: [Shadow]: broken link in draft spec section 9.3 bugzilla@jessica.w3.org

Wednesday, 7 January 2015

• [Bug 27727] Remove DOMError from IDB bugzilla@jessica.w3.org
• Re: Defining a constructor for Element and friends Boris Zbarsky
• [Bug 27780] New: [Custom]: "All Algorithms in One Diagram" bugzilla@jessica.w3.org
• Re: Defining a constructor for Element and friends Anne van Kesteren
• Re: Defining a constructor for Element and friends Boris Zbarsky
• FYI: Deep linking Arthur Barstow
• RE: ES6 and upgrading custom elements Domenic Denicola
• Defining a constructor for Element and friends Anne van Kesteren
• Re: ES6 and upgrading custom elements Anne van Kesteren
• Re: [Selection] Should selection.getRangeAt return a clone or a reference? Koji Ishii
• RE: ES6 and upgrading custom elements Domenic Denicola
• [Bug 27775] New: [Shadow]: Define the behavior of *closed* shadow trees. bugzilla@jessica.w3.org
• Re: [Selection] Should selection.getRangeAt return a clone or a reference? Tim Down

Tuesday, 6 January 2015

• Re: [Selection] Should selection.getRangeAt return a clone or a reference? Ehsan Akhgari
• Re: [Selection] Should selection.getRangeAt return a clone or a reference? Olli Pettay
• RE: [Selection] Should selection.getRangeAt return a clone or a reference? Ben Peters
• [Selection] Should selection.getRangeAt return a clone or a reference? Ryosuke Niwa
• IndieUI Teleconference Agenda; 7 January at 22:00Z for 60 minutes Janina Sajka
• Re: Spring meeting in Paris? Ryosuke Niwa
• Re: ES6 and upgrading custom elements Dimitri Glazkov
• Re: ES6 and upgrading custom elements Anne van Kesteren
• Re: ES6 and upgrading custom elements Dimitri Glazkov
• Re: ES6 and upgrading custom elements Anne van Kesteren
• Re: ES6 and upgrading custom elements Dimitri Glazkov
• Re: ES6 and upgrading custom elements Anne van Kesteren
• [Bug 27770] New: [Custom]: Improve the wording in element upgrade algorithm bugzilla@jessica.w3.org
• Re: pull request on custom elements spec Dimitri Glazkov
• Re: ES6 and upgrading custom elements Dimitri Glazkov
• [Bug 27769] New: [Custom]: ES6 section needs to be updated bugzilla@jessica.w3.org
• [Bug 27768] New: [Custom]: "Parsing Custom Elements" bugzilla@jessica.w3.org
• [Bug 27544] [IndexedDB] "and and" typo bugzilla@jessica.w3.org
• ES6 and upgrading custom elements Anne van Kesteren
• [Bug 27762] New: [Custom]: what happens with Unresolved Elements when removed from the tree? bugzilla@jessica.w3.org
• pull request on custom elements spec Steve Faulkner

Monday, 5 January 2015

• [Bug 27757] New: [Shadow]: how is the autofocus attribute supposed to be handled? bugzilla@jessica.w3.org
• [Bug 27751] New: [Custom]: suggest note on requirements bugzilla@jessica.w3.org
• Re: custom elements without the dash Steve Faulkner
• Re: custom elements without the dash Anne van Kesteren
• Re: custom elements without the dash Steve Faulkner
• Re: custom elements without the dash Jirka Kosek
• Re: custom elements without the dash Steve Faulkner
• Re: custom elements without the dash Anne van Kesteren
• custom elements without the dash Steve Faulkner
• [Bug 25813] [Custom]: Throw Exception when EXTENDS and PROTOTYPE have a mismatch bugzilla@jessica.w3.org

Friday, 2 January 2015

• [Bug 27727] New: Remove DOMError from IDB bugzilla@jessica.w3.org

Thursday, 1 January 2015

• [Bug 27721] New: Partial interfaces must not inherit bugzilla@jessica.w3.org

Last message date: Tuesday, 31 March 2015 23:50:02 UTC