public-webapps@w3.org from July to September 2015 by date

Wednesday, 30 September 2015

• Re: Proposal: CSS WG / WebApps Joint Meeting for Shadow DOM Styling Ryosuke Niwa
• Re: Indexed DB + Promises Tab Atkins Jr.
• Re: Indexed DB + Promises Kyle Huey
• Re: Indexed DB + Promises Tab Atkins Jr.
• Re: Indexed DB + Promises Ben Kelly
• Re: Indexed DB + Promises Jake Archibald
• Re: Indexed DB + Promises Conrad Irwin
• Re: Indexed DB + Promises David Rajchenbach-Teller
• Re: Indexed DB + Promises David Rajchenbach-Teller
• Re: Indexed DB + Promises Jake Archibald

Tuesday, 29 September 2015

• Re: Indexed DB + Promises Jonas Sicking
• RE: Indexed DB + Promises Domenic Denicola
• Re: Proposal: CSS WG / WebApps Joint Meeting for Shadow DOM Styling Arthur Barstow
• Re: Proposal: CSS WG / WebApps Joint Meeting for Shadow DOM Styling Chaals McCathie Nevile
• Re: Proposal: CSS WG / WebApps Joint Meeting for Shadow DOM Styling Alan Stearns
• Re: [XHR] Error type when setting request headers. Ms2ger
• [XHR] Error type when setting request headers. Yves Lafon
• Re: Proposal: CSS WG / WebApps Joint Meeting for Shadow DOM Styling John Daggett
• Re: Proposal: CSS WG / WebApps Joint Meeting for Shadow DOM Styling Hayato Ito

Monday, 28 September 2015

• Proposal: CSS WG / WebApps Joint Meeting for Shadow DOM Styling Ryosuke Niwa
• Re: Shadow DOM Styling Meeting on September 18, 2015 Ryosuke Niwa
• RE: Indexed DB + Promises Aaron Powell
• Re: Indexed DB + Promises Marc Fawzi
• Re: Indexed DB + Promises David Rajchenbach-Teller
• Re: Indexed DB + Promises Marc Fawzi
• Re: Indexed DB + Promises Marc Fawzi
• Re: Indexed DB + Promises Joshua Bell
• Re: Indexed DB + Promises Marc Fawzi
• Indexed DB + Promises Joshua Bell

Saturday, 26 September 2015

• [Bug 25097] Update HTTP and HTTPAUTH references to new HTTPbis specs bugzilla@jessica.w3.org

Friday, 25 September 2015

• [XHR] keeping1740974@gmail.com

Thursday, 24 September 2015

• CfC: Transition "Secure Contexts" to CR; deadline October 1st. Mike West

Wednesday, 23 September 2015

• Re: RfC: Service Workers Arthur Barstow
• [webapps] spec title editorial nit [I18N-ISSUE-433] Phillips, Addison
• Re: Directory Upload Joshua Bell
• RE: RfC: Service Workers Phillips, Addison

Monday, 21 September 2015

• Re: Are web components *seriously* not namespaced? Henri Manson
• RE: Normative references to Workers. Domenic Denicola
• Re: Normative references to Workers. Xiaoqian Wu
• Re: Normative references to Workers. Anne van Kesteren
• Re: Normative references to Workers. Arthur Barstow
• Re: RfC: Service Workers Arthur Barstow
• RE: Service Workers Jungkee Song
• RfC: Service Workers Arthur Barstow
• Re: Normative references to Workers. Ms2ger
• Re: Normative references to Workers. Xiaoqian Wu

Friday, 18 September 2015

• [Bug 29136] New: Keyboard events should specify their target when more than 1 document exists bugzilla@jessica.w3.org
• Re: Service Workers 1 and Nightly Jungkee Song
• Re: Service Workers 1 and Nightly Arthur Barstow
• Service Workers 1 and Nightly Jungkee Song

Wednesday, 16 September 2015

• Re: Normative references to Workers. Arthur Barstow
• Re: Normative references to Workers. Mike West

Tuesday, 15 September 2015

• Re: Normative references to Workers. Philippe Le Hegaret
• Re: Normative references to Workers. Daniel Veditz
• Re: Normative references to Workers. Tab Atkins Jr.
• Re: Normative references to Workers. Ian Hickson
• Normative references to Workers. Mike West

Friday, 11 September 2015

• Secure Contexts: It's worth taking another look. Mike West

Thursday, 10 September 2015

• Shadow DOM Styling Meeting on September 18, 2015 Dimitri Glazkov

Wednesday, 9 September 2015

• Re: Shadow DOM spec for v1 is ready to be reviewed Anne van Kesteren
• [CSSWG][css-cascade-4] Last Call for Comments on CSS Cascading and Inheritance Level 4 fantasai

Monday, 7 September 2015

• Reminder: [TPAC2015] Registration is now open for Oct 26-30 meeting week; deadline October 7 Arthur Barstow
• Re: Shadow DOM spec for v1 is ready to be reviewed Hayato Ito

