public-webapps-github@w3.org from July 2016 by date

Sunday, 31 July 2016

• Re: [slightlyoff/ServiceWorker] Receivers of ranged responses must ensure all ranges come from the same underlying resource (#703) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Create F2F agenda - 28-29 July 2016 (#932) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Create F2F agenda - 28-29 July 2016 (#932) Jake Archibald
• [w3c/touch-events] Add informative note about not doing naive "touch OR mouse etc" event handling (#71) Patrick H. Lauke
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) bmaurer
• Re: [w3ctag/spec-reviews] Generic Sensor API (#110) Tobie Langel
• Re: [whatwg/dom] Figure out what to do with XMLDocument (#278) Anne van Kesteren
• Re: [whatwg/dom] iterable declaration on NodeList is invalid (#284) Anne van Kesteren
• Re: [slightlyoff/ServiceWorker] OCSP fetches bypass service worker (#564) Anne van Kesteren
• Re: [whatwg/storage] Exposing cross-origin resource size (#31) Anne van Kesteren
• Re: [whatwg/encoding] Add UTF-7 to replacement encoding list? (#68) Anne van Kesteren
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Anne van Kesteren
• Re: [w3ctag/spec-reviews] Bluetooth API Security Model (#90) Marcos Cáceres
• Re: [whatwg/streams] light weight transformations (#461) Dominic Tarr

Saturday, 30 July 2016

• Re: [w3c/gamepad] Added GamepadPose (#25) Brandon Jones
• Re: [whatwg/streams] light weight transformations (#461) Anders Riutta
• Re: [w3c/gamepad] Added GamepadPose and GamepadCapabilities (#25) Brandon Jones
• Re: [w3ctag/spec-reviews] Review of WakeLock API and suitability for overall platform requested by 31 August 2016 (#126) David Baron
• Re: [w3ctag/spec-reviews] Notifications API (#94) Andrew Betts
• Re: [w3ctag/spec-reviews] TV Control Feedback (#111) Travis Leithead
• Re: [w3ctag/spec-reviews] TV Control Feedback (#111) Peter Linss
• Re: [w3ctag/spec-reviews] TV-Specific Web Subsetting (#105) Alex Russell
• Re: [w3ctag/spec-reviews] Generic Sensor API (#110) Travis Leithead
• Re: [w3ctag/spec-reviews] Generic Sensor API (#110) Travis Leithead
• Re: [w3ctag/spec-reviews] Privacy Mode (#101) Hadley Beeman
• Re: [w3ctag/spec-reviews] TAG Review of HTML 5.1 (#119) Hadley Beeman
• Re: [w3ctag/spec-reviews] TAG Review of HTML 5.1 (#119) Hadley Beeman
• Re: [w3ctag/spec-reviews] TAG Review of HTML 5.1 (#119) Daniel Appelquist
• Re: [w3ctag/spec-reviews] WebUSB (#108) Daniel Appelquist
• Re: [w3ctag/spec-reviews] relative URLs are not updated pushState() (#118) Travis Leithead
• Re: [w3ctag/spec-reviews] relative URLs are not updated pushState() (#118) Travis Leithead
• Re: [w3ctag/spec-reviews] ARIA (#107) Daniel Appelquist
• Re: [w3ctag/spec-reviews] relative URLs are not updated pushState() (#118) Alex Russell
• Re: [w3ctag/spec-reviews] Ambient Light Sensor API (#115) Tobie Langel
• Re: [w3ctag/spec-reviews] TV Control Feedback (#111) Daniel Appelquist
• Re: [w3ctag/spec-reviews] Ambient Light Sensor API (#115) Alex Russell
• Re: [w3ctag/spec-reviews] TV Control Feedback (#111) Daniel Appelquist
• Re: [w3ctag/spec-reviews] TV Control Feedback (#111) Daniel Appelquist
• Re: [w3ctag/spec-reviews] Review secure contexts (#124) Daniel Appelquist
• Re: [w3ctag/spec-reviews] Review secure contexts (#124) Daniel Appelquist
• Re: [w3ctag/spec-reviews] Review secure contexts (#124) Daniel Appelquist
• Re: [w3ctag/spec-reviews] URNbis documents (#117) Mark Nottingham
• Re: [w3ctag/spec-reviews] URNbis documents (#117) Mark Nottingham
• Re: [w3ctag/spec-reviews] Progressive Web Apps (#123) Daniel Appelquist
• Re: [w3ctag/spec-reviews] First Party Cookies (#114) Hadley Beeman
• Re: [w3ctag/spec-reviews] Progressive Web Apps (#123) Andrew Betts
• Re: [w3ctag/spec-reviews] Review Web Annotations specs (#93) Mark Nottingham
• Re: [w3ctag/spec-reviews] Streams General issue (#92) Daniel Appelquist
• Re: [w3ctag/spec-reviews] Bluetooth API Security Model (#90) Alex Russell
• Re: [w3ctag/spec-reviews] Bluetooth API Security Model (#90) Alex Russell
• Re: [w3ctag/spec-reviews] Write up the Secure Stop issue for ddorwin (#73) Travis Leithead
• Re: [w3ctag/spec-reviews] Write up the Secure Stop issue for ddorwin (#73) Travis Leithead
• Re: [w3ctag/spec-reviews] Bluetooth API Security Model (#90) Daniel Appelquist
• Re: [w3ctag/spec-reviews] Geofencing FPWD (#89) Hadley Beeman
• Re: [w3ctag/spec-reviews] Storage persistence (#85) Hadley Beeman
• Re: [w3ctag/spec-reviews] Storage persistence (#85) Hadley Beeman
• Re: [w3ctag/spec-reviews] Indexed DB getAll(), openKeyCursor() and objectStoreNames (#84) Daniel Appelquist
• Re: [w3ctag/spec-reviews] Indexed DB getAll(), openKeyCursor() and objectStoreNames (#84) Daniel Appelquist
• Re: [w3ctag/spec-reviews] Do we have feedback on Web Payment group's response to security & privacy questionnaire? (#125) Mark Nottingham
• Re: [w3ctag/spec-reviews] Do we have feedback on Web Payment group's response to security & privacy questionnaire? (#125) Mark Nottingham
• Re: [w3ctag/spec-reviews] Security Questionnaire (#77) Mark Nottingham
• Re: [w3ctag/spec-reviews] Do we have feedback on Web Payment group's response to security & privacy questionnaire? (#125) Daniel Appelquist
• Re: [w3ctag/spec-reviews] Security Questionnaire (#77) Mark Nottingham
• Re: [w3ctag/spec-reviews] Security Questionnaire (#77) Mark Nottingham
• Re: [w3ctag/spec-reviews] Write up the Secure Stop issue for ddorwin (#73) Daniel Appelquist
• Re: [heycam/webidl] More meaniful lables (#136) Tobie Langel
• Re: [w3ctag/spec-reviews] Task Scheduling (#72) David Baron
• Re: [w3ctag/spec-reviews] Potential for coordination about task scheduling (#72) Daniel Appelquist
• Re: [w3ctag/spec-reviews] requestIdleCallback (#70) David Baron
• [w3c/gamepad] Add a Project Description and Project URL (#29) chris van wiemeersch
• Re: [w3ctag/spec-reviews] Presentation API Request for Feedback (#61) Travis Leithead
• Re: [w3ctag/spec-reviews] Presentation API Request for Feedback (#61) Travis Leithead
• Re: [w3ctag/spec-reviews] Review WAPA (Accessibility) proposal (#63) Daniel Appelquist
• Re: [w3c/gamepad] Determine how Multi-touch surfaces should be handled. (#27) chris van wiemeersch
• Re: [w3ctag/spec-reviews] Browser Fingerprinting Document (#38) David Baron
• Re: [w3ctag/spec-reviews] Browser Fingerprinting Document (#38) Alex Russell
• Re: [w3c/gamepad] Added GamepadPose and GamepadCapabilities (#25) chris van wiemeersch
• Re: [w3c/gamepad] Added GamepadPose and GamepadCapabilities (#25) chris van wiemeersch
• Re: [w3ctag/spec-reviews] Browser Fingerprinting Document (#38) Daniel Appelquist
• Re: [w3c/charter-html] Indicate relationship with the WHATWG (#112) Florian Rivoal
• Re: [whatwg/streams] light weight transformations (#461) Dominic Tarr
• Re: [whatwg/streams] light weight transformations (#461) Anders Riutta

Friday, 29 July 2016

• Re: [slightlyoff/ServiceWorker] clarify behavior when fetch event handler throws (#896) Marijn Kruisselbrink
• Re: [whatwg/fetch] Support same-origin, strict-origin, strict-origin-when-cross-origin in request' referrer policy (#342) Francois Marier
• Re: [whatwg/fetch] Referrer policies: add the missing policies (fixes #342) (#346) Francois Marier
• [whatwg/fetch] Referrer policies: add the missing policies (fixes #342) (#346) Francois Marier
• Re: [w3c/editing] ly 29th F2F Agenda Item - Set Virtual Keyboard Enter Key Text (#142) gked
• [w3c/editing] ly 29th F2F Agenda Item - Set Virtual Keyboard Enter Key Text (#142) gked
• Re: [heycam/webidl] Make globals and things they inherit from have immutable prototypes (#133) Jeff Walden
• [whatwg/encoding] Add UTF-7 to replacement encoding list? (#68) jungshik
• Re: [w3c/editing] July 29th F2F Agenda Item - Opt-in/opt-out of editing features and menus (#141) gked
• [w3c/editing] July 29th F2F Agenda Item - Opt-in/opt-out of editing features and menus (#141) gked
• [w3c/editing] July 29th F2F Agenda Item - Non-cancelable event 2 of 2 (#140) gked
• Re: [w3c/editing] July 29th F2F Agenda Item - Data and dataTransfer attributes (#139) gked
• [w3c/editing] July 29th F2F Agenda Item - Data and dataTransfer attributes (#139) gked
• [whatwg/dom] "unclosed node of node" reads confusingly (#285) Tab Atkins Jr.
• Re: [w3c/editing] July 29th F2F Agenda Item - static ranges (#138) gked
• [w3c/editing] July 29th F2F Agenda Item - static ranges (#138) gked
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) Chris Dumez
• Re: [slightlyoff/ServiceWorker] Reporting URL for SW update failures (#877) Jake Archibald
• Re: [w3c/editing] July 29th F2F Agenda Item - Non-cancelable event (#137) gked
• [w3c/editing] July 29th F2F Agenda Item - Non-cancelable event (#137) gked
• Re: [w3c/editing] July 29th F2F Agenda Item - History handling (undo/redo) (#136) gked
• Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) Jake Archibald
• [w3c/editing] July 29th F2F Agenda Item - History handling (undo/redo) (#136) gked
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) Philip Jägenstedt
• Re: [w3c/editing] July 29th F2F Agenda Item - Clipboard events (#135) gked
• [w3c/editing] July 29th F2F Agenda Item - Clipboard events (#135) gked
• Re: [w3c/WebPlatformWG] F2F Agenda Item - Dragging and dropping (#60) gked
• Re: [w3c/WebPlatformWG] F2F Agenda Item - Dragging and dropping (#60) gked
• Re: [w3c/WebPlatformWG] F2F Agenda Item - Dragging and dropping (#60) gked
• Re: [w3c/editing] July 29th F2F Agenda Item - Dragging and dropping (#134) gked
• [w3c/editing] July 29th F2F Agenda Item - Dragging and dropping (#134) gked
• Re: [slightlyoff/ServiceWorker] cache.match should create partial responses if given a range request (#913) Jake Archibald
• [slightlyoff/ServiceWorker] Block 206s entering the cache (via put & addAll) (#937) Jake Archibald
• Re: [w3c/WebPlatformWG] F2F Agenda Item - Dragging and dropping (#60) gked
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Jake Archibald
• [whatwg/streams] Repo/package confusion (#487) Anders Riutta
• Re: [slightlyoff/ServiceWorker] ServiceWorkerContainer spec lists `onerror` as an event handler (#912) Jungkee Song
• Re: [whatwg/dom] Figure out what to do with XMLDocument (#278) Chris Dumez
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) Chris Dumez
• Re: [slightlyoff/ServiceWorker] Should mixed content always be blocked? (#813) Anne van Kesteren
• Re: [w3c/charter-html] Indicate relationship with the WHATWG (#112) Anne van Kesteren
• [whatwg/fetch] The comma-delimited combined value definition does not support Set-Cookie headers (#345) Malisa
• [w3c/WebPlatformWG] F2F Agenda Item - Dragging and dropping (#60) gked
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) Philip Jägenstedt
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) Chris Dumez
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) Matthew Phillips
• Re: [w3c/charter-html] define roles for the entire set of stakeholders (#19) chaals
• Re: [w3c/charter-html] Innovation (#9) chaals
• Re: [w3c/charter-html] Clarify the problem space (#18) chaals
• Re: [w3c/charter-html] unclear about wg leadership bullet point (#11) chaals
• Re: [w3c/charter-html] Innovation (#9) chaals
• Re: [w3c/charter-html] Bugs get property triaged, prioritized, and addressed (#2) chaals
• Re: [w3c/charter-html] Bugs get property triaged, prioritized, and addressed (#2) chaals
• Re: [w3c/charter-html] Groups split (#14) chaals
• Re: [w3c/charter-html] Groups split (#14) chaals
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) Johannes Wilm
• Re: [whatwg/storage] Exposing cross-origin resource size (#31) Ehsan Akhgari
• Re: [whatwg/storage] Exposing cross-origin resource size (#31) Jake Archibald
• Re: [w3c/charter-html] Embrace modern spec dev practices (#7) chaals
• Re: [w3c/charter-html] Embrace modern spec dev practices (#7) chaals
• Re: [w3c/charter-html] Test based standardization (#3) chaals
• Re: [w3c/charter-html] Test based standardization (#3) chaals
• Re: [w3c/charter-html] Indicate relationship with the WHATWG (#112) chaals
• Re: [w3c/charter-html] Indicate relationship with the WHATWG (#112) chaals
• Re: [w3c/charter-html] Work on HTML (#130) chaals
• Re: [w3c/charter-html] Styling for readability (#115) chaals
• Re: [w3c/charter-html] Styling for readability (#115) chaals
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) Jake Archibald
• [w3c/manifest] Define how the manifest is fetched (#481) Jake Archibald
• Re: [w3c/WebPlatformWG] Add items that interest me for the editing tf meeting. (#59) chaals
• Re: [slightlyoff/ServiceWorker] OCSP fetches bypass service worker (#564) Jungkee Song
• Re: [whatwg/dom] iterable declaration on NodeList is invalid (#284) Boris Zbarsky
• Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Should mixed content always be blocked? (#813) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Should mixed content always be blocked? (#813) Anne van Kesteren
• Re: [slightlyoff/ServiceWorker] Should mixed content always be blocked? (#813) Jake Archibald
• Re: [slightlyoff/ServiceWorker] should UA check for updates on navigate when there is no fetch event? (#905) Alex Russell
• Re: [slightlyoff/ServiceWorker] consider firing a "clientcontrolled" event on ServiceWorkerGlobalScope (#886) Jake Archibald
• Re: [slightlyoff/ServiceWorker] ServiceWorkerContainer spec lists `onerror` as an event handler (#912) Alex Russell
• Re: [slightlyoff/ServiceWorker] Receivers of ranged responses must ensure all ranges come from the same underlying resource (#703) Jake Archibald
• Re: [slightlyoff/ServiceWorker] should async waitUntil() work in .then() handler of promise passed to previous waitUntil()? (#935) Jake Archibald
• Re: [slightlyoff/ServiceWorker] should async waitUntil() work in .then() handler of promise passed to previous waitUntil()? (#935) Alex Russell
• Re: [slightlyoff/ServiceWorker] Should waitUntil() fast fail if a single extension promise rejects? (#936) Alex Russell
• Re: [slightlyoff/ServiceWorker] Receivers of ranged responses must ensure all ranges come from the same underlying resource (#703) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Receivers of ranged responses must ensure all ranges come from the same underlying resource (#703) Alex Russell
• Re: [slightlyoff/ServiceWorker] should FetchEvent.request.cache reflect non-fetch browser cache controls? (#875) Anne van Kesteren
• Re: [slightlyoff/ServiceWorker] Should mixed content always be blocked? (#813) Anne van Kesteren
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) Anne van Kesteren
• Re: [whatwg/dom] Make Attr a Node again (#102) Anne van Kesteren
• Re: [whatwg/fetch] Add trailer support to network responses (#344) Anne van Kesteren
• Re: [whatwg/fetch] Access to the HTTP trailer (#34) Mark Nottingham
• Re: [w3c/manifest] Adding the webapp's badge to the manifest (#480) Kenneth Rohde Christiansen
• Re: [whatwg/fetch] Add trailer support to network responses (#344) Mark Nottingham
• Re: [whatwg/fetch] Add trailer support to network responses (#344) Anne van Kesteren
• Re: [whatwg/fetch] Add trailer support to network responses (#344) Anne van Kesteren
• Re: [whatwg/fetch] Add trailer support to network responses (#344) Anne van Kesteren
• Re: [whatwg/fetch] Add trailer support to network responses (#344) Anne van Kesteren
• [whatwg/streams] Editorial changes to the socket example (#486) Adam Rice
• Re: [whatwg/fetch] Add trailer support to network responses (#344) Wenbo Zhu
• Re: [whatwg/fetch] Add trailer support to network responses (#344) Yutaka Hirano
• Re: [whatwg/fetch] Add trailer support to network responses (#344) Anne van Kesteren
• Re: [whatwg/fetch] Access to the HTTP trailer (#34) Anne van Kesteren
• Re: [whatwg/fetch] Add trailer support to network responses (#344) Yutaka Hirano
• Re: [whatwg/fetch] Add trailer support to network responses (#344) Anne van Kesteren
• Re: [whatwg/fetch] Access to the HTTP trailer (#34) Yutaka Hirano
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) yosin
• Re: [whatwg/xhr] good (#81) Anne van Kesteren
• Re: [whatwg/encoding] "URL parsing HTML form submission" (#67) Anne van Kesteren
• Re: [whatwg/encoding] "URL parsing HTML form submission" (#67) Anne van Kesteren
• Re: [whatwg/dom] iterable declaration on NodeList is invalid (#284) Anne van Kesteren
• Re: [whatwg/encoding] "In equations, all numbers are integers, additio..." (#66) Anne van Kesteren
• [w3c/WebPlatformWG] Add items that interest me for the editing tf meeting. (#59) Dave Tapuska
• [whatwg/encoding] "URL parsing HTML form submission" (#67) Adam Rice
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) Johannes Wilm
• [whatwg/encoding] "In equations, all numbers are integers, additio..." (#66) Adam Rice
• Re: [whatwg/streams] "socket.setTCPWindowSize" (#483) Adam Rice
• Re: [whatwg/streams] "socket.setTCPWindowSize" (#483) Adam Rice
• Re: [whatwg/dom] iterable declaration on NodeList is invalid (#284) Boris Zbarsky
• [whatwg/dom] iterable declaration on NodeList is invalid (#284) Boris Zbarsky
• [whatwg/xhr] good (#81) chengxuwang
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) yosin
• Re: [w3c/webcomponents] Polyfilling custom elements with native Shadow DOM support (#534) Trey Shugart
• Re: [w3c/webcomponents] Polyfilling custom elements with native Shadow DOM support (#534) Trey Shugart
• Re: [whatwg/dom] Make Attr a Node again (#102) Chris Dumez
• Re: [whatwg/dom] Make Attr a Node again (#102) Philip Jägenstedt
• [w3c/webcomponents] Polyfilling custom elements with native Shadow DOM support (#534) Trey Shugart
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) Jeffrey Yasskin

Thursday, 28 July 2016

• Re: [w3c/manifest] Adding the webapp's badge to the manifest (#480) Marcos Cáceres
• [w3ctag/packaging-on-the-web] Can a package be authenticated to come from a particular secure origin? (#30) Jeffrey Yasskin
• Re: [slightlyoff/ServiceWorker] Should waitUntil() fast fail if a single extension promise rejects? (#936) Jake Archibald
• Re: [slightlyoff/ServiceWorker] should async waitUntil() work in .then() handler of promise passed to previous waitUntil()? (#935) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Does accessing ExtendableEvent's extend lifetime promises race? (#931) Jake Archibald
• Re: [slightlyoff/ServiceWorker] clarify behavior when fetch event handler throws (#896) Inian
• Re: [slightlyoff/ServiceWorker] Need to review the algorithms for creating a new environment settings object (#919) Jungkee Song
• Re: [slightlyoff/ServiceWorker] Need to review the algorithms for creating a new environment settings object (#919) Jungkee Song
• Re: [slightlyoff/ServiceWorker] Should WindowClient.navigate(url) navigate with "replacement enabled"? (#918) Jake Archibald
• Re: [slightlyoff/ServiceWorker] More clarity around waiting for an active worker to finish (#916) Jake Archibald
• Re: [slightlyoff/ServiceWorker] ServiceWorkerContainer spec lists `onerror` as an event handler (#912) Jake Archibald
• Re: [slightlyoff/ServiceWorker] should UA check for updates on navigate when there is no fetch event? (#905) Jake Archibald
• Re: [slightlyoff/ServiceWorker] clarify behavior when fetch event handler throws (#896) Jake Archibald
• Re: [slightlyoff/ServiceWorker] clarify behavior when fetch event handler throws (#896) Jake Archibald
• Re: [slightlyoff/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) Jake Archibald
• Re: [slightlyoff/ServiceWorker] potential http cache issues with importScripts() (#894) Jake Archibald
• Re: [slightlyoff/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) Jake Archibald
• Re: [slightlyoff/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Create F2F agenda - 28-29 July 2016 (#932) Jake Archibald
• Re: [slightlyoff/ServiceWorker] clarify secure context requirements in Handle Fetch (#890) Jake Archibald
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) Johannes Wilm
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) Chong Zhang
• Re: [slightlyoff/ServiceWorker] spec exactly how to order non-window Client objects (#887) beidson
• Re: [slightlyoff/ServiceWorker] spec exactly how to order non-window Client objects (#887) aliams
• Re: [slightlyoff/ServiceWorker] clarify that Clients.matchAll() only returns Window Client objects with active documents (#888) Jake Archibald
• Re: [slightlyoff/ServiceWorker] spec exactly how to order non-window Client objects (#887) beidson
• Re: [slightlyoff/ServiceWorker] spec exactly how to order non-window Client objects (#887) Jake Archibald
• Re: [slightlyoff/ServiceWorker] ServiceWorker lifetime and respondWith() with a user-constructed ReadableStream (#882) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Split the cache API into its own spec (#879) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870) Jungkee Song
• Re: [slightlyoff/ServiceWorker] Should mixed content always be blocked? (#813) Mike West
• Re: [slightlyoff/ServiceWorker] should FetchEvent.request.cache reflect non-fetch browser cache controls? (#875) Jake Archibald
• Re: [slightlyoff/ServiceWorker] why does Register algorithm step 5.3.1 check for an active worker? (#856) Jake Archibald
• Re: [slightlyoff/ServiceWorker] FetchEvent.respondWith does something weird with the body of a response (#850) Jungkee Song
• Re: [slightlyoff/ServiceWorker] html no longer defines "referrer source" (#834) Jungkee Song
• Re: [slightlyoff/ServiceWorker] Resolve Job Promise can resolve jobs with an incorrect value (#829) Jungkee Song
• [w3c/permissions] Guidance on whether to add an API to the permissions spec (#116) Jeffrey Yasskin
• Re: [whatwg/fetch] Add trailer support to network responses (#344) Louis Ryan
• Re: [whatwg/dom] Make Attr a Node again (#102) Chris Dumez
• Re: [slightlyoff/ServiceWorker] Should mixed content always be blocked? (#813) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Should the active worker move to environment settings object? (#811) Jungkee Song
• Re: [slightlyoff/ServiceWorker] spec behavior when ServiceWorkerContainer parent client is dead (#777) aliams
• Re: [slightlyoff/ServiceWorker] Create F2F agenda - 28-29 July 2016 (#932) Jake Archibald
• [w3ctag/spec-reviews] Review origin policy. (#127) Mike West
• Re: [w3c/manifest] Adding the webapp's badge to the manifest (#480) Sebastian Kippe
• Re: [w3c/manifest] Adding the webapp's badge to the manifest (#480) Peter Beverloo
• Re: [whatwg/fetch] Add trailer support to network responses (#344) Anne van Kesteren
• [whatwg/fetch] Add trailer support to network responses (#344) Anne van Kesteren
• Re: [slightlyoff/ServiceWorker] Create F2F agenda - 28-29 July 2016 (#932) Jake Archibald
• Re: [slightlyoff/ServiceWorker] spec behavior when ServiceWorkerContainer parent client is dead (#777) Jake Archibald
• Re: [slightlyoff/ServiceWorker] spec behavior when ServiceWorkerContainer parent client is dead (#777) Jake Archibald
• Re: [slightlyoff/ServiceWorker] spec behavior when ServiceWorkerContainer parent client is dead (#777) Marijn Kruisselbrink
• Re: [slightlyoff/ServiceWorker] serviceworker for iframes with srcdoc (#765) Jungkee Song
• Re: [slightlyoff/ServiceWorker] Remove frameType, maybe add ancestorOrigins (#732) Jake Archibald
• Re: [slightlyoff/ServiceWorker] spec should be more explicit about accessing internal body on opaque Responses (#710) Jake Archibald
• Re: [slightlyoff/ServiceWorker] OCSP fetches bypass service worker (#564) Jake Archibald
• Re: [w3c/manifest] Adding the webapp's badge to the manifest (#480) Kenneth Rohde Christiansen
• [whatwg/fetch] Non-null response body check is a no-op (#343) Anne van Kesteren
• Re: [whatwg/streams] "Web sockets do not provide any way to tell when..." (#485) Takeshi Yoshino
• Re: [whatwg/streams] "if (controller.byobRequest)" (#484) Takeshi Yoshino
• Re: [whatwg/streams] "socket.setTCPWindowSize" (#483) Takeshi Yoshino
• Re: [whatwg/streams] "socket.setTCPWindowSize" (#483) Takeshi Yoshino
• [whatwg/streams] "Web sockets do not provide any way to tell when..." (#485) Adam Rice
• Re: [whatwg/streams] "if (controller.byobRequest)" (#484) Adam Rice
• Re: [whatwg/streams] "if (controller.byobRequest)" (#484) Adam Rice
• [whatwg/streams] "if (controller.byobRequest)" (#484) Adam Rice
• [whatwg/streams] "socket.setTCPWindowSize" (#483) Adam Rice
• Re: [w3ctag/spec-reviews] WebRTC (#14) Mark Nottingham
• Re: [w3ctag/spec-reviews] WebRTC (#14) Daniel Appelquist
• Re: [whatwg/fetch] Access to the HTTP trailer (#34) Anne van Kesteren
• [whatwg/streams] "ws.onend" (#482) Adam Rice
• Re: [whatwg/fetch] Support same-origin, strict-origin, strict-origin-when-cross-origin in request' referrer policy (#342) Anne van Kesteren
• Re: [whatwg/url] Url definition should define the fragment as optional (#134) Anne van Kesteren
• Re: [whatwg/url] Url definition should define the fragment as optional (#134) Anne van Kesteren
• Re: [slightlyoff/ServiceWorker] OCSP fetches bypass service worker (#564) Anne van Kesteren
• Re: [w3c/permissions] Add pointerlock to the permissions enum? (#67) Anne van Kesteren
• Re: [w3c/permissions] Add pointerlock to the permissions enum? (#67) Anne van Kesteren
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) Anne van Kesteren
• Re: [w3c/permissions] Add pointerlock to the permissions enum? (#67) raymeskhoury
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) raymeskhoury
• Re: [whatwg/url] Url definition should define the fragment as optional (#134) Michael[tm] Smith
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) Johannes Wilm
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) yosin
• Re: [whatwg/fetch] Support same-origin, strict-origin, strict-origin-when-cross-origin in request' referrer policy (#342) Michael[tm] Smith
• [whatwg/fetch] Support same-origin, strict-origin, strict-origin-when-cross-origin in request' referrer policy (#342) tnguyen
• Re: [w3ctag/spec-reviews] Browser Fingerprinting Document (#38) Nick Doty
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) Johannes Wilm
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) yosin
• Re: [slightlyoff/ServiceWorker] should async waitUntil() work in .then() handler of promise passed to previous waitUntil()? (#935) Ben Kelly
• Re: [w3c/gamepad] Added GamepadPose and GamepadCapabilities (#25) Brandon Jones
• Re: [w3c/WebPlatformWG] added one more item to the agenda (#55) gked
• Re: [w3c/WebPlatformWG] added one more item to the agenda (#55) gked

Wednesday, 27 July 2016

• [slightlyoff/ServiceWorker] Should waitUntil() fast fail if a single extension promise rejects? (#936) Ben Kelly
• Re: [slightlyoff/ServiceWorker] clarify secure context requirements in Handle Fetch (#890) Salvador de la Puente González
• Re: [w3c/WebPlatformWG] added issues 131/132 (#58) Johannes Wilm
• [w3c/WebPlatformWG] added issues 131/132 (#58) Johannes Wilm
• [w3c/gamepad] IDL array[]s no longer exist (#28) Domenic Denicola
• Re: [w3c/gamepad] Added GamepadPose and GamepadCapabilities (#25) Domenic Denicola
• [w3c/WebPlatformWG] further cleanup (#57) Johannes Wilm
• Re: [w3c/WebPlatformWG] further cleanup (#57) Johannes Wilm
• [w3c/WebPlatformWG] small cleanups (#56) Johannes Wilm
• Re: [w3c/WebPlatformWG] small cleanups (#56) Johannes Wilm
• [slightlyoff/ServiceWorker] should async waitUntil() work in .then() handler of promise passed to previous waitUntil()? (#935) Ben Kelly
• Re: [slightlyoff/ServiceWorker] clarify secure context requirements in Handle Fetch (#890) Jake Archibald
• [w3c/WebPlatformWG] added one more item to the agenda (#55) gked
• Re: [whatwg/fetch] Only append Authorization if none is set (#198) Anne van Kesteren
• Re: [slightlyoff/ServiceWorker] clarify secure context requirements in Handle Fetch (#890) Salvador de la Puente González
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) Johannes Wilm
• Re: [whatwg/url] Let webkitURL be an alias of the URL constructor (#135) Domenic Denicola
• Re: [slightlyoff/ServiceWorker] html no longer defines "referrer source" (#834) Domenic Denicola
• Re: [slightlyoff/ServiceWorker] OCSP fetches bypass service worker (#564) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Receivers of ranged responses must ensure all ranges come from the same underlying resource (#703) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Add cookie accessor/setter methods? (#707) Benjamin C. Wiley Sittler
• Re: [slightlyoff/ServiceWorker] Remove frameType, maybe add ancestorOrigins (#732) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Add cookie accessor/setter methods? (#707) Benjamin C. Wiley Sittler
• Re: [slightlyoff/ServiceWorker] serviceworker for iframes with srcdoc (#765) Jake Archibald
• Re: [whatwg/url] Let webkitURL be an alias of the URL constructor (#135) Anne van Kesteren
• Re: [slightlyoff/ServiceWorker] navigations that are not intercepted should still allow interception on further redirects (#793) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Should the active worker move to environment settings object? (#811) Jake Archibald
• Re: [slightlyoff/ServiceWorker] ExtendableMessageEvent.source cannot be SameObject (#816) Jake Archibald
• Re: [slightlyoff/ServiceWorker] html no longer defines "referrer source" (#834) Jake Archibald
• Re: [slightlyoff/ServiceWorker] FetchEvent.respondWith does something weird with the body of a response (#850) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Unregister algorithm step 6.1 is no longer necessary (#855) Jake Archibald
• Re: [slightlyoff/ServiceWorker] why does Register algorithm step 5.3.1 check for an active worker? (#856) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Drop isReload (#873) Jake Archibald
• Re: [slightlyoff/ServiceWorker] should FetchEvent.request.cache reflect non-fetch browser cache controls? (#875) Jake Archibald
• Re: [slightlyoff/ServiceWorker] should FetchEvent.request.cache reflect non-fetch browser cache controls? (#875) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Split the cache API into its own spec (#879) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Move service worker spec into w3c (#881) Jake Archibald
• Re: [slightlyoff/ServiceWorker] ServiceWorker lifetime and respondWith() with a user-constructed ReadableStream (#882) Jake Archibald
• Re: [slightlyoff/ServiceWorker] addAll should resolve when the cache is fully & successfully written (#884) Jake Archibald
• Re: [slightlyoff/ServiceWorker] spec exactly how to order non-window Client objects (#887) Jake Archibald
• Re: [slightlyoff/ServiceWorker] clarify that Clients.matchAll() only returns Window Client objects with active documents (#888) Jake Archibald
• Re: [slightlyoff/ServiceWorker] clarify secure context requirements in Handle Fetch (#890) Jake Archibald
• Re: [slightlyoff/ServiceWorker] clarify secure context requirements in Handle Fetch (#890) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) Jake Archibald
• Re: [slightlyoff/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) Jake Archibald
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) Chong Zhang
• Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) Johannes Wilm
• [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) Chong Zhang
• Re: [slightlyoff/ServiceWorker] potential http cache issues with importScripts() (#894) Jake Archibald
• Re: [slightlyoff/ServiceWorker] clarify behavior when fetch event handler throws (#896) Jake Archibald
• [w3c/permissions] feat(algorithms): allow calling with a PermissionName (#115) Jeffrey Yasskin
• Re: [slightlyoff/ServiceWorker] ServiceWorkerContainer spec lists `onerror` as an event handler (#912) Jake Archibald
• Re: [slightlyoff/ServiceWorker] More clarity around waiting for an active worker to finish (#916) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Why doesn't cache.match support `cacheName` (#917) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Why doesn't cache.match support `cacheName` (#917) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Should WindowClient.navigate(url) navigate with "replacement enabled"? (#918) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Need to review the algorithms for creating a new environment settings object (#919) Jake Archibald
• [whatwg/url] Let webkitURL be an alias of the URL constructor (#135) Philip Jägenstedt
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) Jeffrey Yasskin
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) Jeffrey Yasskin
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) Jeffrey Yasskin
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) Jeffrey Yasskin
• Re: [slightlyoff/ServiceWorker] Create F2F agenda - 28-29 July 2016 (#932) Jake Archibald
• Re: [w3ctag/spec-reviews] Review WAPA (Accessibility) proposal (#63) Travis Leithead
• Re: [whatwg/fetch] Only append Authorization if none is set (#198) youennf
• Re: [whatwg/fetch] Only append Authorization if none is set (#198) Anne van Kesteren
• Re: [whatwg/fetch] Only append Authorization if none is set (#198) youennf
• Re: [whatwg/fetch] Only append Authorization if none is set (#198) Anne van Kesteren
• Re: [whatwg/fetch] Only append Authorization if none is set (#198) youennf
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) Anne van Kesteren
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) Anne van Kesteren
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) Anne van Kesteren
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) Anne van Kesteren
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) Jeffrey Yasskin
• Re: [whatwg/fetch] Access to the HTTP trailer (#34) Anne van Kesteren
• Re: [whatwg/fetch] Only append Authorization if none is set (#198) Anne van Kesteren
• Re: [whatwg/fetch] Only append Authorization if none is set (#198) youennf
• Re: [whatwg/fetch] RFC: a mechanism to bypass CORS preflight (#210) Takeshi Yoshino
• Re: [whatwg/fetch] RFC: a mechanism to bypass CORS preflight (#210) Mike West
• Re: [whatwg/fetch] RFC: a mechanism to bypass CORS preflight (#210) Takeshi Yoshino
• Re: [whatwg/fetch] Add steps to intercept requests using foreign fetch. (#329) Anne van Kesteren
• Re: [whatwg/fetch] Add steps to intercept requests using foreign fetch. (#329) Anne van Kesteren
• Re: [whatwg/fetch] Add steps to intercept requests using foreign fetch. (#329) Anne van Kesteren
• Re: [whatwg/fetch] Add steps to intercept requests using foreign fetch. (#329) Anne van Kesteren
• Re: [whatwg/fetch] Add steps to intercept requests using foreign fetch. (#329) Anne van Kesteren
• Re: [whatwg/fetch] Add steps to intercept requests using foreign fetch. (#329) Anne van Kesteren
• Re: [whatwg/fetch] Add steps to intercept requests using foreign fetch. (#329) Anne van Kesteren
• Re: [whatwg/fetch] Add steps to intercept requests using foreign fetch. (#329) Anne van Kesteren
• Re: [whatwg/fetch] Add steps to intercept requests using foreign fetch. (#329) Anne van Kesteren
• Re: [w3c/pointerlock] Add pointerlock to the permissions enum (#5) Anne van Kesteren
• [w3c/editing] How to handle IME-alike input for European languages on Mac OS X for accent marks on long key press (#132) Johannes Wilm
• [w3c/editing] How to combine data and transferData attributes? (#131) Johannes Wilm

Tuesday, 26 July 2016

• [w3c/permissions] refactor(permission state): pass the settings object explicitly (#114) Jeffrey Yasskin
• Re: [whatwg/streams] light weight transformations (#461) Gabriel Wicke
• Re: [w3c/permissions] Editorial fixes (#100) Jeffrey Yasskin
• Re: [w3c/touch-events] Add interaction with pointer events and compat mouse events (#70) Rick Byers
• Re: [w3c/pointerlock] Add pointerlock to the permissions enum (#5) Vincent Scheib
• Re: [w3c/pointerlock] Add pointerlock to the permissions enum (#5) Anne van Kesteren
• Re: [w3c/uievents] 4.1 and 4.9 keypress is deprecated (#96) Gary Kacmarcik
• Re: [w3c/uievents] 9.4 mutation events are deprecated (#103) Gary Kacmarcik
• Re: [w3c/uievents] 9.4 mutation events are deprecated (#103) Gary Kacmarcik
• Re: [w3c/uievents] 9.4 mutation events are deprecated (#102) Gary Kacmarcik
• Re: [w3c/uievents] 4.1 and 4.9 keypress is deprecated (#96) Gary Kacmarcik
• Re: [w3c/uievents] 4.1 and 4.9 keypress is deprecated (#96) Gary Kacmarcik
• Re: [whatwg/fetch] Add steps to intercept requests using foreign fetch. (#329) Marijn Kruisselbrink
• [w3c/pointerlock] Add pointerlock to the permissions enum (#5) Vincent Scheib
• Re: [w3c/uievents] Typo in 3.2 (#94) Gary Kacmarcik
• Re: [slightlyoff/ServiceWorker] spec should be more explicit about accessing internal body on opaque Responses (#710) aliams
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Salvador de la Puente González
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Salvador de la Puente González
• Re: [slightlyoff/ServiceWorker] clarify secure context requirements in Handle Fetch (#890) Salvador de la Puente González
• Re: [slightlyoff/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) Inian
• Re: [whatwg/fetch] HTTP/2 server push support (#51) Anne van Kesteren
• Re: [whatwg/fetch] Access to the HTTP trailer (#34) Anne van Kesteren
• Re: [whatwg/fetch] HTTP/2 server push support (#51) Ilya Grigorik
• Re: [whatwg/dom] Remove SVGZoomEvent? (#283) Ms2ger
• Re: [whatwg/fetch] HTTP/2 server push support (#51) Martin Thomson
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) Takeshi Yoshino
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) Takeshi Yoshino
• [whatwg/url] Url definition should define the fragment as optional (#134) David Burns
• Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) Salvador de la Puente González
• Re: [slightlyoff/ServiceWorker] clarify secure context requirements in Handle Fetch (#890) Jake Archibald
• Re: [slightlyoff/ServiceWorker] clarify secure context requirements in Handle Fetch (#890) Anne van Kesteren
• Re: [w3c/push-api] applicationServerKey is never used in subscribe() (#209) Martin Thomson
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) Anne van Kesteren
• Re: [w3c/permissions] Flesh out request("push") (#111) Martin Thomson
• Re: [slightlyoff/ServiceWorker] More clarity around waiting for an active worker to finish (#916) aliams
• Re: [slightlyoff/ServiceWorker] spec exactly how to order non-window Client objects (#887) aliams
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/permissions] Check request() polyfill and update spec to match (#113) Marcos Cáceres
• [w3c/permissions] Check request() polyfill and update spec to match (#113) Jeffrey Yasskin
• Re: [w3c/manifest] Adding the webapp's badge to the manifest (#480) Marcos Cáceres
• [w3c/permissions] Flesh out request("geolocation") (#112) Jeffrey Yasskin

Monday, 25 July 2016

• Re: [w3c/manifest] Adding the webapp's badge to the manifest (#480) Peter Beverloo
• Re: [w3c/manifest] Adding the webapp's badge to the manifest (#480) Ben
• [w3c/permissions] Flesh out request("push") (#111) Jeffrey Yasskin
• [w3c/push-api] applicationServerKey is never used in subscribe() (#209) Jeffrey Yasskin
• Re: [slightlyoff/ServiceWorker] Should WindowClient.navigate(url) navigate with "replacement enabled"? (#918) aliams
• Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) Ben Kelly
• Re: [w3c/WebPlatformWG] Update 16-07-28-29SW.md (#54) chaals
• Re: [slightlyoff/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) Nathan Schloss
• Re: [slightlyoff/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) Nathan Schloss
• Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) Salvador de la Puente González
• Re: [slightlyoff/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) Murali Ramanujam
• [w3c/WebPlatformWG] Update 16-07-28-29SW.md (#54) Nathan Schloss
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Create F2F agenda - 28-29 July 2016 (#932) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Should mixed content always be blocked? (#813) Jake Archibald
• Re: [slightlyoff/ServiceWorker] clarify Request.isReload for sub-resources (#827) Jake Archibald
• Re: [slightlyoff/ServiceWorker] clarify Request.isReload for sub-resources (#827) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Provide cache.putAll() method (#867) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Provide cache.putAll() method (#867) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Add a way to detect reloading only client (#872) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Add a way to detect reloading only client (#872) Jake Archibald
• [w3c/manifest] Adding the webapp's badge to the manifest (#480) Peter Beverloo
• Re: [slightlyoff/ServiceWorker] Where are ServiceWorker data stored? (#883) Jake Archibald
• Re: [slightlyoff/ServiceWorker] spec exactly how to order non-window Client objects (#887) Jake Archibald
• Re: [slightlyoff/ServiceWorker] clarify secure context requirements in Handle Fetch (#890) Jake Archibald
• Re: [slightlyoff/ServiceWorker] clarify secure context requirements in Handle Fetch (#890) Jake Archibald
• Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) sleevi
• Re: [w3c/WebPlatformWG] add Johannes Wilm to participant list (#53) Johannes Wilm
• [w3c/WebPlatformWG] add Johannes Wilm to participant list (#53) Johannes Wilm
• Re: [slightlyoff/ServiceWorker] clarify secure context requirements in Handle Fetch (#890) Jake Archibald
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) Anne van Kesteren
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) Peter Beverloo
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) Ben Kelly
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) Anne van Kesteren
• Re: [w3c/push-api] Send notifications in batch (#208) Peter Beverloo
• Re: [w3c/push-api] Send notifications in batch (#208) Peter Beverloo
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) Ben Kelly
• Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) Jake Archibald
• Re: [slightlyoff/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) Jake Archibald
• Re: [slightlyoff/ServiceWorker] why cant i register a embedded function as for shared worker? (#902) Jake Archibald
• Re: [slightlyoff/ServiceWorker] should UA check for updates on navigate when there is no fetch event? (#905) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Make ServiceWorkers more tailored for "always offline" websites (#907) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Make ServiceWorkers more tailored for "always offline" websites (#907) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Authenticated PWA ? (#909) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Authenticated PWA ? (#909) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Authenticated PWA ? (#909) Jake Archibald
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) Anne van Kesteren
• [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) Anne van Kesteren
• Re: [whatwg/fetch] no-referrer should not set referer header (#323) Anne van Kesteren
• Re: [whatwg/fetch] no-referrer should not set referer header (#323) Anne van Kesteren
• Re: [whatwg/fetch] no-referrer should not set referer header (#323) jeisinger
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) Jungkee Song
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) Jungkee Song
• Re: [w3c/push-api] typedef object JSON; is incorrect (#204) Anne van Kesteren
• Re: [w3c/push-api] typedef object JSON; is incorrect (#204) Anne van Kesteren
• Re: [w3c/push-api] typedef object JSON; is incorrect (#204) Michael van Ouwerkerk
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) Anne van Kesteren
• Re: [w3c/push-api] typedef object JSON; is incorrect (#204) Anne van Kesteren
• Re: [w3c/push-api] Running tidy (#207) Michael van Ouwerkerk
• Re: [w3c/push-api] JSON.parse produces any not object (#206) Michael van Ouwerkerk
• Re: [w3c/push-api] typedef object JSON; is incorrect (#204) Michael van Ouwerkerk
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) Jungkee Song
• Re: [whatwg/fetch] Block text/csv for requests whose type is "script"? (#337) Mike West
• Re: [w3c/gamepad] Added GamepadPose and GamepadCapabilities (#25) Christopher Rodriguez

Sunday, 24 July 2016

• Re: [whatwg/fetch] response.ok = false for opaque responses may be misleading (#299) Liam
• Re: [w3c/editing] We should keep data in UI events for beforeInput that does the text/plain serialization. We should add dataTransfer to the editing spec for other mime types(html, text with line breaks, etc) (#106) Johannes Wilm
• Re: [w3c/editing] We should ensure drag/drop also fires beforeInput (#107) Johannes Wilm
• Re: [w3c/editing] RESOLUTION: We are going to focus on describing ce=typing as a priority. (#85) Johannes Wilm
• Re: [w3c/editing] RESOLUTION: We are going to focus on describing ce=typing as a priority. (#85) Johannes Wilm
• Re: [w3c/gamepad] Determine how Multi-touch surfaces should be handled. (#27) Christopher Rodriguez
• Re: [whatwg/encoding] Editorial: make gb18030 math more clear (#65) Anne van Kesteren
• [whatwg/encoding] Editorial: make gb18030 math more clear (#65) Anne van Kesteren
• Re: [whatwg/encoding] Please double-check the end of the EUDC range (#53) Anne van Kesteren
• Re: [whatwg/encoding] Please double-check the end of the EUDC range (#53) Anne van Kesteren
• Re: [whatwg/encoding] Please double-check the end of the EUDC range (#53) Anne van Kesteren
• Re: [whatwg/encoding] Please double-check the end of the EUDC range (#53) vyv03354
• Re: [whatwg/encoding] Please double-check the end of the EUDC range (#53) Anne van Kesteren
• Re: [whatwg/encoding] Please double-check the end of the EUDC range (#53) Anne van Kesteren
• Re: [whatwg/encoding] Please double-check the end of the EUDC range (#53) vyv03354
• Re: [whatwg/encoding] Correct [Exposed] syntax (#64) Anne van Kesteren
• Re: [whatwg/encoding] Correct [Exposed] syntax (#64) Anne van Kesteren
• [whatwg/encoding] Correct [Exposed] syntax (#64) Ms2ger

Saturday, 23 July 2016

• [w3c/uievents] 9.4 mutation events are deprecated (#103) Léonie Watson
• [w3c/uievents] 9.4 mutation events are deprecated (#102) Léonie Watson
• [w3c/uievents] 5.7 composition events use case (#101) Léonie Watson
• [w3c/uievents] 5.5 input events notifications (#100) Léonie Watson
• [w3c/uievents] 5.4.2 focusin and focusout bubble use case? (#99) Léonie Watson
• [w3c/uievents] 5.2 focus events accessibility (#98) Léonie Watson
• [w3c/uievents] 5.12 event types (#97) Léonie Watson
• Re: [whatwg/dom] Remove SVGZoomEvent? (#283) Anne van Kesteren
• [w3c/uievents] 4.1 and 4.9 keypress is deprecated (#96) Léonie Watson
• [w3c/uievents] 3.4 and 3.5 duplicate HTML spec (#95) Léonie Watson
• [w3c/uievents] Typo in 3.2 (#94) Léonie Watson
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) Anne van Kesteren
• [w3c/push-api] Send notifications in batch (#208) Marco Colli
• Re: [slightlyoff/ServiceWorker] Create a new ReadableStream in FetchEvent.respondWith (#934) Jungkee Song
• Re: [w3c/IndexedDB] Asynchronously executing a request should queue a task to fire events (#83) Anthony Ramine
• [w3c/push-api] Running tidy (#207) Martin Thomson
• Re: [slightlyoff/ServiceWorker] Run the latest Bikeshed (#933) Jungkee Song
• Re: [slightlyoff/ServiceWorker] Run the latest Bikeshed (#933) Jungkee Song
• [w3c/push-api] JSON.parse produces any not object (#206) Martin Thomson
• [whatwg/dom] Remove SVGZoomEvent? (#283) Ms2ger
• Re: [whatwg/dom] MutationObserver with querySelector for elements (#77) Ryosuke Niwa
• Re: [whatwg/dom] MutationObserver with querySelector for elements (#77) Muromi Ukari

Friday, 22 July 2016

• Re: [w3c/permissions] Add persistent storage (#39) Tab Atkins Jr.
• [w3c/push-api] Define behaviour of pushsubscriptionchange in the event of an error (#205) Ben Last
• Re: [whatwg/fetch] Delay network errors to prevent port scanning (#338) Patrick McManus
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) Anne van Kesteren
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Jake Archibald
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) Jeffrey Yasskin
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) Anne van Kesteren
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) Ben Kelly
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) Anne van Kesteren
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) Jeffrey Yasskin
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) Ben Kelly
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) Anne van Kesteren
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) Anne van Kesteren
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) Jeffrey Yasskin
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) Anne van Kesteren
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) Jeffrey Yasskin
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) Anne van Kesteren
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) Anne van Kesteren
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) Anne van Kesteren
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) Ben Kelly
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) Anne van Kesteren
• Re: [slightlyoff/ServiceWorker] Create F2F agenda - 28-29 July 2016 (#932) Joshua Bell
• Re: [w3c/push-api] Use the correct terminology for secure contexts (#203) Michael van Ouwerkerk
• Re: [w3c/push-api] Spec should use "secure context" terminology (#202) Michael van Ouwerkerk
• Re: [slightlyoff/ServiceWorker] Create F2F agenda - 28-29 July 2016 (#932) Ingvar Stepanyan
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) Ben Kelly
• Re: [slightlyoff/ServiceWorker] Create F2F agenda - 28-29 July 2016 (#932) Marijn Kruisselbrink
• Re: [slightlyoff/ServiceWorker] Create F2F agenda - 28-29 July 2016 (#932) Ben Kelly
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) Ben Kelly
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) Jeffrey Yasskin
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) Jeffrey Yasskin
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) Jeffrey Yasskin
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) Ben Kelly
• [w3c/DOM-Parsing] How should createContextualFragment interact with `<script>` inside `<template>`? (#19) Boris Zbarsky
• Re: [whatwg/fetch] Make it clearer that cache mode "default" follows normal logic (#340) Anne van Kesteren
• Re: [whatwg/fetch] Delay network errors to prevent port scanning (#338) Patrick McManus
• Re: [whatwg/fetch] Delay network errors to prevent port scanning (#338) Anne van Kesteren
• Re: [whatwg/fetch] Possible typo in header value definition (#332) Mark Nottingham
• Re: [whatwg/fetch] Possible typo in header value definition (#332) Julian Reschke
• Re: [w3c/push-api] typedef object JSON; is incorrect (#204) Anne van Kesteren
• Re: [w3c/push-api] typedef object JSON; is incorrect (#204) Anne van Kesteren
• Re: [w3c/push-api] typedef object JSON; is incorrect (#204) Domenic Denicola
• [whatwg/fetch] Make it clearer that cache mode "default" follows normal logic (#340) Anne van Kesteren
• Re: [slightlyoff/ServiceWorker] Run the latest Bikeshed (#933) Anne van Kesteren
• Re: [w3c/push-api] typedef object JSON; is incorrect (#204) Anne van Kesteren
• Re: [whatwg/fetch] URLs with username/password (#26) Anne van Kesteren
• Re: [whatwg/fetch] URLs with username/password (#26) Anne van Kesteren
• Re: [w3c/push-api] typedef object JSON; is incorrect (#204) Domenic Denicola
• Re: [slightlyoff/ServiceWorker] Run the latest Bikeshed (#933) Domenic Denicola
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) Anne van Kesteren
• Re: [whatwg/fetch] Listing headers safe only for certain values is a bad idea (#313) Anne van Kesteren
• Re: [w3ctag/spec-reviews] WebRTC (#14) Mark Nottingham
• Re: [whatwg/fetch] Some link corrections (#333) Anne van Kesteren
• Re: [whatwg/fetch] Some link corrections (#333) Anne van Kesteren
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) Anne van Kesteren
• Re: [whatwg/fetch] response.ok = false for opaque responses may be misleading (#299) Anne van Kesteren
• Re: [whatwg/fetch] Give user entered data: URI documents the HTTPS state 'modern' (#243) Anne van Kesteren
• Re: [whatwg/fetch] Give user entered data: URI documents the HTTPS state 'modern' (#243) Anne van Kesteren
• Re: [whatwg/fetch] need setHeaderFunction( request => newHeaders ) function called before request sent (#156) Anne van Kesteren
• Re: [whatwg/fetch] need setHeaderFunction( request => newHeaders ) function called before request sent (#156) Anne van Kesteren
• Re: [whatwg/fetch] Remove about:unicorn (#147) Anne van Kesteren
• Re: [whatwg/fetch] Client being null for client requests doesn't work with the fetch registry (#81) Anne van Kesteren
• Re: [whatwg/xhr] " Returns the response's body." (#80) Anne van Kesteren
• Re: [whatwg/fetch] Cache mode: fromCache (#40) Anne van Kesteren
• [w3c/manifest] Additional property to define a webapp to be single instance (single-tab) (#479) leolux
• [whatwg/xhr] " Returns the response's body." (#80) znqlsx
• [whatwg/fetch] Reconsider treatment of non-GET for non-HTTP(S) schemes (#339) Anne van Kesteren
• Re: [w3c/webcomponents] Shadow DOM, <style>, and document.styleSheets (#56) Ryosuke Niwa
• Re: [w3c/webcomponents] Shadow DOM, <style>, and document.styleSheets (#56) Anne van Kesteren
• Re: [w3c/webcomponents] Shadow DOM, <style>, and document.styleSheets (#56) Ryosuke Niwa
• Re: [slightlyoff/ServiceWorker] When does the openWindow promise resolve? (#728) Jungkee Song
• Re: [slightlyoff/ServiceWorker] When does the openWindow promise resolve? (#728) Jungkee Song
• Re: [w3c/webcomponents] Shadow DOM, <style>, and document.styleSheets (#56) Anne van Kesteren
• Re: [w3c/webcomponents] Shadow DOM, <style>, and document.styleSheets (#56) Ryosuke Niwa
• Re: [w3c/push-api] typedef object JSON; is incorrect (#204) Anne van Kesteren
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) Anne van Kesteren
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) Anne van Kesteren
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) Anne van Kesteren
• Re: [whatwg/storage] Integrate with the Permissions spec. (#36) Anne van Kesteren
• Re: [w3c/webcomponents] Shadow DOM, <style>, and document.styleSheets (#56) Anne van Kesteren
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Anne van Kesteren
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#277) Anne van Kesteren
• Re: [whatwg/dom] Upstream retargeting algorithm (#276) Anne van Kesteren
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Anne van Kesteren
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Anne van Kesteren
• Re: [w3c/webcomponents] Shadow DOM, <style>, and document.styleSheets (#56) Hayato Ito
• Re: [w3c/permissions] Editorial fixes (#100) Jeffrey Yasskin
• Re: [whatwg/fetch] How response bodies get from a service worker to the main page is not very clear (#330) Yutaka Hirano
• Re: [slightlyoff/ServiceWorker] Create a new ReadableStream in FetchEvent.respondWith (#934) Yutaka Hirano
• Re: [slightlyoff/ServiceWorker] Create a new ReadableStream in FetchEvent.respondWith (#934) Yutaka Hirano
• Re: [slightlyoff/ServiceWorker] Create a new ReadableStream in FetchEvent.respondWith (#934) Yutaka Hirano
• [slightlyoff/ServiceWorker] Create a new ReadableStream in FetchEvent.respondWith (#934) Yutaka Hirano
• Re: [slightlyoff/ServiceWorker] Run the latest Bikeshed (#933) Yutaka Hirano
• [slightlyoff/ServiceWorker] Run the latest Bikeshed (#933) Yutaka Hirano
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Hayato Ito
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Hayato Ito
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Hayato Ito
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Hayato Ito
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Hayato Ito
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Hayato Ito
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) jan-ivar

Thursday, 21 July 2016

• Re: [w3c/webcomponents] [idea] Allow HTML Element attributes to accept any type of value, not just strings. (#519) Trey Shugart
• Re: [w3c/FileAPI] Use BufferSource instead of ArrayBuffer or ArrayBufferView (#38) Marijn Kruisselbrink
• Re: [w3c/FileAPI] Re-add FileReader.readAsBinaryString() ? (#39) Marijn Kruisselbrink
• Re: [whatwg/dom] cancelBubble legacy property (#211) Philip Jägenstedt
• Re: [w3c/FileAPI] Re-add readAsBinaryString() (#44) Marijn Kruisselbrink
• Re: [w3c/FileAPI] Re-add readAsBinaryString() (#44) Marijn Kruisselbrink
• [w3c/FileAPI] Re-word the way the various read operations are defined (#45) Marijn Kruisselbrink
• Re: [w3c/selection-api] Triple-click selection bounds (#70) Ryosuke Niwa
• Re: [w3c/push-api] typedef object JSON; is incorrect (#204) Peter Beverloo
• Re: [w3c/push-api] typedef object JSON; is incorrect (#204) Domenic Denicola
• Re: [w3c/push-api] typedef object JSON; is incorrect (#204) Peter Beverloo
• Re: [w3c/permissions] Editorial fixes (#100) Jeffrey Yasskin
• Re: [w3c/permissions] Editorial fixes (#100) Jeffrey Yasskin
• [w3c/push-api] typedef object JSON; is incorrect (#204) Domenic Denicola
• Re: [whatwg/dom] cancelBubble legacy property (#211) Chris Rebert
• Re: [w3c/permissions] Guidance on where to put permission related stuff in other specs (#110) Jeffrey Yasskin
• Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) Jeffrey Yasskin
• [whatwg/storage] Integrate with the Permissions spec. (#36) Jeffrey Yasskin
• Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) Mounir Lamouri
• Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) jan-ivar
• Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) Jeffrey Yasskin
• [w3c/selection-api] Triple-click selection bounds (#70) Cyril Auburtin
• Re: [whatwg/fetch] HTTP/2 server push support (#51) rektide
• Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) Jeffrey Yasskin
• Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) jan-ivar
• Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) Anne van Kesteren
• Re: [whatwg/fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) Anne van Kesteren
• Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) Anne van Kesteren
• Re: [w3c/permissions] Guidance on where to put permission related stuff in other specs (#110) Jeffrey Yasskin
• Re: [w3c/IndexedDB] Asynchronously executing a request should queue a task to fire events (#83) Joshua Bell
• Re: [w3c/permissions] Editorial fixes (#100) Jeffrey Yasskin
• Re: [w3c/permissions] Editorial fixes (#100) Jeffrey Yasskin
• Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) Jeffrey Yasskin
• Re: [w3c/IndexedDB] Asynchronously executing a request should queue a task to fire events (#83) Joshua Bell
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Jake Archibald
• Re: [w3c/IndexedDB] Asynchronously executing a request should queue a task to fire events (#83) Joshua Bell
• Re: [w3c/webcomponents] [idea] Allowing custom element registrations on per-shadow-root basis. (#488) Domenic Denicola
• Re: [w3c/webcomponents] [idea] Allowing custom element registrations on per-shadow-root basis. (#488) Domenic Denicola
• Re: [w3c/webcomponents] [idea] Ability to define Custom Element attributes (and optionally enable getters/setters for those attributes). (#517) Domenic Denicola
• Re: [w3c/webcomponents] [idea] Ability to define Custom Element attributes (and optionally enable getters/setters for those attributes). (#517) Domenic Denicola
• Re: [w3c/webcomponents] [idea] Allow HTML Element attributes to accept any type of value, not just strings. (#519) Domenic Denicola
• Re: [w3c/webcomponents] [idea] Allow HTML Element attributes to accept any type of value, not just strings. (#519) Domenic Denicola
• Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) Domenic Denicola
• Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) Mounir Lamouri
• Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) Mounir Lamouri
• Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) Mounir Lamouri
• Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) Mounir Lamouri
• Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) Mounir Lamouri
• Re: [w3c/webcomponents] Should parser extensibility be a design goal? (#113) Domenic Denicola
• Re: [w3c/webcomponents] <iframe> and Window's named properties (#145) Domenic Denicola
• Re: [w3c/webcomponents] Shadow DOM, <style>, and document.styleSheets (#56) Anne van Kesteren
• Re: [w3c/webcomponents] Shadow DOM, <style>, and document.styleSheets (#56) Domenic Denicola
• Re: [whatwg/fetch] Make it more clear that cache mode "default" does respect Cache-Control headers and such (#336) Anne van Kesteren
• Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) Anne van Kesteren
• Re: [whatwg/fetch] Make it more clear that cache mode "default" does respect Cache-Control headers and such (#336) Ben Kelly
• Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) jan-ivar
• Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) jan-ivar
• Re: [w3c/permissions] Guidance on where to put permission related stuff in other specs (#110) Anne van Kesteren
• [whatwg/fetch] Delay network errors to prevent port scanning (#338) Anne van Kesteren
• Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) Anne van Kesteren
• [w3c/IndexedDB] Asynchronously executing a request should queue a task to fire events (#83) Anthony Ramine
• Re: [w3c/editing] inputType for Menu Bar>Edit>Delete (no obvious direction) (#130) Johannes Wilm
• Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) jan-ivar
• Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) jan-ivar
• Re: [w3c/webcomponents] Declarative syntax for custom elements (#136) Hayato Ito
• Re: [w3c/webcomponents] Declarative syntax for custom elements (#136) Hayato Ito
• Re: [w3c/webcomponents] [Custom]: Need adopted callback (bugzilla: 24577) (#210) Anne van Kesteren
• Re: [w3c/webcomponents] [Custom]: Need adopted callback (bugzilla: 24577) (#210) Anne van Kesteren
• Re: [w3c/webcomponents] Declarative syntax for custom elements (#136) Anne van Kesteren
• Re: [w3c/webcomponents] Should parser extensibility be a design goal? (#113) Anne van Kesteren
• [whatwg/fetch] Block text/csv for requests whose type is "script"? (#337) Anne van Kesteren
• Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) Anne van Kesteren
• Re: [whatwg/dom] Set the stage for new custom element adoption semantics (#279) Anne van Kesteren
• Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) Anne van Kesteren
• Re: [w3c/webcomponents] <iframe> and Window's named properties (#145) Anne van Kesteren
• Re: [w3c/webcomponents] Shadow DOM, <style>, and document.styleSheets (#56) Hayato Ito
• Re: [w3c/permissions] Add persistent storage (#39) Anne van Kesteren
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Hayato Ito
• Re: [w3c/webcomponents] Shadow DOM, <style>, and document.styleSheets (#56) Anne van Kesteren
• Re: [w3c/webcomponents] Shadow DOM, <style>, and document.styleSheets (#56) Anne van Kesteren
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Anne van Kesteren
• Re: [whatwg/fetch] Make it more clear that cache mode "default" does respect Cache-Control headers and such (#336) Anne van Kesteren
• Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) Marcos Cáceres
• Re: [whatwg/fetch] Make it more clear that cache mode "default" does respect Cache-Control headers and such (#336) Anne van Kesteren
• Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) jan-ivar
• Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) Marcos Cáceres
• Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) Marcos Cáceres
• Re: [w3c/webcomponents] <iframe> and Window's named properties (#145) Domenic Denicola
• Re: [heycam/webidl] Indicate that thing needs user action to work (#137) Domenic Denicola
• Re: [w3c/webcomponents] Upstream Shadow DOM spec to DOM/HTML Standard (#377) Hayato Ito
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Nathan Schloss
• Re: [w3c/webcomponents] Is or how can Shadow DOM be 'SEO friendly'? (#500) Hayato Ito
• Re: [w3c/webcomponents] Is or how can Shadow DOM be 'SEO friendly'? (#500) Hayato Ito
• Re: [w3c/webcomponents] [idea] distributedCallback for Custom Elements (#527) Hayato Ito
• Re: [w3c/webcomponents] [idea] distributedCallback for Custom Elements (#527) Hayato Ito
• Re: [w3c/webcomponents] Why allow shadow root style to access :host? (#490) Hayato Ito
• Re: [w3c/webcomponents] Why allow shadow root style to access :host? (#490) Hayato Ito
• Re: [w3c/webcomponents] <iframe> and Window's named properties (#145) Hayato Ito
• Re: [w3c/webcomponents] Interaction between CSS and composed tree needs to be better defined (#305) Hayato Ito
• Re: [w3c/webcomponents] Interaction between CSS and composed tree needs to be better defined (#305) Hayato Ito
• Re: [w3c/webcomponents] <iframe> and the History API (#184) Hayato Ito
• Re: [w3c/webcomponents] An API for determining if the focused element is a text editor (#483) Hayato Ito
• Re: [w3c/webcomponents] An API for determining if the focused element is a text editor (#483) Hayato Ito
• Re: [w3c/webcomponents] Idea: ComposedTreeProxy (#516) Hayato Ito
• Re: [w3c/webcomponents] Idea: ComposedTreeProxy (#516) Hayato Ito
• Re: [w3c/webcomponents] Shadow DOM, <style>, and document.styleSheets (#56) Hayato Ito
• Re: [w3c/webcomponents] Shadow DOM, <style>, and document.styleSheets (#56) Hayato Ito
• [heycam/webidl] Indicate that thing needs user action to work (#137) Marcos Cáceres
• [heycam/webidl] More meaniful lables (#136) Marcos Cáceres
• [w3c/permissions] Guidance on where to put permission related stuff in other specs (#110) Marcos Cáceres
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Hayato Ito
• Re: [w3c/selection-api] Define the interaction with user-select CSS property (#46) yosin

Wednesday, 20 July 2016

• Re: [w3ctag/spec-reviews] Indexed DB getAll(), openKeyCursor() and objectStoreNames (#84) Joshua Bell
• Re: [w3ctag/spec-reviews] Indexed DB getAll(), openKeyCursor() and objectStoreNames (#84) littledan
• Re: [w3ctag/spec-reviews] Indexed DB getAll(), openKeyCursor() and objectStoreNames (#84) Joshua Bell
• Re: [w3ctag/spec-reviews] WebRTC (#14) Alex Russell
• Re: [whatwg/fetch] Add option to reject the fetch promise automatically after a certain time elapsed (with no API for arbitrary aborts) (#179) Dan Ostrowski
• Re: [w3ctag/spec-reviews] Indexed DB getAll(), openKeyCursor() and objectStoreNames (#84) Domenic Denicola
• Re: [w3ctag/spec-reviews] Indexed DB getAll(), openKeyCursor() and objectStoreNames (#84) Joshua Bell
• Re: [w3ctag/spec-reviews] Indexed DB getAll(), openKeyCursor() and objectStoreNames (#84) Travis Leithead
• Re: [w3ctag/spec-reviews] Indexed DB getAll(), openKeyCursor() and objectStoreNames (#84) Joshua Bell
• Re: [w3ctag/spec-reviews] Performance Observer Review (formerly Navigation Timing 2 concepts) (#18) Daniel Appelquist
• Re: [w3ctag/spec-reviews] Performance Observer Review (formerly Navigation Timing 2 concepts) (#18) Daniel Appelquist
• Re: [w3ctag/spec-reviews] Indexed DB getAll(), openKeyCursor() and objectStoreNames (#84) Daniel Appelquist
• Re: [w3ctag/spec-reviews] Indexed DB getAll(), openKeyCursor() and objectStoreNames (#84) Daniel Appelquist
• Re: [w3c/permissions] feat(registry): features require a secure context by default, with opt-out (#109) Jeffrey Yasskin
• Re: [w3ctag/spec-reviews] ARIA (#107) Daniel Appelquist
• Re: [w3ctag/spec-reviews] ARIA (#107) Daniel Appelquist
• Re: [whatwg/fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) Philip Jägenstedt
• Re: [whatwg/fetch] Make it more clear that cache mode "default" does respect Cache-Control headers and such (#336) Ehsan Akhgari
• Re: [w3c/gamepad] Added GamepadPose and GamepadCapabilities (#25) Brandon Jones
• Re: [w3c/permissions] Add persistent storage (#39) Jeffrey Yasskin
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Andrew Sutherland
• [w3c/editing] inputType for Menu Bar>Edit>Delete (no obvious direction) (#130) Chong Zhang
• Re: [w3c/gamepad] Added GamepadPose and GamepadCapabilities (#25) chris van wiemeersch
• Re: [slightlyoff/ServiceWorker] More clarity around waiting for an active worker to finish (#916) Matt Falkenhagen
• [w3c/push-api] Use the correct terminology for secure contexts (#203) Peter Beverloo
• Re: [slightlyoff/ServiceWorker] More clarity around waiting for an active worker to finish (#916) Ben Kelly
• Re: [slightlyoff/ServiceWorker] More clarity around waiting for an active worker to finish (#916) Matt Falkenhagen
• Re: [whatwg/fetch] RFC: a mechanism to bypass CORS preflight (#210) Takeshi Yoshino
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Jake Archibald
• Re: [w3c/permissions] Add persistent storage (#39) Anne van Kesteren
• Re: [w3c/permissions] Add "fullscreen" (#26) Anne van Kesteren
• Re: [w3c/permissions] Add "fullscreen" (#26) Anne van Kesteren
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/permissions] Add security considerations section (#49) Marcos Cáceres
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Anne van Kesteren
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Anne van Kesteren
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Anne van Kesteren
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Anne van Kesteren
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Anne van Kesteren
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Anne van Kesteren
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Anne van Kesteren
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Anne van Kesteren
• Re: [whatwg/fetch] Proposal: Support GET bodies (#83) Anne van Kesteren
• Re: [whatwg/fetch] Proposal: Support GET bodies (#83) Anne van Kesteren
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Jake Archibald
• Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) Anne van Kesteren
• Re: [w3c/permissions] Add security considerations section (#49) Anne van Kesteren
• Re: [w3c/permissions] Add security considerations section (#49) Marcos Cáceres
• Re: [whatwg/fullscreen] Drop the iframe ancestor check? (#45) Anne van Kesteren
• [whatwg/fetch] Make it more clear that cache mode "default" does respect Cache-Control headers and such (#336) Anne van Kesteren
• Re: [whatwg/fullscreen] Drop the iframe ancestor check? (#45) Philip Jägenstedt
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Hayato Ito
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Hayato Ito
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Hayato Ito
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Hayato Ito
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Hayato Ito
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Hayato Ito
• Re: [whatwg/fullscreen] Drop the iframe ancestor check? (#45) Xidorn Quan
• Re: [whatwg/fullscreen] Drop the iframe ancestor check? (#45) Philip Jägenstedt
• Re: [w3c/permissions] Why is "retrieve the permission storage" not in "Permission store"? (#84) Jeffrey Yasskin
• Re: [w3c/permissions] Why is "retrieve the permission storage" not in "Permission store"? (#84) Jeffrey Yasskin
• Re: [w3c/permissions] Support for background sync (one-off and periodic) (#29) Jeffrey Yasskin

Tuesday, 19 July 2016

• Re: [w3c/permissions] Add persistent storage (#39) Jeffrey Yasskin
• Re: [w3c/permissions] Add persistent storage (#39) Jeffrey Yasskin
• Re: [w3c/permissions] Add "fullscreen" (#26) Jeffrey Yasskin
• Re: [w3c/permissions] Permissions may change status in other ways than "trying to access" (#43) Jeffrey Yasskin
• Re: [w3c/permissions] Permissions may change status in other ways than "trying to access" (#43) Jeffrey Yasskin
• Re: [w3c/permissions] Add "nfc" to enum PermissionName (#47) Jeffrey Yasskin
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Andrew Sutherland
• Re: [w3c/permissions] Add security considerations section (#49) Jeffrey Yasskin
• Re: [w3c/permissions] Add "pointerlock" to enum PermissionName (#50) Jeffrey Yasskin
• Re: [w3c/permissions] Add "pointerlock" to enum PermissionName (#50) Jeffrey Yasskin
• Re: [w3c/permissions] Add pointerlock to the permissions enum? (#67) Jeffrey Yasskin
• Re: [w3c/permissions] Don't assume implicit grant from getUserMedia. (#78) Jeffrey Yasskin
• Re: [w3c/permissions] Don't assume implicit grant from getUserMedia. (#78) Jeffrey Yasskin
• Re: [w3c/permissions] Permission API has terminology issues one could drive a truck through. (#85) Jeffrey Yasskin
• Re: [w3c/permissions] Permission API has terminology issues one could drive a truck through. (#85) Jeffrey Yasskin
• Re: [w3c/permissions] Model temporary permissions better (#86) Jeffrey Yasskin
• Re: [w3c/permissions] Model temporary permissions better (#86) Jeffrey Yasskin
• Re: [w3c/permissions] Specify how request and revoke work on push and midi permissions. (#90) Jeffrey Yasskin
• Re: [w3c/permissions] Specify how request and revoke work on push and midi permissions. (#90) Jeffrey Yasskin
• Re: [w3c/permissions] Separate "request access" from "request permission"? (#94) Jeffrey Yasskin
• Re: [w3c/permissions] Separate "request access" from "request permission"? (#94) Jeffrey Yasskin
• Re: [w3c/permissions] Add 'webvr' to "Permission Registry" enum (#108) Jeffrey Yasskin
• Re: [w3c/permissions] Allow features to 'require a secure context'. (#109) Jeffrey Yasskin
• Re: [w3c/permissions] Allow features to 'require a secure context'. (#109) Jeffrey Yasskin
• [w3c/push-api] Spec should use "secure context" terminology (#202) Jeffrey Yasskin
• [heycam/webidl] State that by default all objects are created in the relevant realm of `this` (#135) Domenic Denicola
• Re: [whatwg/fetch] Call out to Referrer Policy to set policy on redirect (#335) Anne van Kesteren
• Re: [whatwg/fetch] Call out to Referrer Policy to set policy on redirect (#335) Anne van Kesteren
• Re: [whatwg/fetch] HTTP-redirect fetch should invoke "Set request's referrer policy on redirect" (#334) Anne van Kesteren
• Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) Inian
• Re: [w3ctag/spec-reviews] Review secure contexts (#124) Mike West
• Re: [whatwg/fetch] HTTP-redirect fetch should invoke "Set request's referrer policy on redirect" (#334) Emily Stark
• Re: [heycam/webidl] Should probably spec a hasInstance for named constructors (#134) Boris Zbarsky
• Re: [heycam/webidl] Should probably spec a hasInstance for named constructors (#134) Boris Zbarsky
• Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) Anne van Kesteren
• Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) Anne van Kesteren
• Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) Anne van Kesteren
• Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) Ingvar Stepanyan
• Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) Inian
• Re: [heycam/webidl] Should probably spec a hasInstance for named constructors (#134) Domenic Denicola
• Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) Philip Jägenstedt
• [heycam/webidl] Should probably spec a hasInstance for named constructors (#134) Boris Zbarsky
• Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) Mounir Lamouri
• Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) Mounir Lamouri
• Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) Mounir Lamouri
• Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) Jake Archibald
• [slightlyoff/ServiceWorker] Create F2F agenda - 28-29 July 2016 (#932) Jake Archibald
• Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) Domenic Denicola
• Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) Anne van Kesteren
• Re: [whatwg/dom] Define dataset as a mixin for HTMLElement and SVGElement (#280) Anne van Kesteren
• Re: [w3c/WebPlatformWG] Minor typo (#52) Yves Lafon
• Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) Domenic Denicola
• Re: [whatwg/dom] Define dataset as a mixin for HTMLElement and SVGElement (#280) Domenic Denicola
• Re: [slightlyoff/ServiceWorker] Does accessing ExtendableEvent's extend lifetime promises race? (#931) Jake Archibald
• [w3c/WebPlatformWG] Minor typo (#52) Jake Archibald
• Re: [whatwg/fetch] HTTP-redirect fetch should invoke "Set request's referrer policy on redirect" (#334) Anne van Kesteren
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Anne van Kesteren
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Anne van Kesteren
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Anne van Kesteren
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Anne van Kesteren
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Anne van Kesteren
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Jake Archibald
• Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) Anne van Kesteren
• Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) Anne van Kesteren
• Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) Anne van Kesteren
• Re: [whatwg/fullscreen] Drop the iframe ancestor check? (#45) Anne van Kesteren
• Re: [whatwg/fullscreen] Drop the iframe ancestor check? (#45) Anne van Kesteren
• Re: [whatwg/fetch] Possible typo in header value definition (#332) Anne van Kesteren
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) chaals
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) chaals
• Re: [whatwg/fetch] RFC: a mechanism to bypass CORS preflight (#210) Anne van Kesteren
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Anne van Kesteren
• Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496) Hayato Ito
• Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496) Hayato Ito
• Re: [whatwg/dom] Define dataset as a mixin for HTMLElement and SVGElement (#280) Anne van Kesteren
• Re: [whatwg/fetch] RFC: a mechanism to bypass CORS preflight (#210) Takeshi Yoshino
• Re: [whatwg/dom] Define dataset as a mixin for HTMLElement and SVGElement (#280) Nikos Andronikos
• Re: [heycam/webidl] Use OrdinaryGetOwnProperty. (#131) Cameron McCormack
• Re: [heycam/webidl] Use OrdinaryGetOwnProperty. (#131) Cameron McCormack
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Hayato Ito
• Re: [w3c/uievents] Fix #89. Make some of legacy UIEvents composed events (#93) Hayato Ito
• Re: [w3c/permissions] Allow features to 'require a secure context'. (#109) Martin Thomson
• Re: [w3c/webcomponents] [idea] distributedCallback for Custom Elements (#527) Hayato Ito
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Domenic Denicola
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Hayato Ito

Monday, 18 July 2016

• Re: [w3c/permissions] Allow features to 'require a secure context'. (#109) Jeffrey Yasskin
• [w3c/permissions] Allow features to 'require a secure context'. (#109) Jeffrey Yasskin
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Joseph Orbegoso Pea
• Re: [whatwg/streams] Broadcast ReadableStream (#481) A. Matías Quezada
• Re: [whatwg/streams] Broadcast ReadableStream (#481) A. Matías Quezada
• Re: [whatwg/streams] Broadcast ReadableStream (#481) Domenic Denicola
• [whatwg/streams] Broadcast ReadableStream (#481) A. Matías Quezada
• Re: [w3c/WebPlatformWG] Brady will be at the Service Workers F2F next week too. (#51) Yves Lafon
• [w3c/WebPlatformWG] Brady will be at the Service Workers F2F next week too. (#51) hober
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Zambonifofex
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Domenic Denicola
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Zambonifofex
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) Eric Bidelman
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Domenic Denicola
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Zambonifofex
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) Andrea Giammarchi
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) Ryosuke Niwa
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) Eric Bidelman
• Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) Mounir Lamouri
• Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) Mounir Lamouri
• Re: [w3c/FileAPI] Re-add readAsBinaryString() (#44) Anne van Kesteren
• Re: [w3c/FileAPI] Re-add readAsBinaryString() (#44) Joshua Bell
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Alex Russell
• Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) Mounir Lamouri
• Re: [w3c/FileAPI] Re-add readAsBinaryString() (#44) Anne van Kesteren
• Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) Mounir Lamouri
• Re: [w3c/FileAPI] Re-add readAsBinaryString() (#44) Anne van Kesteren
• Re: [w3c/FileAPI] Re-add readAsBinaryString() (#44) Joshua Bell
• Re: [w3c/IndexedDB] Naming for "v2" ? (#82) Léonie Watson
• Re: [w3c/webcomponents] The custom element state when constructor thrown (#533) Domenic Denicola
• Re: [whatwg/dom] Set the stage for preventing double custom element constructor calls (#282) Anne van Kesteren
• Re: [whatwg/dom] Set the stage for preventing double custom element constructor calls (#282) Domenic Denicola
• Re: [whatwg/dom] Set the stage for preventing double custom element constructor calls (#282) Anne van Kesteren
• Re: [whatwg/dom] Set the stage for preventing double custom element constructor calls (#282) Domenic Denicola
• Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) Mounir Lamouri
• Re: [w3c/gamepad] Added GamepadPose and GamepadCapabilities (#25) Brandon Jones
• [slightlyoff/ServiceWorker] Does accessing ExtendableEvent's extend lifetime promises race? (#931) Jungkee Song
• Re: [whatwg/fetch] Content-Length on HEAD (#135) Anne van Kesteren
• Re: [whatwg/fetch] Content-Length on HEAD (#135) Anne van Kesteren
• Re: [whatwg/fetch] Content-Length on HEAD (#135) Anne van Kesteren
• Re: [slightlyoff/ServiceWorker] Remove monkeypatches in the event disptaching behaviors (72315b9) Jungkee Song
• Re: [whatwg/fetch] fetch filter the symbols (#331) Anne van Kesteren
• Re: [slightlyoff/ServiceWorker] Should Cache-Control: private be respected? (#926) Ingvar Stepanyan
• Re: [slightlyoff/ServiceWorker] Remove monkeypatches in the event disptaching behaviors (72315b9) Anne van Kesteren
• Re: [slightlyoff/ServiceWorker] Should Cache-Control: private be respected? (#926) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Should Cache-Control: private be respected? (#926) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Remove monkeypatches in the event disptaching behaviors (72315b9) Jungkee Song
• Re: [slightlyoff/ServiceWorker] Should Cache-Control: private be respected? (#926) Ben Kelly
• Re: [whatwg/dom] Set the stage for preventing double custom element constructor calls (#282) Anne van Kesteren
• Re: [whatwg/dom] Set the stage for preventing double custom element constructor calls (#282) Anne van Kesteren
• Re: [whatwg/dom] Set the stage for preventing double custom element constructor calls (#282) Anne van Kesteren
• Re: [whatwg/dom] Set the stage for preventing double custom element constructor calls (#282) Anne van Kesteren
• Re: [slightlyoff/ServiceWorker] Should Cache-Control: private be respected? (#926) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Should Cache-Control: private be respected? (#926) Anne van Kesteren
• Re: [whatwg/dom] Define dataset as a mixin for HTMLElement and SVGElement (#280) Anne van Kesteren
• Re: [whatwg/xhr] Should we be pinning Blob URIs on fetches? (#79) Anne van Kesteren
• Re: [whatwg/xhr] failed to load data in sapui5 RowRepaeater (#78) Anne van Kesteren
• Re: [whatwg/url] Which reality should location.pathname setter match? (#133) Anne van Kesteren
• Re: [whatwg/url] Trailing dot and origin compuation (#132) Anne van Kesteren
• Re: [whatwg/url] Which reality should location.pathname setter match? (#133) PhistucK
• Re: [whatwg/url] Which reality should location.pathname setter match? (#133) PhistucK
• Re: [slightlyoff/ServiceWorker] Remove monkeypatches in the event disptaching behaviors (72315b9) Anne van Kesteren
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Anne van Kesteren
• Re: [whatwg/url] Which reality should location.pathname setter match? (#133) Anne van Kesteren
• Re: [w3c/DOM-Parsing] Step 1 of createContextualFragment is not enough (#17) Anthony Ramine
• Re: [w3c/FileAPI] Re-add readAsBinaryString() (#44) Anne van Kesteren
• Re: [w3c/DOM-Parsing] Step 1 of createContextualFragment is not enough (#17) ArkadiuszMichalski
• Re: [w3c/DOM-Parsing] Step 1 of createContextualFragment is not enough (#17) Anthony Ramine
• Re: [w3c/DOM-Parsing] Step 1 of createContextualFragment is not enough (#17) ArkadiuszMichalski
• Re: [w3c/DOM-Parsing] Step 1 of createContextualFragment is not enough (#17) Anthony Ramine
• Re: [w3c/DOM-Parsing] Step 1 of createContextualFragment is not enough (#17) ArkadiuszMichalski
• Re: [heycam/webidl] Make globals and things they inherit from have immutable prototypes (#133) Anne van Kesteren
• Re: [slightlyoff/ServiceWorker] Documentation mistake (#927) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Documentation mistake (#927) Jake Archibald
• Re: [slightlyoff/ServiceWorker] ServiceWorkers doesn't update in Chrome of subscribers after 24 hours (even after 5 days) (#930) Jake Archibald
• Re: [slightlyoff/ServiceWorker] ServiceWorkers doesn't update in Chrome of subscribers after 24 hours (even after 5 days) (#930) Jake Archibald
• Re: [whatwg/fullscreen] Should we apply !important to "object-fit: contain"? (#44) Anne van Kesteren
• Re: [whatwg/fetch] Aborting a fetch (#27) Jake Archibald
• Re: [whatwg/fullscreen] Should we apply !important to "object-fit: contain"? (#44) Anne van Kesteren
• Re: [w3c/WebPlatformWG] Update 16-07-29-Editing.md (#50) Léonie Watson
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Zambonifofex
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Ryosuke Niwa
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) smaug----
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Anne van Kesteren
• Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) Anne van Kesteren
• Re: [whatwg/streams] JSIDL vs WebIDL (#45) youennf
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Ryosuke Niwa
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Domenic Denicola
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Ryosuke Niwa
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Domenic Denicola
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Ryosuke Niwa
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Domenic Denicola
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Ryosuke Niwa
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Domenic Denicola
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Joseph Orbegoso Pea
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Domenic Denicola
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Joseph Orbegoso Pea
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Joseph Orbegoso Pea
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Domenic Denicola
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Joseph Orbegoso Pea
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Domenic Denicola
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Domenic Denicola
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Joseph Orbegoso Pea
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Ryosuke Niwa
• Re: [w3c/selection-api] Normative references (#69) Ryosuke Niwa
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) Ryosuke Niwa
• Re: [w3c/webcomponents] [idea] distributedCallback for Custom Elements (#527) Joseph Orbegoso Pea
• Re: [w3c/webcomponents] [idea] distributedCallback for Custom Elements (#527) Joseph Orbegoso Pea
• Re: [w3c/webcomponents] [idea] distributedCallback for Custom Elements (#527) Joseph Orbegoso Pea
• Re: [w3c/webcomponents] Event retargetting in layman's terms? (#528) Joseph Orbegoso Pea
• Re: [w3c/webcomponents] Event retargetting in layman's terms? (#528) Ryosuke Niwa
• Re: [w3c/webcomponents] Event retargetting in layman's terms? (#528) Joseph Orbegoso Pea
• [slightlyoff/ServiceWorker] ServiceWorkers doesn't update in Chrome of subscribers after 24 hours (even after 5 days) (#930) Vitaly Baranovsky
• [w3c/WebPlatformWG] Update 16-07-29-Editing.md (#50) Dave Tapuska

Sunday, 17 July 2016

• Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20) William J. Edney
• Re: [whatwg/fetch] Add option to automatically abort response stream if the data stopped arriving for longer than a specified time (#180) apet-as
• Re: [whatwg/streams] Add URL.createObjectURL(stream) support (#480) Ádám Lippai
• Re: [whatwg/streams] Add URL.createObjectURL(stream) support (#480) Domenic Denicola
• [whatwg/streams] Add URL.createObjectURL(stream) support (#480) Ádám Lippai
• Re: [w3c/DOM-Parsing] Proposal: add a method in DOMParser for parsing non-UTF8 XML documents (#18) Yen Chi Hsuan
• Re: [w3c/DOM-Parsing] Proposal: add a method in DOMParser for parsing non-UTF8 XML documents (#18) Yen Chi Hsuan

Saturday, 16 July 2016

• Re: [w3c/IndexedDB] Naming for "v2" ? (#82) beidson
• Re: [w3c/IndexedDB] Naming for "v2" ? (#82) Anthony Ramine
• Re: [whatwg/fetch] Aborting a fetch (#27) Cristian Sima
• [w3c/permissions] Add 'webvr' to "Permission Registry" enum (#108) chris van wiemeersch
• Re: [w3c/webcomponents] Event retargetting in layman's terms? (#528) Ryosuke Niwa
• Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) Joseph Orbegoso Pea
• Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) Joseph Orbegoso Pea

Friday, 15 July 2016

• [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) Jeffrey Yasskin
• Re: [w3c/WebPlatformWG] Add Chong Zhang to "will attend" list (#49) Léonie Watson
• [w3c/WebPlatformWG] Add Chong Zhang to "will attend" list (#49) Chong Zhang
• Re: [w3c/webcomponents] Event retargetting in layman's terms? (#528) Joseph Orbegoso Pea
• Re: [w3c/IndexedDB] Specify IDBOpenDBRequest processing as a queue? (#79) Joshua Bell
• Re: [w3c/IndexedDB] Specify IDBOpenDBRequest processing as a queue? (#79) Joshua Bell
• Re: [w3c/IndexedDB] Specify IDBOpenDBRequest processing as a queue? (#79) Joshua Bell
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Ryosuke Niwa
• Re: [w3c/IndexedDB] Specify IDBOpenDBRequest processing as a queue? (#79) Anthony Ramine
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Joseph Orbegoso Pea
• Re: [w3c/IndexedDB] task behavior for open requests is poorly specified (#9) Joshua Bell
• Re: [w3c/IndexedDB] deleteDatabase's "versionchange" should be deferred if upgrade is running (#78) Joshua Bell
• Re: [w3c/IndexedDB] Specify IDBOpenDBRequest processing as a queue? (#79) Joshua Bell
• Re: [w3c/IndexedDB] Specify IDBOpenDBRequest processing as a queue? (#79) Joshua Bell
• Re: [w3c/IndexedDB] task behavior for open requests is poorly specified (#9) Joshua Bell
• Re: [w3c/IndexedDB] deleteDatabase's "versionchange" should be deferred if upgrade is running (#78) Joshua Bell
• Re: [w3c/IndexedDB] The steps for opening a database are racy (#81) Joshua Bell
• Re: [w3c/IndexedDB] The steps for opening a database are racy (#81) Joshua Bell
• Re: [heycam/webidl] Add namespaces (#121) Domenic Denicola
• Re: [heycam/webidl] Add namespaces (#121) Boris Zbarsky
• Re: [whatwg/fetch] Possible typo in header value definition (#332) Malisa
• Re: [heycam/webidl] Add namespaces (#121) Domenic Denicola
• Re: [w3c/webcomponents] Allow or prohibit observedAttributes to observe 'style' attribute? (#521) Domenic Denicola
• Re: [w3c/webcomponents] Allow or prohibit observedAttributes to observe 'style' attribute? (#521) Domenic Denicola
• Re: [w3c/WebPlatformWG] Publish First Public Working Draft for HTML 5.2? (#43) Léonie Watson
• Re: [w3c/WebPlatformWG] Publish First Public Working Draft for HTML 5.2? (#43) Léonie Watson
• [whatwg/fetch] Call out to Referrer Policy to set policy on redirect (#335) Emily Stark
• Re: [whatwg/fetch] HTTP-redirect fetch should invoke "Set request's referrer policy on redirect" (#334) Emily Stark
• [whatwg/fetch] HTTP-redirect fetch should invoke "Set request's referrer policy on redirect" (#334) Emily Stark
• Re: [w3c/IndexedDB] Naming for "v2" ? (#82) beidson
• Re: [w3c/IndexedDB] Naming for "v2" ? (#82) Jonas Sicking
• [w3c/DOM-Parsing] Proposal: add a method in DOMParser for parsing non-UTF8 XML documents (#18) Yen Chi Hsuan
• [w3c/IndexedDB] Naming for "v2" ? (#82) Joshua Bell
• Re: [w3c/webcomponents] Allow or prohibit observedAttributes to observe 'style' attribute? (#521) Koji Ishii
• Re: [w3c/screen-orientation] Allow lock Orientation more than one orientation (#91) Jason
• Re: [slightlyoff/ServiceWorker] Expose GeoLocation to workers (#745) Alex Russell
• Re: [slightlyoff/ServiceWorker] Expose GeoLocation to workers (#745) Alex Russell
• Re: [heycam/webidl] Add namespaces (#121) Boris Zbarsky
• Re: [heycam/webidl] Add namespaces (#121) Boris Zbarsky
• Re: [whatwg/streams] Stack details are omitted in output of tap-spec (#478) Takeshi Yoshino
• Re: [whatwg/streams] Use e => t.error(e) than t.error for catching exceptions in a then-callback (#479) Takeshi Yoshino
• Re: [whatwg/streams] Use e => t.error(e) than t.error for catching exceptions in a then-callback (#479) Takeshi Yoshino
• Re: [w3c/editing] We should keep data in UI events for beforeInput that does the text/plain serialization. We should add dataTransfer to the editing spec for other mime types(html, text with line breaks, etc) (#106) Johannes Wilm
• [whatwg/xhr] Should we be pinning Files (#79) Manish Goregaokar
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Hayato Ito
• Re: [w3c/push-api] Options are...optional. (#201) Michael van Ouwerkerk
• Re: [w3c/push-api] Allow UA to not implement all PushSubscriptionOptions (#200) Michael van Ouwerkerk
• Re: [w3c/screen-orientation] screen-orientation.change events should be cancellable (#92) Jesse MacFadyen
• Re: [slightlyoff/ServiceWorker] 28-29 July 2016 Service Workers meeting - W3C Web platform Working Group (#929) Jake Archibald
• Re: [w3c/screen-orientation] screen-orientation.change events should be cancellable (#92) Marcos Cáceres
• [slightlyoff/ServiceWorker] 28-29 July 2016 Service Workers meeting - W3C Web platform Working Group (#929) Richard Maher
• [w3c/screen-orientation] screen-orientation.change events should be cancellable (#92) Jesse MacFadyen
• Re: [w3c/screen-orientation] Allow lock Orientation more than one orientation (#91) Jesse MacFadyen
• [whatwg/fetch] Some link corrections (#333) Domenic Denicola

Thursday, 14 July 2016

• Re: [slightlyoff/ServiceWorker] openWindow with a WebApp manifests (#720) Dominick Ng
• Re: [whatwg/streams] Stack details are omitted in output of tap-spec (#478) Domenic Denicola
• Re: [w3c/FileAPI] Streams is hot, FileReader.readAs____ is not (#40) Domenic Denicola
• [w3c/FileAPI] Re-add readAsBinaryString() (#44) Joshua Bell
• Re: [heycam/webidl] Make globals and things they inherit from have immutable prototypes (#133) Domenic Denicola
• Re: [w3c/webcomponents] The custom element state when constructor thrown (#533) Domenic Denicola
• Re: [heycam/webidl] Make globals and things they inherit from have immutable prototypes (#133) littledan
• [whatwg/dom] Set the stage for preventing double custom element constructor calls (#282) Domenic Denicola
• Re: [heycam/webidl] Make globals and things they inherit from have immutable prototypes (#133) littledan
• Re: [w3c/webcomponents] The custom element state when constructor thrown (#533) Domenic Denicola
• [heycam/webidl] Make globals and things they inherit from have immutable prototypes (#133) Domenic Denicola
• Re: [w3c/touch-events] convert deprecated <dl> based WebIDL to Contiguous IDL (#69) Patrick H. Lauke
• Re: [w3c/touch-events] convert deprecated <dl> based WebIDL to Contiguous IDL (#69) Patrick H. Lauke
• Re: [heycam/webidl] Use OrdinaryGetOwnProperty. (#131) Domenic Denicola
• Re: [w3c/webcomponents] Event retargetting in layman's terms? (#528) Ryosuke Niwa
• Re: [w3c/touch-events] convert deprecated <dl> based WebIDL to Contiguous IDL (#69) Rick Byers
• Re: [w3c/touch-events] convert deprecated <dl> based WebIDL to Contiguous IDL (#69) Rick Byers
• Re: [whatwg/dom] Set the stage for new custom element adoption semantics (#279) Domenic Denicola
• Re: [whatwg/dom] Set the stage for new custom element adoption semantics (#279) Domenic Denicola
• Re: [whatwg/fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) Mounir Lamouri
• Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) Inian
• Re: [whatwg/streams] Use e => t.error(e) than t.error for catching exceptions in a then-callback (#479) Domenic Denicola
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) Andrea Giammarchi
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) Zambonifofex
• Re: [w3c/push-api] Options are...optional. (#201) Peter Beverloo
• Re: [slightlyoff/ServiceWorker] openWindow with a WebApp manifests (#720) Ben Kelly
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) Andrea Giammarchi
• [whatwg/url] Which reality should location.pathname setter match? (#133) PhistucK
• Re: [slightlyoff/ServiceWorker] Firing an event when service worker wakes up (#928) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Firing an event when service worker wakes up (#928) Jake Archibald
• [whatwg/streams] Use e => t.error(e) than t.error for catching exceptions in a then-callback (#479) Takeshi Yoshino
• Re: [w3c/screen-orientation] Allow lock Orientation more than one orientation (#91) Mounir Lamouri
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) Takeshi Yoshino
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) Takeshi Yoshino
• [slightlyoff/ServiceWorker] Firing an event when service worker wakes up (#928) Lewis Phạm
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) Takeshi Yoshino
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) Takeshi Yoshino
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) Takeshi Yoshino
• [whatwg/streams] Stack details is omitted in output of tap-spec (#478) Takeshi Yoshino
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) Linus Unnebäck
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) Takeshi Yoshino
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) Takeshi Yoshino
• Re: [slightlyoff/ServiceWorker] openWindow with a WebApp manifests (#720) Dominick Ng
• Re: [w3c/FileAPI] Implementations allow all values in type getter (#43) Manish Goregaokar
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) Hayato Ito
• [whatwg/dom] Add relatedTarget to event dispatch (#281) Hayato Ito
• Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) Dominic Cooney
• [w3c/push-api] Options are...optional. (#201) Martin Thomson
• Re: [w3c/push-api] Allow UA to not implement all PushSubscriptionOptions (#200) Martin Thomson

Wednesday, 13 July 2016

• [slightlyoff/ServiceWorker] Documentation mistake (#927) David Scales
• Re: [w3c/FileAPI] Implementations allow all values in type getter (#43) Jonas Sicking
• Re: [whatwg/fullscreen] Should we apply !important to "object-fit: contain"? (#44) Philip Jägenstedt
• Re: [whatwg/fullscreen] Should we apply !important to "object-fit: contain"? (#44) Xidorn Quan
• [w3c/uievents-key] ContextMenu key's description mentions defunct "OS" key (#28) Chris Rebert
• Re: [whatwg/fetch] Possible typo in header value definition (#332) Jeena Lee
• Re: [w3c/screen-orientation] Allow lock Orientation more than one orientation (#91) Jesse MacFadyen
• Re: [w3c/permissions] Editorial fixes (#100) Tab Atkins Jr.
• Re: [w3c/permissions] Editorial fixes (#100) Tab Atkins Jr.
• Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) Domenic Denicola
• Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) Adam Klein
• Re: [w3c/permissions] Editorial fixes (#100) Jeffrey Yasskin
• Re: [w3c/FileAPI] Implementations allow all values in type getter (#43) Joshua Bell
• Re: [whatwg/dom] Set the stage for new custom element adoption semantics (#279) Domenic Denicola
• Re: [whatwg/dom] Set the stage for new custom element adoption semantics (#279) Domenic Denicola
• Re: [w3c/permissions] Editorial fixes (#100) Jeffrey Yasskin
• Re: [w3c/permissions] Editorial fixes (#100) Jeffrey Yasskin
• Re: [w3c/permissions] Editorial fixes (#100) Jeffrey Yasskin
• Re: [w3c/permissions] Editorial fixes (#100) Jeffrey Yasskin
• Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) Domenic Denicola
• Re: [slightlyoff/ServiceWorker] Should 'fetch' be an event, or some different API? (#256) hemanth.hm
• Re: [w3c/push-api] Allow UA to not implement all PushSubscriptionOptions (#200) Peter Beverloo
• Re: [w3c/touch-events] Add interaction with pointer events and compat mouse events (#70) Rick Byers
• Re: [whatwg/fullscreen] Should we apply !important to "object-fit: contain"? (#44) Philip Jägenstedt
• [w3c/touch-events] Add interaction with pointer events and compat mouse events (#70) Rick Byers
• Re: [whatwg/fullscreen] Should we apply !important to "object-fit: contain"? (#44) Xidorn Quan
• Re: [w3c/permissions] Editorial fixes (#100) Jeffrey Yasskin
• Re: [w3c/permissions] Editorial fixes (#100) Jeffrey Yasskin
• Re: [w3c/permissions] Editorial fixes (#100) Jeffrey Yasskin
• Re: [whatwg/fullscreen] Should we apply !important to "object-fit: contain"? (#44) Philip Jägenstedt
• Re: [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (#99) Jeffrey Yasskin
• Re: [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (#99) Jeffrey Yasskin
• Re: [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (#99) Jeffrey Yasskin
• Re: [whatwg/fullscreen] Drop the iframe ancestor check? (#45) Philip Jägenstedt
• Re: [w3c/permissions] Remove object-based permissions (#42) Jeffrey Yasskin
• Re: [whatwg/fullscreen] Drop the iframe ancestor check? (#45) Xidorn Quan
• Re: [whatwg/fullscreen] Drop the iframe ancestor check? (#45) Philip Jägenstedt
• Re: [whatwg/fullscreen] Drop the iframe ancestor check? (#45) Xidorn Quan
• Re: [slightlyoff/ServiceWorker] Stop monkeypatching event dispatch (#924) Jungkee Song
• [whatwg/fullscreen] Drop the iframe ancestor check? (#45) Philip Jägenstedt
• [w3c/FileAPI] Implementations allow all values in type getter (#43) Manish Goregaokar
• Re: [whatwg/streams] Should write() always error the stream when it rejects the promise it returned? (#476) Takeshi Yoshino
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) Takeshi Yoshino
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) Takeshi Yoshino
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) Andrea Giammarchi
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) Trey Shugart
• Re: [w3c/permissions] Remove object-based permissions (#42) Marcos Cáceres
• Re: [w3c/webcomponents] Allow or prohibit observedAttributes to observe 'style' attribute? (#521) smaug----
• Re: [w3c/touch-events] convert deprecated <dl> based WebIDL to Contiguous IDL (#69) Patrick H. Lauke
• [w3c/touch-events] convert deprecated <dl> based WebIDL to Contiguous IDL (#69) Patrick H. Lauke
• Re: [w3c/permissions] docs(contributing): improve the guidelines for changes (#106) Marcos Cáceres
• Re: [w3c/permissions] docs(contributing): improve the guidelines for changes (#106) Marcos Cáceres
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) Andrea Giammarchi
• Re: [w3c/webcomponents] Event retargetting in layman's terms? (#528) Joseph Orbegoso Pea
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/IndexedDB] Specify IDBOpenDBRequest processing as a queue? (#79) Anthony Ramine
• Re: [w3c/WebPlatformWG] grisha_pullRequest_AddtlAttendees (#48) chaals
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (#99) Marcos Cáceres
• Re: [w3c/permissions] chore(editors): add W3C editor IDs (#105) Marcos Cáceres
• Re: [w3c/permissions] chore(editors): add W3C editor IDs (#105) Marcos Cáceres
• Re: [w3c/permissions] how to tidy? (#98) Marcos Cáceres
• Re: [w3c/permissions] how to tidy? (#98) Marcos Cáceres
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) David Steinkopff
• Re: [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (#99) Marcos Cáceres
• Re: [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (#99) Marcos Cáceres
• Re: [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (#99) Marcos Cáceres
• Re: [w3c/permissions] Move the Permissions registry (#103) Marcos Cáceres
• Re: [w3c/permissions] Exceptions in promise using algorithms (#102) Marcos Cáceres
• Re: [w3c/permissions] Exceptions in promise using algorithms (#102) Marcos Cáceres
• Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) Joseph Orbegoso Pea
• Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) Zambonifofex
• Re: [w3c/permissions] Exceptions in promise using algorithms (#102) Jeffrey Yasskin
• Re: [w3c/webcomponents] Allow or prohibit observedAttributes to observe 'style' attribute? (#521) Koji Ishii
• Re: [w3c/permissions] Move the Permissions registry (#103) Jeffrey Yasskin
• Re: [slightlyoff/ServiceWorker] Stop monkeypatching event dispatch (#924) Jungkee Song
• Re: [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/webcomponents] The custom element state when constructor thrown (#533) Koji Ishii
• Re: [w3c/webcomponents] The custom element state when constructor thrown (#533) Domenic Denicola
• Re: [w3c/webcomponents] Shadow DOM and requestPointerLock() (#192) Hayato Ito
• Re: [w3c/webcomponents] Shadow DOM and requestPointerLock() (#192) Takayoshi Kochi
• Re: [w3c/permissions] Editorial fixes (#100) Jeffrey Yasskin
• Re: [w3c/permissions] Editorial fixes (#100) Jeffrey Yasskin
• Re: [w3c/permissions] Editorial fixes (#100) Jeffrey Yasskin
• Re: [w3c/permissions] Editorial fixes (#100) Jeffrey Yasskin
• Re: [w3c/permissions] Editorial fixes (#100) Jeffrey Yasskin
• Re: [w3c/permissions] Editorial fixes (#100) Jeffrey Yasskin
• Re: [w3c/permissions] Editorial fixes (#100) Jeffrey Yasskin
• Re: [w3c/permissions] Editorial fixes (#100) Jeffrey Yasskin
• Re: [w3c/permissions] Editorial fixes (#100) Jeffrey Yasskin
• Re: [w3c/permissions] Editorial fixes (#100) Jeffrey Yasskin
• Re: [w3c/permissions] Editorial fixes (#100) Jeffrey Yasskin
• Re: [w3c/permissions] Editorial fixes (#100) Jeffrey Yasskin
• Re: [w3c/permissions] Editorial fixes (#100) Jeffrey Yasskin
• Re: [w3c/permissions] Editorial fixes (#100) Jeffrey Yasskin
• Re: [w3c/permissions] Editorial fixes (#100) Jeffrey Yasskin
• Re: [w3c/permissions] Editorial fixes (#100) Jeffrey Yasskin

Tuesday, 12 July 2016

• Re: [w3c/webcomponents] The custom element state when constructor thrown (#533) Ryosuke Niwa
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Joseph Orbegoso Pea
• [w3c/permissions] docs(contributing): improve the guidelines for changes (#106) Jeffrey Yasskin
• Re: [w3c/webcomponents] The custom element state when constructor thrown (#533) Joseph Orbegoso Pea
• Re: [w3c/webcomponents] Are document fragments "inert"? (#532) Joseph Orbegoso Pea
• Re: [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (#99) Jeffrey Yasskin
• [w3c/push-api] Allow UA to not implement all PushSubscriptionOptions (#200) Martin Thomson
• [w3c/permissions] chore(editors): add W3C editor IDs (#105) Jeffrey Yasskin
• Re: [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (#99) Jeffrey Yasskin
• Re: [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (#99) Jeffrey Yasskin
• Re: [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (#99) Jeffrey Yasskin
• Re: [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (#99) Jeffrey Yasskin
• Re: [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (a9e27e4) Jeffrey Yasskin
• Re: [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (a9e27e4) Jeffrey Yasskin
• Re: [w3c/permissions] chore(navigator-and-workernavigator-extension): remove redudant text (#104) Jeffrey Yasskin
• Re: [w3c/touch-events] Specify what browsers do on non-touch devices (#64) Patrick H. Lauke
• Re: [w3c/screen-orientation] Allow lock Orientation more than one orientation (#91) Mounir Lamouri
• Re: [w3c/screen-orientation] Allow lock Orientation more than one orientation (#91) Mounir Lamouri
• [whatwg/fetch] Possible typo in header value definition (#332) Jeena Lee
• Re: [w3c/webcomponents] Allow or prohibit observedAttributes to observe 'style' attribute? (#521) Ryosuke Niwa
• [w3c/screen-orientation] Allow lock Orientation more than one orientation (#91) Jason
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Vincent Scheib
• Re: [w3c/pointerlock] PointerLock and Shadow DOM (#3) Vincent Scheib
• Re: [w3c/WebPlatformWG] grisha_pullRequest_AddtlAttendees (#48) gked
• [w3c/WebPlatformWG] grisha_pullRequest_AddtlAttendees (#48) gked
• [whatwg/xhr] failed to load data in sapui5 RowRepaeater (#78) NikhilPuri12
• Re: [w3c/permissions] how to tidy? (#98) Jeffrey Yasskin
• Re: [w3c/IndexedDB] The steps for opening a database are racy (#81) Joshua Bell
• Re: [w3c/webcomponents] The custom element state when constructor thrown (#533) Domenic Denicola
• Re: [whatwg/fetch] How response bodies get from a service worker to the main page is not very clear (#330) Domenic Denicola
• Re: [whatwg/streams] [WritableStream] Locking semantics (#474) Domenic Denicola
• Re: [w3c/permissions] Remove object-based permissions (#42) Jeffrey Yasskin
• [w3c/IndexedDB] The steps for opening a database are racy (#81) Anthony Ramine
• Re: [w3c/WebPlatformWG] Add jungkees to attendees list (#47) Léonie Watson
• [w3c/WebPlatformWG] Add jungkees to attendees list (#47) Jungkee Song
• [whatwg/fullscreen] Should we apply !important to "object-fit: contain"? (#44) Xidorn Quan
• Re: [slightlyoff/ServiceWorker] Should Cache-Control: private be respected? (#926) Ben Kelly
• Re: [w3c/permissions] chore(examples): Modernize JS examples (#101) Jeffrey Yasskin
• Re: [whatwg/streams] [WritableStream] Locking semantics (#474) Takeshi Yoshino
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) Takeshi Yoshino
• Re: [w3c/webcomponents] Allow or prohibit observedAttributes to observe 'style' attribute? (#521) smaug----
• Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) Philip Jägenstedt
• Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) Philip Jägenstedt
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) Takeshi Yoshino
• [slightlyoff/ServiceWorker] Should Cache-Control: private be respected? (#926) Ingvar Stepanyan
• Re: [w3c/permissions] chore(examples): Modernize JS examples (#101) Marcos Cáceres
• Re: [w3c/permissions] chore(examples): Modernize JS examples (#101) Marcos Cáceres
• [w3c/webcomponents] The custom element state when constructor thrown (#533) Koji Ishii
• Re: [whatwg/fetch] How response bodies get from a service worker to the main page is not very clear (#330) Yutaka Hirano
• Re: [w3c/WebPlatformWG] Kenji recording his plan to attend (#45) Yves Lafon
• Re: [w3c/WebPlatformWG] added name to list (#44) Yves Lafon
• Re: [w3c/WebPlatformWG] Kenji recording his plan to attend (#46) Yves Lafon
• [w3c/WebPlatformWG] Kenji recording his plan to attend (#46) Kenji Baheux
• [w3c/WebPlatformWG] Kenji recording his plan to attend (#45) Kenji Baheux
• Re: [w3c/webcomponents] Events whose composed flag should be true (#513) Hayato Ito
• [w3c/uievents] Fix #89. Make some of legacy UIEvents composed events (#93) Hayato Ito
• [w3c/WebPlatformWG] added name to list (#44) ephox-mogran
• Re: [w3c/webcomponents] Events whose composed flag should be true (#513) Hayato Ito
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Takayoshi Kochi
• Re: [w3c/permissions] chore(examples): Modernize JS examples (#101) Marcos Cáceres
• Re: [w3c/permissions] chore(examples): Modernize JS examples (#101) Marcos Cáceres
• Re: [w3c/permissions] chore(examples): Modernize JS examples (#101) Marcos Cáceres
• Re: [w3c/permissions] chore(examples): Modernize JS examples (#101) Marcos Cáceres
• Re: [w3c/permissions] how to tidy? (#98) Marcos Cáceres
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Takayoshi Kochi
• Re: [w3c/webcomponents] Events whose composed flag should be true (#513) Domenic Denicola
• Re: [w3c/webcomponents] Allow or prohibit observedAttributes to observe 'style' attribute? (#521) Domenic Denicola
• [w3ctag/spec-reviews] Review of WakeLock API and suitability for overall platform requested by 31 August 2016 (#126) Frederick Hirsch
• Re: [w3c/webcomponents] Events whose composed flag should be true (#513) Hayato Ito
• Re: [w3c/webcomponents] Events whose composed flag should be true (#513) Hayato Ito
• [whatwg/dom] Define dataset as a mixin for HTMLElement and SVGElement (#280) Nikos Andronikos

Monday, 11 July 2016

• Re: [w3c/webcomponents] Events whose composed flag should be true (#513) Hayato Ito
• Re: [w3c/webcomponents] Events whose composed flag should be true (#513) Hayato Ito
• Re: [w3c/permissions] Add screen sharing permissions (#45) Martin Thomson
• Re: [w3c/permissions] Add screen sharing permissions (#45) Martin Thomson
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Hayato Ito
• Re: [w3c/webcomponents] Invalid constructor when invoking the constructor directly (#531) Trey Shugart
• Re: [w3c/webcomponents] Invalid constructor when invoking the constructor directly (#531) Hayato Ito
• Re: [w3c/webcomponents] Invalid constructor when invoking the constructor directly (#531) Hayato Ito
• Re: [w3c/webcomponents] Are document fragments "inert"? (#532) Hayato Ito
• Re: [w3c/webcomponents] Are document fragments "inert"? (#532) Ryosuke Niwa
• [w3c/webcomponents] Are document fragments "intert"? (#532) Joseph Orbegoso Pea
• Re: [w3c/permissions] how to tidy? (#98) Jeffrey Yasskin
• Re: [w3c/webcomponents] Events whose composed flag should be true (#513) Ryosuke Niwa
• Re: [w3c/permissions] chore(examples): Modernize JS examples (#101) Jeffrey Yasskin
• Re: [w3c/permissions] chore(examples): Modernize JS examples (#101) Jeffrey Yasskin
• Re: [w3c/permissions] chore(examples): Modernize JS examples (#101) Jeffrey Yasskin
• Re: [w3c/permissions] chore(examples): Modernize JS examples (#101) Jeffrey Yasskin
• Re: [w3c/permissions] chore(examples): Modernize JS examples (#101) Jeffrey Yasskin
• Re: [w3c/permissions] chore(examples): Modernize JS examples (#101) Jeffrey Yasskin
• Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) Mounir Lamouri
• Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) Mounir Lamouri
• [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) Mounir Lamouri
• Re: [whatwg/fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) Philip Jägenstedt
• Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) Philip Jägenstedt
• Re: [w3c/webcomponents] Invalid constructor when invoking the constructor directly (#531) Domenic Denicola
• [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) Mounir Lamouri
• Re: [w3c/screen-orientation] Fullscreen Element Stack Not Found in Fullscreen (#88) Mounir Lamouri
• Re: [whatwg/fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) Philip Jägenstedt
• [w3c/webcomponents] Invalid constructor when invoking the constructor directly (#531) Michael Kriegel
• Re: [w3c/permissions] Faking permissions (#54) Marcos Cáceres
• Re: [w3c/permissions] Faking permissions (#54) Marcos Cáceres
• [w3c/DOM-Parsing] Step 1 of createContextualFragment is not enough (#17) Anthony Ramine
• Re: [w3c/permissions] navigator.permissions.request (#48) Marcos Cáceres
• Re: [w3c/permissions] Add screen sharing permissions (#45) Marcos Cáceres
• Re: [w3c/FileAPI] Improve readability of Blob-related statements (#42) Zhen Zhang
• Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) Ryosuke Niwa
• Re: [w3c/permissions] Remove object-based permissions (#42) Marcos Cáceres
• Re: [w3c/permissions] Remove object-based permissions (#42) Marcos Cáceres
• [w3c/FileAPI] Improve readability of Blob-related statements (#42) Zhen Zhang
• [w3c/permissions] chore(navigator-and-workernavigator-extension): remove redudant text (#104) Marcos Cáceres
• [w3c/permissions] Move the Permissions registry (#103) Marcos Cáceres
• [w3c/permissions] Exceptions in promise using methods (#102) Marcos Cáceres
• [w3c/permissions] chore(examples): Modernize JS examples (#101) Marcos Cáceres
• Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) Hayato Ito
• [w3c/permissions] Editorial fixes (#100) Marcos Cáceres
• Re: [w3c/webcomponents] Event retargetting in layman's terms? (#528) Hayato Ito
• Re: [w3c/webcomponents] Event retargetting in layman's terms? (#528) Hayato Ito
• [whatwg/url] Trailing dot and origin compuation (#132) Timothy Guan-tin Chien
• Re: [w3c/permissions] What should "retrieve the permission state" do for pickers? (#8) Marcos Cáceres
• [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (#99) Marcos Cáceres
• Re: [slightlyoff/ServiceWorker] Eliminate usage of entry and incumbent settings objects (#922) Domenic Denicola
• [w3c/permissions] how to tidy? (#98) Marcos Cáceres
• Re: [slightlyoff/ServiceWorker] Run the latest Bikeshed (#925) Jungkee Song

Saturday, 9 July 2016

• Re: [whatwg/fetch] referrer same-origin constraint is a footgun for people trying to "copy" a Request (#245) Ben Kelly
• Re: [slightlyoff/ServiceWorker] DOMParser within ServiceWorkers (#846) Jake Archibald
• Re: [slightlyoff/ServiceWorker] DOMParser within ServiceWorkers (#846) Anne van Kesteren
• Re: [slightlyoff/ServiceWorker] DOMParser within ServiceWorkers (#846) Inian
• Re: [slightlyoff/ServiceWorker] Consider relying on eTags (or other headers) for service worker dependencies to check for updates (#839) Ben Kelly
• Re: [slightlyoff/ServiceWorker] Byte by byte match does not capture developer friendly behaviour (#639) Marco Colli
• Re: [slightlyoff/ServiceWorker] Introduce `Service-Worker-Max-Age` header (#721) Marco Colli
• Re: [slightlyoff/ServiceWorker] Consider relying on eTags (or other headers) for service worker dependencies to check for updates (#839) Marco Colli
• Re: [slightlyoff/ServiceWorker] DOMParser within ServiceWorkers (#846) Jake Archibald
• [whatwg/fetch] fetch filter the symbols (#331) sam
• Re: [w3c/gamepad] Added touched property to GamepadButton (#26) Brandon Jones
• [w3c/gamepad] Determine how Multi-touch surfaces should be handled. (#27) Brandon Jones

Friday, 8 July 2016

• Re: [w3c/gamepad] Added touched property to GamepadButton (#26) chris van wiemeersch
• Re: [w3c/gamepad] Added touched property to GamepadButton (#26) Ted Mielczarek
• Re: [w3c/gamepad] Added touched property to GamepadButton (#26) Ted Mielczarek
• Re: [slightlyoff/ServiceWorker] DOMParser within ServiceWorkers (#846) Inian
• Re: [w3c/gamepad] Added touched property to GamepadButton (#26) Brandon Jones
• Re: [w3c/IndexedDB] Specify IDBOpenDBRequest processing as a queue? (#79) Joshua Bell
• Re: [w3c/gamepad] Added touched property to GamepadButton (#26) Brandon Jones
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Vincent Scheib
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Vincent Scheib
• [slightlyoff/ServiceWorker] Run the latest Bikeshed (#925) Domenic Denicola
• Re: [whatwg/fetch] How response bodies get from a service worker to the main page is not very clear (#330) Domenic Denicola
• Re: [w3c/webcomponents] [idea] distributedCallback for Custom Elements (#527) Joseph Orbegoso Pea
• Re: [w3c/IndexedDB] Make IDBRequest.error and IDBRequest.transaction nullable (#80) Joshua Bell
• Re: [w3c/IndexedDB] Make IDBRequest.error and IDBRequest.transaction nullable (#80) Joshua Bell
• Re: [w3c/gamepad] Added touched property to GamepadButton (#26) Brandon Jones
• Re: [whatwg/fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) Mounir Lamouri
• Re: [w3c/screen-orientation] Timing of triggering change event doesn't look right (#89) Mounir Lamouri
• Re: [w3c/screen-orientation] Timing of triggering change event doesn't look right (#89) Mounir Lamouri
• Re: [w3c/screen-orientation] Use animation frame task (#40) Mounir Lamouri
• Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) Ben Kelly
• Re: [whatwg/fetch] How response bodies get from a service worker to the main page is not very clear (#330) Ben Kelly
• Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) Anne van Kesteren
• Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) Boris Zbarsky
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Hayato Ito
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Anne van Kesteren
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Domenic Denicola
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Hayato Ito
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Domenic Denicola
• Re: [w3c/gamepad] Added touched property to GamepadButton (#26) Ted Mielczarek
• Re: [slightlyoff/ServiceWorker] Update for changes to HTML's script-fetching algorithms (#923) Jungkee Song
• [w3c/IndexedDB] Make IDBRequest.error nullable (#80) Anthony Ramine
• Re: [whatwg/xhr] ionic app not statrting (#77) Anne van Kesteren
• [whatwg/xhr] ionic app not statrting (#77) androiddeveloper88
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Takayoshi Kochi
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Takayoshi Kochi
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Takayoshi Kochi
• Re: [w3c/push-api] PushSubscriptionOptions ArrayBuffer lifetime issues (#198) Martin Thomson
• Re: [w3c/push-api] Make applicationServerKey [SameObject] not [Throws] (#199) Martin Thomson
• Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) Yoav Weiss
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Takayoshi Kochi
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Takayoshi Kochi
• Re: [slightlyoff/ServiceWorker] Expose GeoLocation to workers (#745) Richard Maher
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Takayoshi Kochi
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Ryosuke Niwa
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Takayoshi Kochi
• Re: [whatwg/fetch] How response bodies get from a service worker to the main page is not very clear (#330) Yutaka Hirano
• Re: [whatwg/fetch] How response bodies get from a service worker to the main page is not very clear (#330) Yutaka Hirano
• Re: [slightlyoff/ServiceWorker] Expose GeoLocation to workers (#745) Richard Maher
• Re: [whatwg/fetch] How response bodies get from a service worker to the main page is not very clear (#330) Anne van Kesteren
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Takayoshi Kochi
• Re: [whatwg/fetch] How response bodies get from a service worker to the main page is not very clear (#330) Yutaka Hirano
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Anne van Kesteren
• Re: [whatwg/fetch] How response bodies get from a service worker to the main page is not very clear (#330) Anne van Kesteren
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Takayoshi Kochi
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Takayoshi Kochi
• Re: [w3c/gamepad] Added GamepadPose and GamepadCapabilities (#25) Brandon Jones
• Re: [whatwg/fetch] How response bodies get from a service worker to the main page is not very clear (#330) Yutaka Hirano
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Ryosuke Niwa
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Ryosuke Niwa
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Hayato Ito
• Re: [w3c/gamepad] Added touched property to GamepadButton (#26) chris van wiemeersch
• Re: [w3c/gamepad] Added GamepadPose and GamepadCapabilities (#25) chris van wiemeersch

Thursday, 7 July 2016

• Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) Ryosuke Niwa
• Re: [w3c/gamepad] Added GamepadPose and GamepadCapabilities (#25) Brandon Jones
• Re: [w3c/gamepad] Added touched property to GamepadButton (#26) Brandon Jones
• Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) Boris Zbarsky
• Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) Boris Zbarsky
• Re: [whatwg/streams] IsFiniteNonNegativeNumber() could be used in more places (#475) Domenic Denicola
• Re: [whatwg/streams] Tidy up range checking (#477) Domenic Denicola
• Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Ryosuke Niwa
• Re: [whatwg/dom] Do not throw for query() and queryAll() (#39) Rafał Pocztarski
• [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) Domenic Denicola
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Vincent Scheib
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Vincent Scheib
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Vincent Scheib
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Vincent Scheib
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Vincent Scheib
• Re: [whatwg/dom] Do not throw for query() and queryAll() (#39) Anne van Kesteren
• Re: [whatwg/dom] "In a document" confusion (#238) Anne van Kesteren
• [whatwg/fetch] How response bodies get from a service worker to the main page is not very clear (#330) Domenic Denicola
• [w3c/push-api] Make applicationServerKey [SameObject] not [Throws] (#199) John Mellor
• Re: [whatwg/dom] Do not throw for query() and queryAll() (#39) Rafał Pocztarski
• Re: [w3c/push-api] PushSubscriptionOptions ArrayBuffer lifetime issues (#198) John Mellor
• Re: [w3ctag/spec-reviews] Privacy Mode (#101) Daniel Appelquist
• Re: [slightlyoff/ServiceWorker] Update for changes to HTML's script-fetching algorithms (#923) Domenic Denicola
• [w3ctag/spec-reviews] Do we have feedback on Web Payment group's response to security & privacy questionnaire? (#125) Daniel Appelquist
• Re: [slightlyoff/ServiceWorker] Expose GeoLocation to workers (#745) Léonie Watson
• Re: [whatwg/dom] Do not throw for query() and queryAll() (#39) Philip Jägenstedt
• Re: [whatwg/dom] Do not throw for query() and queryAll() (#39) Anne van Kesteren
• Re: [slightlyoff/ServiceWorker] Expose GeoLocation to workers (#745) Rik de Boer
• Re: [slightlyoff/ServiceWorker] When does the openWindow promise resolve? (#728) Jungkee Song
• Re: [whatwg/dom] Do not throw for query() and queryAll() (#39) Philip Jägenstedt
• Re: [whatwg/dom] Do not throw for query() and queryAll() (#39) Rafał Pocztarski
• Re: [whatwg/dom] Do not throw for query() and queryAll() (#39) Philip Jägenstedt
• Re: [whatwg/dom] Do not throw for query() and queryAll() (#39) Rafał Pocztarski
• Re: [slightlyoff/ServiceWorker] Expose GeoLocation to workers (#745) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Expose GeoLocation to workers (#745) Richard Maher
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) Takeshi Yoshino
• Re: [whatwg/dom] Rename "in a (shadow-including) document" (#275) Anne van Kesteren
• Re: [whatwg/dom] Rename "in a (shadow-including) document" (#275) Anne van Kesteren
• Re: [whatwg/dom] Rename "in a (shadow-including) document" (#275) Anne van Kesteren
• Re: [slightlyoff/ServiceWorker] ServiceWorkerContainer spec lists `onerror` as an event handler (#912) Makoto Shimazu
• Re: [w3c/manifest] Ability to claim web app (#476) Arthur Stolyar
• Re: [w3c/manifest] Ability to claim web app (#476) Ben Francis
• Re: [whatwg/xhr] 😠 (#76) Anne van Kesteren
• Re: [w3c/manifest] Ability to claim web app (#476) Kenneth Rohde Christiansen
• Re: [w3c/manifest] Ability to claim web app (#476) Anne van Kesteren
• Re: [w3c/manifest] Ability to claim web app (#476) Arthur Stolyar
• Re: [w3c/manifest] Ability to claim web app (#476) Anne van Kesteren
• Re: [w3c/editing] We should keep data in UI events for beforeInput that does the text/plain serialization. We should add dataTransfer to the editing spec for other mime types(html, text with line breaks, etc) (#106) Johannes Wilm
• Re: [whatwg/xhr] 😠 (#76) Marcos Cáceres
• [whatwg/xhr] 😠 (#76) countrygirl351
• Re: [w3ctag/spec-reviews] Review secure contexts (#124) Mike West
• Re: [w3c/webcomponents] Events whose composed flag should be true (#513) Ryosuke Niwa
• Re: [w3c/webcomponents] Events whose composed flag should be true (#513) Ryosuke Niwa
• Re: [w3c/webcomponents] Events whose composed flag should be true (#513) Ryosuke Niwa
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Takayoshi Kochi
• Re: [w3c/manifest] Ability to claim web app (#476) Marcos Cáceres
• Re: [w3c/manifest] Ability to claim web app (#476) Marcos Cáceres
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Hayato Ito
• Re: [slightlyoff/ServiceWorker] Expose GeoLocation to workers (#745) Marcos Cáceres
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Takayoshi Kochi
• Re: [w3c/manifest] Ability to claim web app (#476) Marcos Cáceres
• Re: [w3c/manifest] Add optional Transition Screen member (#478) Marcos Cáceres
• Re: [w3c/manifest] Add optional Transition Screen member (#478) Marcos Cáceres
• Re: [WICG/directory-upload] Security issue of directory upload: pretend to download when actaully to upload a directory (#38) Duan Yao
• Re: [w3ctag/spec-reviews] Progressive Web Apps (#123) Marcos Cáceres
• Re: [w3ctag/spec-reviews] Progressive Web Apps (#123) Marcos Cáceres

Wednesday, 6 July 2016

• Re: [w3ctag/spec-reviews] Review secure contexts (#124) Daniel Appelquist
• Re: [w3ctag/spec-reviews] Review secure contexts (#124) Travis Leithead
• [w3ctag/spec-reviews] Review secure contexts (#124) Daniel Appelquist
• Re: [w3ctag/spec-reviews] Review Web Annotations specs (#93) Daniel Appelquist
• Re: [w3ctag/spec-reviews] Review Web Annotations specs (#93) Daniel Appelquist
• Re: [w3ctag/spec-reviews] Accelerated Mobile Pages (AMP) (#122) Daniel Appelquist
• Re: [w3ctag/spec-reviews] Accelerated Mobile Pages (AMP) (#122) Daniel Appelquist
• Re: [w3ctag/spec-reviews] Accelerated Mobile Pages (AMP) (#122) Daniel Appelquist
• Re: [w3ctag/spec-reviews] Progressive Web Apps (#123) Daniel Appelquist
• Re: [w3ctag/spec-reviews] Progressive Web Apps (#123) Daniel Appelquist
• Re: [w3ctag/spec-reviews] Progressive Web Apps (#123) Daniel Appelquist
• Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) Domenic Denicola
• Re: [whatwg/dom] Set the stage for new custom element adoption semantics (#279) Domenic Denicola
• [whatwg/dom] Set the stage for new custom element adoption semantics (#279) Domenic Denicola
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) Elliott Sprehn
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) Ryosuke Niwa
• Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) Ryosuke Niwa
• Re: [whatwg/streams] Should write() always error the stream when it rejects the promise it returned? (#476) Domenic Denicola
• [w3c/manifest] Add optional Transition Screen member (#478) Rob Dolin (MSFT)
• Re: [whatwg/streams] [WritableStream] Locking semantics (#474) Domenic Denicola
• [whatwg/streams] Tidy up range checking (#477) Domenic Denicola
• [whatwg/dom] Figure out what to do with XMLDocument (#278) Domenic Denicola
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) Zambonifofex
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) Takeshi Yoshino
• Re: [w3c/push-api] PushSubscriptionOptions ArrayBuffer lifetime issues (#198) Anne van Kesteren
• Re: [w3c/push-api] PushSubscriptionOptions ArrayBuffer lifetime issues (#198) Kit Cambridge
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) Eric Bidelman
• [whatwg/streams] Should write() always error the stream when it rejects the promise it returned? (#476) Takeshi Yoshino
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) Domenic Denicola
• Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) Domenic Denicola
• [slightlyoff/ServiceWorker] Stop monkeypatching event dispatch (#924) Anne van Kesteren
• Re: [w3c/manifest] Ability to claim web app (#476) Anne van Kesteren
• Re: [w3c/manifest] Ability to claim web app (#476) Sebastian Kippe
• Re: [w3c/manifest] Ability to claim web app (#476) Anne van Kesteren
• Re: [w3c/manifest] Ability to claim web app (#476) Marcos Cáceres
• Re: [w3c/manifest] Ability to claim web app (#476) Marcos Cáceres
• Re: [w3c/manifest] Ability to claim web app (#476) Sebastian Kippe
• Re: [w3c/manifest] Ability to claim web app (#476) Marcos Cáceres
• Re: [w3c/manifest] Ability to claim web app (#476) Marcos Cáceres
• Re: [w3c/manifest] Ability to claim web app (#476) Sebastian Kippe
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) Joseph Orbegoso Pea
• Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) Ryosuke Niwa
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) Ryosuke Niwa
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) Joseph Orbegoso Pea
• Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) Anne van Kesteren
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) Ryosuke Niwa
• Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) Ryosuke Niwa
• Re: [w3c/push-api] PushSubscriptionOptions ArrayBuffer lifetime issues (#198) Anne van Kesteren
• Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) Anne van Kesteren
• Re: [w3c/permissions] Add terms to Shepherd (#64) Marcos Cáceres
• Re: [w3c/permissions] Add terms to Shepherd (#64) Marcos Cáceres
• Re: [w3c/permissions] Add terms to Shepherd (#64) Marcos Cáceres
• Re: [w3c/manifest] Integration with service workers (#161) Marcos Cáceres
• Re: [w3c/manifest] Ability to claim web app (#476) Marcos Cáceres
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) Zambonifofex
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) Bede Overend
• Re: [w3c/manifest] Add beforeinstallprompt event (#417) Matt Giuca

Tuesday, 5 July 2016

• [w3c/manifest] Add screenshots object (#477) Rob Dolin (MSFT)
• [w3c/manifest] Ability to claim web app (#476) Rob Dolin (MSFT)
• Re: [w3c/manifest] Integration with service workers (#161) Rob Dolin (MSFT)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) Zambonifofex
• Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) Ryosuke Niwa
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) Ryosuke Niwa
• Re: [whatwg/streams] IsFiniteNonNegativeNumber() could be used in more places (#475) Domenic Denicola
• Re: [whatwg/streams] IsFiniteNonNegativeNumber() could be used in more places (#475) Ben Kelly
• [whatwg/streams] IsFiniteNonNegativeNumber() could be used in more places (#475) Ben Kelly
• [w3c/push-api] PushSubscriptionOptions ArrayBuffer lifetime issues (#198) John Mellor
• [w3c/WebPlatformWG] Publish First Public Working Draft for HTML 5.2? (#43) chaals
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Ben Kelly
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Ben Kelly
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Ben Kelly
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#277) Hayato Ito
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Ben Kelly
• [whatwg/streams] [WritableStream] Locking semantics (#474) Takeshi Yoshino
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Jake Archibald
• Re: [whatwg/dom] Add relatedTarget to event dispatch (#277) Anne van Kesteren
• [whatwg/dom] Add relatedTarget to event dispatch (#277) Anne van Kesteren
• [whatwg/dom] Upstream retargeting algorithm (#276) Anne van Kesteren
• Re: [whatwg/dom] Point out that initial about:blank also results in quirks mode (#268) Anne van Kesteren
• Re: [whatwg/dom] Point out that initial about:blank also results in quirks mode (#268) Anne van Kesteren
• Re: [whatwg/dom] Note that about:blank also results in quirks mode (#272) Anne van Kesteren
• Re: [slightlyoff/ServiceWorker] Expose GeoLocation to workers (#745) Richard Maher
• Re: [w3c/WebPlatformWG] Kenji Baheux recording his plan to attend (#42) Léonie Watson
• [whatwg/fullscreen] Allow element in Shadow DOM to become fullscreen (#42) Takayoshi Kochi
• Re: [w3ctag/spec-reviews] Progressive Web Apps (#123) Marcos Cáceres
• Re: [w3ctag/spec-reviews] Progressive Web Apps (#123) Andrew Betts
• [w3c/WebPlatformWG] Kenji Baheux recording his plan to attend (#42) Kenji Baheux
• Re: [w3c/manifest] Include Minimal Store/Catalog MetaData in Manifest (#448) Marcos Cáceres
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Takayoshi Kochi
• Re: [w3ctag/spec-reviews] Progressive Web Apps (#123) Marcos Cáceres
• Re: [w3ctag/spec-reviews] Accelerated Mobile Pages (AMP) (#122) Andrew Betts
• Re: [w3ctag/spec-reviews] Progressive Web Apps (#123) Andrew Betts
• Re: [w3c/manifest] Add beforeinstallprompt event (#417) Matt Giuca

Monday, 4 July 2016

• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) bmaurer
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) bmaurer
• Re: [whatwg/url] Figure out what to do with youtube IDNA issues (#131) Anne van Kesteren
• Re: [whatwg/url] Figure out what to do with youtube IDNA issues (#131) Anne van Kesteren
• Re: [whatwg/url] Figure out what to do with youtube IDNA issues (#131) Anne van Kesteren
• [whatwg/fullscreen] Use new "allowed to use" algorithm once introduced (#41) Anne van Kesteren
• Re: [whatwg/dom] "In a document" confusion (#238) Anne van Kesteren
• Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) Takeshi Yoshino
• Re: [whatwg/dom] Rename "in a (shadow-including) document" (#275) Anne van Kesteren
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Anne van Kesteren
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Jake Archibald
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Jake Archibald
• Re: [whatwg/fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) Philip Jägenstedt
• Re: [whatwg/fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) Philip Jägenstedt
• Re: [whatwg/dom] "In a document" confusion (#238) Anne van Kesteren
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Hayato Ito
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Takayoshi Kochi
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Takayoshi Kochi
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Anne van Kesteren
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Anne van Kesteren
• Re: [whatwg/xhr] "representing the same bytes" (#75) Anne van Kesteren
• Re: [w3c/manifest] Add beforeinstallprompt event (#417) Kenneth Rohde Christiansen
• Re: [w3c/manifest] Add beforeinstallprompt event (#417) Marcos Cáceres

Sunday, 3 July 2016

• Re: [slightlyoff/ServiceWorker] Expose GeoLocation to workers (#745) Rik de Boer
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Alex Russell
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) bmaurer
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Jake Archibald
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) Joseph Orbegoso Pea
• Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) Joseph Orbegoso Pea
• Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) Anne van Kesteren

Saturday, 2 July 2016

• Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) Joseph Orbegoso Pea
• Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) Joseph Orbegoso Pea
• Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) Joseph Orbegoso Pea
• Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) Domenic Denicola
• Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) Joseph Orbegoso Pea
• Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) Alex Russell
• [whatwg/xhr] "representing the same bytes" (#75) Domenic Denicola
• Re: [w3c/webcomponents] Should innerHTML propagate custom element constructor exceptions? (#525) Domenic Denicola
• Re: [w3c/webcomponents] Should innerHTML propagate custom element constructor exceptions? (#525) Ryosuke Niwa
• Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) Ryosuke Niwa
• Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) Joseph Orbegoso Pea
• Re: [w3c/webcomponents] [idea] distributedCallback for Custom Elements (#527) Joseph Orbegoso Pea
• Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) Joseph Orbegoso Pea

Friday, 1 July 2016

• [slightlyoff/ServiceWorker] Update for changes to HTML's script-fetching algorithms (#923) Domenic Denicola
• Re: [whatwg/dom] "In a document" confusion (#238) Domenic Denicola
• Re: [whatwg/dom] "In a document" confusion (#238) smaug----
• Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) Domenic Denicola
• Re: [whatwg/dom] "In a document" confusion (#238) Domenic Denicola
• Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) Inian
• Re: [slightlyoff/ServiceWorker] Need to review the algorithms for creating a new environment settings object (#919) Alex Russell
• Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) Ben Kelly
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Hayato Ito
• [whatwg/url] Figure out what to do with youtube IDNA issues (#131) Ms2ger
• Re: [whatwg/url] Basic URL Parse point 1 (#130) Álvaro Carneiro
• Re: [whatwg/url] Basic URL Parse point 1 (#130) Álvaro Carneiro
• Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) Trey Shugart
• Re: [whatwg/url] Basic URL Parse point 1 (#130) Anne van Kesteren
• Re: [whatwg/dom] "In a document" confusion (#238) Anne van Kesteren
• Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) Joseph Orbegoso Pea
• Re: [whatwg/url] Basic URL Parse point 1 (#130) Álvaro Carneiro
• [whatwg/dom] Rename "in a (shadow-including) document" (#275) Anne van Kesteren
• Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) Trey Shugart
• Re: [whatwg/url] Basic URL Parse point 1 (#130) Anne van Kesteren
• [whatwg/url] Basic URL Parse point 1 (#130) Álvaro Carneiro
• Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) Joseph Orbegoso Pea
• Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) Anne van Kesteren
• Re: [whatwg/xhr] Property to disable following redirects (#74) Anne van Kesteren
• Re: [whatwg/fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) Xidorn Quan
• Re: [whatwg/fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) Xidorn Quan
• Re: [whatwg/fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) Xidorn Quan
• Re: [whatwg/fullscreen] Propose to always render elements in the top layer as if it is fixed positioned (#19) Xidorn Quan
• Re: [whatwg/fullscreen] Propose to always render elements in the top layer as if it is fixed positioned (#19) Xidorn Quan
• Re: [whatwg/xhr] Property to disable following redirects (#74) zpul
• Re: [whatwg/xhr] Property to disable following redirects (#74) Anne van Kesteren
• Re: [whatwg/xhr] Property to disable following redirects (#74) Anne van Kesteren
• [whatwg/xhr] Property to disable following redirects (#74) zpul
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Takayoshi Kochi
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Takayoshi Kochi
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Takayoshi Kochi
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Takayoshi Kochi
• Re: [w3c/pointerlock] Update for Shadow DOM (#4) Hayato Ito
• Re: [w3c/DOM-Parsing] Significant normative and editorial updates (#16) Travis Leithead
• Re: [w3c/DOM-Parsing] Apply serialization algorithm fixes based on testing (#14) Travis Leithead
• Re: [w3c/DOM-Parsing] Significant normative and editorial updates (#16) Travis Leithead
• Re: [w3c/DOM-Parsing] Significant normative and editorial updates (#16) Travis Leithead
• Re: [slightlyoff/ServiceWorker] Need to review the algorithms for creating a new environment settings object (#919) Domenic Denicola
• Re: [slightlyoff/ServiceWorker] Need to review the algorithms for creating a new environment settings object (#919) Alex Russell
• Re: [heycam/webidl] Allow constructor<ClassType> as a type accepted by functions. (#101) smaug----
• Re: [w3c/manifest] Add beforeinstallprompt event (#417) Dominick Ng

Last message date: Sunday, 31 July 2016 23:09:21 UTC