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

A. Matías Quezada

Re: [whatwg/streams] Broadcast ReadableStream (#481) (Monday, 18 July)
Re: [whatwg/streams] Broadcast ReadableStream (#481) (Monday, 18 July)
[whatwg/streams] Broadcast ReadableStream (#481) (Monday, 18 July)

Adam Klein

Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Wednesday, 13 July)

Adam Rice

[whatwg/streams] Editorial changes to the socket example (#486) (Friday, 29 July)
[whatwg/encoding] "URL parsing HTML form submission" (#67) (Friday, 29 July)
[whatwg/encoding] "In equations, all numbers are integers, additio..." (#66) (Friday, 29 July)
Re: [whatwg/streams] "socket.setTCPWindowSize" (#483) (Friday, 29 July)
Re: [whatwg/streams] "socket.setTCPWindowSize" (#483) (Friday, 29 July)
[whatwg/streams] "Web sockets do not provide any way to tell when..." (#485) (Thursday, 28 July)
Re: [whatwg/streams] "if (controller.byobRequest)" (#484) (Thursday, 28 July)
Re: [whatwg/streams] "if (controller.byobRequest)" (#484) (Thursday, 28 July)
[whatwg/streams] "if (controller.byobRequest)" (#484) (Thursday, 28 July)
[whatwg/streams] "socket.setTCPWindowSize" (#483) (Thursday, 28 July)
[whatwg/streams] "ws.onend" (#482) (Thursday, 28 July)

Alex Russell

Re: [w3ctag/spec-reviews] TV-Specific Web Subsetting (#105) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] relative URLs are not updated pushState() (#118) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Ambient Light Sensor API (#115) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Bluetooth API Security Model (#90) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Bluetooth API Security Model (#90) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Browser Fingerprinting Document (#38) (Saturday, 30 July)
Re: [slightlyoff/ServiceWorker] should UA check for updates on navigate when there is no fetch event? (#905) (Friday, 29 July)
Re: [slightlyoff/ServiceWorker] ServiceWorkerContainer spec lists `onerror` as an event handler (#912) (Friday, 29 July)
Re: [slightlyoff/ServiceWorker] should async waitUntil() work in .then() handler of promise passed to previous waitUntil()? (#935) (Friday, 29 July)
Re: [slightlyoff/ServiceWorker] Should waitUntil() fast fail if a single extension promise rejects? (#936) (Friday, 29 July)
Re: [slightlyoff/ServiceWorker] Receivers of ranged responses must ensure all ranges come from the same underlying resource (#703) (Friday, 29 July)
Re: [w3ctag/spec-reviews] WebRTC (#14) (Wednesday, 20 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Monday, 18 July)
Re: [slightlyoff/ServiceWorker] Expose GeoLocation to workers (#745) (Friday, 15 July)
Re: [slightlyoff/ServiceWorker] Expose GeoLocation to workers (#745) (Friday, 15 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Sunday, 3 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Saturday, 2 July)
Re: [slightlyoff/ServiceWorker] Need to review the algorithms for creating a new environment settings object (#919) (Friday, 1 July)
Re: [slightlyoff/ServiceWorker] Need to review the algorithms for creating a new environment settings object (#919) (Friday, 1 July)

aliams

Re: [slightlyoff/ServiceWorker] spec exactly how to order non-window Client objects (#887) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] spec behavior when ServiceWorkerContainer parent client is dead (#777) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] spec should be more explicit about accessing internal body on opaque Responses (#710) (Tuesday, 26 July)
Re: [slightlyoff/ServiceWorker] More clarity around waiting for an active worker to finish (#916) (Tuesday, 26 July)
Re: [slightlyoff/ServiceWorker] spec exactly how to order non-window Client objects (#887) (Tuesday, 26 July)
Re: [slightlyoff/ServiceWorker] Should WindowClient.navigate(url) navigate with "replacement enabled"? (#918) (Monday, 25 July)

Anders Riutta

Re: [whatwg/streams] light weight transformations (#461) (Saturday, 30 July)
Re: [whatwg/streams] light weight transformations (#461) (Saturday, 30 July)
[whatwg/streams] Repo/package confusion (#487) (Friday, 29 July)

Andrea Giammarchi

Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 18 July)
Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 14 July)
Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 14 July)
Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 13 July)
Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 13 July)

Andrew Betts

Re: [w3ctag/spec-reviews] Notifications API (#94) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Progressive Web Apps (#123) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Progressive Web Apps (#123) (Tuesday, 5 July)
Re: [w3ctag/spec-reviews] Accelerated Mobile Pages (AMP) (#122) (Tuesday, 5 July)
Re: [w3ctag/spec-reviews] Progressive Web Apps (#123) (Tuesday, 5 July)

Andrew Sutherland

Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Wednesday, 20 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Tuesday, 19 July)

androiddeveloper88

[whatwg/xhr] ionic app not statrting (#77) (Friday, 8 July)

Anne van Kesteren

Re: [whatwg/dom] Figure out what to do with XMLDocument (#278) (Sunday, 31 July)
Re: [whatwg/dom] iterable declaration on NodeList is invalid (#284) (Sunday, 31 July)
Re: [slightlyoff/ServiceWorker] OCSP fetches bypass service worker (#564) (Sunday, 31 July)
Re: [whatwg/storage] Exposing cross-origin resource size (#31) (Sunday, 31 July)
Re: [whatwg/encoding] Add UTF-7 to replacement encoding list? (#68) (Sunday, 31 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Sunday, 31 July)
Re: [slightlyoff/ServiceWorker] Should mixed content always be blocked? (#813) (Friday, 29 July)
Re: [w3c/charter-html] Indicate relationship with the WHATWG (#112) (Friday, 29 July)
Re: [slightlyoff/ServiceWorker] Should mixed content always be blocked? (#813) (Friday, 29 July)
Re: [slightlyoff/ServiceWorker] should FetchEvent.request.cache reflect non-fetch browser cache controls? (#875) (Friday, 29 July)
Re: [slightlyoff/ServiceWorker] Should mixed content always be blocked? (#813) (Friday, 29 July)
Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Friday, 29 July)
Re: [whatwg/dom] Make Attr a Node again (#102) (Friday, 29 July)
Re: [whatwg/fetch] Add trailer support to network responses (#344) (Friday, 29 July)
Re: [whatwg/fetch] Add trailer support to network responses (#344) (Friday, 29 July)
Re: [whatwg/fetch] Add trailer support to network responses (#344) (Friday, 29 July)
Re: [whatwg/fetch] Add trailer support to network responses (#344) (Friday, 29 July)
Re: [whatwg/fetch] Add trailer support to network responses (#344) (Friday, 29 July)
Re: [whatwg/fetch] Add trailer support to network responses (#344) (Friday, 29 July)
Re: [whatwg/fetch] Access to the HTTP trailer (#34) (Friday, 29 July)
Re: [whatwg/fetch] Add trailer support to network responses (#344) (Friday, 29 July)
Re: [whatwg/xhr] good (#81) (Friday, 29 July)
Re: [whatwg/encoding] "URL parsing HTML form submission" (#67) (Friday, 29 July)
Re: [whatwg/encoding] "URL parsing HTML form submission" (#67) (Friday, 29 July)
Re: [whatwg/dom] iterable declaration on NodeList is invalid (#284) (Friday, 29 July)
Re: [whatwg/encoding] "In equations, all numbers are integers, additio..." (#66) (Friday, 29 July)
Re: [whatwg/fetch] Add trailer support to network responses (#344) (Thursday, 28 July)
[whatwg/fetch] Add trailer support to network responses (#344) (Thursday, 28 July)
[whatwg/fetch] Non-null response body check is a no-op (#343) (Thursday, 28 July)
Re: [whatwg/fetch] Access to the HTTP trailer (#34) (Thursday, 28 July)
Re: [whatwg/fetch] Support same-origin, strict-origin, strict-origin-when-cross-origin in request' referrer policy (#342) (Thursday, 28 July)
Re: [whatwg/url] Url definition should define the fragment as optional (#134) (Thursday, 28 July)
Re: [whatwg/url] Url definition should define the fragment as optional (#134) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] OCSP fetches bypass service worker (#564) (Thursday, 28 July)
Re: [w3c/permissions] Add pointerlock to the permissions enum? (#67) (Thursday, 28 July)
Re: [w3c/permissions] Add pointerlock to the permissions enum? (#67) (Thursday, 28 July)
Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Thursday, 28 July)
Re: [whatwg/fetch] Only append Authorization if none is set (#198) (Wednesday, 27 July)
Re: [whatwg/url] Let webkitURL be an alias of the URL constructor (#135) (Wednesday, 27 July)
Re: [whatwg/fetch] Only append Authorization if none is set (#198) (Wednesday, 27 July)
Re: [whatwg/fetch] Only append Authorization if none is set (#198) (Wednesday, 27 July)
Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Wednesday, 27 July)
Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Wednesday, 27 July)
Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Wednesday, 27 July)
Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Wednesday, 27 July)
Re: [whatwg/fetch] Access to the HTTP trailer (#34) (Wednesday, 27 July)
Re: [whatwg/fetch] Only append Authorization if none is set (#198) (Wednesday, 27 July)
Re: [whatwg/fetch] Add steps to intercept requests using foreign fetch. (#329) (Wednesday, 27 July)
Re: [whatwg/fetch] Add steps to intercept requests using foreign fetch. (#329) (Wednesday, 27 July)
Re: [whatwg/fetch] Add steps to intercept requests using foreign fetch. (#329) (Wednesday, 27 July)
Re: [whatwg/fetch] Add steps to intercept requests using foreign fetch. (#329) (Wednesday, 27 July)
Re: [whatwg/fetch] Add steps to intercept requests using foreign fetch. (#329) (Wednesday, 27 July)
Re: [whatwg/fetch] Add steps to intercept requests using foreign fetch. (#329) (Wednesday, 27 July)
Re: [whatwg/fetch] Add steps to intercept requests using foreign fetch. (#329) (Wednesday, 27 July)
Re: [whatwg/fetch] Add steps to intercept requests using foreign fetch. (#329) (Wednesday, 27 July)
Re: [whatwg/fetch] Add steps to intercept requests using foreign fetch. (#329) (Wednesday, 27 July)
Re: [w3c/pointerlock] Add pointerlock to the permissions enum (#5) (Wednesday, 27 July)
Re: [w3c/pointerlock] Add pointerlock to the permissions enum (#5) (Tuesday, 26 July)
Re: [whatwg/fetch] HTTP/2 server push support (#51) (Tuesday, 26 July)
Re: [whatwg/fetch] Access to the HTTP trailer (#34) (Tuesday, 26 July)
Re: [slightlyoff/ServiceWorker] clarify secure context requirements in Handle Fetch (#890) (Tuesday, 26 July)
Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Tuesday, 26 July)
Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Monday, 25 July)
Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Monday, 25 July)
Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Monday, 25 July)
[whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) (Monday, 25 July)
Re: [whatwg/fetch] no-referrer should not set referer header (#323) (Monday, 25 July)
Re: [whatwg/fetch] no-referrer should not set referer header (#323) (Monday, 25 July)
Re: [w3c/push-api] typedef object JSON; is incorrect (#204) (Monday, 25 July)
Re: [w3c/push-api] typedef object JSON; is incorrect (#204) (Monday, 25 July)
Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Monday, 25 July)
Re: [w3c/push-api] typedef object JSON; is incorrect (#204) (Monday, 25 July)
Re: [whatwg/encoding] Editorial: make gb18030 math more clear (#65) (Sunday, 24 July)
[whatwg/encoding] Editorial: make gb18030 math more clear (#65) (Sunday, 24 July)
Re: [whatwg/encoding] Please double-check the end of the EUDC range (#53) (Sunday, 24 July)
Re: [whatwg/encoding] Please double-check the end of the EUDC range (#53) (Sunday, 24 July)
Re: [whatwg/encoding] Please double-check the end of the EUDC range (#53) (Sunday, 24 July)
Re: [whatwg/encoding] Please double-check the end of the EUDC range (#53) (Sunday, 24 July)
Re: [whatwg/encoding] Please double-check the end of the EUDC range (#53) (Sunday, 24 July)
Re: [whatwg/encoding] Correct [Exposed] syntax (#64) (Sunday, 24 July)
Re: [whatwg/encoding] Correct [Exposed] syntax (#64) (Sunday, 24 July)
Re: [whatwg/dom] Remove SVGZoomEvent? (#283) (Saturday, 23 July)
Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Saturday, 23 July)
Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Friday, 22 July)
Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Friday, 22 July)
Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Friday, 22 July)
Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Friday, 22 July)
Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Friday, 22 July)
Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Friday, 22 July)
Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Friday, 22 July)
Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Friday, 22 July)
Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Friday, 22 July)
Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Friday, 22 July)
Re: [whatwg/fetch] Make it clearer that cache mode "default" follows normal logic (#340) (Friday, 22 July)
Re: [whatwg/fetch] Delay network errors to prevent port scanning (#338) (Friday, 22 July)
Re: [w3c/push-api] typedef object JSON; is incorrect (#204) (Friday, 22 July)
Re: [w3c/push-api] typedef object JSON; is incorrect (#204) (Friday, 22 July)
[whatwg/fetch] Make it clearer that cache mode "default" follows normal logic (#340) (Friday, 22 July)
Re: [slightlyoff/ServiceWorker] Run the latest Bikeshed (#933) (Friday, 22 July)
Re: [w3c/push-api] typedef object JSON; is incorrect (#204) (Friday, 22 July)
Re: [whatwg/fetch] URLs with username/password (#26) (Friday, 22 July)
Re: [whatwg/fetch] URLs with username/password (#26) (Friday, 22 July)
Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Friday, 22 July)
Re: [whatwg/fetch] Listing headers safe only for certain values is a bad idea (#313) (Friday, 22 July)
Re: [whatwg/fetch] Some link corrections (#333) (Friday, 22 July)
Re: [whatwg/fetch] Some link corrections (#333) (Friday, 22 July)
Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Friday, 22 July)
Re: [whatwg/fetch] response.ok = false for opaque responses may be misleading (#299) (Friday, 22 July)
Re: [whatwg/fetch] Give user entered data: URI documents the HTTPS state 'modern' (#243) (Friday, 22 July)
Re: [whatwg/fetch] Give user entered data: URI documents the HTTPS state 'modern' (#243) (Friday, 22 July)
Re: [whatwg/fetch] need setHeaderFunction( request => newHeaders ) function called before request sent (#156) (Friday, 22 July)
Re: [whatwg/fetch] need setHeaderFunction( request => newHeaders ) function called before request sent (#156) (Friday, 22 July)
Re: [whatwg/fetch] Remove about:unicorn (#147) (Friday, 22 July)
Re: [whatwg/fetch] Client being null for client requests doesn't work with the fetch registry (#81) (Friday, 22 July)
Re: [whatwg/xhr] " Returns the response's body." (#80) (Friday, 22 July)
Re: [whatwg/fetch] Cache mode: fromCache (#40) (Friday, 22 July)
[whatwg/fetch] Reconsider treatment of non-GET for non-HTTP(S) schemes (#339) (Friday, 22 July)
Re: [w3c/webcomponents] Shadow DOM, <style>, and document.styleSheets (#56) (Friday, 22 July)
Re: [w3c/webcomponents] Shadow DOM, <style>, and document.styleSheets (#56) (Friday, 22 July)
Re: [w3c/push-api] typedef object JSON; is incorrect (#204) (Friday, 22 July)
Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Friday, 22 July)
Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Friday, 22 July)
Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Friday, 22 July)
Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Friday, 22 July)
Re: [w3c/webcomponents] Shadow DOM, <style>, and document.styleSheets (#56) (Friday, 22 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Friday, 22 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#277) (Friday, 22 July)
Re: [whatwg/dom] Upstream retargeting algorithm (#276) (Friday, 22 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Friday, 22 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Friday, 22 July)
Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) (Thursday, 21 July)
Re: [whatwg/fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) (Thursday, 21 July)
Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) (Thursday, 21 July)
Re: [w3c/webcomponents] Shadow DOM, <style>, and document.styleSheets (#56) (Thursday, 21 July)
Re: [whatwg/fetch] Make it more clear that cache mode "default" does respect Cache-Control headers and such (#336) (Thursday, 21 July)
Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) (Thursday, 21 July)
Re: [w3c/permissions] Guidance on where to put permission related stuff in other specs (#110) (Thursday, 21 July)
[whatwg/fetch] Delay network errors to prevent port scanning (#338) (Thursday, 21 July)
Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) (Thursday, 21 July)
Re: [w3c/webcomponents] [Custom]: Need adopted callback (bugzilla: 24577) (#210) (Thursday, 21 July)
Re: [w3c/webcomponents] [Custom]: Need adopted callback (bugzilla: 24577) (#210) (Thursday, 21 July)
Re: [w3c/webcomponents] Declarative syntax for custom elements (#136) (Thursday, 21 July)
Re: [w3c/webcomponents] Should parser extensibility be a design goal? (#113) (Thursday, 21 July)
[whatwg/fetch] Block text/csv for requests whose type is "script"? (#337) (Thursday, 21 July)
Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Thursday, 21 July)
Re: [whatwg/dom] Set the stage for new custom element adoption semantics (#279) (Thursday, 21 July)
Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) (Thursday, 21 July)
Re: [w3c/webcomponents] <iframe> and Window's named properties (#145) (Thursday, 21 July)
Re: [w3c/permissions] Add persistent storage (#39) (Thursday, 21 July)
Re: [w3c/webcomponents] Shadow DOM, <style>, and document.styleSheets (#56) (Thursday, 21 July)
Re: [w3c/webcomponents] Shadow DOM, <style>, and document.styleSheets (#56) (Thursday, 21 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Thursday, 21 July)
Re: [whatwg/fetch] Make it more clear that cache mode "default" does respect Cache-Control headers and such (#336) (Thursday, 21 July)
Re: [whatwg/fetch] Make it more clear that cache mode "default" does respect Cache-Control headers and such (#336) (Thursday, 21 July)
Re: [w3c/permissions] Add persistent storage (#39) (Wednesday, 20 July)
Re: [w3c/permissions] Add "fullscreen" (#26) (Wednesday, 20 July)
Re: [w3c/permissions] Add "fullscreen" (#26) (Wednesday, 20 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Wednesday, 20 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Wednesday, 20 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Wednesday, 20 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Wednesday, 20 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Wednesday, 20 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Wednesday, 20 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Wednesday, 20 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Wednesday, 20 July)
Re: [whatwg/fetch] Proposal: Support GET bodies (#83) (Wednesday, 20 July)
Re: [whatwg/fetch] Proposal: Support GET bodies (#83) (Wednesday, 20 July)
Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) (Wednesday, 20 July)
Re: [w3c/permissions] Add security considerations section (#49) (Wednesday, 20 July)
Re: [whatwg/fullscreen] Drop the iframe ancestor check? (#45) (Wednesday, 20 July)
[whatwg/fetch] Make it more clear that cache mode "default" does respect Cache-Control headers and such (#336) (Wednesday, 20 July)
Re: [whatwg/fetch] Call out to Referrer Policy to set policy on redirect (#335) (Tuesday, 19 July)
Re: [whatwg/fetch] Call out to Referrer Policy to set policy on redirect (#335) (Tuesday, 19 July)
Re: [whatwg/fetch] HTTP-redirect fetch should invoke "Set request's referrer policy on redirect" (#334) (Tuesday, 19 July)
Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) (Tuesday, 19 July)
Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) (Tuesday, 19 July)
Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) (Tuesday, 19 July)
Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) (Tuesday, 19 July)
Re: [whatwg/dom] Define dataset as a mixin for HTMLElement and SVGElement (#280) (Tuesday, 19 July)
Re: [whatwg/fetch] HTTP-redirect fetch should invoke "Set request's referrer policy on redirect" (#334) (Tuesday, 19 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Tuesday, 19 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Tuesday, 19 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Tuesday, 19 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Tuesday, 19 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Tuesday, 19 July)
Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) (Tuesday, 19 July)
Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) (Tuesday, 19 July)
Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) (Tuesday, 19 July)
Re: [whatwg/fullscreen] Drop the iframe ancestor check? (#45) (Tuesday, 19 July)
Re: [whatwg/fullscreen] Drop the iframe ancestor check? (#45) (Tuesday, 19 July)
Re: [whatwg/fetch] Possible typo in header value definition (#332) (Tuesday, 19 July)
Re: [whatwg/fetch] RFC: a mechanism to bypass CORS preflight (#210) (Tuesday, 19 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Tuesday, 19 July)
Re: [whatwg/dom] Define dataset as a mixin for HTMLElement and SVGElement (#280) (Tuesday, 19 July)
Re: [w3c/FileAPI] Re-add readAsBinaryString() (#44) (Monday, 18 July)
Re: [w3c/FileAPI] Re-add readAsBinaryString() (#44) (Monday, 18 July)
Re: [w3c/FileAPI] Re-add readAsBinaryString() (#44) (Monday, 18 July)
Re: [whatwg/dom] Set the stage for preventing double custom element constructor calls (#282) (Monday, 18 July)
Re: [whatwg/dom] Set the stage for preventing double custom element constructor calls (#282) (Monday, 18 July)
Re: [whatwg/fetch] Content-Length on HEAD (#135) (Monday, 18 July)
Re: [whatwg/fetch] Content-Length on HEAD (#135) (Monday, 18 July)
Re: [whatwg/fetch] Content-Length on HEAD (#135) (Monday, 18 July)
Re: [whatwg/fetch] fetch filter the symbols (#331) (Monday, 18 July)
Re: [slightlyoff/ServiceWorker] Remove monkeypatches in the event disptaching behaviors (72315b9) (Monday, 18 July)
Re: [whatwg/dom] Set the stage for preventing double custom element constructor calls (#282) (Monday, 18 July)
Re: [whatwg/dom] Set the stage for preventing double custom element constructor calls (#282) (Monday, 18 July)
Re: [whatwg/dom] Set the stage for preventing double custom element constructor calls (#282) (Monday, 18 July)
Re: [whatwg/dom] Set the stage for preventing double custom element constructor calls (#282) (Monday, 18 July)
Re: [slightlyoff/ServiceWorker] Should Cache-Control: private be respected? (#926) (Monday, 18 July)
Re: [whatwg/dom] Define dataset as a mixin for HTMLElement and SVGElement (#280) (Monday, 18 July)
Re: [whatwg/xhr] Should we be pinning Blob URIs on fetches? (#79) (Monday, 18 July)
Re: [whatwg/xhr] failed to load data in sapui5 RowRepaeater (#78) (Monday, 18 July)
Re: [whatwg/url] Which reality should location.pathname setter match? (#133) (Monday, 18 July)
Re: [whatwg/url] Trailing dot and origin compuation (#132) (Monday, 18 July)
Re: [slightlyoff/ServiceWorker] Remove monkeypatches in the event disptaching behaviors (72315b9) (Monday, 18 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Monday, 18 July)
Re: [whatwg/url] Which reality should location.pathname setter match? (#133) (Monday, 18 July)
Re: [w3c/FileAPI] Re-add readAsBinaryString() (#44) (Monday, 18 July)
Re: [heycam/webidl] Make globals and things they inherit from have immutable prototypes (#133) (Monday, 18 July)
Re: [whatwg/fullscreen] Should we apply !important to "object-fit: contain"? (#44) (Monday, 18 July)
Re: [whatwg/fullscreen] Should we apply !important to "object-fit: contain"? (#44) (Monday, 18 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Monday, 18 July)
Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Monday, 18 July)
Re: [slightlyoff/ServiceWorker] DOMParser within ServiceWorkers (#846) (Saturday, 9 July)
Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Friday, 8 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Friday, 8 July)
Re: [whatwg/xhr] ionic app not statrting (#77) (Friday, 8 July)
Re: [whatwg/fetch] How response bodies get from a service worker to the main page is not very clear (#330) (Friday, 8 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Friday, 8 July)
Re: [whatwg/fetch] How response bodies get from a service worker to the main page is not very clear (#330) (Friday, 8 July)
Re: [whatwg/dom] Do not throw for query() and queryAll() (#39) (Thursday, 7 July)
Re: [whatwg/dom] "In a document" confusion (#238) (Thursday, 7 July)
Re: [whatwg/dom] Do not throw for query() and queryAll() (#39) (Thursday, 7 July)
Re: [whatwg/dom] Rename "in a (shadow-including) document" (#275) (Thursday, 7 July)
Re: [whatwg/dom] Rename "in a (shadow-including) document" (#275) (Thursday, 7 July)
Re: [whatwg/dom] Rename "in a (shadow-including) document" (#275) (Thursday, 7 July)
Re: [whatwg/xhr] 😠 (#76) (Thursday, 7 July)
Re: [w3c/manifest] Ability to claim web app (#476) (Thursday, 7 July)
Re: [w3c/manifest] Ability to claim web app (#476) (Thursday, 7 July)
Re: [w3c/push-api] PushSubscriptionOptions ArrayBuffer lifetime issues (#198) (Wednesday, 6 July)
[slightlyoff/ServiceWorker] Stop monkeypatching event dispatch (#924) (Wednesday, 6 July)
Re: [w3c/manifest] Ability to claim web app (#476) (Wednesday, 6 July)
Re: [w3c/manifest] Ability to claim web app (#476) (Wednesday, 6 July)
Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Wednesday, 6 July)
Re: [w3c/push-api] PushSubscriptionOptions ArrayBuffer lifetime issues (#198) (Wednesday, 6 July)
Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Wednesday, 6 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#277) (Tuesday, 5 July)
[whatwg/dom] Add relatedTarget to event dispatch (#277) (Tuesday, 5 July)
[whatwg/dom] Upstream retargeting algorithm (#276) (Tuesday, 5 July)
Re: [whatwg/dom] Point out that initial about:blank also results in quirks mode (#268) (Tuesday, 5 July)
Re: [whatwg/dom] Point out that initial about:blank also results in quirks mode (#268) (Tuesday, 5 July)
Re: [whatwg/dom] Note that about:blank also results in quirks mode (#272) (Tuesday, 5 July)
Re: [whatwg/url] Figure out what to do with youtube IDNA issues (#131) (Monday, 4 July)
Re: [whatwg/url] Figure out what to do with youtube IDNA issues (#131) (Monday, 4 July)
Re: [whatwg/url] Figure out what to do with youtube IDNA issues (#131) (Monday, 4 July)
[whatwg/fullscreen] Use new "allowed to use" algorithm once introduced (#41) (Monday, 4 July)
Re: [whatwg/dom] "In a document" confusion (#238) (Monday, 4 July)
Re: [whatwg/dom] Rename "in a (shadow-including) document" (#275) (Monday, 4 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Monday, 4 July)
Re: [whatwg/dom] "In a document" confusion (#238) (Monday, 4 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Monday, 4 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Monday, 4 July)
Re: [whatwg/xhr] "representing the same bytes" (#75) (Monday, 4 July)
Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Sunday, 3 July)
Re: [whatwg/url] Basic URL Parse point 1 (#130) (Friday, 1 July)
Re: [whatwg/dom] "In a document" confusion (#238) (Friday, 1 July)
[whatwg/dom] Rename "in a (shadow-including) document" (#275) (Friday, 1 July)
Re: [whatwg/url] Basic URL Parse point 1 (#130) (Friday, 1 July)
Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Friday, 1 July)
Re: [whatwg/xhr] Property to disable following redirects (#74) (Friday, 1 July)
Re: [whatwg/xhr] Property to disable following redirects (#74) (Friday, 1 July)
Re: [whatwg/xhr] Property to disable following redirects (#74) (Friday, 1 July)

Anthony Ramine

Re: [w3c/IndexedDB] Asynchronously executing a request should queue a task to fire events (#83) (Saturday, 23 July)
[w3c/IndexedDB] Asynchronously executing a request should queue a task to fire events (#83) (Thursday, 21 July)
Re: [w3c/DOM-Parsing] Step 1 of createContextualFragment is not enough (#17) (Monday, 18 July)
Re: [w3c/DOM-Parsing] Step 1 of createContextualFragment is not enough (#17) (Monday, 18 July)
Re: [w3c/DOM-Parsing] Step 1 of createContextualFragment is not enough (#17) (Monday, 18 July)
Re: [w3c/IndexedDB] Naming for "v2" ? (#82) (Saturday, 16 July)
Re: [w3c/IndexedDB] Specify IDBOpenDBRequest processing as a queue? (#79) (Friday, 15 July)
Re: [w3c/IndexedDB] Specify IDBOpenDBRequest processing as a queue? (#79) (Wednesday, 13 July)
[w3c/IndexedDB] The steps for opening a database are racy (#81) (Tuesday, 12 July)
[w3c/DOM-Parsing] Step 1 of createContextualFragment is not enough (#17) (Monday, 11 July)
[w3c/IndexedDB] Make IDBRequest.error nullable (#80) (Friday, 8 July)

apet-as

Re: [whatwg/fetch] Add option to automatically abort response stream if the data stopped arriving for longer than a specified time (#180) (Sunday, 17 July)

ArkadiuszMichalski

Re: [w3c/DOM-Parsing] Step 1 of createContextualFragment is not enough (#17) (Monday, 18 July)
Re: [w3c/DOM-Parsing] Step 1 of createContextualFragment is not enough (#17) (Monday, 18 July)
Re: [w3c/DOM-Parsing] Step 1 of createContextualFragment is not enough (#17) (Monday, 18 July)

Arthur Stolyar

Re: [w3c/manifest] Ability to claim web app (#476) (Thursday, 7 July)
Re: [w3c/manifest] Ability to claim web app (#476) (Thursday, 7 July)

Bede Overend

Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 6 July)

beidson

Re: [slightlyoff/ServiceWorker] spec exactly how to order non-window Client objects (#887) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] spec exactly how to order non-window Client objects (#887) (Thursday, 28 July)
Re: [w3c/IndexedDB] Naming for "v2" ? (#82) (Saturday, 16 July)
Re: [w3c/IndexedDB] Naming for "v2" ? (#82) (Friday, 15 July)

Ben

Re: [w3c/manifest] Adding the webapp's badge to the manifest (#480) (Monday, 25 July)

Ben Francis

Re: [w3c/manifest] Ability to claim web app (#476) (Thursday, 7 July)

Ben Kelly

Re: [slightlyoff/ServiceWorker] should async waitUntil() work in .then() handler of promise passed to previous waitUntil()? (#935) (Thursday, 28 July)
[slightlyoff/ServiceWorker] Should waitUntil() fast fail if a single extension promise rejects? (#936) (Wednesday, 27 July)
[slightlyoff/ServiceWorker] should async waitUntil() work in .then() handler of promise passed to previous waitUntil()? (#935) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) (Monday, 25 July)
Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Monday, 25 July)
Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Monday, 25 July)
Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Friday, 22 July)
Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Friday, 22 July)
Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Friday, 22 July)
Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Friday, 22 July)
Re: [slightlyoff/ServiceWorker] Create F2F agenda - 28-29 July 2016 (#932) (Friday, 22 July)
Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Friday, 22 July)
Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Friday, 22 July)
Re: [whatwg/fetch] Make it more clear that cache mode "default" does respect Cache-Control headers and such (#336) (Thursday, 21 July)
Re: [slightlyoff/ServiceWorker] More clarity around waiting for an active worker to finish (#916) (Wednesday, 20 July)
Re: [slightlyoff/ServiceWorker] Should Cache-Control: private be respected? (#926) (Monday, 18 July)
Re: [slightlyoff/ServiceWorker] openWindow with a WebApp manifests (#720) (Thursday, 14 July)
Re: [slightlyoff/ServiceWorker] Should Cache-Control: private be respected? (#926) (Tuesday, 12 July)
Re: [whatwg/fetch] referrer same-origin constraint is a footgun for people trying to "copy" a Request (#245) (Saturday, 9 July)
Re: [slightlyoff/ServiceWorker] Consider relying on eTags (or other headers) for service worker dependencies to check for updates (#839) (Saturday, 9 July)
Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Friday, 8 July)
Re: [whatwg/fetch] How response bodies get from a service worker to the main page is not very clear (#330) (Friday, 8 July)
Re: [whatwg/streams] IsFiniteNonNegativeNumber() could be used in more places (#475) (Tuesday, 5 July)
[whatwg/streams] IsFiniteNonNegativeNumber() could be used in more places (#475) (Tuesday, 5 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Tuesday, 5 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Tuesday, 5 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Tuesday, 5 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Tuesday, 5 July)
Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Friday, 1 July)

Ben Last

[w3c/push-api] Define behaviour of pushsubscriptionchange in the event of an error (#205) (Friday, 22 July)

Benjamin C. Wiley Sittler

Re: [slightlyoff/ServiceWorker] Add cookie accessor/setter methods? (#707) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] Add cookie accessor/setter methods? (#707) (Wednesday, 27 July)

bmaurer

Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Sunday, 31 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Monday, 4 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Monday, 4 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Sunday, 3 July)

Boris Zbarsky

Re: [whatwg/dom] iterable declaration on NodeList is invalid (#284) (Friday, 29 July)
Re: [whatwg/dom] iterable declaration on NodeList is invalid (#284) (Friday, 29 July)
[whatwg/dom] iterable declaration on NodeList is invalid (#284) (Friday, 29 July)
[w3c/DOM-Parsing] How should createContextualFragment interact with `<script>` inside `<template>`? (#19) (Friday, 22 July)
Re: [heycam/webidl] Should probably spec a hasInstance for named constructors (#134) (Tuesday, 19 July)
Re: [heycam/webidl] Should probably spec a hasInstance for named constructors (#134) (Tuesday, 19 July)
[heycam/webidl] Should probably spec a hasInstance for named constructors (#134) (Tuesday, 19 July)
Re: [heycam/webidl] Add namespaces (#121) (Friday, 15 July)
Re: [heycam/webidl] Add namespaces (#121) (Friday, 15 July)
Re: [heycam/webidl] Add namespaces (#121) (Friday, 15 July)
Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Friday, 8 July)
Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Thursday, 7 July)
Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Thursday, 7 July)

Brandon Jones

Re: [w3c/gamepad] Added GamepadPose (#25) (Saturday, 30 July)
Re: [w3c/gamepad] Added GamepadPose and GamepadCapabilities (#25) (Saturday, 30 July)
Re: [w3c/gamepad] Added GamepadPose and GamepadCapabilities (#25) (Thursday, 28 July)
Re: [w3c/gamepad] Added GamepadPose and GamepadCapabilities (#25) (Wednesday, 20 July)
Re: [w3c/gamepad] Added GamepadPose and GamepadCapabilities (#25) (Monday, 18 July)
Re: [w3c/gamepad] Added touched property to GamepadButton (#26) (Saturday, 9 July)
[w3c/gamepad] Determine how Multi-touch surfaces should be handled. (#27) (Saturday, 9 July)
Re: [w3c/gamepad] Added touched property to GamepadButton (#26) (Friday, 8 July)
Re: [w3c/gamepad] Added touched property to GamepadButton (#26) (Friday, 8 July)
Re: [w3c/gamepad] Added touched property to GamepadButton (#26) (Friday, 8 July)
Re: [w3c/gamepad] Added GamepadPose and GamepadCapabilities (#25) (Friday, 8 July)
Re: [w3c/gamepad] Added GamepadPose and GamepadCapabilities (#25) (Thursday, 7 July)
Re: [w3c/gamepad] Added touched property to GamepadButton (#26) (Thursday, 7 July)

Cameron McCormack

Re: [heycam/webidl] Use OrdinaryGetOwnProperty. (#131) (Tuesday, 19 July)
Re: [heycam/webidl] Use OrdinaryGetOwnProperty. (#131) (Tuesday, 19 July)

chaals

Re: [w3c/charter-html] define roles for the entire set of stakeholders (#19) (Friday, 29 July)
Re: [w3c/charter-html] Innovation (#9) (Friday, 29 July)
Re: [w3c/charter-html] Clarify the problem space (#18) (Friday, 29 July)
Re: [w3c/charter-html] unclear about wg leadership bullet point (#11) (Friday, 29 July)
Re: [w3c/charter-html] Innovation (#9) (Friday, 29 July)
Re: [w3c/charter-html] Bugs get property triaged, prioritized, and addressed (#2) (Friday, 29 July)
Re: [w3c/charter-html] Bugs get property triaged, prioritized, and addressed (#2) (Friday, 29 July)
Re: [w3c/charter-html] Groups split (#14) (Friday, 29 July)
Re: [w3c/charter-html] Groups split (#14) (Friday, 29 July)
Re: [w3c/charter-html] Embrace modern spec dev practices (#7) (Friday, 29 July)
Re: [w3c/charter-html] Embrace modern spec dev practices (#7) (Friday, 29 July)
Re: [w3c/charter-html] Test based standardization (#3) (Friday, 29 July)
Re: [w3c/charter-html] Test based standardization (#3) (Friday, 29 July)
Re: [w3c/charter-html] Indicate relationship with the WHATWG (#112) (Friday, 29 July)
Re: [w3c/charter-html] Indicate relationship with the WHATWG (#112) (Friday, 29 July)
Re: [w3c/charter-html] Work on HTML (#130) (Friday, 29 July)
Re: [w3c/charter-html] Styling for readability (#115) (Friday, 29 July)
Re: [w3c/charter-html] Styling for readability (#115) (Friday, 29 July)
Re: [w3c/WebPlatformWG] Add items that interest me for the editing tf meeting. (#59) (Friday, 29 July)
Re: [w3c/WebPlatformWG] Update 16-07-28-29SW.md (#54) (Monday, 25 July)
Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 19 July)
Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 19 July)
Re: [w3c/WebPlatformWG] grisha_pullRequest_AddtlAttendees (#48) (Wednesday, 13 July)
[w3c/WebPlatformWG] Publish First Public Working Draft for HTML 5.2? (#43) (Tuesday, 5 July)

chengxuwang

[whatwg/xhr] good (#81) (Friday, 29 July)

Chong Zhang

Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Thursday, 28 July)
Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Wednesday, 27 July)
[w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Wednesday, 27 July)
[w3c/editing] inputType for Menu Bar>Edit>Delete (no obvious direction) (#130) (Wednesday, 20 July)
[w3c/WebPlatformWG] Add Chong Zhang to "will attend" list (#49) (Friday, 15 July)

Chris Dumez

Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Friday, 29 July)
Re: [whatwg/dom] Figure out what to do with XMLDocument (#278) (Friday, 29 July)
Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Friday, 29 July)
Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Friday, 29 July)
Re: [whatwg/dom] Make Attr a Node again (#102) (Friday, 29 July)
Re: [whatwg/dom] Make Attr a Node again (#102) (Thursday, 28 July)

Chris Rebert

Re: [whatwg/dom] cancelBubble legacy property (#211) (Thursday, 21 July)
[w3c/uievents-key] ContextMenu key's description mentions defunct "OS" key (#28) (Wednesday, 13 July)

chris van wiemeersch

[w3c/gamepad] Add a Project Description and Project URL (#29) (Saturday, 30 July)
Re: [w3c/gamepad] Determine how Multi-touch surfaces should be handled. (#27) (Saturday, 30 July)
Re: [w3c/gamepad] Added GamepadPose and GamepadCapabilities (#25) (Saturday, 30 July)
Re: [w3c/gamepad] Added GamepadPose and GamepadCapabilities (#25) (Saturday, 30 July)
Re: [w3c/gamepad] Added GamepadPose and GamepadCapabilities (#25) (Wednesday, 20 July)
[w3c/permissions] Add 'webvr' to "Permission Registry" enum (#108) (Saturday, 16 July)
Re: [w3c/gamepad] Added touched property to GamepadButton (#26) (Friday, 8 July)
Re: [w3c/gamepad] Added touched property to GamepadButton (#26) (Friday, 8 July)
Re: [w3c/gamepad] Added GamepadPose and GamepadCapabilities (#25) (Friday, 8 July)

Christopher Rodriguez

Re: [w3c/gamepad] Added GamepadPose and GamepadCapabilities (#25) (Monday, 25 July)
Re: [w3c/gamepad] Determine how Multi-touch surfaces should be handled. (#27) (Sunday, 24 July)

countrygirl351

[whatwg/xhr] 😠 (#76) (Thursday, 7 July)

Cristian Sima

Re: [whatwg/fetch] Aborting a fetch (#27) (Saturday, 16 July)

Cyril Auburtin

[w3c/selection-api] Triple-click selection bounds (#70) (Thursday, 21 July)

Dan Ostrowski

Re: [whatwg/fetch] Add option to reject the fetch promise automatically after a certain time elapsed (with no API for arbitrary aborts) (#179) (Wednesday, 20 July)

Daniel Appelquist

Re: [w3ctag/spec-reviews] TAG Review of HTML 5.1 (#119) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] WebUSB (#108) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] ARIA (#107) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] TV Control Feedback (#111) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] TV Control Feedback (#111) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] TV Control Feedback (#111) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Review secure contexts (#124) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Review secure contexts (#124) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Review secure contexts (#124) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Progressive Web Apps (#123) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Streams General issue (#92) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Bluetooth API Security Model (#90) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Indexed DB getAll(), openKeyCursor() and objectStoreNames (#84) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Indexed DB getAll(), openKeyCursor() and objectStoreNames (#84) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Do we have feedback on Web Payment group's response to security & privacy questionnaire? (#125) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Write up the Secure Stop issue for ddorwin (#73) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Potential for coordination about task scheduling (#72) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Review WAPA (Accessibility) proposal (#63) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Browser Fingerprinting Document (#38) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] WebRTC (#14) (Thursday, 28 July)
Re: [w3ctag/spec-reviews] Performance Observer Review (formerly Navigation Timing 2 concepts) (#18) (Wednesday, 20 July)
Re: [w3ctag/spec-reviews] Performance Observer Review (formerly Navigation Timing 2 concepts) (#18) (Wednesday, 20 July)
Re: [w3ctag/spec-reviews] Indexed DB getAll(), openKeyCursor() and objectStoreNames (#84) (Wednesday, 20 July)
Re: [w3ctag/spec-reviews] Indexed DB getAll(), openKeyCursor() and objectStoreNames (#84) (Wednesday, 20 July)
Re: [w3ctag/spec-reviews] ARIA (#107) (Wednesday, 20 July)
Re: [w3ctag/spec-reviews] ARIA (#107) (Wednesday, 20 July)
Re: [w3ctag/spec-reviews] Privacy Mode (#101) (Thursday, 7 July)
[w3ctag/spec-reviews] Do we have feedback on Web Payment group's response to security & privacy questionnaire? (#125) (Thursday, 7 July)
Re: [w3ctag/spec-reviews] Review secure contexts (#124) (Wednesday, 6 July)
[w3ctag/spec-reviews] Review secure contexts (#124) (Wednesday, 6 July)
Re: [w3ctag/spec-reviews] Review Web Annotations specs (#93) (Wednesday, 6 July)
Re: [w3ctag/spec-reviews] Review Web Annotations specs (#93) (Wednesday, 6 July)
Re: [w3ctag/spec-reviews] Accelerated Mobile Pages (AMP) (#122) (Wednesday, 6 July)
Re: [w3ctag/spec-reviews] Accelerated Mobile Pages (AMP) (#122) (Wednesday, 6 July)
Re: [w3ctag/spec-reviews] Accelerated Mobile Pages (AMP) (#122) (Wednesday, 6 July)
Re: [w3ctag/spec-reviews] Progressive Web Apps (#123) (Wednesday, 6 July)
Re: [w3ctag/spec-reviews] Progressive Web Apps (#123) (Wednesday, 6 July)
Re: [w3ctag/spec-reviews] Progressive Web Apps (#123) (Wednesday, 6 July)

Dave Tapuska

[w3c/WebPlatformWG] Add items that interest me for the editing tf meeting. (#59) (Friday, 29 July)
[w3c/WebPlatformWG] Update 16-07-29-Editing.md (#50) (Monday, 18 July)

David Baron

Re: [w3ctag/spec-reviews] Review of WakeLock API and suitability for overall platform requested by 31 August 2016 (#126) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Task Scheduling (#72) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] requestIdleCallback (#70) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Browser Fingerprinting Document (#38) (Saturday, 30 July)

David Burns

[whatwg/url] Url definition should define the fragment as optional (#134) (Tuesday, 26 July)

David Scales

[slightlyoff/ServiceWorker] Documentation mistake (#927) (Wednesday, 13 July)

David Steinkopff

Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 13 July)

Domenic Denicola

[w3c/gamepad] IDL array[]s no longer exist (#28) (Wednesday, 27 July)
Re: [w3c/gamepad] Added GamepadPose and GamepadCapabilities (#25) (Wednesday, 27 July)
Re: [whatwg/url] Let webkitURL be an alias of the URL constructor (#135) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] html no longer defines "referrer source" (#834) (Wednesday, 27 July)
Re: [w3c/push-api] typedef object JSON; is incorrect (#204) (Friday, 22 July)
Re: [w3c/push-api] typedef object JSON; is incorrect (#204) (Friday, 22 July)
Re: [slightlyoff/ServiceWorker] Run the latest Bikeshed (#933) (Friday, 22 July)
Re: [w3c/push-api] typedef object JSON; is incorrect (#204) (Thursday, 21 July)
[w3c/push-api] typedef object JSON; is incorrect (#204) (Thursday, 21 July)
Re: [w3c/webcomponents] [idea] Allowing custom element registrations on per-shadow-root basis. (#488) (Thursday, 21 July)
Re: [w3c/webcomponents] [idea] Allowing custom element registrations on per-shadow-root basis. (#488) (Thursday, 21 July)
Re: [w3c/webcomponents] [idea] Ability to define Custom Element attributes (and optionally enable getters/setters for those attributes). (#517) (Thursday, 21 July)
Re: [w3c/webcomponents] [idea] Ability to define Custom Element attributes (and optionally enable getters/setters for those attributes). (#517) (Thursday, 21 July)
Re: [w3c/webcomponents] [idea] Allow HTML Element attributes to accept any type of value, not just strings. (#519) (Thursday, 21 July)
Re: [w3c/webcomponents] [idea] Allow HTML Element attributes to accept any type of value, not just strings. (#519) (Thursday, 21 July)
Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) (Thursday, 21 July)
Re: [w3c/webcomponents] Should parser extensibility be a design goal? (#113) (Thursday, 21 July)
Re: [w3c/webcomponents] <iframe> and Window's named properties (#145) (Thursday, 21 July)
Re: [w3c/webcomponents] Shadow DOM, <style>, and document.styleSheets (#56) (Thursday, 21 July)
Re: [w3c/webcomponents] <iframe> and Window's named properties (#145) (Thursday, 21 July)
Re: [heycam/webidl] Indicate that thing needs user action to work (#137) (Thursday, 21 July)
Re: [w3ctag/spec-reviews] Indexed DB getAll(), openKeyCursor() and objectStoreNames (#84) (Wednesday, 20 July)
[heycam/webidl] State that by default all objects are created in the relevant realm of `this` (#135) (Tuesday, 19 July)
Re: [heycam/webidl] Should probably spec a hasInstance for named constructors (#134) (Tuesday, 19 July)
Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) (Tuesday, 19 July)
Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) (Tuesday, 19 July)
Re: [whatwg/dom] Define dataset as a mixin for HTMLElement and SVGElement (#280) (Tuesday, 19 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Tuesday, 19 July)
Re: [whatwg/streams] Broadcast ReadableStream (#481) (Monday, 18 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Monday, 18 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Monday, 18 July)
Re: [w3c/webcomponents] The custom element state when constructor thrown (#533) (Monday, 18 July)
Re: [whatwg/dom] Set the stage for preventing double custom element constructor calls (#282) (Monday, 18 July)
Re: [whatwg/dom] Set the stage for preventing double custom element constructor calls (#282) (Monday, 18 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Monday, 18 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Monday, 18 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Monday, 18 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Monday, 18 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Monday, 18 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Monday, 18 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Monday, 18 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Monday, 18 July)
Re: [whatwg/streams] Add URL.createObjectURL(stream) support (#480) (Sunday, 17 July)
Re: [heycam/webidl] Add namespaces (#121) (Friday, 15 July)
Re: [heycam/webidl] Add namespaces (#121) (Friday, 15 July)
Re: [w3c/webcomponents] Allow or prohibit observedAttributes to observe 'style' attribute? (#521) (Friday, 15 July)
Re: [w3c/webcomponents] Allow or prohibit observedAttributes to observe 'style' attribute? (#521) (Friday, 15 July)
[whatwg/fetch] Some link corrections (#333) (Friday, 15 July)
Re: [whatwg/streams] Stack details are omitted in output of tap-spec (#478) (Thursday, 14 July)
Re: [w3c/FileAPI] Streams is hot, FileReader.readAs____ is not (#40) (Thursday, 14 July)
Re: [heycam/webidl] Make globals and things they inherit from have immutable prototypes (#133) (Thursday, 14 July)
Re: [w3c/webcomponents] The custom element state when constructor thrown (#533) (Thursday, 14 July)
[whatwg/dom] Set the stage for preventing double custom element constructor calls (#282) (Thursday, 14 July)
Re: [w3c/webcomponents] The custom element state when constructor thrown (#533) (Thursday, 14 July)
[heycam/webidl] Make globals and things they inherit from have immutable prototypes (#133) (Thursday, 14 July)
Re: [heycam/webidl] Use OrdinaryGetOwnProperty. (#131) (Thursday, 14 July)
Re: [whatwg/dom] Set the stage for new custom element adoption semantics (#279) (Thursday, 14 July)
Re: [whatwg/dom] Set the stage for new custom element adoption semantics (#279) (Thursday, 14 July)
Re: [whatwg/streams] Use e => t.error(e) than t.error for catching exceptions in a then-callback (#479) (Thursday, 14 July)
Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Wednesday, 13 July)
Re: [whatwg/dom] Set the stage for new custom element adoption semantics (#279) (Wednesday, 13 July)
Re: [whatwg/dom] Set the stage for new custom element adoption semantics (#279) (Wednesday, 13 July)
Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Wednesday, 13 July)
Re: [w3c/webcomponents] The custom element state when constructor thrown (#533) (Wednesday, 13 July)
Re: [w3c/webcomponents] The custom element state when constructor thrown (#533) (Tuesday, 12 July)
Re: [whatwg/fetch] How response bodies get from a service worker to the main page is not very clear (#330) (Tuesday, 12 July)
Re: [whatwg/streams] [WritableStream] Locking semantics (#474) (Tuesday, 12 July)
Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Tuesday, 12 July)
Re: [w3c/webcomponents] Allow or prohibit observedAttributes to observe 'style' attribute? (#521) (Tuesday, 12 July)
Re: [w3c/webcomponents] Invalid constructor when invoking the constructor directly (#531) (Monday, 11 July)
Re: [slightlyoff/ServiceWorker] Eliminate usage of entry and incumbent settings objects (#922) (Monday, 11 July)
[slightlyoff/ServiceWorker] Run the latest Bikeshed (#925) (Friday, 8 July)
Re: [whatwg/fetch] How response bodies get from a service worker to the main page is not very clear (#330) (Friday, 8 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Friday, 8 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Friday, 8 July)
Re: [whatwg/streams] IsFiniteNonNegativeNumber() could be used in more places (#475) (Thursday, 7 July)
Re: [whatwg/streams] Tidy up range checking (#477) (Thursday, 7 July)
[w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Thursday, 7 July)
[whatwg/fetch] How response bodies get from a service worker to the main page is not very clear (#330) (Thursday, 7 July)
Re: [slightlyoff/ServiceWorker] Update for changes to HTML's script-fetching algorithms (#923) (Thursday, 7 July)
Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Wednesday, 6 July)
Re: [whatwg/dom] Set the stage for new custom element adoption semantics (#279) (Wednesday, 6 July)
[whatwg/dom] Set the stage for new custom element adoption semantics (#279) (Wednesday, 6 July)
Re: [whatwg/streams] Should write() always error the stream when it rejects the promise it returned? (#476) (Wednesday, 6 July)
Re: [whatwg/streams] [WritableStream] Locking semantics (#474) (Wednesday, 6 July)
[whatwg/streams] Tidy up range checking (#477) (Wednesday, 6 July)
[whatwg/dom] Figure out what to do with XMLDocument (#278) (Wednesday, 6 July)
Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 6 July)
Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Wednesday, 6 July)
Re: [whatwg/streams] IsFiniteNonNegativeNumber() could be used in more places (#475) (Tuesday, 5 July)
Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) (Saturday, 2 July)
[whatwg/xhr] "representing the same bytes" (#75) (Saturday, 2 July)
Re: [w3c/webcomponents] Should innerHTML propagate custom element constructor exceptions? (#525) (Saturday, 2 July)
[slightlyoff/ServiceWorker] Update for changes to HTML's script-fetching algorithms (#923) (Friday, 1 July)
Re: [whatwg/dom] "In a document" confusion (#238) (Friday, 1 July)
Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Friday, 1 July)
Re: [whatwg/dom] "In a document" confusion (#238) (Friday, 1 July)
Re: [slightlyoff/ServiceWorker] Need to review the algorithms for creating a new environment settings object (#919) (Friday, 1 July)

Dominic Cooney

Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Thursday, 14 July)

Dominic Tarr

Re: [whatwg/streams] light weight transformations (#461) (Sunday, 31 July)
Re: [whatwg/streams] light weight transformations (#461) (Saturday, 30 July)

Dominick Ng

Re: [slightlyoff/ServiceWorker] openWindow with a WebApp manifests (#720) (Thursday, 14 July)
Re: [slightlyoff/ServiceWorker] openWindow with a WebApp manifests (#720) (Thursday, 14 July)
Re: [w3c/manifest] Add beforeinstallprompt event (#417) (Friday, 1 July)

Duan Yao

Re: [WICG/directory-upload] Security issue of directory upload: pretend to download when actaully to upload a directory (#38) (Thursday, 7 July)

Ehsan Akhgari

Re: [whatwg/storage] Exposing cross-origin resource size (#31) (Friday, 29 July)
Re: [whatwg/fetch] Make it more clear that cache mode "default" does respect Cache-Control headers and such (#336) (Wednesday, 20 July)

Elliott Sprehn

Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 6 July)

Emily Stark

Re: [whatwg/fetch] HTTP-redirect fetch should invoke "Set request's referrer policy on redirect" (#334) (Tuesday, 19 July)
[whatwg/fetch] Call out to Referrer Policy to set policy on redirect (#335) (Friday, 15 July)
Re: [whatwg/fetch] HTTP-redirect fetch should invoke "Set request's referrer policy on redirect" (#334) (Friday, 15 July)
[whatwg/fetch] HTTP-redirect fetch should invoke "Set request's referrer policy on redirect" (#334) (Friday, 15 July)

ephox-mogran

[w3c/WebPlatformWG] added name to list (#44) (Tuesday, 12 July)

Eric Bidelman

Florian Rivoal

Re: [w3c/charter-html] Indicate relationship with the WHATWG (#112) (Saturday, 30 July)

Francois Marier

Re: [whatwg/fetch] Support same-origin, strict-origin, strict-origin-when-cross-origin in request' referrer policy (#342) (Friday, 29 July)
Re: [whatwg/fetch] Referrer policies: add the missing policies (fixes #342) (#346) (Friday, 29 July)
[whatwg/fetch] Referrer policies: add the missing policies (fixes #342) (#346) (Friday, 29 July)

Frederick Hirsch

[w3ctag/spec-reviews] Review of WakeLock API and suitability for overall platform requested by 31 August 2016 (#126) (Tuesday, 12 July)

Gabriel Wicke

Re: [whatwg/streams] light weight transformations (#461) (Tuesday, 26 July)

Gary Kacmarcik

Re: [w3c/uievents] 4.1 and 4.9 keypress is deprecated (#96) (Tuesday, 26 July)
Re: [w3c/uievents] 9.4 mutation events are deprecated (#103) (Tuesday, 26 July)
Re: [w3c/uievents] 9.4 mutation events are deprecated (#103) (Tuesday, 26 July)
Re: [w3c/uievents] 9.4 mutation events are deprecated (#102) (Tuesday, 26 July)
Re: [w3c/uievents] 4.1 and 4.9 keypress is deprecated (#96) (Tuesday, 26 July)
Re: [w3c/uievents] 4.1 and 4.9 keypress is deprecated (#96) (Tuesday, 26 July)
Re: [w3c/uievents] Typo in 3.2 (#94) (Tuesday, 26 July)

gked

Re: [w3c/editing] ly 29th F2F Agenda Item - Set Virtual Keyboard Enter Key Text (#142) (Friday, 29 July)
[w3c/editing] ly 29th F2F Agenda Item - Set Virtual Keyboard Enter Key Text (#142) (Friday, 29 July)
Re: [w3c/editing] July 29th F2F Agenda Item - Opt-in/opt-out of editing features and menus (#141) (Friday, 29 July)
[w3c/editing] July 29th F2F Agenda Item - Opt-in/opt-out of editing features and menus (#141) (Friday, 29 July)
[w3c/editing] July 29th F2F Agenda Item - Non-cancelable event 2 of 2 (#140) (Friday, 29 July)
Re: [w3c/editing] July 29th F2F Agenda Item - Data and dataTransfer attributes (#139) (Friday, 29 July)
[w3c/editing] July 29th F2F Agenda Item - Data and dataTransfer attributes (#139) (Friday, 29 July)
Re: [w3c/editing] July 29th F2F Agenda Item - static ranges (#138) (Friday, 29 July)
[w3c/editing] July 29th F2F Agenda Item - static ranges (#138) (Friday, 29 July)
Re: [w3c/editing] July 29th F2F Agenda Item - Non-cancelable event (#137) (Friday, 29 July)
[w3c/editing] July 29th F2F Agenda Item - Non-cancelable event (#137) (Friday, 29 July)
Re: [w3c/editing] July 29th F2F Agenda Item - History handling (undo/redo) (#136) (Friday, 29 July)
[w3c/editing] July 29th F2F Agenda Item - History handling (undo/redo) (#136) (Friday, 29 July)
Re: [w3c/editing] July 29th F2F Agenda Item - Clipboard events (#135) (Friday, 29 July)
[w3c/editing] July 29th F2F Agenda Item - Clipboard events (#135) (Friday, 29 July)
Re: [w3c/WebPlatformWG] F2F Agenda Item - Dragging and dropping (#60) (Friday, 29 July)
Re: [w3c/WebPlatformWG] F2F Agenda Item - Dragging and dropping (#60) (Friday, 29 July)
Re: [w3c/WebPlatformWG] F2F Agenda Item - Dragging and dropping (#60) (Friday, 29 July)
Re: [w3c/editing] July 29th F2F Agenda Item - Dragging and dropping (#134) (Friday, 29 July)
[w3c/editing] July 29th F2F Agenda Item - Dragging and dropping (#134) (Friday, 29 July)
Re: [w3c/WebPlatformWG] F2F Agenda Item - Dragging and dropping (#60) (Friday, 29 July)
[w3c/WebPlatformWG] F2F Agenda Item - Dragging and dropping (#60) (Friday, 29 July)
Re: [w3c/WebPlatformWG] added one more item to the agenda (#55) (Thursday, 28 July)
Re: [w3c/WebPlatformWG] added one more item to the agenda (#55) (Thursday, 28 July)
[w3c/WebPlatformWG] added one more item to the agenda (#55) (Wednesday, 27 July)
Re: [w3c/WebPlatformWG] grisha_pullRequest_AddtlAttendees (#48) (Tuesday, 12 July)
[w3c/WebPlatformWG] grisha_pullRequest_AddtlAttendees (#48) (Tuesday, 12 July)

Hadley Beeman

Re: [w3ctag/spec-reviews] Privacy Mode (#101) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] TAG Review of HTML 5.1 (#119) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] TAG Review of HTML 5.1 (#119) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] First Party Cookies (#114) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Geofencing FPWD (#89) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Storage persistence (#85) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Storage persistence (#85) (Saturday, 30 July)

Hayato Ito

Re: [w3c/webcomponents] Shadow DOM, <style>, and document.styleSheets (#56) (Friday, 22 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Friday, 22 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Friday, 22 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Friday, 22 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Friday, 22 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Friday, 22 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Friday, 22 July)
Re: [w3c/webcomponents] Declarative syntax for custom elements (#136) (Thursday, 21 July)
Re: [w3c/webcomponents] Declarative syntax for custom elements (#136) (Thursday, 21 July)
Re: [w3c/webcomponents] Shadow DOM, <style>, and document.styleSheets (#56) (Thursday, 21 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Thursday, 21 July)
Re: [w3c/webcomponents] Upstream Shadow DOM spec to DOM/HTML Standard (#377) (Thursday, 21 July)
Re: [w3c/webcomponents] Is or how can Shadow DOM be 'SEO friendly'? (#500) (Thursday, 21 July)
Re: [w3c/webcomponents] Is or how can Shadow DOM be 'SEO friendly'? (#500) (Thursday, 21 July)
Re: [w3c/webcomponents] [idea] distributedCallback for Custom Elements (#527) (Thursday, 21 July)
Re: [w3c/webcomponents] [idea] distributedCallback for Custom Elements (#527) (Thursday, 21 July)
Re: [w3c/webcomponents] Why allow shadow root style to access :host? (#490) (Thursday, 21 July)
Re: [w3c/webcomponents] Why allow shadow root style to access :host? (#490) (Thursday, 21 July)
Re: [w3c/webcomponents] <iframe> and Window's named properties (#145) (Thursday, 21 July)
Re: [w3c/webcomponents] Interaction between CSS and composed tree needs to be better defined (#305) (Thursday, 21 July)
Re: [w3c/webcomponents] Interaction between CSS and composed tree needs to be better defined (#305) (Thursday, 21 July)
Re: [w3c/webcomponents] <iframe> and the History API (#184) (Thursday, 21 July)
Re: [w3c/webcomponents] An API for determining if the focused element is a text editor (#483) (Thursday, 21 July)
Re: [w3c/webcomponents] An API for determining if the focused element is a text editor (#483) (Thursday, 21 July)
Re: [w3c/webcomponents] Idea: ComposedTreeProxy (#516) (Thursday, 21 July)
Re: [w3c/webcomponents] Idea: ComposedTreeProxy (#516) (Thursday, 21 July)
Re: [w3c/webcomponents] Shadow DOM, <style>, and document.styleSheets (#56) (Thursday, 21 July)
Re: [w3c/webcomponents] Shadow DOM, <style>, and document.styleSheets (#56) (Thursday, 21 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Thursday, 21 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Wednesday, 20 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Wednesday, 20 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Wednesday, 20 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Wednesday, 20 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Wednesday, 20 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Wednesday, 20 July)
Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496) (Tuesday, 19 July)
Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496) (Tuesday, 19 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Tuesday, 19 July)
Re: [w3c/uievents] Fix #89. Make some of legacy UIEvents composed events (#93) (Tuesday, 19 July)
Re: [w3c/webcomponents] [idea] distributedCallback for Custom Elements (#527) (Tuesday, 19 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Tuesday, 19 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Friday, 15 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#281) (Thursday, 14 July)
[whatwg/dom] Add relatedTarget to event dispatch (#281) (Thursday, 14 July)
Re: [w3c/webcomponents] Shadow DOM and requestPointerLock() (#192) (Wednesday, 13 July)
Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Tuesday, 12 July)
[w3c/uievents] Fix #89. Make some of legacy UIEvents composed events (#93) (Tuesday, 12 July)
Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Tuesday, 12 July)
Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Tuesday, 12 July)
Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Tuesday, 12 July)
Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Monday, 11 July)
Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Monday, 11 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Monday, 11 July)
Re: [w3c/webcomponents] Invalid constructor when invoking the constructor directly (#531) (Monday, 11 July)
Re: [w3c/webcomponents] Invalid constructor when invoking the constructor directly (#531) (Monday, 11 July)
Re: [w3c/webcomponents] Are document fragments "inert"? (#532) (Monday, 11 July)
Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Monday, 11 July)
Re: [w3c/webcomponents] Event retargetting in layman's terms? (#528) (Monday, 11 July)
Re: [w3c/webcomponents] Event retargetting in layman's terms? (#528) (Monday, 11 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Friday, 8 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Friday, 8 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Friday, 8 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Thursday, 7 July)
Re: [whatwg/dom] Add relatedTarget to event dispatch (#277) (Tuesday, 5 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Monday, 4 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 1 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 1 July)

hemanth.hm

Re: [slightlyoff/ServiceWorker] Should 'fetch' be an event, or some different API? (#256) (Wednesday, 13 July)

hober

[w3c/WebPlatformWG] Brady will be at the Service Workers F2F next week too. (#51) (Monday, 18 July)

Ilya Grigorik

Re: [whatwg/fetch] HTTP/2 server push support (#51) (Tuesday, 26 July)

Ingvar Stepanyan

Re: [slightlyoff/ServiceWorker] Create F2F agenda - 28-29 July 2016 (#932) (Friday, 22 July)
Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Tuesday, 19 July)
Re: [slightlyoff/ServiceWorker] Should Cache-Control: private be respected? (#926) (Monday, 18 July)
[slightlyoff/ServiceWorker] Should Cache-Control: private be respected? (#926) (Tuesday, 12 July)

Inian

Re: [slightlyoff/ServiceWorker] clarify behavior when fetch event handler throws (#896) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Tuesday, 26 July)
Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Tuesday, 19 July)
Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Tuesday, 19 July)
Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Thursday, 14 July)
Re: [slightlyoff/ServiceWorker] DOMParser within ServiceWorkers (#846) (Saturday, 9 July)
Re: [slightlyoff/ServiceWorker] DOMParser within ServiceWorkers (#846) (Friday, 8 July)
Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Friday, 1 July)

Jake Archibald

Re: [slightlyoff/ServiceWorker] Receivers of ranged responses must ensure all ranges come from the same underlying resource (#703) (Sunday, 31 July)
Re: [slightlyoff/ServiceWorker] Create F2F agenda - 28-29 July 2016 (#932) (Sunday, 31 July)
Re: [slightlyoff/ServiceWorker] Create F2F agenda - 28-29 July 2016 (#932) (Sunday, 31 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Sunday, 31 July)
Re: [slightlyoff/ServiceWorker] Reporting URL for SW update failures (#877) (Friday, 29 July)
Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Friday, 29 July)
Re: [slightlyoff/ServiceWorker] cache.match should create partial responses if given a range request (#913) (Friday, 29 July)
[slightlyoff/ServiceWorker] Block 206s entering the cache (via put & addAll) (#937) (Friday, 29 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Friday, 29 July)
Re: [whatwg/storage] Exposing cross-origin resource size (#31) (Friday, 29 July)
Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Friday, 29 July)
[w3c/manifest] Define how the manifest is fetched (#481) (Friday, 29 July)
Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) (Friday, 29 July)
Re: [slightlyoff/ServiceWorker] Should mixed content always be blocked? (#813) (Friday, 29 July)
Re: [slightlyoff/ServiceWorker] Should mixed content always be blocked? (#813) (Friday, 29 July)
Re: [slightlyoff/ServiceWorker] consider firing a "clientcontrolled" event on ServiceWorkerGlobalScope (#886) (Friday, 29 July)
Re: [slightlyoff/ServiceWorker] Receivers of ranged responses must ensure all ranges come from the same underlying resource (#703) (Friday, 29 July)
Re: [slightlyoff/ServiceWorker] should async waitUntil() work in .then() handler of promise passed to previous waitUntil()? (#935) (Friday, 29 July)
Re: [slightlyoff/ServiceWorker] Receivers of ranged responses must ensure all ranges come from the same underlying resource (#703) (Friday, 29 July)
Re: [slightlyoff/ServiceWorker] Should waitUntil() fast fail if a single extension promise rejects? (#936) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] should async waitUntil() work in .then() handler of promise passed to previous waitUntil()? (#935) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] Does accessing ExtendableEvent's extend lifetime promises race? (#931) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] Should WindowClient.navigate(url) navigate with "replacement enabled"? (#918) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] More clarity around waiting for an active worker to finish (#916) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] ServiceWorkerContainer spec lists `onerror` as an event handler (#912) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] should UA check for updates on navigate when there is no fetch event? (#905) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] clarify behavior when fetch event handler throws (#896) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] clarify behavior when fetch event handler throws (#896) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] potential http cache issues with importScripts() (#894) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] Create F2F agenda - 28-29 July 2016 (#932) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] clarify secure context requirements in Handle Fetch (#890) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] clarify that Clients.matchAll() only returns Window Client objects with active documents (#888) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] spec exactly how to order non-window Client objects (#887) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] ServiceWorker lifetime and respondWith() with a user-constructed ReadableStream (#882) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] Split the cache API into its own spec (#879) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] should FetchEvent.request.cache reflect non-fetch browser cache controls? (#875) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] why does Register algorithm step 5.3.1 check for an active worker? (#856) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] Should mixed content always be blocked? (#813) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] Create F2F agenda - 28-29 July 2016 (#932) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] Create F2F agenda - 28-29 July 2016 (#932) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] spec behavior when ServiceWorkerContainer parent client is dead (#777) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] spec behavior when ServiceWorkerContainer parent client is dead (#777) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] Remove frameType, maybe add ancestorOrigins (#732) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] spec should be more explicit about accessing internal body on opaque Responses (#710) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] OCSP fetches bypass service worker (#564) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] clarify secure context requirements in Handle Fetch (#890) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] OCSP fetches bypass service worker (#564) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] Receivers of ranged responses must ensure all ranges come from the same underlying resource (#703) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] Remove frameType, maybe add ancestorOrigins (#732) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] serviceworker for iframes with srcdoc (#765) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] navigations that are not intercepted should still allow interception on further redirects (#793) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] Should the active worker move to environment settings object? (#811) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] ExtendableMessageEvent.source cannot be SameObject (#816) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] html no longer defines "referrer source" (#834) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] FetchEvent.respondWith does something weird with the body of a response (#850) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] Unregister algorithm step 6.1 is no longer necessary (#855) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] why does Register algorithm step 5.3.1 check for an active worker? (#856) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] Drop isReload (#873) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] should FetchEvent.request.cache reflect non-fetch browser cache controls? (#875) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] should FetchEvent.request.cache reflect non-fetch browser cache controls? (#875) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] Split the cache API into its own spec (#879) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] Move service worker spec into w3c (#881) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] ServiceWorker lifetime and respondWith() with a user-constructed ReadableStream (#882) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] addAll should resolve when the cache is fully & successfully written (#884) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] spec exactly how to order non-window Client objects (#887) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] clarify that Clients.matchAll() only returns Window Client objects with active documents (#888) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] clarify secure context requirements in Handle Fetch (#890) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] clarify secure context requirements in Handle Fetch (#890) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] potential http cache issues with importScripts() (#894) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] clarify behavior when fetch event handler throws (#896) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] ServiceWorkerContainer spec lists `onerror` as an event handler (#912) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] More clarity around waiting for an active worker to finish (#916) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] Why doesn't cache.match support `cacheName` (#917) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] Why doesn't cache.match support `cacheName` (#917) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] Should WindowClient.navigate(url) navigate with "replacement enabled"? (#918) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] Need to review the algorithms for creating a new environment settings object (#919) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] Create F2F agenda - 28-29 July 2016 (#932) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] clarify secure context requirements in Handle Fetch (#890) (Tuesday, 26 July)
Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Monday, 25 July)
Re: [slightlyoff/ServiceWorker] Create F2F agenda - 28-29 July 2016 (#932) (Monday, 25 July)
Re: [slightlyoff/ServiceWorker] Should mixed content always be blocked? (#813) (Monday, 25 July)
Re: [slightlyoff/ServiceWorker] clarify Request.isReload for sub-resources (#827) (Monday, 25 July)
Re: [slightlyoff/ServiceWorker] clarify Request.isReload for sub-resources (#827) (Monday, 25 July)
Re: [slightlyoff/ServiceWorker] Provide cache.putAll() method (#867) (Monday, 25 July)
Re: [slightlyoff/ServiceWorker] Provide cache.putAll() method (#867) (Monday, 25 July)
Re: [slightlyoff/ServiceWorker] Add a way to detect reloading only client (#872) (Monday, 25 July)
Re: [slightlyoff/ServiceWorker] Add a way to detect reloading only client (#872) (Monday, 25 July)
Re: [slightlyoff/ServiceWorker] Where are ServiceWorker data stored? (#883) (Monday, 25 July)
Re: [slightlyoff/ServiceWorker] spec exactly how to order non-window Client objects (#887) (Monday, 25 July)
Re: [slightlyoff/ServiceWorker] clarify secure context requirements in Handle Fetch (#890) (Monday, 25 July)
Re: [slightlyoff/ServiceWorker] clarify secure context requirements in Handle Fetch (#890) (Monday, 25 July)
Re: [slightlyoff/ServiceWorker] clarify secure context requirements in Handle Fetch (#890) (Monday, 25 July)
Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) (Monday, 25 July)
Re: [slightlyoff/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Monday, 25 July)
Re: [slightlyoff/ServiceWorker] why cant i register a embedded function as for shared worker? (#902) (Monday, 25 July)
Re: [slightlyoff/ServiceWorker] should UA check for updates on navigate when there is no fetch event? (#905) (Monday, 25 July)
Re: [slightlyoff/ServiceWorker] Make ServiceWorkers more tailored for "always offline" websites (#907) (Monday, 25 July)
Re: [slightlyoff/ServiceWorker] Make ServiceWorkers more tailored for "always offline" websites (#907) (Monday, 25 July)
Re: [slightlyoff/ServiceWorker] Authenticated PWA ? (#909) (Monday, 25 July)
Re: [slightlyoff/ServiceWorker] Authenticated PWA ? (#909) (Monday, 25 July)
Re: [slightlyoff/ServiceWorker] Authenticated PWA ? (#909) (Monday, 25 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Friday, 22 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Friday, 22 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Thursday, 21 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Wednesday, 20 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Wednesday, 20 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Wednesday, 20 July)
Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Tuesday, 19 July)
[slightlyoff/ServiceWorker] Create F2F agenda - 28-29 July 2016 (#932) (Tuesday, 19 July)
Re: [slightlyoff/ServiceWorker] Does accessing ExtendableEvent's extend lifetime promises race? (#931) (Tuesday, 19 July)
[w3c/WebPlatformWG] Minor typo (#52) (Tuesday, 19 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Tuesday, 19 July)
Re: [slightlyoff/ServiceWorker] Should Cache-Control: private be respected? (#926) (Monday, 18 July)
Re: [slightlyoff/ServiceWorker] Should Cache-Control: private be respected? (#926) (Monday, 18 July)
Re: [slightlyoff/ServiceWorker] Should Cache-Control: private be respected? (#926) (Monday, 18 July)
Re: [slightlyoff/ServiceWorker] Documentation mistake (#927) (Monday, 18 July)
Re: [slightlyoff/ServiceWorker] Documentation mistake (#927) (Monday, 18 July)
Re: [slightlyoff/ServiceWorker] ServiceWorkers doesn't update in Chrome of subscribers after 24 hours (even after 5 days) (#930) (Monday, 18 July)
Re: [slightlyoff/ServiceWorker] ServiceWorkers doesn't update in Chrome of subscribers after 24 hours (even after 5 days) (#930) (Monday, 18 July)
Re: [whatwg/fetch] Aborting a fetch (#27) (Monday, 18 July)
Re: [slightlyoff/ServiceWorker] 28-29 July 2016 Service Workers meeting - W3C Web platform Working Group (#929) (Friday, 15 July)
Re: [slightlyoff/ServiceWorker] Firing an event when service worker wakes up (#928) (Thursday, 14 July)
Re: [slightlyoff/ServiceWorker] Firing an event when service worker wakes up (#928) (Thursday, 14 July)
Re: [slightlyoff/ServiceWorker] DOMParser within ServiceWorkers (#846) (Saturday, 9 July)
Re: [slightlyoff/ServiceWorker] DOMParser within ServiceWorkers (#846) (Saturday, 9 July)
Re: [slightlyoff/ServiceWorker] Expose GeoLocation to workers (#745) (Thursday, 7 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Tuesday, 5 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Tuesday, 5 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Tuesday, 5 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Tuesday, 5 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Monday, 4 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Monday, 4 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Monday, 4 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Monday, 4 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Monday, 4 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Monday, 4 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Monday, 4 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Sunday, 3 July)

jan-ivar

Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) (Friday, 22 July)
Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) (Thursday, 21 July)
Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) (Thursday, 21 July)
Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) (Thursday, 21 July)
Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) (Thursday, 21 July)
Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) (Thursday, 21 July)
Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) (Thursday, 21 July)
Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) (Thursday, 21 July)

Jason

Re: [w3c/screen-orientation] Allow lock Orientation more than one orientation (#91) (Friday, 15 July)
[w3c/screen-orientation] Allow lock Orientation more than one orientation (#91) (Tuesday, 12 July)

Jeena Lee

Re: [whatwg/fetch] Possible typo in header value definition (#332) (Wednesday, 13 July)
[whatwg/fetch] Possible typo in header value definition (#332) (Tuesday, 12 July)

Jeff Walden

Re: [heycam/webidl] Make globals and things they inherit from have immutable prototypes (#133) (Friday, 29 July)

Jeffrey Yasskin

Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Friday, 29 July)
[w3ctag/packaging-on-the-web] Can a package be authenticated to come from a particular secure origin? (#30) (Thursday, 28 July)
[w3c/permissions] Guidance on whether to add an API to the permissions spec (#116) (Thursday, 28 July)
[w3c/permissions] feat(algorithms): allow calling with a PermissionName (#115) (Wednesday, 27 July)
Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Wednesday, 27 July)
Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Wednesday, 27 July)
Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Wednesday, 27 July)
Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Wednesday, 27 July)
Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Wednesday, 27 July)
[w3c/permissions] refactor(permission state): pass the settings object explicitly (#114) (Tuesday, 26 July)
Re: [w3c/permissions] Editorial fixes (#100) (Tuesday, 26 July)
[w3c/permissions] Check request() polyfill and update spec to match (#113) (Tuesday, 26 July)
[w3c/permissions] Flesh out request("geolocation") (#112) (Tuesday, 26 July)
[w3c/permissions] Flesh out request("push") (#111) (Monday, 25 July)
[w3c/push-api] applicationServerKey is never used in subscribe() (#209) (Monday, 25 July)
Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Friday, 22 July)
Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Friday, 22 July)
Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Friday, 22 July)
Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Friday, 22 July)
Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Friday, 22 July)
Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Friday, 22 July)
Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Friday, 22 July)
Re: [w3c/permissions] Editorial fixes (#100) (Friday, 22 July)
Re: [w3c/permissions] Editorial fixes (#100) (Thursday, 21 July)
Re: [w3c/permissions] Editorial fixes (#100) (Thursday, 21 July)
Re: [w3c/permissions] Guidance on where to put permission related stuff in other specs (#110) (Thursday, 21 July)
Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) (Thursday, 21 July)
[whatwg/storage] Integrate with the Permissions spec. (#36) (Thursday, 21 July)
Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) (Thursday, 21 July)
Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) (Thursday, 21 July)
Re: [w3c/permissions] Guidance on where to put permission related stuff in other specs (#110) (Thursday, 21 July)
Re: [w3c/permissions] Editorial fixes (#100) (Thursday, 21 July)
Re: [w3c/permissions] Editorial fixes (#100) (Thursday, 21 July)
Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) (Thursday, 21 July)
Re: [w3c/permissions] feat(registry): features require a secure context by default, with opt-out (#109) (Wednesday, 20 July)
Re: [w3c/permissions] Add persistent storage (#39) (Wednesday, 20 July)
Re: [w3c/permissions] Why is "retrieve the permission storage" not in "Permission store"? (#84) (Wednesday, 20 July)
Re: [w3c/permissions] Why is "retrieve the permission storage" not in "Permission store"? (#84) (Wednesday, 20 July)
Re: [w3c/permissions] Support for background sync (one-off and periodic) (#29) (Wednesday, 20 July)
Re: [w3c/permissions] Add persistent storage (#39) (Tuesday, 19 July)
Re: [w3c/permissions] Add persistent storage (#39) (Tuesday, 19 July)
Re: [w3c/permissions] Add "fullscreen" (#26) (Tuesday, 19 July)
Re: [w3c/permissions] Permissions may change status in other ways than "trying to access" (#43) (Tuesday, 19 July)
Re: [w3c/permissions] Permissions may change status in other ways than "trying to access" (#43) (Tuesday, 19 July)
Re: [w3c/permissions] Add "nfc" to enum PermissionName (#47) (Tuesday, 19 July)
Re: [w3c/permissions] Add security considerations section (#49) (Tuesday, 19 July)
Re: [w3c/permissions] Add "pointerlock" to enum PermissionName (#50) (Tuesday, 19 July)
Re: [w3c/permissions] Add "pointerlock" to enum PermissionName (#50) (Tuesday, 19 July)
Re: [w3c/permissions] Add pointerlock to the permissions enum? (#67) (Tuesday, 19 July)
Re: [w3c/permissions] Don't assume implicit grant from getUserMedia. (#78) (Tuesday, 19 July)
Re: [w3c/permissions] Don't assume implicit grant from getUserMedia. (#78) (Tuesday, 19 July)
Re: [w3c/permissions] Permission API has terminology issues one could drive a truck through. (#85) (Tuesday, 19 July)
Re: [w3c/permissions] Permission API has terminology issues one could drive a truck through. (#85) (Tuesday, 19 July)
Re: [w3c/permissions] Model temporary permissions better (#86) (Tuesday, 19 July)
Re: [w3c/permissions] Model temporary permissions better (#86) (Tuesday, 19 July)
Re: [w3c/permissions] Specify how request and revoke work on push and midi permissions. (#90) (Tuesday, 19 July)
Re: [w3c/permissions] Specify how request and revoke work on push and midi permissions. (#90) (Tuesday, 19 July)
Re: [w3c/permissions] Separate "request access" from "request permission"? (#94) (Tuesday, 19 July)
Re: [w3c/permissions] Separate "request access" from "request permission"? (#94) (Tuesday, 19 July)
Re: [w3c/permissions] Add 'webvr' to "Permission Registry" enum (#108) (Tuesday, 19 July)
Re: [w3c/permissions] Allow features to 'require a secure context'. (#109) (Tuesday, 19 July)
Re: [w3c/permissions] Allow features to 'require a secure context'. (#109) (Tuesday, 19 July)
[w3c/push-api] Spec should use "secure context" terminology (#202) (Tuesday, 19 July)
Re: [w3c/permissions] Allow features to 'require a secure context'. (#109) (Monday, 18 July)
[w3c/permissions] Allow features to 'require a secure context'. (#109) (Monday, 18 July)
[w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) (Friday, 15 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (#99) (Wednesday, 13 July)
Re: [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (#99) (Wednesday, 13 July)
Re: [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (#99) (Wednesday, 13 July)
Re: [w3c/permissions] Remove object-based permissions (#42) (Wednesday, 13 July)
Re: [w3c/permissions] Exceptions in promise using algorithms (#102) (Wednesday, 13 July)
Re: [w3c/permissions] Move the Permissions registry (#103) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
[w3c/permissions] docs(contributing): improve the guidelines for changes (#106) (Tuesday, 12 July)
Re: [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (#99) (Tuesday, 12 July)
[w3c/permissions] chore(editors): add W3C editor IDs (#105) (Tuesday, 12 July)
Re: [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (#99) (Tuesday, 12 July)
Re: [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (#99) (Tuesday, 12 July)
Re: [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (#99) (Tuesday, 12 July)
Re: [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (#99) (Tuesday, 12 July)
Re: [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (a9e27e4) (Tuesday, 12 July)
Re: [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (a9e27e4) (Tuesday, 12 July)
Re: [w3c/permissions] chore(navigator-and-workernavigator-extension): remove redudant text (#104) (Tuesday, 12 July)
Re: [w3c/permissions] how to tidy? (#98) (Tuesday, 12 July)
Re: [w3c/permissions] Remove object-based permissions (#42) (Tuesday, 12 July)
Re: [w3c/permissions] chore(examples): Modernize JS examples (#101) (Tuesday, 12 July)
Re: [w3c/permissions] how to tidy? (#98) (Monday, 11 July)
Re: [w3c/permissions] chore(examples): Modernize JS examples (#101) (Monday, 11 July)
Re: [w3c/permissions] chore(examples): Modernize JS examples (#101) (Monday, 11 July)
Re: [w3c/permissions] chore(examples): Modernize JS examples (#101) (Monday, 11 July)
Re: [w3c/permissions] chore(examples): Modernize JS examples (#101) (Monday, 11 July)
Re: [w3c/permissions] chore(examples): Modernize JS examples (#101) (Monday, 11 July)
Re: [w3c/permissions] chore(examples): Modernize JS examples (#101) (Monday, 11 July)

jeisinger

Re: [whatwg/fetch] no-referrer should not set referer header (#323) (Monday, 25 July)

Jesse MacFadyen

Re: [w3c/screen-orientation] screen-orientation.change events should be cancellable (#92) (Friday, 15 July)
[w3c/screen-orientation] screen-orientation.change events should be cancellable (#92) (Friday, 15 July)
Re: [w3c/screen-orientation] Allow lock Orientation more than one orientation (#91) (Friday, 15 July)
Re: [w3c/screen-orientation] Allow lock Orientation more than one orientation (#91) (Wednesday, 13 July)

Johannes Wilm

Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Friday, 29 July)
Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Friday, 29 July)
Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Thursday, 28 July)
Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Thursday, 28 July)
Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Thursday, 28 July)
Re: [w3c/WebPlatformWG] added issues 131/132 (#58) (Wednesday, 27 July)
[w3c/WebPlatformWG] added issues 131/132 (#58) (Wednesday, 27 July)
[w3c/WebPlatformWG] further cleanup (#57) (Wednesday, 27 July)
Re: [w3c/WebPlatformWG] further cleanup (#57) (Wednesday, 27 July)
[w3c/WebPlatformWG] small cleanups (#56) (Wednesday, 27 July)
Re: [w3c/WebPlatformWG] small cleanups (#56) (Wednesday, 27 July)
Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Wednesday, 27 July)
Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Wednesday, 27 July)
[w3c/editing] How to handle IME-alike input for European languages on Mac OS X for accent marks on long key press (#132) (Wednesday, 27 July)
[w3c/editing] How to combine data and transferData attributes? (#131) (Wednesday, 27 July)
Re: [w3c/WebPlatformWG] add Johannes Wilm to participant list (#53) (Monday, 25 July)
[w3c/WebPlatformWG] add Johannes Wilm to participant list (#53) (Monday, 25 July)
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) (Sunday, 24 July)
Re: [w3c/editing] We should ensure drag/drop also fires beforeInput (#107) (Sunday, 24 July)
Re: [w3c/editing] RESOLUTION: We are going to focus on describing ce=typing as a priority. (#85) (Sunday, 24 July)
Re: [w3c/editing] RESOLUTION: We are going to focus on describing ce=typing as a priority. (#85) (Sunday, 24 July)
Re: [w3c/editing] inputType for Menu Bar>Edit>Delete (no obvious direction) (#130) (Thursday, 21 July)
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) (Friday, 15 July)
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) (Thursday, 7 July)

John Mellor

[w3c/push-api] Make applicationServerKey [SameObject] not [Throws] (#199) (Thursday, 7 July)
Re: [w3c/push-api] PushSubscriptionOptions ArrayBuffer lifetime issues (#198) (Thursday, 7 July)
[w3c/push-api] PushSubscriptionOptions ArrayBuffer lifetime issues (#198) (Tuesday, 5 July)

Jonas Sicking

Re: [w3c/IndexedDB] Naming for "v2" ? (#82) (Friday, 15 July)
Re: [w3c/FileAPI] Implementations allow all values in type getter (#43) (Wednesday, 13 July)

Joseph Orbegoso Pea

Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Monday, 18 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Monday, 18 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Monday, 18 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Monday, 18 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Monday, 18 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Monday, 18 July)
Re: [w3c/webcomponents] [idea] distributedCallback for Custom Elements (#527) (Monday, 18 July)
Re: [w3c/webcomponents] [idea] distributedCallback for Custom Elements (#527) (Monday, 18 July)
Re: [w3c/webcomponents] [idea] distributedCallback for Custom Elements (#527) (Monday, 18 July)
Re: [w3c/webcomponents] Event retargetting in layman's terms? (#528) (Monday, 18 July)
Re: [w3c/webcomponents] Event retargetting in layman's terms? (#528) (Monday, 18 July)
Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Saturday, 16 July)
Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Saturday, 16 July)
Re: [w3c/webcomponents] Event retargetting in layman's terms? (#528) (Friday, 15 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Friday, 15 July)
Re: [w3c/webcomponents] Event retargetting in layman's terms? (#528) (Wednesday, 13 July)
Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Wednesday, 13 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Tuesday, 12 July)
Re: [w3c/webcomponents] The custom element state when constructor thrown (#533) (Tuesday, 12 July)
Re: [w3c/webcomponents] Are document fragments "inert"? (#532) (Tuesday, 12 July)
[w3c/webcomponents] Are document fragments "intert"? (#532) (Monday, 11 July)
Re: [w3c/webcomponents] [idea] distributedCallback for Custom Elements (#527) (Friday, 8 July)
Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 6 July)
Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 6 July)
Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 3 July)
Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) (Sunday, 3 July)
Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) (Saturday, 2 July)
Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) (Saturday, 2 July)
Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) (Saturday, 2 July)
Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) (Saturday, 2 July)
Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Saturday, 2 July)
Re: [w3c/webcomponents] [idea] distributedCallback for Custom Elements (#527) (Saturday, 2 July)
Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Saturday, 2 July)
Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Friday, 1 July)
Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Friday, 1 July)

Joshua Bell

Re: [slightlyoff/ServiceWorker] Create F2F agenda - 28-29 July 2016 (#932) (Friday, 22 July)
Re: [w3c/IndexedDB] Asynchronously executing a request should queue a task to fire events (#83) (Thursday, 21 July)
Re: [w3c/IndexedDB] Asynchronously executing a request should queue a task to fire events (#83) (Thursday, 21 July)
Re: [w3c/IndexedDB] Asynchronously executing a request should queue a task to fire events (#83) (Thursday, 21 July)
Re: [w3ctag/spec-reviews] Indexed DB getAll(), openKeyCursor() and objectStoreNames (#84) (Wednesday, 20 July)
Re: [w3ctag/spec-reviews] Indexed DB getAll(), openKeyCursor() and objectStoreNames (#84) (Wednesday, 20 July)
Re: [w3ctag/spec-reviews] Indexed DB getAll(), openKeyCursor() and objectStoreNames (#84) (Wednesday, 20 July)
Re: [w3ctag/spec-reviews] Indexed DB getAll(), openKeyCursor() and objectStoreNames (#84) (Wednesday, 20 July)
Re: [w3c/FileAPI] Re-add readAsBinaryString() (#44) (Monday, 18 July)
Re: [w3c/FileAPI] Re-add readAsBinaryString() (#44) (Monday, 18 July)
Re: [w3c/IndexedDB] Specify IDBOpenDBRequest processing as a queue? (#79) (Friday, 15 July)
Re: [w3c/IndexedDB] Specify IDBOpenDBRequest processing as a queue? (#79) (Friday, 15 July)
Re: [w3c/IndexedDB] Specify IDBOpenDBRequest processing as a queue? (#79) (Friday, 15 July)
Re: [w3c/IndexedDB] Specify IDBOpenDBRequest processing as a queue? (#79) (Friday, 15 July)
Re: [w3c/IndexedDB] Specify IDBOpenDBRequest processing as a queue? (#79) (Friday, 15 July)
Re: [w3c/IndexedDB] task behavior for open requests is poorly specified (#9) (Friday, 15 July)
Re: [w3c/IndexedDB] deleteDatabase's "versionchange" should be deferred if upgrade is running (#78) (Friday, 15 July)
Re: [w3c/IndexedDB] task behavior for open requests is poorly specified (#9) (Friday, 15 July)
Re: [w3c/IndexedDB] The steps for opening a database are racy (#81) (Friday, 15 July)
Re: [w3c/IndexedDB] deleteDatabase's "versionchange" should be deferred if upgrade is running (#78) (Friday, 15 July)
Re: [w3c/IndexedDB] The steps for opening a database are racy (#81) (Friday, 15 July)
[w3c/IndexedDB] Naming for "v2" ? (#82) (Friday, 15 July)
[w3c/FileAPI] Re-add readAsBinaryString() (#44) (Thursday, 14 July)
Re: [w3c/FileAPI] Implementations allow all values in type getter (#43) (Wednesday, 13 July)
Re: [w3c/IndexedDB] The steps for opening a database are racy (#81) (Tuesday, 12 July)
Re: [w3c/IndexedDB] Specify IDBOpenDBRequest processing as a queue? (#79) (Friday, 8 July)
Re: [w3c/IndexedDB] Make IDBRequest.error and IDBRequest.transaction nullable (#80) (Friday, 8 July)
Re: [w3c/IndexedDB] Make IDBRequest.error and IDBRequest.transaction nullable (#80) (Friday, 8 July)

Julian Reschke

Re: [whatwg/fetch] Possible typo in header value definition (#332) (Friday, 22 July)

Jungkee Song

Re: [slightlyoff/ServiceWorker] ServiceWorkerContainer spec lists `onerror` as an event handler (#912) (Friday, 29 July)
Re: [slightlyoff/ServiceWorker] OCSP fetches bypass service worker (#564) (Friday, 29 July)
Re: [slightlyoff/ServiceWorker] Need to review the algorithms for creating a new environment settings object (#919) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] Need to review the algorithms for creating a new environment settings object (#919) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] FetchEvent.respondWith does something weird with the body of a response (#850) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] html no longer defines "referrer source" (#834) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] Resolve Job Promise can resolve jobs with an incorrect value (#829) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] Should the active worker move to environment settings object? (#811) (Thursday, 28 July)
Re: [slightlyoff/ServiceWorker] serviceworker for iframes with srcdoc (#765) (Thursday, 28 July)
Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Monday, 25 July)
Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Monday, 25 July)
Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Monday, 25 July)
Re: [slightlyoff/ServiceWorker] Create a new ReadableStream in FetchEvent.respondWith (#934) (Saturday, 23 July)
Re: [slightlyoff/ServiceWorker] Run the latest Bikeshed (#933) (Saturday, 23 July)
Re: [slightlyoff/ServiceWorker] Run the latest Bikeshed (#933) (Saturday, 23 July)
Re: [slightlyoff/ServiceWorker] When does the openWindow promise resolve? (#728) (Friday, 22 July)
Re: [slightlyoff/ServiceWorker] When does the openWindow promise resolve? (#728) (Friday, 22 July)
[slightlyoff/ServiceWorker] Does accessing ExtendableEvent's extend lifetime promises race? (#931) (Monday, 18 July)
Re: [slightlyoff/ServiceWorker] Remove monkeypatches in the event disptaching behaviors (72315b9) (Monday, 18 July)
Re: [slightlyoff/ServiceWorker] Remove monkeypatches in the event disptaching behaviors (72315b9) (Monday, 18 July)
Re: [slightlyoff/ServiceWorker] Stop monkeypatching event dispatch (#924) (Wednesday, 13 July)
Re: [slightlyoff/ServiceWorker] Stop monkeypatching event dispatch (#924) (Wednesday, 13 July)
[w3c/WebPlatformWG] Add jungkees to attendees list (#47) (Tuesday, 12 July)
Re: [slightlyoff/ServiceWorker] Run the latest Bikeshed (#925) (Monday, 11 July)
Re: [slightlyoff/ServiceWorker] Update for changes to HTML's script-fetching algorithms (#923) (Friday, 8 July)
Re: [slightlyoff/ServiceWorker] When does the openWindow promise resolve? (#728) (Thursday, 7 July)

jungshik

[whatwg/encoding] Add UTF-7 to replacement encoding list? (#68) (Friday, 29 July)

Kenji Baheux

[w3c/WebPlatformWG] Kenji recording his plan to attend (#46) (Tuesday, 12 July)
[w3c/WebPlatformWG] Kenji recording his plan to attend (#45) (Tuesday, 12 July)
[w3c/WebPlatformWG] Kenji Baheux recording his plan to attend (#42) (Tuesday, 5 July)

Kenneth Rohde Christiansen

Re: [w3c/manifest] Adding the webapp's badge to the manifest (#480) (Friday, 29 July)
Re: [w3c/manifest] Adding the webapp's badge to the manifest (#480) (Thursday, 28 July)
Re: [w3c/manifest] Ability to claim web app (#476) (Thursday, 7 July)
Re: [w3c/manifest] Add beforeinstallprompt event (#417) (Monday, 4 July)

Kit Cambridge

Re: [w3c/push-api] PushSubscriptionOptions ArrayBuffer lifetime issues (#198) (Wednesday, 6 July)

Koji Ishii

Re: [w3c/webcomponents] Allow or prohibit observedAttributes to observe 'style' attribute? (#521) (Friday, 15 July)
Re: [w3c/webcomponents] Allow or prohibit observedAttributes to observe 'style' attribute? (#521) (Wednesday, 13 July)
Re: [w3c/webcomponents] The custom element state when constructor thrown (#533) (Wednesday, 13 July)
[w3c/webcomponents] The custom element state when constructor thrown (#533) (Tuesday, 12 July)

leolux

[w3c/manifest] Additional property to define a webapp to be single instance (single-tab) (#479) (Friday, 22 July)

Lewis Phạm

[slightlyoff/ServiceWorker] Firing an event when service worker wakes up (#928) (Thursday, 14 July)

Liam

Re: [whatwg/fetch] response.ok = false for opaque responses may be misleading (#299) (Sunday, 24 July)

Linus Unnebäck

Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Thursday, 14 July)

littledan

Re: [w3ctag/spec-reviews] Indexed DB getAll(), openKeyCursor() and objectStoreNames (#84) (Wednesday, 20 July)
Re: [heycam/webidl] Make globals and things they inherit from have immutable prototypes (#133) (Thursday, 14 July)
Re: [heycam/webidl] Make globals and things they inherit from have immutable prototypes (#133) (Thursday, 14 July)

Louis Ryan

Re: [whatwg/fetch] Add trailer support to network responses (#344) (Thursday, 28 July)

Léonie Watson

[w3c/uievents] 9.4 mutation events are deprecated (#103) (Saturday, 23 July)
[w3c/uievents] 9.4 mutation events are deprecated (#102) (Saturday, 23 July)
[w3c/uievents] 5.7 composition events use case (#101) (Saturday, 23 July)
[w3c/uievents] 5.5 input events notifications (#100) (Saturday, 23 July)
[w3c/uievents] 5.4.2 focusin and focusout bubble use case? (#99) (Saturday, 23 July)
[w3c/uievents] 5.2 focus events accessibility (#98) (Saturday, 23 July)
[w3c/uievents] 5.12 event types (#97) (Saturday, 23 July)
[w3c/uievents] 4.1 and 4.9 keypress is deprecated (#96) (Saturday, 23 July)
[w3c/uievents] 3.4 and 3.5 duplicate HTML spec (#95) (Saturday, 23 July)
[w3c/uievents] Typo in 3.2 (#94) (Saturday, 23 July)
Re: [w3c/IndexedDB] Naming for "v2" ? (#82) (Monday, 18 July)
Re: [w3c/WebPlatformWG] Update 16-07-29-Editing.md (#50) (Monday, 18 July)
Re: [w3c/WebPlatformWG] Add Chong Zhang to "will attend" list (#49) (Friday, 15 July)
Re: [w3c/WebPlatformWG] Publish First Public Working Draft for HTML 5.2? (#43) (Friday, 15 July)
Re: [w3c/WebPlatformWG] Publish First Public Working Draft for HTML 5.2? (#43) (Friday, 15 July)
Re: [w3c/WebPlatformWG] Add jungkees to attendees list (#47) (Tuesday, 12 July)
Re: [slightlyoff/ServiceWorker] Expose GeoLocation to workers (#745) (Thursday, 7 July)
Re: [w3c/WebPlatformWG] Kenji Baheux recording his plan to attend (#42) (Tuesday, 5 July)

Makoto Shimazu

Re: [slightlyoff/ServiceWorker] ServiceWorkerContainer spec lists `onerror` as an event handler (#912) (Thursday, 7 July)

Malisa

[whatwg/fetch] The comma-delimited combined value definition does not support Set-Cookie headers (#345) (Friday, 29 July)
Re: [whatwg/fetch] Possible typo in header value definition (#332) (Friday, 15 July)

Manish Goregaokar

[whatwg/xhr] Should we be pinning Files (#79) (Friday, 15 July)
Re: [w3c/FileAPI] Implementations allow all values in type getter (#43) (Thursday, 14 July)
[w3c/FileAPI] Implementations allow all values in type getter (#43) (Wednesday, 13 July)

Marco Colli

[w3c/push-api] Send notifications in batch (#208) (Saturday, 23 July)
Re: [slightlyoff/ServiceWorker] Byte by byte match does not capture developer friendly behaviour (#639) (Saturday, 9 July)
Re: [slightlyoff/ServiceWorker] Introduce `Service-Worker-Max-Age` header (#721) (Saturday, 9 July)
Re: [slightlyoff/ServiceWorker] Consider relying on eTags (or other headers) for service worker dependencies to check for updates (#839) (Saturday, 9 July)

Marcos Cáceres

Re: [w3ctag/spec-reviews] Bluetooth API Security Model (#90) (Sunday, 31 July)
Re: [w3c/manifest] Adding the webapp's badge to the manifest (#480) (Thursday, 28 July)
Re: [w3c/permissions] Editorial fixes (#100) (Tuesday, 26 July)
Re: [w3c/permissions] Check request() polyfill and update spec to match (#113) (Tuesday, 26 July)
Re: [w3c/manifest] Adding the webapp's badge to the manifest (#480) (Tuesday, 26 July)
Re: [w3c/permissions] Editorial fixes (#100) (Friday, 22 July)
Re: [w3c/permissions] Editorial fixes (#100) (Friday, 22 July)
Re: [w3c/permissions] Editorial fixes (#100) (Friday, 22 July)
Re: [w3c/permissions] Editorial fixes (#100) (Friday, 22 July)
Re: [w3c/permissions] Editorial fixes (#100) (Friday, 22 July)
Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) (Thursday, 21 July)
Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) (Thursday, 21 July)
Re: [w3c/permissions] feat(prompts): allow UAs to deny non-gesture prompts (#107) (Thursday, 21 July)
[heycam/webidl] Indicate that thing needs user action to work (#137) (Thursday, 21 July)
[heycam/webidl] More meaniful lables (#136) (Thursday, 21 July)
[w3c/permissions] Guidance on where to put permission related stuff in other specs (#110) (Thursday, 21 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 20 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 20 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 20 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 20 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 20 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 20 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 20 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 20 July)
Re: [w3c/permissions] Add security considerations section (#49) (Wednesday, 20 July)
Re: [w3c/permissions] Add security considerations section (#49) (Wednesday, 20 July)
Re: [w3c/screen-orientation] screen-orientation.change events should be cancellable (#92) (Friday, 15 July)
Re: [w3c/permissions] Remove object-based permissions (#42) (Wednesday, 13 July)
Re: [w3c/permissions] docs(contributing): improve the guidelines for changes (#106) (Wednesday, 13 July)
Re: [w3c/permissions] docs(contributing): improve the guidelines for changes (#106) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (#99) (Wednesday, 13 July)
Re: [w3c/permissions] chore(editors): add W3C editor IDs (#105) (Wednesday, 13 July)
Re: [w3c/permissions] chore(editors): add W3C editor IDs (#105) (Wednesday, 13 July)
Re: [w3c/permissions] how to tidy? (#98) (Wednesday, 13 July)
Re: [w3c/permissions] how to tidy? (#98) (Wednesday, 13 July)
Re: [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (#99) (Wednesday, 13 July)
Re: [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (#99) (Wednesday, 13 July)
Re: [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (#99) (Wednesday, 13 July)
Re: [w3c/permissions] Move the Permissions registry (#103) (Wednesday, 13 July)
Re: [w3c/permissions] Exceptions in promise using algorithms (#102) (Wednesday, 13 July)
Re: [w3c/permissions] Exceptions in promise using algorithms (#102) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] chore(examples): Modernize JS examples (#101) (Tuesday, 12 July)
Re: [w3c/permissions] chore(examples): Modernize JS examples (#101) (Tuesday, 12 July)
Re: [w3c/permissions] chore(examples): Modernize JS examples (#101) (Tuesday, 12 July)
Re: [w3c/permissions] chore(examples): Modernize JS examples (#101) (Tuesday, 12 July)
Re: [w3c/permissions] chore(examples): Modernize JS examples (#101) (Tuesday, 12 July)
Re: [w3c/permissions] chore(examples): Modernize JS examples (#101) (Tuesday, 12 July)
Re: [w3c/permissions] how to tidy? (#98) (Tuesday, 12 July)
Re: [w3c/permissions] Faking permissions (#54) (Monday, 11 July)
Re: [w3c/permissions] Faking permissions (#54) (Monday, 11 July)
Re: [w3c/permissions] navigator.permissions.request (#48) (Monday, 11 July)
Re: [w3c/permissions] Add screen sharing permissions (#45) (Monday, 11 July)
Re: [w3c/permissions] Remove object-based permissions (#42) (Monday, 11 July)
Re: [w3c/permissions] Remove object-based permissions (#42) (Monday, 11 July)
[w3c/permissions] chore(navigator-and-workernavigator-extension): remove redudant text (#104) (Monday, 11 July)
[w3c/permissions] Move the Permissions registry (#103) (Monday, 11 July)
[w3c/permissions] Exceptions in promise using methods (#102) (Monday, 11 July)
[w3c/permissions] chore(examples): Modernize JS examples (#101) (Monday, 11 July)
[w3c/permissions] Editorial fixes (#100) (Monday, 11 July)
Re: [w3c/permissions] What should "retrieve the permission state" do for pickers? (#8) (Monday, 11 July)
[w3c/permissions] feat(travis): autopublish with echidna (closes #24) (#99) (Monday, 11 July)
[w3c/permissions] how to tidy? (#98) (Monday, 11 July)
Re: [whatwg/xhr] 😠 (#76) (Thursday, 7 July)
Re: [w3c/manifest] Ability to claim web app (#476) (Thursday, 7 July)
Re: [w3c/manifest] Ability to claim web app (#476) (Thursday, 7 July)
Re: [slightlyoff/ServiceWorker] Expose GeoLocation to workers (#745) (Thursday, 7 July)
Re: [w3c/manifest] Ability to claim web app (#476) (Thursday, 7 July)
Re: [w3c/manifest] Add optional Transition Screen member (#478) (Thursday, 7 July)
Re: [w3c/manifest] Add optional Transition Screen member (#478) (Thursday, 7 July)
Re: [w3ctag/spec-reviews] Progressive Web Apps (#123) (Thursday, 7 July)
Re: [w3ctag/spec-reviews] Progressive Web Apps (#123) (Thursday, 7 July)
Re: [w3c/manifest] Ability to claim web app (#476) (Wednesday, 6 July)
Re: [w3c/manifest] Ability to claim web app (#476) (Wednesday, 6 July)
Re: [w3c/manifest] Ability to claim web app (#476) (Wednesday, 6 July)
Re: [w3c/manifest] Ability to claim web app (#476) (Wednesday, 6 July)
Re: [w3c/permissions] Add terms to Shepherd (#64) (Wednesday, 6 July)
Re: [w3c/permissions] Add terms to Shepherd (#64) (Wednesday, 6 July)
Re: [w3c/permissions] Add terms to Shepherd (#64) (Wednesday, 6 July)
Re: [w3c/manifest] Integration with service workers (#161) (Wednesday, 6 July)
Re: [w3c/manifest] Ability to claim web app (#476) (Wednesday, 6 July)
Re: [w3ctag/spec-reviews] Progressive Web Apps (#123) (Tuesday, 5 July)
Re: [w3c/manifest] Include Minimal Store/Catalog MetaData in Manifest (#448) (Tuesday, 5 July)
Re: [w3ctag/spec-reviews] Progressive Web Apps (#123) (Tuesday, 5 July)
Re: [w3c/manifest] Add beforeinstallprompt event (#417) (Monday, 4 July)

Marijn Kruisselbrink

Re: [slightlyoff/ServiceWorker] clarify behavior when fetch event handler throws (#896) (Friday, 29 July)
Re: [slightlyoff/ServiceWorker] spec behavior when ServiceWorkerContainer parent client is dead (#777) (Thursday, 28 July)
Re: [whatwg/fetch] Add steps to intercept requests using foreign fetch. (#329) (Tuesday, 26 July)
Re: [slightlyoff/ServiceWorker] Create F2F agenda - 28-29 July 2016 (#932) (Friday, 22 July)
Re: [w3c/FileAPI] Use BufferSource instead of ArrayBuffer or ArrayBufferView (#38) (Thursday, 21 July)
Re: [w3c/FileAPI] Re-add FileReader.readAsBinaryString() ? (#39) (Thursday, 21 July)
Re: [w3c/FileAPI] Re-add readAsBinaryString() (#44) (Thursday, 21 July)
Re: [w3c/FileAPI] Re-add readAsBinaryString() (#44) (Thursday, 21 July)
[w3c/FileAPI] Re-word the way the various read operations are defined (#45) (Thursday, 21 July)

Mark Nottingham

Re: [w3ctag/spec-reviews] URNbis documents (#117) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] URNbis documents (#117) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Review Web Annotations specs (#93) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Do we have feedback on Web Payment group's response to security & privacy questionnaire? (#125) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Do we have feedback on Web Payment group's response to security & privacy questionnaire? (#125) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Security Questionnaire (#77) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Security Questionnaire (#77) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Security Questionnaire (#77) (Saturday, 30 July)
Re: [whatwg/fetch] Access to the HTTP trailer (#34) (Friday, 29 July)
Re: [whatwg/fetch] Add trailer support to network responses (#344) (Friday, 29 July)
Re: [w3ctag/spec-reviews] WebRTC (#14) (Thursday, 28 July)
Re: [whatwg/fetch] Possible typo in header value definition (#332) (Friday, 22 July)
Re: [w3ctag/spec-reviews] WebRTC (#14) (Friday, 22 July)

Martin Thomson

Re: [whatwg/fetch] HTTP/2 server push support (#51) (Tuesday, 26 July)
Re: [w3c/push-api] applicationServerKey is never used in subscribe() (#209) (Tuesday, 26 July)
Re: [w3c/permissions] Flesh out request("push") (#111) (Tuesday, 26 July)
[w3c/push-api] Running tidy (#207) (Saturday, 23 July)
[w3c/push-api] JSON.parse produces any not object (#206) (Saturday, 23 July)
Re: [w3c/permissions] Allow features to 'require a secure context'. (#109) (Tuesday, 19 July)
[w3c/push-api] Options are...optional. (#201) (Thursday, 14 July)
Re: [w3c/push-api] Allow UA to not implement all PushSubscriptionOptions (#200) (Thursday, 14 July)
[w3c/push-api] Allow UA to not implement all PushSubscriptionOptions (#200) (Tuesday, 12 July)
Re: [w3c/permissions] Add screen sharing permissions (#45) (Monday, 11 July)
Re: [w3c/permissions] Add screen sharing permissions (#45) (Monday, 11 July)
Re: [w3c/push-api] PushSubscriptionOptions ArrayBuffer lifetime issues (#198) (Friday, 8 July)
Re: [w3c/push-api] Make applicationServerKey [SameObject] not [Throws] (#199) (Friday, 8 July)

Matt Falkenhagen

Re: [slightlyoff/ServiceWorker] More clarity around waiting for an active worker to finish (#916) (Wednesday, 20 July)
Re: [slightlyoff/ServiceWorker] More clarity around waiting for an active worker to finish (#916) (Wednesday, 20 July)

Matt Giuca

Re: [w3c/manifest] Add beforeinstallprompt event (#417) (Wednesday, 6 July)
Re: [w3c/manifest] Add beforeinstallprompt event (#417) (Tuesday, 5 July)

Matthew Phillips

Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Friday, 29 July)

Michael Kriegel

[w3c/webcomponents] Invalid constructor when invoking the constructor directly (#531) (Monday, 11 July)

Michael van Ouwerkerk

Re: [w3c/push-api] typedef object JSON; is incorrect (#204) (Monday, 25 July)
Re: [w3c/push-api] Running tidy (#207) (Monday, 25 July)
Re: [w3c/push-api] JSON.parse produces any not object (#206) (Monday, 25 July)
Re: [w3c/push-api] typedef object JSON; is incorrect (#204) (Monday, 25 July)
Re: [w3c/push-api] Use the correct terminology for secure contexts (#203) (Friday, 22 July)
Re: [w3c/push-api] Spec should use "secure context" terminology (#202) (Friday, 22 July)
Re: [w3c/push-api] Options are...optional. (#201) (Friday, 15 July)
Re: [w3c/push-api] Allow UA to not implement all PushSubscriptionOptions (#200) (Friday, 15 July)

Michael[tm] Smith

Re: [whatwg/url] Url definition should define the fragment as optional (#134) (Thursday, 28 July)
Re: [whatwg/fetch] Support same-origin, strict-origin, strict-origin-when-cross-origin in request' referrer policy (#342) (Thursday, 28 July)

Mike West

Re: [slightlyoff/ServiceWorker] Should mixed content always be blocked? (#813) (Thursday, 28 July)
[w3ctag/spec-reviews] Review origin policy. (#127) (Thursday, 28 July)
Re: [whatwg/fetch] RFC: a mechanism to bypass CORS preflight (#210) (Wednesday, 27 July)
Re: [whatwg/fetch] Block text/csv for requests whose type is "script"? (#337) (Monday, 25 July)
Re: [w3ctag/spec-reviews] Review secure contexts (#124) (Tuesday, 19 July)
Re: [w3ctag/spec-reviews] Review secure contexts (#124) (Thursday, 7 July)

Mounir Lamouri

Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) (Thursday, 21 July)
Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) (Thursday, 21 July)
Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) (Thursday, 21 July)
Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) (Thursday, 21 July)
Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) (Thursday, 21 July)
Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) (Thursday, 21 July)
Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) (Tuesday, 19 July)
Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) (Tuesday, 19 July)
Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) (Tuesday, 19 July)
Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) (Monday, 18 July)
Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) (Monday, 18 July)
Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) (Monday, 18 July)
Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) (Monday, 18 July)
Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) (Monday, 18 July)
Re: [whatwg/fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) (Thursday, 14 July)
Re: [w3c/screen-orientation] Allow lock Orientation more than one orientation (#91) (Thursday, 14 July)
Re: [w3c/screen-orientation] Allow lock Orientation more than one orientation (#91) (Tuesday, 12 July)
Re: [w3c/screen-orientation] Allow lock Orientation more than one orientation (#91) (Tuesday, 12 July)
Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) (Monday, 11 July)
Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) (Monday, 11 July)
[whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) (Monday, 11 July)
[w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) (Monday, 11 July)
Re: [w3c/screen-orientation] Fullscreen Element Stack Not Found in Fullscreen (#88) (Monday, 11 July)
Re: [whatwg/fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) (Friday, 8 July)
Re: [w3c/screen-orientation] Timing of triggering change event doesn't look right (#89) (Friday, 8 July)
Re: [w3c/screen-orientation] Timing of triggering change event doesn't look right (#89) (Friday, 8 July)
Re: [w3c/screen-orientation] Use animation frame task (#40) (Friday, 8 July)

Ms2ger

Re: [whatwg/dom] Remove SVGZoomEvent? (#283) (Tuesday, 26 July)
[whatwg/encoding] Correct [Exposed] syntax (#64) (Sunday, 24 July)
[whatwg/dom] Remove SVGZoomEvent? (#283) (Saturday, 23 July)
[whatwg/url] Figure out what to do with youtube IDNA issues (#131) (Friday, 1 July)

Murali Ramanujam

Re: [slightlyoff/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Monday, 25 July)

Muromi Ukari

Re: [whatwg/dom] MutationObserver with querySelector for elements (#77) (Saturday, 23 July)

Nathan Schloss

Re: [slightlyoff/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Monday, 25 July)
Re: [slightlyoff/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Monday, 25 July)
[w3c/WebPlatformWG] Update 16-07-28-29SW.md (#54) (Monday, 25 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Thursday, 21 July)

Nick Doty

Re: [w3ctag/spec-reviews] Browser Fingerprinting Document (#38) (Thursday, 28 July)

NikhilPuri12

[whatwg/xhr] failed to load data in sapui5 RowRepaeater (#78) (Tuesday, 12 July)

Nikos Andronikos

Re: [whatwg/dom] Define dataset as a mixin for HTMLElement and SVGElement (#280) (Tuesday, 19 July)
[whatwg/dom] Define dataset as a mixin for HTMLElement and SVGElement (#280) (Tuesday, 12 July)

Patrick H. Lauke

[w3c/touch-events] Add informative note about not doing naive "touch OR mouse etc" event handling (#71) (Sunday, 31 July)
Re: [w3c/touch-events] convert deprecated <dl> based WebIDL to Contiguous IDL (#69) (Thursday, 14 July)
Re: [w3c/touch-events] convert deprecated <dl> based WebIDL to Contiguous IDL (#69) (Thursday, 14 July)
Re: [w3c/touch-events] convert deprecated <dl> based WebIDL to Contiguous IDL (#69) (Wednesday, 13 July)
[w3c/touch-events] convert deprecated <dl> based WebIDL to Contiguous IDL (#69) (Wednesday, 13 July)
Re: [w3c/touch-events] Specify what browsers do on non-touch devices (#64) (Tuesday, 12 July)

Patrick McManus

Re: [whatwg/fetch] Delay network errors to prevent port scanning (#338) (Friday, 22 July)
Re: [whatwg/fetch] Delay network errors to prevent port scanning (#338) (Friday, 22 July)

Peter Beverloo

Re: [w3c/manifest] Adding the webapp's badge to the manifest (#480) (Thursday, 28 July)
Re: [w3c/manifest] Adding the webapp's badge to the manifest (#480) (Monday, 25 July)
[w3c/manifest] Adding the webapp's badge to the manifest (#480) (Monday, 25 July)
Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Monday, 25 July)
Re: [w3c/push-api] Send notifications in batch (#208) (Monday, 25 July)
Re: [w3c/push-api] Send notifications in batch (#208) (Monday, 25 July)
Re: [w3c/push-api] typedef object JSON; is incorrect (#204) (Thursday, 21 July)
Re: [w3c/push-api] typedef object JSON; is incorrect (#204) (Thursday, 21 July)
[w3c/push-api] Use the correct terminology for secure contexts (#203) (Wednesday, 20 July)
Re: [w3c/push-api] Options are...optional. (#201) (Thursday, 14 July)
Re: [w3c/push-api] Allow UA to not implement all PushSubscriptionOptions (#200) (Wednesday, 13 July)

Peter Linss

Re: [w3ctag/spec-reviews] TV Control Feedback (#111) (Saturday, 30 July)

Philip Jägenstedt

Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Friday, 29 July)
Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Friday, 29 July)
Re: [whatwg/dom] Make Attr a Node again (#102) (Friday, 29 July)
[whatwg/url] Let webkitURL be an alias of the URL constructor (#135) (Wednesday, 27 July)
Re: [whatwg/dom] cancelBubble legacy property (#211) (Thursday, 21 July)
Re: [whatwg/fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) (Wednesday, 20 July)
Re: [whatwg/fullscreen] Drop the iframe ancestor check? (#45) (Wednesday, 20 July)
Re: [whatwg/fullscreen] Drop the iframe ancestor check? (#45) (Wednesday, 20 July)
Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) (Tuesday, 19 July)
Re: [whatwg/fullscreen] Should we apply !important to "object-fit: contain"? (#44) (Wednesday, 13 July)
Re: [whatwg/fullscreen] Should we apply !important to "object-fit: contain"? (#44) (Wednesday, 13 July)
Re: [whatwg/fullscreen] Should we apply !important to "object-fit: contain"? (#44) (Wednesday, 13 July)
Re: [whatwg/fullscreen] Drop the iframe ancestor check? (#45) (Wednesday, 13 July)
Re: [whatwg/fullscreen] Drop the iframe ancestor check? (#45) (Wednesday, 13 July)
[whatwg/fullscreen] Drop the iframe ancestor check? (#45) (Wednesday, 13 July)
Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43) (Tuesday, 12 July)
Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) (Tuesday, 12 July)
Re: [whatwg/fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) (Monday, 11 July)
Re: [w3c/screen-orientation] Add orientation change source to be used by fullscreen api. (#90) (Monday, 11 July)
Re: [whatwg/fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) (Monday, 11 July)
Re: [whatwg/dom] Do not throw for query() and queryAll() (#39) (Thursday, 7 July)
Re: [whatwg/dom] Do not throw for query() and queryAll() (#39) (Thursday, 7 July)
Re: [whatwg/dom] Do not throw for query() and queryAll() (#39) (Thursday, 7 July)
Re: [whatwg/fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) (Monday, 4 July)
Re: [whatwg/fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) (Monday, 4 July)

PhistucK

Re: [whatwg/url] Which reality should location.pathname setter match? (#133) (Monday, 18 July)
Re: [whatwg/url] Which reality should location.pathname setter match? (#133) (Monday, 18 July)
[whatwg/url] Which reality should location.pathname setter match? (#133) (Thursday, 14 July)

Rafał Pocztarski

Re: [whatwg/dom] Do not throw for query() and queryAll() (#39) (Thursday, 7 July)
Re: [whatwg/dom] Do not throw for query() and queryAll() (#39) (Thursday, 7 July)
Re: [whatwg/dom] Do not throw for query() and queryAll() (#39) (Thursday, 7 July)
Re: [whatwg/dom] Do not throw for query() and queryAll() (#39) (Thursday, 7 July)

raymeskhoury

Re: [w3c/permissions] Add pointerlock to the permissions enum? (#67) (Thursday, 28 July)
Re: [whatwg/storage] Integrate with the Permissions spec. (#36) (Thursday, 28 July)

rektide

Re: [whatwg/fetch] HTTP/2 server push support (#51) (Thursday, 21 July)

Richard Maher

[slightlyoff/ServiceWorker] 28-29 July 2016 Service Workers meeting - W3C Web platform Working Group (#929) (Friday, 15 July)
Re: [slightlyoff/ServiceWorker] Expose GeoLocation to workers (#745) (Friday, 8 July)
Re: [slightlyoff/ServiceWorker] Expose GeoLocation to workers (#745) (Friday, 8 July)
Re: [slightlyoff/ServiceWorker] Expose GeoLocation to workers (#745) (Thursday, 7 July)
Re: [slightlyoff/ServiceWorker] Expose GeoLocation to workers (#745) (Tuesday, 5 July)

Rick Byers

Re: [w3c/touch-events] Add interaction with pointer events and compat mouse events (#70) (Tuesday, 26 July)
Re: [w3c/touch-events] convert deprecated <dl> based WebIDL to Contiguous IDL (#69) (Thursday, 14 July)
Re: [w3c/touch-events] convert deprecated <dl> based WebIDL to Contiguous IDL (#69) (Thursday, 14 July)
Re: [w3c/touch-events] Add interaction with pointer events and compat mouse events (#70) (Wednesday, 13 July)
[w3c/touch-events] Add interaction with pointer events and compat mouse events (#70) (Wednesday, 13 July)

Rik de Boer

Re: [slightlyoff/ServiceWorker] Expose GeoLocation to workers (#745) (Thursday, 7 July)
Re: [slightlyoff/ServiceWorker] Expose GeoLocation to workers (#745) (Sunday, 3 July)

Rob Dolin (MSFT)

[w3c/manifest] Add optional Transition Screen member (#478) (Wednesday, 6 July)
[w3c/manifest] Add screenshots object (#477) (Tuesday, 5 July)
[w3c/manifest] Ability to claim web app (#476) (Tuesday, 5 July)
Re: [w3c/manifest] Integration with service workers (#161) (Tuesday, 5 July)

Ryosuke Niwa

Re: [whatwg/dom] MutationObserver with querySelector for elements (#77) (Saturday, 23 July)
Re: [w3c/webcomponents] Shadow DOM, <style>, and document.styleSheets (#56) (Friday, 22 July)
Re: [w3c/webcomponents] Shadow DOM, <style>, and document.styleSheets (#56) (Friday, 22 July)
Re: [w3c/webcomponents] Shadow DOM, <style>, and document.styleSheets (#56) (Friday, 22 July)
Re: [w3c/selection-api] Triple-click selection bounds (#70) (Thursday, 21 July)
Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 18 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Monday, 18 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Monday, 18 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Monday, 18 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Monday, 18 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Monday, 18 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Monday, 18 July)
Re: [w3c/selection-api] Normative references (#69) (Monday, 18 July)
Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 18 July)
Re: [w3c/webcomponents] Event retargetting in layman's terms? (#528) (Monday, 18 July)
Re: [w3c/webcomponents] Event retargetting in layman's terms? (#528) (Saturday, 16 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Friday, 15 July)
Re: [w3c/webcomponents] Event retargetting in layman's terms? (#528) (Thursday, 14 July)
Re: [w3c/webcomponents] The custom element state when constructor thrown (#533) (Tuesday, 12 July)
Re: [w3c/webcomponents] Allow or prohibit observedAttributes to observe 'style' attribute? (#521) (Tuesday, 12 July)
Re: [w3c/webcomponents] Are document fragments "inert"? (#532) (Monday, 11 July)
Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Monday, 11 July)
Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Monday, 11 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Friday, 8 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Friday, 8 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Friday, 8 July)
Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Thursday, 7 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Thursday, 7 July)
Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Thursday, 7 July)
Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Thursday, 7 July)
Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Thursday, 7 July)
Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 6 July)
Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Wednesday, 6 July)
Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Wednesday, 6 July)
Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 6 July)
Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 6 July)
Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Wednesday, 6 July)
Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Tuesday, 5 July)
Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 5 July)
Re: [w3c/webcomponents] Should innerHTML propagate custom element constructor exceptions? (#525) (Saturday, 2 July)
Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Saturday, 2 July)

Salvador de la Puente González

Re: [slightlyoff/ServiceWorker] clarify secure context requirements in Handle Fetch (#890) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] clarify secure context requirements in Handle Fetch (#890) (Wednesday, 27 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Tuesday, 26 July)
Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Tuesday, 26 July)
Re: [slightlyoff/ServiceWorker] clarify secure context requirements in Handle Fetch (#890) (Tuesday, 26 July)
Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) (Tuesday, 26 July)
Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) (Monday, 25 July)

sam

[whatwg/fetch] fetch filter the symbols (#331) (Saturday, 9 July)

Sebastian Kippe

Re: [w3c/manifest] Adding the webapp's badge to the manifest (#480) (Thursday, 28 July)
Re: [w3c/manifest] Ability to claim web app (#476) (Wednesday, 6 July)
Re: [w3c/manifest] Ability to claim web app (#476) (Wednesday, 6 July)
Re: [w3c/manifest] Ability to claim web app (#476) (Wednesday, 6 July)

sleevi

Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) (Monday, 25 July)

smaug----

Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Monday, 18 July)
Re: [w3c/webcomponents] Allow or prohibit observedAttributes to observe 'style' attribute? (#521) (Wednesday, 13 July)
Re: [w3c/webcomponents] Allow or prohibit observedAttributes to observe 'style' attribute? (#521) (Tuesday, 12 July)
Re: [whatwg/dom] "In a document" confusion (#238) (Friday, 1 July)
Re: [heycam/webidl] Allow constructor<ClassType> as a type accepted by functions. (#101) (Friday, 1 July)

Tab Atkins Jr.

[whatwg/dom] "unclosed node of node" reads confusingly (#285) (Friday, 29 July)
Re: [w3c/permissions] Add persistent storage (#39) (Friday, 22 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)
Re: [w3c/permissions] Editorial fixes (#100) (Wednesday, 13 July)

Takayoshi Kochi

Re: [w3c/webcomponents] Shadow DOM and requestPointerLock() (#192) (Wednesday, 13 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Tuesday, 12 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Tuesday, 12 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Friday, 8 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 8 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 8 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 8 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 8 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 8 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 8 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 8 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 8 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 8 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Thursday, 7 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Thursday, 7 July)
[whatwg/fullscreen] Allow element in Shadow DOM to become fullscreen (#42) (Tuesday, 5 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Tuesday, 5 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Monday, 4 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Monday, 4 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 1 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 1 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 1 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 1 July)

Takeshi Yoshino

Re: [whatwg/streams] "Web sockets do not provide any way to tell when..." (#485) (Thursday, 28 July)
Re: [whatwg/streams] "if (controller.byobRequest)" (#484) (Thursday, 28 July)
Re: [whatwg/streams] "socket.setTCPWindowSize" (#483) (Thursday, 28 July)
Re: [whatwg/streams] "socket.setTCPWindowSize" (#483) (Thursday, 28 July)
Re: [whatwg/fetch] RFC: a mechanism to bypass CORS preflight (#210) (Wednesday, 27 July)
Re: [whatwg/fetch] RFC: a mechanism to bypass CORS preflight (#210) (Wednesday, 27 July)
Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Tuesday, 26 July)
Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Tuesday, 26 July)
Re: [whatwg/fetch] RFC: a mechanism to bypass CORS preflight (#210) (Wednesday, 20 July)
Re: [whatwg/fetch] RFC: a mechanism to bypass CORS preflight (#210) (Tuesday, 19 July)
Re: [whatwg/streams] Stack details are omitted in output of tap-spec (#478) (Friday, 15 July)
Re: [whatwg/streams] Use e => t.error(e) than t.error for catching exceptions in a then-callback (#479) (Friday, 15 July)
Re: [whatwg/streams] Use e => t.error(e) than t.error for catching exceptions in a then-callback (#479) (Friday, 15 July)
[whatwg/streams] Use e => t.error(e) than t.error for catching exceptions in a then-callback (#479) (Thursday, 14 July)
Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Thursday, 14 July)
Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Thursday, 14 July)
Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Thursday, 14 July)
Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Thursday, 14 July)
Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Thursday, 14 July)
[whatwg/streams] Stack details is omitted in output of tap-spec (#478) (Thursday, 14 July)
Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Thursday, 14 July)
Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Thursday, 14 July)
Re: [whatwg/streams] Should write() always error the stream when it rejects the promise it returned? (#476) (Wednesday, 13 July)
Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Wednesday, 13 July)
Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Wednesday, 13 July)
Re: [whatwg/streams] [WritableStream] Locking semantics (#474) (Tuesday, 12 July)
Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Tuesday, 12 July)
Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Tuesday, 12 July)
Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Thursday, 7 July)
Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Wednesday, 6 July)
[whatwg/streams] Should write() always error the stream when it rejects the promise it returned? (#476) (Wednesday, 6 July)
[whatwg/streams] [WritableStream] Locking semantics (#474) (Tuesday, 5 July)
Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Monday, 4 July)

Ted Mielczarek

Re: [w3c/gamepad] Added touched property to GamepadButton (#26) (Friday, 8 July)
Re: [w3c/gamepad] Added touched property to GamepadButton (#26) (Friday, 8 July)
Re: [w3c/gamepad] Added touched property to GamepadButton (#26) (Friday, 8 July)

Timothy Guan-tin Chien

[whatwg/url] Trailing dot and origin compuation (#132) (Monday, 11 July)

tnguyen

[whatwg/fetch] Support same-origin, strict-origin, strict-origin-when-cross-origin in request' referrer policy (#342) (Thursday, 28 July)

Tobie Langel

Re: [w3ctag/spec-reviews] Generic Sensor API (#110) (Sunday, 31 July)
Re: [w3ctag/spec-reviews] Ambient Light Sensor API (#115) (Saturday, 30 July)
Re: [heycam/webidl] More meaniful lables (#136) (Saturday, 30 July)

Travis Leithead

Re: [w3ctag/spec-reviews] TV Control Feedback (#111) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Generic Sensor API (#110) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Generic Sensor API (#110) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] relative URLs are not updated pushState() (#118) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] relative URLs are not updated pushState() (#118) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Write up the Secure Stop issue for ddorwin (#73) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Write up the Secure Stop issue for ddorwin (#73) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Presentation API Request for Feedback (#61) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Presentation API Request for Feedback (#61) (Saturday, 30 July)
Re: [w3ctag/spec-reviews] Review WAPA (Accessibility) proposal (#63) (Wednesday, 27 July)
Re: [w3ctag/spec-reviews] Indexed DB getAll(), openKeyCursor() and objectStoreNames (#84) (Wednesday, 20 July)
Re: [w3ctag/spec-reviews] Review secure contexts (#124) (Wednesday, 6 July)
Re: [w3c/DOM-Parsing] Significant normative and editorial updates (#16) (Friday, 1 July)
Re: [w3c/DOM-Parsing] Apply serialization algorithm fixes based on testing (#14) (Friday, 1 July)
Re: [w3c/DOM-Parsing] Significant normative and editorial updates (#16) (Friday, 1 July)
Re: [w3c/DOM-Parsing] Significant normative and editorial updates (#16) (Friday, 1 July)

Trey Shugart

Re: [w3c/webcomponents] Polyfilling custom elements with native Shadow DOM support (#534) (Friday, 29 July)
Re: [w3c/webcomponents] Polyfilling custom elements with native Shadow DOM support (#534) (Friday, 29 July)
[w3c/webcomponents] Polyfilling custom elements with native Shadow DOM support (#534) (Friday, 29 July)
Re: [w3c/webcomponents] [idea] Allow HTML Element attributes to accept any type of value, not just strings. (#519) (Thursday, 21 July)
Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 13 July)
Re: [w3c/webcomponents] Invalid constructor when invoking the constructor directly (#531) (Monday, 11 July)
Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Friday, 1 July)
Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Friday, 1 July)

Vincent Scheib

Re: [w3c/pointerlock] Add pointerlock to the permissions enum (#5) (Tuesday, 26 July)
[w3c/pointerlock] Add pointerlock to the permissions enum (#5) (Tuesday, 26 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Tuesday, 12 July)
Re: [w3c/pointerlock] PointerLock and Shadow DOM (#3) (Tuesday, 12 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 8 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 8 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Thursday, 7 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Thursday, 7 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Thursday, 7 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Thursday, 7 July)
Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Thursday, 7 July)

Vitaly Baranovsky

[slightlyoff/ServiceWorker] ServiceWorkers doesn't update in Chrome of subscribers after 24 hours (even after 5 days) (#930) (Monday, 18 July)

vyv03354

Re: [whatwg/encoding] Please double-check the end of the EUDC range (#53) (Sunday, 24 July)
Re: [whatwg/encoding] Please double-check the end of the EUDC range (#53) (Sunday, 24 July)

Wenbo Zhu

Re: [whatwg/fetch] Add trailer support to network responses (#344) (Friday, 29 July)

William J. Edney

Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Sunday, 17 July)

Xidorn Quan

Re: [whatwg/fullscreen] Drop the iframe ancestor check? (#45) (Wednesday, 20 July)
Re: [whatwg/fullscreen] Should we apply !important to "object-fit: contain"? (#44) (Wednesday, 13 July)
Re: [whatwg/fullscreen] Should we apply !important to "object-fit: contain"? (#44) (Wednesday, 13 July)
Re: [whatwg/fullscreen] Drop the iframe ancestor check? (#45) (Wednesday, 13 July)
Re: [whatwg/fullscreen] Drop the iframe ancestor check? (#45) (Wednesday, 13 July)
[whatwg/fullscreen] Should we apply !important to "object-fit: contain"? (#44) (Tuesday, 12 July)
Re: [whatwg/fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) (Friday, 1 July)
Re: [whatwg/fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) (Friday, 1 July)
Re: [whatwg/fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) (Friday, 1 July)
Re: [whatwg/fullscreen] Propose to always render elements in the top layer as if it is fixed positioned (#19) (Friday, 1 July)
Re: [whatwg/fullscreen] Propose to always render elements in the top layer as if it is fixed positioned (#19) (Friday, 1 July)

Yen Chi Hsuan

Re: [w3c/DOM-Parsing] Proposal: add a method in DOMParser for parsing non-UTF8 XML documents (#18) (Sunday, 17 July)
Re: [w3c/DOM-Parsing] Proposal: add a method in DOMParser for parsing non-UTF8 XML documents (#18) (Sunday, 17 July)
[w3c/DOM-Parsing] Proposal: add a method in DOMParser for parsing non-UTF8 XML documents (#18) (Friday, 15 July)

Yoav Weiss

Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Friday, 8 July)

yosin

Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Friday, 29 July)
Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Friday, 29 July)
Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Thursday, 28 July)
Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133) (Thursday, 28 July)
Re: [w3c/selection-api] Define the interaction with user-select CSS property (#46) (Thursday, 21 July)

youennf

Re: [whatwg/fetch] Only append Authorization if none is set (#198) (Wednesday, 27 July)
Re: [whatwg/fetch] Only append Authorization if none is set (#198) (Wednesday, 27 July)
Re: [whatwg/fetch] Only append Authorization if none is set (#198) (Wednesday, 27 July)
Re: [whatwg/fetch] Only append Authorization if none is set (#198) (Wednesday, 27 July)
Re: [whatwg/streams] JSIDL vs WebIDL (#45) (Monday, 18 July)

Yutaka Hirano

Re: [whatwg/fetch] Add trailer support to network responses (#344) (Friday, 29 July)
Re: [whatwg/fetch] Add trailer support to network responses (#344) (Friday, 29 July)
Re: [whatwg/fetch] Access to the HTTP trailer (#34) (Friday, 29 July)
Re: [whatwg/fetch] How response bodies get from a service worker to the main page is not very clear (#330) (Friday, 22 July)
Re: [slightlyoff/ServiceWorker] Create a new ReadableStream in FetchEvent.respondWith (#934) (Friday, 22 July)
Re: [slightlyoff/ServiceWorker] Create a new ReadableStream in FetchEvent.respondWith (#934) (Friday, 22 July)
Re: [slightlyoff/ServiceWorker] Create a new ReadableStream in FetchEvent.respondWith (#934) (Friday, 22 July)
[slightlyoff/ServiceWorker] Create a new ReadableStream in FetchEvent.respondWith (#934) (Friday, 22 July)
Re: [slightlyoff/ServiceWorker] Run the latest Bikeshed (#933) (Friday, 22 July)
[slightlyoff/ServiceWorker] Run the latest Bikeshed (#933) (Friday, 22 July)
Re: [whatwg/fetch] How response bodies get from a service worker to the main page is not very clear (#330) (Tuesday, 12 July)
Re: [whatwg/fetch] How response bodies get from a service worker to the main page is not very clear (#330) (Friday, 8 July)
Re: [whatwg/fetch] How response bodies get from a service worker to the main page is not very clear (#330) (Friday, 8 July)
Re: [whatwg/fetch] How response bodies get from a service worker to the main page is not very clear (#330) (Friday, 8 July)
Re: [whatwg/fetch] How response bodies get from a service worker to the main page is not very clear (#330) (Friday, 8 July)

Yves Lafon

Re: [w3c/WebPlatformWG] Minor typo (#52) (Tuesday, 19 July)
Re: [w3c/WebPlatformWG] Brady will be at the Service Workers F2F next week too. (#51) (Monday, 18 July)
Re: [w3c/WebPlatformWG] Kenji recording his plan to attend (#45) (Tuesday, 12 July)
Re: [w3c/WebPlatformWG] added name to list (#44) (Tuesday, 12 July)
Re: [w3c/WebPlatformWG] Kenji recording his plan to attend (#46) (Tuesday, 12 July)

Zambonifofex

Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Monday, 18 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Monday, 18 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Monday, 18 July)
Re: [w3c/webcomponents] Should <link rel="stylesheet"> work inside shadow DOM? (#530) (Monday, 18 July)
Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 14 July)
Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Wednesday, 13 July)
Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 6 July)
Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 6 July)
Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 5 July)

Zhen Zhang

Re: [w3c/FileAPI] Improve readability of Blob-related statements (#42) (Monday, 11 July)
[w3c/FileAPI] Improve readability of Blob-related statements (#42) (Monday, 11 July)

znqlsx

[whatwg/xhr] " Returns the response's body." (#80) (Friday, 22 July)

zpul

Re: [whatwg/xhr] Property to disable following redirects (#74) (Friday, 1 July)
[whatwg/xhr] Property to disable following redirects (#74) (Friday, 1 July)

Ádám Lippai

Re: [whatwg/streams] Add URL.createObjectURL(stream) support (#480) (Sunday, 17 July)
[whatwg/streams] Add URL.createObjectURL(stream) support (#480) (Sunday, 17 July)

Álvaro Carneiro

Re: [whatwg/url] Basic URL Parse point 1 (#130) (Friday, 1 July)
Re: [whatwg/url] Basic URL Parse point 1 (#130) (Friday, 1 July)
Re: [whatwg/url] Basic URL Parse point 1 (#130) (Friday, 1 July)
[whatwg/url] Basic URL Parse point 1 (#130) (Friday, 1 July)

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