Saturday, 5 September 2015

• [Bug 24632] [meta][imports]: The spec should have fewer monkey patches bugzilla@jessica.w3.org
• Re: Shadow DOM spec for v1 is ready to be reviewed Anne van Kesteren

Friday, 4 September 2015

• Re: Tests for new shadow DOM API Ms2ger
• Re: Tests for new shadow DOM API 河内 隆仁

Thursday, 3 September 2015

• Re: Tests for new shadow DOM API Ryosuke Niwa
• RE: Tests for new shadow DOM API Travis Leithead
• Tests for new shadow DOM API Ryosuke Niwa
• Directory Upload Ali Alabbas

Wednesday, 2 September 2015

• Re: [charter] Request for Comments; deadline Sept 10 Arthur Barstow
• Re: Shadow DOM spec for v1 is ready to be reviewed Hayato Ito

Tuesday, 1 September 2015

• Re: Shadow DOM spec for v1 is ready to be reviewed Ryosuke Niwa
• Re: PSA: publish WD of "WebIDL Level 1" Ryosuke Niwa
• Re: PSA: publish WD of "WebIDL Level 1" Anne van Kesteren
• Re: PSA: publish WD of "WebIDL Level 1" Ryosuke Niwa
• Re: PSA: publish WD of "WebIDL Level 1" Yves Lafon
• Re: PSA: publish WD of "WebIDL Level 1" Ms2ger
• Re: PSA: publish WD of "WebIDL Level 1" Yves Lafon
• Re: PSA: publish WD of "WebIDL Level 1" Anne van Kesteren
• RE: PSA: publish WD of "WebIDL Level 1" Domenic Denicola
• Re: PSA: publish WD of "WebIDL Level 1" Ryosuke Niwa

Monday, 31 August 2015

• [Bug 29105] MediaStream Recording API: Consider not using BlobEvent, using Blob and FileReader instead bugzilla@jessica.w3.org
• [Bug 29103] MediaStream Recording API: MediaRecorderErrorEvent is a NoInterfaceObject, consider removing bugzilla@jessica.w3.org
• [Bug 29102] MediaStream Recording API: remove RecordingErrorNameEnum and use DomException instead bugzilla@jessica.w3.org
• [Bug 29104] BlobEvent is defined in both MediaStream Recorder and MediaStream ImageCapture, consider factoring them out. bugzilla@jessica.w3.org
• [Bug 29105] New: MediaStream Recording API: Consider not using BlobEvent, using Blob and FileReader instead bugzilla@jessica.w3.org
• [Bug 29104] New: BlobEvent is defined in both MediaStream Recorder and MediaStream ImageCapture, consider factoring them out. bugzilla@jessica.w3.org
• [Bug 29103] New: MediaStream Recording API: MediaRecorderErrorEvent is a NoInterfaceObject, consider removing bugzilla@jessica.w3.org
• [Bug 29102] New: MediaStream Recording API: remove RecordingErrorNameEnum and use DomException instead bugzilla@jessica.w3.org
• Re: PSA: publish WD of "WebIDL Level 1" Ms2ger
• Re: PSA: publish WD of "WebIDL Level 1" Yves Lafon

Saturday, 29 August 2015

• Re: Clipboard API: remove dangerous formats from mandatory data types Paul Libbrecht

Friday, 28 August 2015

• Re: [charter] Request for Comments; deadline Sept 10 timeless
• Shadow DOM spec for v1 is ready to be reviewed Hayato Ito

Thursday, 27 August 2015

• Re: [clipboard] document.execCommand and clipboard actions Hallvord Reiar Michaelsen Steen
• Re: Clipboard API: remove dangerous formats from mandatory data types Hallvord Reiar Michaelsen Steen

Wednesday, 26 August 2015

• Mozilla/Microsoft support for Native Messaging Anders Rundgren

Tuesday, 25 August 2015

• Minutes from WebApps + HTMLWG Editing Task Force face to face meeting Xiaoqian Wu

Monday, 24 August 2015

• Re: [worker] Integration of WorkerGlobalScope and AbstractWorker Anne van Kesteren
• Re: what's the meaning of lighter blue thick underlined terms in some specs? Michael[tm] Smith

Sunday, 23 August 2015

• what's the meaning of lighter blue thick underlined terms in some specs? =JeffH
• WebApps-ACTION-758: Ask accesibility people about imes Web Applications Working Group Issue Tracker
• [worker] Integration of WorkerGlobalScope and AbstractWorker Bang Seongbeom

Friday, 21 August 2015

• RE: Custom elements "Constructor-Dmitry" baseline proposal Domenic Denicola
• Re: Custom elements "Constructor-Dmitry" baseline proposal Maciej Stachowiak

Wednesday, 19 August 2015

• [Bug 29068] New: Should not reocmmend DocumentEvent.createEvent bugzilla@jessica.w3.org
• Re: Moving W3C Streams to Note and adding disclaimer [was: [charter] What is the plan for Streams API?] Michael[tm] Smith
• Moving W3C Streams to Note and adding disclaimer [was: [charter] What is the plan for Streams API?] Michael[tm] Smith

Tuesday, 18 August 2015

• RE: Copying multi-range selection Phillips, Addison
• Re: Copying multi-range selection Richard Ishida
• Re: Custom elements "Constructor-Dmitry" baseline proposal Anne van Kesteren

Monday, 17 August 2015

• Custom elements "Constructor-Dmitry" baseline proposal Domenic Denicola
• Re: Clipboard API: remove dangerous formats from mandatory data types Paul Libbrecht

Saturday, 15 August 2015

• [url] do not find. Tw Zy

Sunday, 16 August 2015

• Re: Clipboard API: remove dangerous formats from mandatory data types Hallvord Reiar Michaelsen Steen
• Re: Copying multi-range selection Anne van Kesteren

Saturday, 15 August 2015

• RE: Copying multi-range selection Phillips, Addison
• RE: Copying multi-range selection Matitiahu Allouche
• Re: Copying multi-range selection Richard Ishida
• Re: Copying multi-range selection Johannes Wilm
• Re: Copying multi-range selection Anne van Kesteren
• Re: Copying multi-range selection Wafaa Mohiy
• Re: Copying multi-range selection Richard Ishida
• Re: Copying multi-range selection Mark Davis ☕️
• Re: Copying multi-range selection Anne van Kesteren

Friday, 14 August 2015

• Copying multi-range selection Ryosuke Niwa

Wednesday, 12 August 2015

• Re: Custom Element Action Items? Anne van Kesteren
• Re: Is polyfilling future web APIs a good idea? Glen Huang

Tuesday, 11 August 2015

• Re: Custom Element Action Items? Hayato Ito

Monday, 10 August 2015

• [Bug 21836] Remove NotSupportedError on creating index for multiEntry index with array keyPath nobody@w3.org
• [Bug 28456] nested keyPath: allow specification which part should be iterated if it's an array nobody@w3.org
• [Bug 11528] We should add some form of dynamic transaction to IndexedDB nobody@w3.org
• [Bug 10000] Allow expressions in addition to keyPaths when creating indexes nobody@w3.org
• [Bug 22130] Modification for IDBObjectStore's clear and delete method nobody@w3.org
• [Bug 16137] IndexedDB: Add API for enumerating databases nobody@w3.org
• [Bug 22370] Inform script of corruption-induced data loss nobody@w3.org
• [Bug 25223] IDB exposes GC behavior nobody@w3.org
• [Bug 28067] DOMStringList has been removed from DOM nobody@w3.org
• [Bug 29049] Queue a microtask to unset active on transaction nobody@w3.org
• [Bug 25097] Update HTTP and HTTPAUTH references to new HTTPbis specs nobody@w3.org
• [Bug 25097] Update HTTP and HTTPAUTH references to new HTTPbis specs nobody@w3.org
• Re: Is polyfilling future web APIs a good idea? Brian Kardell
• Custom Element Action Items? Wilson Page
• Re: W3C's version of XMLHttpRequest should be abandoned Julian Aubourg
• Re: [charter] What is the plan for Streams API? Anne van Kesteren
• Re: [charter] What is the plan for Streams API? Arthur Barstow
• [Bug 29049] New: Queue a microtask to unset active on transaction nobody@w3.org

Friday, 7 August 2015

• Re: PSA: publish WD of "WebIDL Level 1" Tab Atkins Jr.
• Re: PSA: publish WD of "WebIDL Level 1" Anne van Kesteren
• Re: PSA: publish WD of "WebIDL Level 1" Travis Leithead
• Re: [clipboard] document.execCommand and clipboard actions Johannes Wilm
• RE: W3C's version of XMLHttpRequest should be abandoned Jungkee Song
• [charter] Need clarification about "Fetching resources" Arthur Barstow
• Re: PSA: publish WD of "WebIDL Level 1" Anne van Kesteren
• Re: PSA: publish WD of "WebIDL Level 1" Arthur Barstow
• Re: [charter] What is the plan for Streams API? Anne van Kesteren
• Re: [charter] What is the plan for Streams API? Arthur Barstow
• Re: W3C's version of XMLHttpRequest should be abandoned Arthur Barstow
• Re: Is polyfilling future web APIs a good idea? Glen Huang

Thursday, 6 August 2015

• Re: Is polyfilling future web APIs a good idea? Brian Kardell
• Re: Is polyfilling future web APIs a good idea? Glen Huang
• Re: [clipboard] document.execCommand and clipboard actions yves.konen@ysadi.be
• Re: Is polyfilling future web APIs a good idea? William Jeffries
• RE: W3C's version of XMLHttpRequest should be abandoned Domenic Denicola
• Re: W3C's version of XMLHttpRequest should be abandoned Robin Berjon
• Re: Is polyfilling future web APIs a good idea? MOHAN ARUN
• Re: Is polyfilling future web APIs a good idea? Matthew Robb
• Re: W3C's version of XMLHttpRequest should be abandoned Arthur Barstow
• Re: W3C's version of XMLHttpRequest should be abandoned Hallvord Reiar Michaelsen Steen
• Re: [clipboard] document.execCommand and clipboard actions Hallvord Reiar Michaelsen Steen
• Re: [clipboard] document.execCommand and clipboard actions Hallvord Reiar Michaelsen Steen
• W3C's version of XMLHttpRequest should be abandoned Anne van Kesteren
• Re: [clipboard] document.execCommand and clipboard actions Anne van Kesteren
• Re: Is polyfilling future web APIs a good idea? Glen Huang

Monday, 3 August 2015

• Re: Is polyfilling future web APIs a good idea? MOHAN ARUN

Wednesday, 5 August 2015

• Re: [clipboard] document.execCommand and clipboard actions MOHAN ARUN
• Re: [charter] What is the plan for Streams API? Takeshi Yoshino
• Re: CSS cascading order and Shadow DOM Hayato Ito
• Re: Is polyfilling future web APIs a good idea? Brian Kardell
• Re: Is polyfilling future web APIs a good idea? Glen Huang

Tuesday, 4 August 2015

• [clipboard] document.execCommand and clipboard actions Hallvord Reiar Michaelsen Steen
• Re: PSA: publish WD of "WebIDL Level 1" Tab Atkins Jr.
• CSS cascading order and Shadow DOM Rune Lillesveen
• [charter] What is the plan for Streams API? Arthur Barstow
• Re: Is polyfilling future web APIs a good idea? Brian Kardell
• Fwd: [webappsec] CfC: Proposed non-normative updates to CORS Brad Hill
• Re: Is polyfilling future web APIs a good idea? Glen Huang

Monday, 3 August 2015

• Re: Is polyfilling future web APIs a good idea? Brian Kardell
• Is polyfilling future web APIs a good idea? Glen Huang

Saturday, 1 August 2015

• PSA: Arun Ranganathan is now an Invited Expert Arthur Barstow

Thursday, 30 July 2015

• PSA: publish WD of "WebIDL Level 1" Arthur Barstow
• [charter] Request for Comments; deadline Sept 10 Arthur Barstow
• Minutes from Components face to face Chaals McCathie Nevile

Tuesday, 28 July 2015

• Re: Clipboard API: remove dangerous formats from mandatory data types Chaals McCathie Nevile
• Re: Clipboard API: remove dangerous formats from mandatory data types Hallvord Reiar Michaelsen Steen
• Re: Clipboard API: remove dangerous formats from mandatory data types Chaals McCathie Nevile
• [Bug 28614] Weaken the requirement of the time of running async steps nobody@w3.org
• [Bug 27674] requestFullscreen should return a promise nobody@w3.org
• [Bug 26516] Make resize events etc to be synchronized with animation frames nobody@w3.org
• [Bug 26440] Allow fullscreenchange events to be synchronized with animation frames nobody@w3.org
• [Bug 16502] Define multiple monitor support and per-subdomain nobody@w3.org
• Re: Clipboard API: remove dangerous formats from mandatory data types Wez

Monday, 27 July 2015

• Re: Clipboard API: remove dangerous formats from mandatory data types Hallvord Reiar Michaelsen Steen
• [Bug 28460] Request fullscreen on both iframe and elements inside it could cause undesired result nobody@w3.org

Friday, 24 July 2015

• Re: [clipboard] navigator.registerClipboardFormats( ... ) Daniel Cheng

Wednesday, 22 July 2015

• [clipboard] navigator.registerClipboardFormats( ... ) Hallvord Reiar Michaelsen Steen
• WebApps-ACTION-757: Collect the various minutes and make them as coherent as the reality of the meeting. Web Applications Working Group Issue Tracker

Tuesday, 21 July 2015

• RE: Apple's updated feedback on Custom Elements and Shadow DOM Domenic Denicola
• Re: Apple's updated feedback on Custom Elements and Shadow DOM Maciej Stachowiak
• RE: Apple's updated feedback on Custom Elements and Shadow DOM Domenic Denicola
• RE-SENDING [Apple's updated feedback on Custom Elements and Shadow DOM] Michael[tm] Smith
• Apple's updated feedback on Custom Elements and Shadow DOM Maciej Stachowiak

Monday, 20 July 2015

• [Bug 28967] New: "Legacy" appendices should be normative bugzilla@jessica.w3.org

Saturday, 18 July 2015

• Re: Two new custom elements ideas Derek Gray
• [Bug 26676] Non-fullscreen documents can end up with non-empty fullscreen element stacks bugzilla@jessica.w3.org
• [Bug 27674] requestFullscreen should return a promise bugzilla@jessica.w3.org
• [Bug 28459] Algorithm of exitFullscreen() doesn't work correctly when there are nested fullscreen element bugzilla@jessica.w3.org
• Re: alternate view on constructors for custom elements Ryosuke Niwa

Friday, 17 July 2015

• RE: alternate view on constructors for custom elements Domenic Denicola
• RE: alternate view on constructors for custom elements Travis Leithead
• Two new custom elements ideas Domenic Denicola
• Re: alternate view on constructors for custom elements Boris Zbarsky
• RE: alternate view on constructors for custom elements Domenic Denicola
• alternate view on constructors for custom elements Travis Leithead
• Re: The key custom elements question: custom constructors? Boris Zbarsky
• Re: The key custom elements question: custom constructors? Anne van Kesteren
• Re: The key custom elements question: custom constructors? Boris Zbarsky
• Re: The key custom elements question: custom constructors? Anne van Kesteren
• RE: The key custom elements question: custom constructors? Domenic Denicola
• [Bug 28614] Weaken the requirement of the time of running async steps bugzilla@jessica.w3.org
• [Bug 27162] Browser differences in graphical layout of fullscreen mode. bugzilla@jessica.w3.org
• Re: Informal Service Worker working session Alex Russell
• Re: The key custom elements question: custom constructors? Anne van Kesteren
• Re: Cross-page locking mechanism for indexedDB/web storage/FileHandle ? duanyao

Thursday, 16 July 2015

• Re: The key custom elements question: custom constructors? Jonas Sicking
• RE: The key custom elements question: custom constructors? Domenic Denicola
• RE: The key custom elements question: custom constructors? Domenic Denicola
• Re: The key custom elements question: custom constructors? Jonas Sicking
• Re: [WebIDL] T[] migration Jonas Sicking
• Re: [WebIDL] T[] migration Martin Thomson
• Re: The key custom elements question: custom constructors? Anne van Kesteren
• RE: The key custom elements question: custom constructors? Domenic Denicola
• RE: [WebIDL] T[] migration Domenic Denicola
• Re: [WebIDL] T[] migration Boris Zbarsky
• Re: The key custom elements question: custom constructors? Anne van Kesteren
• Re: [WebIDL] T[] migration Boris Zbarsky
• Re: [WebIDL] T[] migration Anne van Kesteren
• RE: The key custom elements question: custom constructors? Domenic Denicola
• Re: [WebIDL] T[] migration chaals@yandex-team.ru
• Re: [WebIDL] T[] migration Anne van Kesteren
• [WebIDL] T[] migration Travis Leithead
• RfC: LCWD of Tracking Compliance and Scope; deadline October 7 Arthur Barstow
• Re: The key custom elements question: custom constructors? Olli Pettay
• RE: The key custom elements question: custom constructors? Domenic Denicola
• RE: The key custom elements question: custom constructors? Travis Leithead
• Re: The key custom elements question: custom constructors? Olli Pettay
• The key custom elements question: custom constructors? Domenic Denicola
• Re: Cross-page locking mechanism for indexedDB/web storage/FileHandle ? Jonas Sicking

Wednesday, 15 July 2015

• Re: Informal Service Worker working session Benjamin Kelly
• Re: Cross-page locking mechanism for indexedDB/web storage/FileHandle ? Joshua Bell
• [Bug 26677] Clarify when :fullscreen applies bugzilla@jessica.w3.org
• [Bug 26676] Non-fullscreen documents can end up with non-empty fullscreen element stacks bugzilla@jessica.w3.org
• [Bug 27863] Not need to specify moving element in top layer and fullscreen stack bugzilla@jessica.w3.org
• [Bug 27865] Merge fullscreen element stack into top layer bugzilla@jessica.w3.org
• Cross-page locking mechanism for indexedDB/web storage/FileHandle ? 段垚

Tuesday, 14 July 2015

• Re: [html-imports] Syntax is "mystic and daunting" [Was: Re: HTML5 includes from within <body>] anatoly techtonik
• Re: [html-imports] Syntax is "mystic and daunting" [Was: Re: HTML5 includes from within <body>] anatoly techtonik
• [html-imports] Syntax is "mystic and daunting" [Was: Re: HTML5 includes from within <body>] Arthur Barstow
• HTML5 includes from within <body> anatoly techtonik

Monday, 13 July 2015

• Re: Custom Elements: "createdCallback" & cloning Ryosuke Niwa
• Re: Custom Elements: "createdCallback" & cloning Olli Pettay
• Re: Custom Elements: "createdCallback" & cloning Anne van Kesteren
• Re: Custom Elements: "createdCallback" & cloning Anne van Kesteren

Sunday, 12 July 2015

• Re: Custom Elements: "createdCallback" & cloning Dominic Cooney
• Re: Custom Elements: "createdCallback" & cloning Olli Pettay
• Re: Custom Elements: "createdCallback" & cloning Anne van Kesteren

Friday, 10 July 2015

• [Bug 28938] New: Consider adding sourceDevice property to UIEvent bugzilla@jessica.w3.org
• Re: Custom Elements: "createdCallback" & cloning Dominic Cooney
• Re: Custom Elements: is="" Dominic Cooney

Wednesday, 8 July 2015

• Re: Components F2F Michael[tm] Smith
• Re: Components F2F Mark Giffin

Tuesday, 7 July 2015

• Re: Components F2F Dimitri Glazkov
• [Bug 28924] New: Is CompositionEvent supposed to have .locale? bugzilla@jessica.w3.org
• Re: Async Image -> ImageData conversion Anne van Kesteren
• Re: Async Image -> ImageData conversion Ashley Gullen
• Re: Async Image -> ImageData conversion Anne van Kesteren
• WBS Reminder - Registration for the F2F meeting of the Web Applications Working Group (2015-07-21/2015-07-21 in Bay Area, CA US) responses due 2015-07-14 W3C WBS Mailer
• [Bug 21066] Provide an event path API bugzilla@jessica.w3.org
• [Bug 25458] [Shadow]: The return type of Event.path should leverage WebIDL sequences bugzilla@jessica.w3.org
• [Bug 24586] Remove FileList bugzilla@jessica.w3.org

Monday, 6 July 2015

• Re: Async Image -> ImageData conversion Ashley Gullen
• Re: [admin] Moving Custom Elements bugs to Github [Was: Re: Custom Elements bugs will be also migrated] Xiaoqian Wu
• Re: [admin] Moving Custom Elements bugs to Github [Was: Re: Custom Elements bugs will be also migrated] Hayato Ito
• [Bug 26643] Figure out how "If a reflecting IDL attribute has the type HTMLElement, or an interface that descends from HTMLElement" should work in the context of shadow dom. bugzilla@jessica.w3.org
• [Bug 25715] [imports]: Unify loading and dependency resolution model with ES6 modules bugzilla@jessica.w3.org
• [Bug 25473] [Custom]: Add support for focus navigation similar to input type=date bugzilla@jessica.w3.org
• [Bug 25669] [Custom]: Make ES6 prose normative when ES6 ships bugzilla@jessica.w3.org
• [Bug 27769] [Custom]: ES6 section needs to be updated bugzilla@jessica.w3.org
• [Bug 27440] [Custom]: callbacks don't deal with exceptions bugzilla@jessica.w3.org
• [Bug 27405] [Custom]: Convert all ES5 references to ES6 bugzilla@jessica.w3.org
• [Bug 25669] [Custom]: Make ES6 prose normative when ES6 ships bugzilla@jessica.w3.org
• [Bug 27768] [Custom]: Make "Parsing Custom Elements" section more explicit bugzilla@jessica.w3.org
• [Bug 27375] [Shadow]: Define whether <style>s in shadow trees are loaded bugzilla@jessica.w3.org
• [Bug 26934] [Shadow]: How should Element.requestPointerLock() work in shadow DOM? bugzilla@jessica.w3.org
• [Bug 26583] [Custom]: Add the possibility to extend the custom element bugzilla@jessica.w3.org
• [Bug 25696] [imports]: <link media> bugzilla@jessica.w3.org
• [Bug 25669] [Custom]: Make ES6 prose normative when ES6 ships bugzilla@jessica.w3.org
• [Bug 27914] [Custom]: Typo instantation ---> instantiation bugzilla@jessica.w3.org
• [Bug 26656] Figure out how form owner should work in shadow dom bugzilla@jessica.w3.org
• [Bug 26898] [imports]: <link rel=import> shouldn't be active when added by innerHTML bugzilla@jessica.w3.org
• [Bug 27780] [Custom]: "All Algorithms in One Diagram" bugzilla@jessica.w3.org
• [Bug 26845] [Shadow] "All other HTML elements in the shadow trees must behave as if they were part of the document tree." does not deal with the case when the host is not in the document tree bugzilla@jessica.w3.org
• [Bug 25484] [Explainer]: Example querySelectors need to select IDs bugzilla@jessica.w3.org
• [Bug 25924] [Imports]: The spec. is not very specific about the edge cases of the load bugzilla@jessica.w3.org
• [Bug 24629] [Explainer]: attachedCallback / detachedCallback are now enteredView and leftView? bugzilla@jessica.w3.org
• [Bug 24577] [Custom]: Need adopted callback bugzilla@jessica.w3.org
• [Bug 25568] [imports]: Respect the crossOrigin attribute bugzilla@jessica.w3.org
• [Bug 27611] [Custom]: SVG diagram accessibility bugzilla@jessica.w3.org
• [Bug 28545] Declarative syntax for custom elements bugzilla@jessica.w3.org
• [Bug 26852] [Custom]: Specify preference of localName and typeExtension in createElement bugzilla@jessica.w3.org
• [Bug 24579] [Custom]: make callbacks more explicit bugzilla@jessica.w3.org
• [Bug 27496] [Explainer]: mispell on inherifance bugzilla@jessica.w3.org
• [Bug 27260] [Custom]: Need to define global/Realm handling for registerElement bugzilla@jessica.w3.org
• [Bug 24570] [Custom]: Callback for cloneNode/importNode bugzilla@jessica.w3.org
• [Bug 24087] [Custom]: Rename document.registerElement to document.define or document.defineElement bugzilla@jessica.w3.org
• [Bug 27379] [Shadow] How should element.requestFullscreen(); work in shadow dom bugzilla@jessica.w3.org
• [Bug 28051] [imports]: showing <dialog> from import bugzilla@jessica.w3.org
• [Bug 27762] [Custom]: Make unresolved state an explicit flag. bugzilla@jessica.w3.org
• [Bug 26846] [Shadow] it is unclear how elements in older shadow trees should work in case the newer shadow tree lacks <shadow> bugzilla@jessica.w3.org
• [Bug 28086] [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
• [Bug 24632] [meta][imports]: The spec should have fewer monkey patches bugzilla@jessica.w3.org
• [Bug 25566] [imports]: Supporting more than just the script-src CSP directive in imports. bugzilla@jessica.w3.org
• [Bug 28547] Remove the support for inherting from builtin subclasses of HTMLElement and SVGElement bugzilla@jessica.w3.org
• [Bug 28092] [Custom]: Clarify in informative note that cloning/importing also enqueues created callback bugzilla@jessica.w3.org
• [Bug 24655] [Custom]: Consider turning processing stack + queues into its own primitive bugzilla@jessica.w3.org
• [Bug 27380] [Shadow] How should various document internal references work when SVG is being used in shadow DOM bugzilla@jessica.w3.org
• [Bug 27017] [Custom]: Constructor/prototype linkage needs to actually be defined, since it's dynamic, not static bugzilla@jessica.w3.org
• [Bug 26681] [imports]: Script execution order should be stated more clearly bugzilla@jessica.w3.org
• [Bug 27836] Scripts in HTML Imports should be scoped to the import (treat imports as script modules) bugzilla@jessica.w3.org
• [Bug 26943] [Custom] Should attachedCallback/detachedCallback callbacks be called when element is added to / removed from shadom dom which is attached to a in-document host? bugzilla@jessica.w3.org
• [Bug 27978] [Custom]: attachedCallback has no protocol for indicating that the custom tag is not applicable in this context bugzilla@jessica.w3.org
• [Bug 25818] [imports]: The dedup behavior with redirects should be clarified. bugzilla@jessica.w3.org
• [Bug 27975] [Custom]: No way to unregister a component bugzilla@jessica.w3.org
• [Bug 24578] [Custom]: define registry primitive; ("namespace" support needed?) bugzilla@jessica.w3.org
• [Bug 26638] [Custom]: sorted element queue definition is not in sync with Imports bugzilla@jessica.w3.org
• [Bug 25669] [Custom]: Make ES6 prose normative when ES6 ships bugzilla@jessica.w3.org
• [Bug 27976] [Custom]: type extensions should be available as custom tags, not only through <baseTag is="..."> bugzilla@jessica.w3.org
• [Bug 28158] [Custom]: inflexible extends as fixed element type bugzilla@jessica.w3.org
• [Bug 26576] [Custom]: Add informative text about importNode bugzilla@jessica.w3.org
• [Bug 28449] [Shadow]: Allow certain pseudo-classes in content selectors bugzilla@jessica.w3.org
• [Bug 26682] [imports]: The relationship between import and browsing context should be stated more clearly bugzilla@jessica.w3.org
• [Bug 26713] DOMFocusIn/DOMFocusOut in ShadowDOM spec should be renamed to focusin/focusout bugzilla@jessica.w3.org
• [Bug 25610] [imports]: Want an informative section about implications of how CSP + Imports is defined bugzilla@jessica.w3.org
• [Bug 24876] [Custom Elements]: Custom elements should be display: block by default bugzilla@jessica.w3.org
• [Bug 25470] [imports]: improve description of async to clarify execution order bugzilla@jessica.w3.org
• [Bug 24042] [imports]: Parser should not wait on external resources inside imports bugzilla@jessica.w3.org
• [Bug 22409] Custom elements need da (microtask) hookup bugzilla@jessica.w3.org
• [Bug 28543] Custom elements should call user defined constructor synchronously bugzilla@jessica.w3.org
• [Bug 25563] [Shadow]: Define the impact of ordering on relevant HTML elements bugzilla@jessica.w3.org
• [Bug 24578] [Custom]: define registry primitive; ("namespace" support needed?) bugzilla@jessica.w3.org
• [Bug 27835] registerElement() should be scoped to modules bugzilla@jessica.w3.org
• [Bug 25916] [Explainer]: Custom pseudo elements are still used in the examples. bugzilla@jessica.w3.org
• [Bug 28544] Custom elements should not upgrade elements by setting prototype bugzilla@jessica.w3.org
• [Bug 24848] [imports]: ES6 module loader should be aware modules in HTML Imports bugzilla@jessica.w3.org
• [Bug 25319] [imports]: Want some kind of imperative API bugzilla@jessica.w3.org
• [Bug 24756] [imports]: Cascading order for stylesheets of imported documents should be stated more clearly bugzilla@jessica.w3.org
• [Bug 24866] [Custom]: Consider adding inserted/removed callback bugzilla@jessica.w3.org
• [Bug 24106] FKA: No defined way to get keyboard focus into and out of a shadow DOM component bugzilla@jessica.w3.org
• [Bug 27437] [Custom]: Be clear about whether attached callback should be enqueued when setting prototype bugzilla@jessica.w3.org
• [Bug 27770] [Custom]: Improve the wording in element upgrade algorithm bugzilla@jessica.w3.org
• [Bug 27975] [Custom]: No way to unregister a component bugzilla@jessica.w3.org
• [Bug 26233] [imports]: Typo: "overnride" bugzilla@jessica.w3.org
• [Bug 27751] [Custom]: suggest note on requirements bugzilla@jessica.w3.org
• [Bug 24398] [Explainer]: typo ":" should be "=" bugzilla@jessica.w3.org
• [Bug 28541] Custom elements should use ES6 class constructor bugzilla@jessica.w3.org
• [Bug 24178] [Custom]: No way to differentiate attribute namespaces in attributeChanged callback bugzilla@jessica.w3.org
• [Bug 26065] [Explainer]: bugzilla@jessica.w3.org
• [Bug 25830] [Custom]: What should be the name of the generated constructor returned by registerElement? bugzilla@jessica.w3.org
• [Bug 24603] [Custom]: Need callback for form submit data bugzilla@jessica.w3.org
• [Bug 26213] Need a shadowRoots MutationObserver option bugzilla@jessica.w3.org
• [Bug 27977] [Custom]: mixin pattern: custom elements should be able to extend any base tag with is= bugzilla@jessica.w3.org
• [Bug 27538] [Custom]: Tone of note doesn't reflect severity bugzilla@jessica.w3.org
• [Bug 27366] Define how shadow DOM should be handled when host is adopted to a new document bugzilla@jessica.w3.org
• [Bug 28542] [Shadow] Replace node distribution mechanism by the named slot proposal bugzilla@jessica.w3.org
• [Bug 27643] [Custom]: Section 10 prototype is not defined bugzilla@jessica.w3.org
• [Bug 25007] [imports]: Want New LinkImport method to return a promise. bugzilla@jessica.w3.org
• [Bug 27325] [Shadow]: Figure out how session history should work for <iframe>s in shadow DOM bugzilla@jessica.w3.org
• [Bug 28546] document.registerElement should take a template as an argument bugzilla@jessica.w3.org
• [Bug 27016] [Custom]: Custom element constructor behavior makes no sense bugzilla@jessica.w3.org

Saturday, 4 July 2015

• Informal Service Worker working session Alex Russell

Friday, 3 July 2015

• [Bug 28890] New: scroll should be a simple Event not a UIEvent bugzilla@jessica.w3.org
• [Bug 27863] Not need to specify moving element in top layer and fullscreen stack bugzilla@jessica.w3.org
• Re: Async Image -> ImageData conversion Anne van Kesteren
• Re: Async Image -> ImageData conversion Ashley Gullen
• Re: [shadow-dom] ::before/after on shadow hosts 河内 隆仁
• Re: [shadow-dom] ::before/after on shadow hosts 河内 隆仁
• Re: CR: Web Storage (Second Edition) timeless

Thursday, 2 July 2015

• Re: Async Image -> ImageData conversion Jeff Muizelaar
• RE: [ime-api] [blink-dev] Removing IME API code from Blink Travis Leithead
• Re: Async Image -> ImageData conversion Justin Novosad
• Re: Components F2F chaals@yandex-team.ru
• Re: Better focus support for Shadow DOM 河内 隆仁
• Re: Components F2F Anne van Kesteren
• Custom Elements: "createdCallback" & cloning Anne van Kesteren
• Re: Custom Elements: is="" Ryosuke Niwa
• Re: Components F2F Ryosuke Niwa

Wednesday, 1 July 2015

• Re: [shadow-dom] ::before/after on shadow hosts Tab Atkins Jr.
• RE: PSA: publishing new WD of Service Workers on June 25 Jungkee Song
• Re: [admin] Moving Custom Elements bugs to Github [Was: Re: Custom Elements bugs will be also migrated] Xiaoqian Wu
• Re: [admin] Moving Custom Elements bugs to Github [Was: Re: Custom Elements bugs will be also migrated] Hayato Ito
• Re: PSA: publishing new WD of Service Workers on June 25 timeless
• Re: [shadow-dom] ::before/after on shadow hosts Hayato Ito
• Re: [shadow-dom] ::before/after on shadow hosts Elliott Sprehn
• Re: [shadow-dom] ::before/after on shadow hosts Hayato Ito
• Re: [shadow-dom] ::before/after on shadow hosts Hayato Ito
• Re: [shadow-dom] ::before/after on shadow hosts Erik Isaksen

Last message date: Wednesday, 30 September 2015 21:21:02 UTC