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

achristensen07

• Re: [whatwg/url] file: URL with a port number through the host setter (#97) (Thursday, 29 December)
• Re: [whatwg/url] file: URL with a port number through the host setter (#97) (Thursday, 29 December)
• Re: [whatwg/url] Add non-special-URL hosts (#185) (Wednesday, 28 December)
• Re: [whatwg/url] Add non-special-URL hosts (#185) (Wednesday, 28 December)
• Re: [whatwg/dom] initEvent should not require three parameters (#387) (Friday, 23 December)
• Re: [whatwg/dom] initEvent should not require three parameters (#387) (Wednesday, 21 December)
• Re: [whatwg/dom] initEvent should not require three parameters (#387) (Tuesday, 20 December)
• [whatwg/dom] initEvent should not require three parameters (#387) (Tuesday, 20 December)
• Re: [whatwg/url] unicode fragments (#150) (Thursday, 8 December)
• Re: [whatwg/url] unicode fragments (#150) (Thursday, 8 December)
• Re: [whatwg/url] Semi-colon (;) should be illegal in URL hostname parsing (#159) (Thursday, 1 December)

Adam Rice

• Re: [whatwg/streams] alert underlyingSink when [[strategySize]]() fails (#628) (Tuesday, 13 December)
• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Wednesday, 7 December)
• Re: [whatwg/streams] Specify ReadableStream.[[Transfer]] (#623) (Tuesday, 6 December)
• Re: [whatwg/streams] Do not leak the closed promise on errored release (#626) (Tuesday, 6 December)
• [whatwg/streams] Do not leak the closed promise on errored release (#626) (Tuesday, 6 December)
• [whatwg/streams] Remove ZERO WIDTH JOINER characters (#624) (Monday, 5 December)
• Re: [whatwg/streams] Aborting a stream should wait for pending writes (#619) (Monday, 5 December)
• Re: [whatwg/streams] Aborting a stream should wait for pending writes (#619) (Monday, 5 December)
• Re: [whatwg/streams] Aborting a stream should wait for pending writes (#619) (Monday, 5 December)
• Re: [whatwg/streams] Aborting a stream should wait for pending writes (#619) (Monday, 5 December)
• Re: [whatwg/streams] Aborting a stream should wait for pending writes (#619) (Monday, 5 December)
• Re: [whatwg/streams] Aborting a stream should wait for pending writes (#619) (Monday, 5 December)
• Re: [whatwg/streams] Aborting a stream should wait for pending writes (#619) (Monday, 5 December)
• Re: [whatwg/streams] Aborting a stream should wait for pending writes (#619) (Monday, 5 December)
• Re: [whatwg/streams] Aborting a stream should wait for pending writes (#619) (Friday, 2 December)
• Re: [whatwg/streams] Aborting a stream should wait for pending writes (#619) (Friday, 2 December)
• [whatwg/streams] Reference defining "transforming [promise] by a fulfillment handler" ? (#622) (Friday, 2 December)
• Re: [whatwg/streams] Why are [[writeRequests]] and [[queue]] separate? (#589) (Friday, 2 December)
• Re: [whatwg/streams] Note about underlyingSink close() method is misleading (#617) (Thursday, 1 December)
• Re: [whatwg/streams] Aborting a stream should wait for pending writes (#619) (Thursday, 1 December)
• Re: [whatwg/streams] Aborting a stream should wait for pending writes (#619) (Thursday, 1 December)

Alex Russell

• Re: [whatwg/fetch] Only specific APIs should skip the fetch event when called within a service worker (#303) (Friday, 16 December)

aliams

• Re: [w3c/IndexedDB] Add non-normative documentation for methods/properties. (#121) (Tuesday, 6 December)
• Re: [w3c/IndexedDB] Parity between key retrieval steps and type conversions (#122) (Tuesday, 6 December)
• Re: [w3c/IndexedDB] Add non-normative documentation for methods/properties. (#121) (Friday, 2 December)
• Re: [w3c/IndexedDB] Add non-normative documentation for methods/properties. (#121) (Friday, 2 December)

Andrea Giammarchi

• Re: [whatwg/fetch] Aborting a fetch (#27) (Friday, 16 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 12 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 12 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 12 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 12 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 11 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 11 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 10 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 10 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Friday, 9 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Friday, 9 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 6 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 6 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 6 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 6 December)

Andrew Sutherland

• Re: [w3c/ServiceWorker] Change behavior of skipWaiting() (#1019) (Friday, 2 December)

Andy Earnshaw

• Re: [w3c/webcomponents] [idea] [shadow-dom] Provide a version number on shadow roots so they can be distinguished. (#610) (Saturday, 3 December)

Anne van Kesteren

• Re: [whatwg/url] Add non-special-URL hosts (#185) (Friday, 30 December)
• Re: [whatwg/url] file: URL with a port number through the host setter (#97) (Friday, 30 December)
• Re: [whatwg/url] Add non-special-URL hosts (#185) (Friday, 30 December)
• Re: [whatwg/url] IPv4 parser: handle the empty string (#189) (Friday, 30 December)
• Re: [whatwg/fetch] Editorial: let Infra define byte-lowercasing/uppercasing (#445) (Friday, 30 December)
• Re: [whatwg/fetch] Editorial: let Infra define byte-lowercasing/uppercasing (#445) (Friday, 30 December)
• Re: [whatwg/url] Add non-special-URL hosts (#185) (Friday, 30 December)
• Re: [whatwg/streams] Meta: add a service worker to the spec (#637) (Friday, 30 December)
• Re: [whatwg/streams] Meta: add a service worker to the spec (#637) (Friday, 30 December)
• Re: [whatwg/url] Something is causing the </main> to be closed prematurely (#190) (Friday, 30 December)
• Re: [whatwg/url] No need for null passwords (#186) (Friday, 30 December)
• Re: [whatwg/url] file: URL with a port number through the host setter (#97) (Thursday, 29 December)
• Re: [whatwg/url] Disallow duplicate @ in authority state (#31) (Thursday, 29 December)
• Re: [whatwg/url] Disallow duplicate @ in authority state (#31) (Thursday, 29 December)
• Re: [whatwg/url] Investigate aligning application/x-www-form-urlencoded with URL's query (#18) (Thursday, 29 December)
• Re: [whatwg/url] Investigate aligning application/x-www-form-urlencoded with URL's query (#18) (Thursday, 29 December)
• Re: [whatwg/url] IPv4 parser and the empty string as input (#96) (Thursday, 29 December)
• Re: [whatwg/url] IPv4 parser and the empty string as input (#96) (Thursday, 29 December)
• Re: [whatwg/url] IPv4 parser: handle the empty string (#189) (Thursday, 29 December)
• [whatwg/url] IPv4 parser: handle the empty string (#189) (Thursday, 29 December)
• Re: [whatwg/url] Parsing an empty host (#79) (Thursday, 29 December)
• Re: [whatwg/url] SIngle quotes in queries should be percent encoded? (#172) (Thursday, 29 December)
• Re: [whatwg/url] Percent-decode more stuff? (#87) (Thursday, 29 December)
• Re: [whatwg/url] Stop decoding all %2e's in paths (#156) (Thursday, 29 December)
• Re: [whatwg/url] Add non-special-URL hosts (#185) (Thursday, 29 December)
• Re: [whatwg/fetch] "3.3. `X-Content-Type-Options` header" (#444) (Thursday, 29 December)
• Re: [whatwg/url] Add non-special-URL hosts (#185) (Thursday, 29 December)
• Re: [whatwg/url] Add non-special-URL hosts (#185) (Thursday, 29 December)
• Re: [w3c/IndexedDB] Specify timing of transaction deactivation more precisely (#87) (Thursday, 29 December)
• Re: [whatwg/url] No need for null passwords (#186) (Thursday, 29 December)
• Re: [whatwg/url] No need for null passwords (#186) (Thursday, 29 December)
• Re: [whatwg/url] Add non-special-URL hosts (#185) (Thursday, 29 December)
• Re: [whatwg/url] URLSearchParams delete and iterator ambiguity (#188) (Wednesday, 28 December)
• Re: [whatwg/url] remove need for "//" after protocol? (#182) (Wednesday, 28 December)
• Re: [whatwg/url] Add non-special-URL hosts (#185) (Wednesday, 28 December)
• Re: [whatwg/url] No need for null passwords (#186) (Wednesday, 28 December)
• Re: [whatwg/url] remove need for "//" after protocol? (#182) (Wednesday, 28 December)
• Re: [whatwg/url] Splicing URLSearchParams? (#183) (Wednesday, 28 December)
• Re: [whatwg/url] Splicing URLSearchParams? (#183) (Wednesday, 28 December)
• Re: [whatwg/url] Splicing URLSearchParams? (#183) (Wednesday, 28 December)
• [whatwg/url] A password is not a user's credentials (#187) (Wednesday, 28 December)
• [whatwg/url] No need for null passwords (#186) (Wednesday, 28 December)
• Re: [whatwg/url] Add non-special-URL hosts (#185) (Wednesday, 28 December)
• Re: [whatwg/url] empty auth vs no auth -- same? (#181) (Wednesday, 28 December)
• Re: [whatwg/url] remove need for "//" after protocol? (#182) (Wednesday, 28 December)
• Re: [whatwg/url] Splicing URLSearchParams? (#183) (Wednesday, 28 December)
• Re: [whatwg/url] Add non-special-URL hosts (#185) (Wednesday, 28 December)
• [whatwg/url] Add non-special-URL hosts (#185) (Wednesday, 28 December)
• Re: [heycam/webidl] Adding slots [initial braindump] (#258) (Wednesday, 28 December)
• Re: [whatwg/url] Make application/x-www-form-urlencoded encode filenames (#178) (Wednesday, 28 December)
• Re: [whatwg/url] File names in application/x-www-form-urlencoded serializer (#109) (Wednesday, 28 December)
• Re: [whatwg/url] Non-Windows-file URL definition (#128) (Wednesday, 28 December)
• Re: [whatwg/url] Editorial: reduce ambiguity in syntax section (#179) (Wednesday, 28 December)
• Re: [whatwg/url] Editorial: add some URL parsing examples (#177) (Wednesday, 28 December)
• Re: [whatwg/url] Make it clearer that just about anything is parseable, probably via some examples (#119) (Wednesday, 28 December)
• Re: [whatwg/url] Editorial: add some URL parsing examples (#177) (Wednesday, 28 December)
• Re: [whatwg/url] Editorial: removing extra "and" in IPv4 parser (#180) (Wednesday, 28 December)
• Re: [whatwg/url] Editorial: extra "and" in IPv4 parser (#173) (Wednesday, 28 December)
• Re: [whatwg/url] Editorial: removing extra "and" in IPv4 parser (#180) (Wednesday, 28 December)
• Re: [whatwg/url] Editorial: removing extra "and" in IPv4 parser (#180) (Wednesday, 28 December)
• Re: [whatwg/url] What to do with /reference-implementation/ (#162) (Wednesday, 28 December)
• Re: [whatwg/fetch] fetch() doesn't properly handle errors from pre-flight responses with CORS (#443) (Wednesday, 28 December)
• Re: [whatwg/url] Splicing URLSearchParams? (#183) (Wednesday, 28 December)
• Re: [whatwg/url] empty auth vs no auth -- same? (#181) (Wednesday, 28 December)
• Re: [whatwg/url] remove need for "//" after protocol? (#182) (Wednesday, 28 December)
• Re: [whatwg/url] remove need for "//" after protocol? (#182) (Wednesday, 28 December)
• Re: [whatwg/fetch] fetch() doesn't properly handle errors from pre-flight responses with CORS (#443) (Wednesday, 28 December)
• Re: [whatwg/fetch] fetch() doesn't properly handle errors from pre-flight responses with CORS (#443) (Tuesday, 27 December)
• Re: [whatwg/fetch] Add "fetch" as a destination for "connect-src" bound features (#442) (Tuesday, 27 December)
• Re: [whatwg/fetch] Allow * for Access-Control-Expose-Headers (#252) (Tuesday, 27 December)
• Re: [whatwg/fetch] fetch() doesn't properly handle errors from pre-flight responses with CORS (#443) (Tuesday, 27 December)
• Re: [whatwg/url] empty auth vs no auth -- same? (#181) (Tuesday, 27 December)
• Re: [whatwg/url] Consider railroad diagrams in syntax sections to aid understanding (#67) (Friday, 23 December)
• Re: [whatwg/dom] Provide an opt-out for inputs overriding form DOM API (#388) (Thursday, 22 December)
• Re: [w3c/ServiceWorker] reserved Client objects and redirected navigations (#1031) (Thursday, 22 December)
• Re: [whatwg/dom] Provide an opt-out for inputs overriding form DOM API (#388) (Thursday, 22 December)
• Re: [w3c/webcomponents] "is" attribute for autonomous custom elements (#603) (Thursday, 22 December)
• Re: [w3c/webcomponents] "is" attribute for autonomous custom elements (#603) (Thursday, 22 December)
• Re: [whatwg/dom] initEvent should not require three parameters (#387) (Thursday, 22 December)
• Re: [whatwg/dom] initEvent should not require three parameters (#387) (Wednesday, 21 December)
• Re: [whatwg/encoding] Decode without BOM (#85) (Tuesday, 20 December)
• Re: [w3c/IndexedDB] transaction should either take DOMStringList or DOMStringList needs to be iterable (#85) (Tuesday, 20 December)
• Re: [whatwg/url] Consider railroad diagrams in syntax sections to aid understanding (#67) (Tuesday, 20 December)
• Re: [whatwg/url] Consider railroad diagrams in syntax sections to aid understanding (#67) (Tuesday, 20 December)
• Re: [whatwg/url] URLSearchParams: calling .set() and .append() should return itself (#90) (Tuesday, 20 December)
• Re: [whatwg/fetch] Define "to read a request" more specifically (#441) (Tuesday, 20 December)
• Re: [whatwg/fetch] Define "to read a request" more specifically (#441) (Tuesday, 20 December)
• Re: [whatwg/fetch] Define "to read a request" more specifically (#441) (Tuesday, 20 December)
• Re: [whatwg/url] What to do with /reference-implementation/ (#162) (Tuesday, 20 December)
• Re: [whatwg/fetch] WIP: Changing skip-service-worker flag to use-service-workers enum (#435) (Tuesday, 20 December)
• Re: [whatwg/fetch] WIP: Changing skip-service-worker flag to use-service-workers enum (#435) (Tuesday, 20 December)
• Re: [heycam/webidl] Consider simplifying serializers (#188) (Tuesday, 20 December)
• Re: [whatwg/fetch] Remove an obsolete note for ReadableStream type (#440) (Tuesday, 20 December)
• Re: [w3c/clipboard-apis] Import and set up ReSpec (#36) (Tuesday, 20 December)
• Re: [whatwg/fetch] Remove an obsolete not for ReadableStream type (#440) (Tuesday, 20 December)
• Re: [whatwg/url] Editorial: removing extra "and" in IPv4 parser (#180) (Tuesday, 20 December)
• Re: [whatwg/url] Trailing dot and origin compuation (#132) (Tuesday, 20 December)
• Re: [whatwg/url] Editorial: clarify that a trailing dot is significant (#176) (Tuesday, 20 December)
• Re: [whatwg/url] URLSearchParams: calling .set() and .append() should return itself (#90) (Tuesday, 20 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Tuesday, 20 December)
• Re: [heycam/webidl] Adding slots [initial braindump] (#258) (Tuesday, 20 December)
• Re: [whatwg/url] URLSearchParams: calling .set() and .append() should return itself (#90) (Tuesday, 20 December)
• Re: [whatwg/url] Editorial: clarify that a trailing dot is significant (#176) (Tuesday, 20 December)
• Re: [whatwg/url] Trailing dot and origin compuation (#132) (Tuesday, 20 December)
• Re: [heycam/webidl] Should mixins be able to add overloads? (#261) (Tuesday, 20 December)
• Re: [whatwg/dom] 3603108154 (#386) (Tuesday, 20 December)
• Re: [whatwg/url] URL.pathname getter for file URLs produces odd result on Windows (#103) (Monday, 19 December)
• Re: [whatwg/url] Validating and escaping mismatch in pathname (#112) (Monday, 19 December)
• Re: [whatwg/url] Validating and escaping mismatch in pathname (#112) (Monday, 19 December)
• Re: [whatwg/url] Editorial: add some URL parsing examples (#177) (Monday, 19 December)
• Re: [whatwg/url] Editorial: add some URL parsing examples (#177) (Monday, 19 December)
• Re: [whatwg/url] Editorial: add some URL parsing examples (#177) (Monday, 19 December)
• Re: [whatwg/url] Editorial: add some URL parsing examples (#177) (Monday, 19 December)
• Re: [whatwg/url] Editorial: add some URL parsing examples (#177) (Monday, 19 December)
• Re: [whatwg/url] Non-Windows-file URL definition (#128) (Monday, 19 December)
• [whatwg/url] Editorial: reduce ambiguity in syntax section (#179) (Monday, 19 December)
• Re: [whatwg/url] Editorial: clarify the "shorten a path" algorithm (#174) (Monday, 19 December)
• Re: [whatwg/url] Editorial: add some URL parsing examples (#177) (Monday, 19 December)
• Re: [whatwg/url] Editorial: clarify the "shorten a path" algorithm (#174) (Monday, 19 December)
• Re: [whatwg/url] Editorial: clarify the "shorten a path" algorithm (#174) (Monday, 19 December)
• Re: [whatwg/url] Make application/x-www-form-urlencoded encode filenames (#178) (Monday, 19 December)
• [whatwg/url] Make application/x-www-form-urlencoded encode filenames (#178) (Monday, 19 December)
• Re: [whatwg/url] File names in application/x-www-form-urlencoded serializer (#109) (Monday, 19 December)
• Re: [whatwg/fullscreen] Reject exitFullscreen() in inactive documents (#68) (Monday, 19 December)
• Re: [whatwg/url] Editorial: add some URL parsing examples (#177) (Monday, 19 December)
• [whatwg/url] Editorial: add some URL parsing examples (#177) (Monday, 19 December)
• Re: [whatwg/url] URLSearchParams: calling .set() and .append() should return itself (#90) (Monday, 19 December)
• Re: [whatwg/url] Trailing dot and origin compuation (#132) (Monday, 19 December)
• [whatwg/url] Editorial: clarify that a trailing dot is significant (#176) (Monday, 19 December)
• Re: [whatwg/url] Disallow "!" in host (#98) (Monday, 19 December)
• Re: [whatwg/url] Disallow "!" in host (#98) (Monday, 19 December)
• Re: [whatwg/fetch] upload progress return response.json()? (#389) (Monday, 19 December)
• Re: [whatwg/url] application/x-www-form-urlencoded serializer does not handle enough (#83) (Monday, 19 December)
• Re: [whatwg/url] application/x-www-form-urlencoded serializer does not handle enough (#83) (Monday, 19 December)
• Re: [whatwg/url] Consider URLUtils.prototype.toString({as:"unicode"}) (#64) (Monday, 19 December)
• Re: [whatwg/url] Consider URLUtils.prototype.toString({as:"unicode"}) (#64) (Monday, 19 December)
• Re: [whatwg/url] Sort URLSearchParams prior to stringification (#26) (Monday, 19 December)
• Re: [whatwg/url] Creation of URLSearchParams from Object/Map (#27) (Monday, 19 December)
• [whatwg/url] Simplify constructing URLSearchParams (#175) (Monday, 19 December)
• Re: [whatwg/url] Convenience method for serializing URLSearchParams (#142) (Monday, 19 December)
• Re: [whatwg/url] Convenience method for serializing URLSearchParams (#142) (Monday, 19 December)
• [heycam/webidl] Allowing something to be the serializer and stringifier (#260) (Monday, 19 December)
• [heycam/webidl] Serialized value should allow any string type (#259) (Monday, 19 December)
• Re: [whatwg/url] What to do with /reference-implementation/ (#162) (Monday, 19 December)
• Re: [whatwg/url] handling invalid octal ip address (#164) (Monday, 19 December)
• Re: [whatwg/url] handling invalid octal ip address (#164) (Monday, 19 December)
• Re: [whatwg/url] path /. (#161) (Monday, 19 December)
• Re: [whatwg/url] path /. (#161) (Monday, 19 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Monday, 19 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Monday, 19 December)
• Re: [heycam/webidl] Adding slots [initial braindump] (#258) (Monday, 19 December)
• Re: [w3c/ServiceWorker] what should Client.url return for a reserved Worker Client? (#1034) (Monday, 19 December)
• Re: [whatwg/fetch] nosniff and images (#395) (Monday, 19 December)
• Re: [whatwg/fetch] Only use nosniff for "script" and "style" (#438) (Monday, 19 December)
• Re: [whatwg/fetch] nosniff and images (#395) (Monday, 19 December)
• Re: [whatwg/dom] cancelBubble legacy property (#211) (Monday, 19 December)
• Re: [whatwg/dom] cancelBubble legacy property (#211) (Monday, 19 December)
• Re: [whatwg/dom] Add Event's cancelBubble attribute (#383) (Monday, 19 December)
• Re: [w3c/ServiceWorker] what should Client.url return for a reserved Worker Client? (#1034) (Monday, 19 December)
• Re: [heycam/webidl] Adding slots [initial braindump] (#258) (Monday, 19 December)
• Re: [whatwg/fetch] Setting body as ReadableStream at POST request (#439) (Monday, 19 December)
• Re: [whatwg/fetch] Setting body as ReadableStream at POST request (#439) (Monday, 19 December)
• Re: [whatwg/fetch] upload progress return response.json()? (#389) (Monday, 19 December)
• Re: [whatwg/dom] Add Event's cancelBubble attribute (#383) (Monday, 19 December)
• Re: [whatwg/url] Editorial: clarify the "shorten a path" algorithm (#174) (Monday, 19 December)
• [whatwg/encoding] Decode without BOM (#85) (Sunday, 18 December)
• Re: [whatwg/xhr] Dell Diagnosis IF Support Assistant installed THEN it stalls with several errors & warnings (#104) (Sunday, 18 December)
• Re: [whatwg/url] SIngle quotes in queries should be percent encoded? (#172) (Sunday, 18 December)
• Re: [w3c/IndexedDB] transaction should either take DOMStringList or DOMStringList needs to be iterable (#85) (Saturday, 17 December)
• Re: [whatwg/dom] Point to IndexedDB for DOMStringList (#385) (Saturday, 17 December)
• Re: [w3c/IndexedDB] DOMStringList has been removed from DOM (#28) (Saturday, 17 December)
• Re: [whatwg/dom] Point to IndexedDB for DOMStringList (#385) (Saturday, 17 December)
• Re: [w3c/ServiceWorker] what should Client.url return for a reserved Worker Client? (#1034) (Saturday, 17 December)
• Re: [whatwg/fetch] WIP: Changing skip-service-worker flag to use-service-workers enum (#435) (Friday, 16 December)
• Re: [w3c/ServiceWorker] Content-Type requirement of service worker importScripts() (#1032) (Friday, 16 December)
• Re: [whatwg/dom] cancelBubble legacy property (#211) (Friday, 16 December)
• Re: [whatwg/fetch] nosniff and images (#395) (Friday, 16 December)
• Re: [whatwg/fetch] nosniff and images (#395) (Friday, 16 December)
• Re: [whatwg/fetch] nosniff and images (#395) (Friday, 16 December)
• [whatwg/fetch] Only use nosniff for "script" and "style" (#438) (Friday, 16 December)
• Re: [whatwg/fetch] Link directly to the concept-settings-object-referrer-policy anchor. (#432) (Friday, 16 December)
• Re: [whatwg/fetch] Clarify Body package data algorithm with multipart/form-data MIME type (#424) (Friday, 16 December)
• Re: [whatwg/fetch] Clarify Body package data algorithm with multipart/form-data MIME type (#424) (Friday, 16 December)
• Re: [whatwg/fetch] Clarification of Body package data algorithm with bytes, FormData and multipart/form-data MIME type (#392) (Friday, 16 December)
• Re: [whatwg/fetch] Only specific APIs should skip the fetch event when called within a service worker (#303) (Friday, 16 December)
• Re: [whatwg/fetch] Only specific APIs should skip the fetch event when called within a service worker (#303) (Friday, 16 December)
• Re: [w3c/ServiceWorker] Consider mechanisms to bypass the service worker for things that we know won't be in it's cache (#1026) (Friday, 16 December)
• Re: [w3c/ServiceWorker] Consider mechanisms to bypass the service worker for things that we know won't be in it's cache (#1026) (Friday, 16 December)
• Re: [w3c/ServiceWorker] Consider mechanisms to bypass the service worker for things that we know won't be in it's cache (#1026) (Friday, 16 December)
• Re: [whatwg/fetch] Clarify Body package data algorithm with multipart/form-data MIME type (#424) (Friday, 16 December)
• Re: [whatwg/fetch] Clarify Body package data algorithm with multipart/form-data MIME type (#424) (Friday, 16 December)
• Re: [whatwg/fetch] Clarify Body package data algorithm with multipart/form-data MIME type (#424) (Friday, 16 December)
• Re: [whatwg/fetch] Clarify Body package data algorithm with multipart/form-data MIME type (#424) (Friday, 16 December)
• Re: [whatwg/fullscreen] Reject exitFullscreen() in inactive documents (#68) (Friday, 16 December)
• Re: [whatwg/fullscreen] Define what happens with requestFullscreen() and exitFullscreen() in inactive document (#67) (Friday, 16 December)
• Re: [whatwg/fullscreen] Reject exitFullscreen() in inactive documents (#68) (Friday, 16 December)
• Re: [whatwg/fetch] WIP: Changing skip-service-worker flag to use-service-workers enum (#435) (Friday, 16 December)
• Re: [whatwg/fetch] WIP: Changing skip-service-worker flag to use-service-workers enum (#435) (Friday, 16 December)
• Re: [whatwg/fetch] WIP: Changing skip-service-worker flag to use-service-workers enum (#435) (Friday, 16 December)
• Re: [whatwg/fetch] WIP: Changing skip-service-worker flag to use-service-workers enum (#435) (Friday, 16 December)
• Re: [w3c/ServiceWorker] Consider providing `navigation` event (#1028) (Friday, 16 December)
• Re: [whatwg/fullscreen] Editorial: resolve promises, don't fulfill them (#69) (Friday, 16 December)
• Re: [whatwg/fullscreen] Check the fullscreen element in the animation frame task for exit (#66) (Friday, 16 December)
• Re: [whatwg/fullscreen] Editorial: resolve promises, don't fulfill them (#69) (Friday, 16 December)
• Re: [whatwg/fullscreen] Editorial: resolve promises, don't fulfill them (#69) (Friday, 16 December)
• Re: [whatwg/fetch] Only specific APIs should skip the fetch event when called within a service worker (#303) (Friday, 16 December)
• Re: [w3c/ServiceWorker] Consider mechanisms to bypass the service worker for things that we know won't be in it's cache (#1026) (Friday, 16 December)
• Re: [whatwg/storage] Check PermissionState instead of PermissionStatus (#39) (Friday, 16 December)
• Re: [whatwg/storage] Check PermissionState instead of PermissionStatus (#39) (Friday, 16 December)
• Re: [whatwg/storage] Check PermissionState instead of PermissionStatus (#39) (Friday, 16 December)
• Re: [whatwg/storage] Check PermissionState instead of PermissionStatus (#39) (Friday, 16 December)
• Re: [whatwg/fullscreen] Define fully exit fullscreen in terms of exitFullscreen({ fully: true }) (#65) (Friday, 16 December)
• Re: [whatwg/fullscreen] Define fully exit fullscreen in terms of exitFullscreen({ fully: true }) (#65) (Friday, 16 December)
• Re: [whatwg/fullscreen] Check the fullscreen element in the animation frame task for exit (#66) (Friday, 16 December)
• Re: [whatwg/fullscreen] Check the fullscreen element in the animation frame task for exit (#66) (Friday, 16 December)
• Re: [whatwg/fullscreen] Check the fullscreen element in the animation frame task for exit (#66) (Friday, 16 December)
• Re: [whatwg/fullscreen] Reject exitFullscreen() in inactive documents (#68) (Friday, 16 December)
• Re: [whatwg/fullscreen] Reject exitFullscreen() in inactive documents (#68) (Friday, 16 December)
• Re: [whatwg/fullscreen] Reject exitFullscreen() in inactive documents (#68) (Friday, 16 December)
• Re: [whatwg/fullscreen] Define fully exit fullscreen in terms of exitFullscreen({ fully: true }) (#65) (Friday, 16 December)
• Re: [whatwg/storage] Check PermissionState instead of PermissionStatus (#39) (Friday, 16 December)
• Re: [whatwg/dom] cancelBubble legacy property (#211) (Friday, 16 December)
• Re: [w3c/IndexedDB] DOMStringList should have [Exposed=(Window,Worker)] (#118) (Friday, 16 December)
• Re: [whatwg/dom] Point to IndexedDB for DOMStringList (#385) (Friday, 16 December)
• Re: [whatwg/dom] Editorial: remove stray : from Mixin Slotable (#384) (Friday, 16 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Friday, 16 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Friday, 16 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Friday, 16 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Friday, 16 December)
• Re: [w3c/IndexedDB] transaction should either take DOMStringList or DOMStringList needs to be iterable (#85) (Friday, 16 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Friday, 16 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Friday, 16 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Friday, 16 December)
• Re: [whatwg/fetch] Only specific APIs should skip the fetch event when called within a service worker (#303) (Friday, 16 December)
• Re: [whatwg/fetch] WIP: Making a skip-local-service-worker flag (#435) (Friday, 16 December)
• Re: [whatwg/fetch] WIP: Making a skip-local-service-worker flag (#435) (Friday, 16 December)
• Re: [whatwg/fetch] WIP: Making a skip-local-service-worker flag (#435) (Friday, 16 December)
• Re: [whatwg/fullscreen] Define fully exit fullscreen in terms of exitFullscreen({ fully: true }) (#65) (Friday, 16 December)
• Re: [whatwg/fetch] Make Request constructor more forgiving (#377) (Friday, 16 December)
• Re: [whatwg/fetch] WIP: Making a skip-local-service-worker flag (#435) (Thursday, 15 December)
• Re: [whatwg/fetch] WIP: Making a skip-local-service-worker flag (#435) (Thursday, 15 December)
• Re: [whatwg/xhr] Make FormData a cloneable object (#55) (Sunday, 11 December)
• Re: [whatwg/url] unicode fragments (#150) (Friday, 9 December)
• Re: [whatwg/url] Percent encode fragments too (#169) (Friday, 9 December)
• Re: [heycam/webidl] Exception cleanup (#250) (Friday, 9 December)
• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Friday, 9 December)
• Re: [whatwg/dom] Add Event's cancelBubble attribute (#383) (Friday, 9 December)
• Re: [whatwg/xhr] Consider setting omit-Origin-header-flag for same origin requests (#31) (Friday, 9 December)
• Re: [whatwg/fetch] Should we send an Origin header for no-cors fetches? (#225) (Friday, 9 December)
• Re: [whatwg/fetch] Remove request's omit-Origin-header flag (#431) (Friday, 9 December)
• Re: [whatwg/fetch] Should we send an Origin header for no-cors fetches? (#225) (Friday, 9 December)
• Re: [whatwg/fetch] Handle null and failure for Access-Control-Expose-Headers (#434) (Friday, 9 December)
• Re: [whatwg/fetch] Handle null and failure for Access-Control-Expose-Headers (#434) (Friday, 9 December)
• Re: [whatwg/fetch] Access-Control-Expose-Headers parsing failure not handled in main fetch (#433) (Friday, 9 December)
• Re: [whatwg/url] IPv4 number parser on "0x0a" (#167) (Friday, 9 December)
• Re: [whatwg/url] Parse IPv4 number "0x0a" correctly (#171) (Friday, 9 December)
• [whatwg/fetch] Handle null and failure for Access-Control-Expose-Headers (#434) (Friday, 9 December)
• Re: [whatwg/url] IPv4 number parser on "0x0a" (#167) (Friday, 9 December)
• [whatwg/url] Parse IPv4 number "0x0a" correctly (#171) (Friday, 9 December)
• Re: [whatwg/url] IPv4 number parser on "0x0a" (#167) (Friday, 9 December)
• Re: [whatwg/url] Parsing an empty host (#79) (Friday, 9 December)
• Re: [w3c/webcomponents] fullscreenchange should be dispatched on each ancestor shadow root (#614) (Friday, 9 December)
• Re: [whatwg/fetch] Clarify Body package data algorithm with multipart/form-data MIME type (#424) (Friday, 9 December)
• Re: [whatwg/fetch] Clarify Body package data algorithm with multipart/form-data MIME type (#424) (Friday, 9 December)
• Re: [heycam/webidl] Exception cleanup (#250) (Friday, 9 December)
• Re: [whatwg/url] Semi-colon (;) should be illegal in URL hostname parsing (#159) (Friday, 9 December)
• Re: [w3c/webcomponents] fullscreenchange should be dispatched on each ancestor shadow root (#614) (Friday, 9 December)
• Re: [whatwg/url] unicode fragments (#150) (Friday, 9 December)
• Re: [whatwg/fetch] Link directly to the concept-settings-object-referrer-policy anchor. (#432) (Friday, 9 December)
• Re: [whatwg/url] Encode percent(%)s that are not part of a percent-encoded byte when parsing a URL (#170) (Thursday, 8 December)
• Re: [whatwg/url] Encode percent(%)s that are not part of a percent-encoded byte when parsing a URL (#170) (Thursday, 8 December)
• Re: [whatwg/dom] cancelBubble legacy property (#211) (Thursday, 8 December)
• Re: [whatwg/url] unicode fragments (#150) (Thursday, 8 December)
• Re: [whatwg/fetch] Should we send an Origin header for no-cors fetches? (#225) (Thursday, 8 December)
• Re: [whatwg/fetch] Should we send an Origin header for no-cors fetches? (#225) (Thursday, 8 December)
• Re: [whatwg/url] Percent encode fragments too (#169) (Thursday, 8 December)
• Re: [whatwg/url] unicode fragments (#150) (Thursday, 8 December)
• Re: [whatwg/fetch] why not add an option of json (#430) (Thursday, 8 December)
• Re: [whatwg/fetch] why not add an option of json (#430) (Thursday, 8 December)
• Re: [heycam/webidl] Add missing legacy error names. (#251) (Thursday, 8 December)
• Re: [heycam/webidl] Disallow nullable Promise types. (#248) (Thursday, 8 December)
• Re: [heycam/webidl] Disallow nullable Promise types. (#248) (Thursday, 8 December)
• Re: [whatwg/url] unicode fragments (#150) (Thursday, 8 December)
• Re: [whatwg/url] unicode fragments (#150) (Thursday, 8 December)
• [whatwg/url] Percent encode fragments too (#169) (Thursday, 8 December)
• Re: [whatwg/xhr] Consider setting omit-Origin-header-flag for same origin requests (#31) (Thursday, 8 December)
• Re: [whatwg/fetch] Should we send an Origin header for no-cors fetches? (#225) (Thursday, 8 December)
• Re: [whatwg/fetch] Remove request's omit-Origin-header flag (#431) (Thursday, 8 December)
• Re: [whatwg/fetch] Should we send an Origin header for no-cors fetches? (#225) (Thursday, 8 December)
• Re: [w3c/FileAPI] Blob.close() has several problems (#10) (Thursday, 8 December)
• Re: [whatwg/storage] Error handling in estimate() (#38) (Wednesday, 7 December)
• Re: [whatwg/dom] Add Event's cancelBubble attribute (#383) (Wednesday, 7 December)
• Re: [whatwg/dom] Add Event's cancelBubble attribute (#383) (Wednesday, 7 December)
• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Wednesday, 7 December)
• Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78) (Wednesday, 7 December)
• Re: [whatwg/fetch] Should we send an Origin header for no-cors fetches? (#225) (Wednesday, 7 December)
• [whatwg/fetch] Remove request's omit-Origin-header flag (#431) (Wednesday, 7 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Wednesday, 7 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Wednesday, 7 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Wednesday, 7 December)
• Re: [whatwg/fetch] why not add an option of json (#430) (Wednesday, 7 December)
• Re: [whatwg/fetch] Meta: Give Travis the full path to the java binary (#427) (Wednesday, 7 December)
• Re: [whatwg/dom] Inform event handler about the default action of an event (#382) (Wednesday, 7 December)
• Re: [whatwg/url] Add a couple more links for scheme related concepts. (#168) (Wednesday, 7 December)
• Re: [whatwg/url] Add a couple more links for scheme related concepts. (#168) (Wednesday, 7 December)
• Re: [whatwg/url] Add a couple more links for scheme related concepts. (#168) (Wednesday, 7 December)
• Re: [w3c/DOM-Parsing] Define the origin of the documents returned from DOMParser (#24) (Wednesday, 7 December)
• Re: [whatwg/dom] Add Event's cancelBubble attribute (#383) (Wednesday, 7 December)
• Re: [whatwg/dom] Add Event's cancelBubble attribute (#383) (Wednesday, 7 December)
• [whatwg/dom] Add Event's cancelBubble attribute (#383) (Wednesday, 7 December)
• Re: [w3c/DOM-Parsing] Define the origin of the documents returned from DOMParser (#24) (Wednesday, 7 December)
• Re: [whatwg/storage] Error handling in estimate() (#38) (Wednesday, 7 December)
• Re: [w3c/FileAPI] Blob.close() has several problems (#10) (Wednesday, 7 December)
• Re: [whatwg/fetch] See if resource exists (#428) (Wednesday, 7 December)
• Re: [whatwg/fetch] See if resource exists (#428) (Wednesday, 7 December)
• Re: [whatwg/dom] Copy the origin pointer when cloning a document (#380) (Wednesday, 7 December)
• Re: [whatwg/dom] cloneNode should probably define the new Document's origin (#378) (Wednesday, 7 December)
• Re: [whatwg/dom] Meta: run output through the HTML checker (#381) (Wednesday, 7 December)
• Re: [whatwg/dom] Meta: run output through the HTML checker (#381) (Wednesday, 7 December)

Anton Antonov

• Re: [whatwg/fetch] Aborting a fetch (#27) (Thursday, 15 December)

Appunni M

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

ArturoWipe

• Re: [w3c/ServiceWorker] activation of the Service Worker on an iframe context (#1029) (Friday, 16 December)
• Re: [w3c/ServiceWorker] activation of the Service Worker on an iframe context (#1029) (Friday, 16 December)
• [w3c/ServiceWorker] activation of the Service Worker on an iframe context (#1029) (Thursday, 15 December)

asmusf

• Re: [w3c/uievents-key] Ed: Unicode character encodings are shown (#33) (Friday, 16 December)
• Re: [w3c/uievents-key] Supplementary characters in ES6 can use code point values (#31) (Friday, 16 December)
• Re: [w3c/uievents] Editorial: Capital letter equivalents for bicameral scripts (#123) (Friday, 16 December)
• Re: [w3c/uievents] Dead keys and unsupported base characters (#120) (Friday, 16 December)
• Re: [w3c/uievents] What is an 'appropriate' Unicode code point? (#119) (Friday, 16 December)

beidson

• Re: [w3c/IndexedDB] Specify timing of transaction deactivation more precisely (#87) (Saturday, 31 December)
• Re: [w3c/IndexedDB] Specify timing of transaction deactivation more precisely (#87) (Saturday, 31 December)
• Re: [w3c/IndexedDB] Remove DOMStringList (#128) (Tuesday, 13 December)
• Re: [w3c/IndexedDB] Add support for async update or another way to prepopulate the databade (#126) (Monday, 5 December)
• Re: [w3c/IndexedDB] Add support for async update or another way to prepopulate the databade (#126) (Sunday, 4 December)

Ben Kelly

• Re: [w3c/ServiceWorker] clarify that manually constructed ExtendableEvent objects may not extend lifetime via waitUntil() (#1040) (Thursday, 22 December)
• Re: [w3c/ServiceWorker] clarify that manually constructed ExtendableEvent objects may not extend lifetime via waitUntil() (#1040) (Thursday, 22 December)
• Re: [w3c/ServiceWorker] clarify that manually constructed ExtendableEvent objects may not extend lifetime via waitUntil() (#1040) (Thursday, 22 December)
• [w3c/ServiceWorker] clarify that manually constructed ExtendableEvent objects may not extend lifetime via waitUntil() (#1040) (Thursday, 22 December)
• Re: [w3c/ServiceWorker] reserved Client objects and redirected navigations (#1031) (Thursday, 22 December)
• Re: [w3c/ServiceWorker] async waitUntil() does not allow extension on final promise resolution? (#1039) (Wednesday, 21 December)
• [w3c/ServiceWorker] async waitUntil() detail missing? (#1039) (Wednesday, 21 December)
• Re: [w3c/ServiceWorker] spec should be more explicit about accessing internal body on opaque Responses (#710) (Wednesday, 21 December)
• Re: [w3c/ServiceWorker] what should Client.url return for a reserved Worker Client? (#1034) (Tuesday, 20 December)
• Re: [w3c/ServiceWorker] reserved Client objects and redirected navigations (#1031) (Tuesday, 20 December)
• Re: [w3c/ServiceWorker] reserved Client objects and redirected navigations (#1031) (Monday, 19 December)
• Re: [w3c/ServiceWorker] reserved Client objects and redirected navigations (#1031) (Monday, 19 December)
• [w3c/ServiceWorker] consider how Client API should behave with bfcache (#1038) (Monday, 19 December)
• [w3c/ServiceWorker] `Clients.matchAll()` should exclude the current environment (#1037) (Monday, 19 December)
• [w3c/ServiceWorker] Support returning ServiceWorker Client environments from `Clients.matchAll()` (#1036) (Monday, 19 December)
• Re: [w3c/ServiceWorker] what should Client.url return for a reserved Worker Client? (#1034) (Monday, 19 December)
• Re: [w3c/ServiceWorker] reserved Client objects and redirected navigations (#1031) (Monday, 19 December)
• Re: [w3c/ServiceWorker] reserved Client objects and redirected navigations (#1031) (Monday, 19 December)
• Re: [w3c/ServiceWorker] what should Client.url return for a reserved Worker Client? (#1034) (Saturday, 17 December)
• Re: [w3c/ServiceWorker] what should Client.url return for a reserved Worker Client? (#1034) (Saturday, 17 December)
• Re: [w3c/ServiceWorker] reserved Client objects and redirected navigations (#1031) (Friday, 16 December)
• [w3c/ServiceWorker] what should Client.url return for a reserved Worker Client? (#1034) (Friday, 16 December)
• Re: [w3c/ServiceWorker] Content-Type requirement of service worker importScripts() (#1032) (Friday, 16 December)
• [w3c/ServiceWorker] mimetype requirement of service worker importScripts() (#1032) (Friday, 16 December)
• Re: [w3c/ServiceWorker] reserved Client objects and redirected navigations (#1031) (Friday, 16 December)
• Re: [whatwg/fetch] Only specific APIs should skip the fetch event when called within a service worker (#303) (Friday, 16 December)
• Re: [whatwg/fetch] Only specific APIs should skip the fetch event when called within a service worker (#303) (Friday, 16 December)
• [w3c/ServiceWorker] reserved Client objects and redirected navigations (#1031) (Friday, 16 December)
• Re: [w3c/ServiceWorker] Consider mechanisms to bypass the service worker for things that we know won't be in it's cache (#1026) (Friday, 16 December)
• Re: [w3c/ServiceWorker] Consider mechanisms to bypass the service worker for things that we know won't be in it's cache (#1026) (Friday, 16 December)
• Re: [w3c/ServiceWorker] Consider mechanisms to bypass the service worker for things that we know won't be in it's cache (#1026) (Friday, 16 December)
• Re: [whatwg/fetch] Only specific APIs should skip the fetch event when called within a service worker (#303) (Friday, 16 December)
• Re: [whatwg/fetch] Only specific APIs should skip the fetch event when called within a service worker (#303) (Friday, 16 December)
• [w3c/ServiceWorker] Client.reserved references wrong context state? (#1030) (Thursday, 15 December)
• Re: [whatwg/fetch] consider exposing and allowing script to set Request priority (#436) (Thursday, 15 December)
• Re: [w3c/ServiceWorker] activation of the Service Worker on an iframe context (#1029) (Thursday, 15 December)
• Re: [w3c/ServiceWorker] activation of the Service Worker on an iframe context (#1029) (Thursday, 15 December)
• Re: [w3c/ServiceWorker] activation of the Service Worker on an iframe context (#1029) (Thursday, 15 December)
• Re: [whatwg/fetch] consider exposing and allowing script to set Request priority (#436) (Thursday, 15 December)
• [whatwg/fetch] consider exposing and allowing script to set Request priority (#436) (Wednesday, 14 December)
• Re: [w3c/ServiceWorker] Consider providing `navigation` event (#1028) (Wednesday, 14 December)
• Re: [w3c/ServiceWorker] Consider providing `navigation` event (#1028) (Wednesday, 14 December)
• Re: [w3c/ServiceWorker] spec should be more explicit about accessing internal body on opaque Responses (#710) (Wednesday, 14 December)
• Re: [w3c/ServiceWorker] Include imported scripts to byte-check (#1023) (Wednesday, 14 December)
• Re: [w3c/ServiceWorker] Consider mechanisms to bypass the service worker for things that we know won't be in it's cache (#1026) (Tuesday, 13 December)
• Re: [w3c/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Tuesday, 13 December)
• Re: [w3c/ServiceWorker] consider allowing static routing only for "foreign fetch" for anonymous requests (#1024) (Tuesday, 13 December)
• Re: [w3c/ServiceWorker] When should "imported scripts updated flag" be unset? (#1021) (Tuesday, 13 December)
• Re: [w3c/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Tuesday, 13 December)
• [w3c/ServiceWorker] consider allowing static routing only for "foreign fetch" for anonymous requests (#1024) (Monday, 12 December)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Monday, 12 December)
• Re: [w3c/ServiceWorker] When should "imported scripts updated flag" be unset? (#1021) (Monday, 12 December)
• Re: [w3c/ServiceWorker] When should "imported scripts updated flag" be unset? (#1021) (Monday, 12 December)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Monday, 12 December)
• Re: [w3c/ServiceWorker] Inconsistent behaviour when client-side certificates are required (#1022) (Sunday, 11 December)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Saturday, 10 December)
• Re: [w3c/ServiceWorker] When should "imported scripts updated flag" be unset? (#1021) (Saturday, 10 December)
• Re: [w3c/ServiceWorker] When should "imported scripts updated flag" be unset? (#1021) (Thursday, 8 December)
• Re: [w3c/ServiceWorker] When should "imported scripts updated flag" be unset? (#1021) (Wednesday, 7 December)
• Re: [w3c/ServiceWorker] allow service worker produced resources to be marked as "cachable" (#962) (Friday, 2 December)
• Re: [w3c/ServiceWorker] allow service worker produced resources to be marked as "cachable" (#962) (Thursday, 1 December)
• Re: [w3c/ServiceWorker] allow service worker produced resources to be marked as "cachable" (#962) (Thursday, 1 December)

Bevis Tseng

• Re: [w3c/IndexedDB] Specify timing of transaction deactivation more precisely (#87) (Thursday, 29 December)

Boris Zbarsky

• Re: [heycam/webidl] Consider simplifying serializers (#188) (Friday, 23 December)
• Re: [heycam/webidl] Serialized value should allow any string type (#259) (Thursday, 22 December)
• Re: [heycam/webidl] Consider simplifying serializers (#188) (Thursday, 22 December)
• Re: [heycam/webidl] Should mixins be able to add overloads? (#261) (Tuesday, 20 December)
• Re: [heycam/webidl] Should mixins be able to add overloads? (#261) (Tuesday, 20 December)
• Re: [heycam/webidl] Should mixins be able to add overloads? (#261) (Monday, 19 December)
• [heycam/webidl] Should mixins be able to add overloads? (#261) (Monday, 19 December)
• Re: [heycam/webidl] Allowing something to be the serializer and stringifier (#260) (Monday, 19 December)
• Re: [whatwg/url] toJSON() serialization (#137) (Monday, 19 December)
• Re: [w3c/clipboard-apis] Where would one get a DataTransfer to hand to the ClipboardEvent constructor? (#33) (Friday, 16 December)
• Re: [w3c/clipboard-apis] Where would one get a DataTransfer to hand to the ClipboardEvent constructor? (#33) (Friday, 16 December)
• Re: [w3c/clipboard-apis] Where would one get a DataTransfer to hand to the ClipboardEvent constructor? (#33) (Friday, 16 December)
• Re: [w3c/clipboard-apis] Where would one get a DataTransfer to hand to the ClipboardEvent constructor? (#33) (Friday, 16 December)
• [w3c/clipboard-apis] Where would one get a DataTransfer to hand to the ClipboardEvent constructor? (#33) (Friday, 16 December)
• Re: [heycam/webidl] Are operations on the `[[BackingMap]]` and `[[BackingSet]]` page-hookable? And if not, why not? (#254) (Monday, 12 December)
• Re: [heycam/webidl] Are operations on the `[[BackingMap]]` and `[[BackingSet]]` page-hookable? And if not, why not? (#254) (Monday, 12 December)
• Re: [heycam/webidl] Are operations on the `[[BackingMap]]` and `[[BackingSet]]` page-hookable? And if not, why not? (#254) (Monday, 12 December)
• Re: [heycam/webidl] Are operations on the `[[BackingMap]]` and `[[BackingSet]]` page-hookable? And if not, why not? (#254) (Monday, 12 December)
• Re: [heycam/webidl] Are operations on the `[[BackingMap]]` and `[[BackingSet]]` page-hookable? And if not, why not? (#254) (Monday, 12 December)
• [heycam/webidl] Are operations on the `[[BackingMap]]` and `[[BackingSet]]` page-hookable? And if not, why not? (#254) (Monday, 12 December)
• Re: [heycam/webidl] Disallow nullable Promise types. (#248) (Thursday, 8 December)
• Re: [heycam/webidl] Should perform security check for constructors (#249) (Thursday, 8 December)
• Re: [heycam/webidl] Disallow nullable Promise types. (#248) (Thursday, 8 December)

bORm

• Re: [whatwg/fetch] upload progress return response.json()? (#389) (Monday, 19 December)

Brad Hill

• Re: [whatwg/fetch] Should we send an Origin header for no-cors fetches? (#225) (Friday, 2 December)

Brett Zamir

• Re: [w3c/IndexedDB] Add non-normative documentation for methods/properties. Resolves #110 (61ad40a) (Tuesday, 6 December)

chaals

• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 6 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 6 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Tuesday, 6 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Tuesday, 6 December)

Chong Zhang

• Re: [w3c/uievents] Should DOM be modified before or after compositionupdate? edge/IE do one thing, chrome/saf/firefox do another? (#66) (Monday, 19 December)
• Re: [w3c/uievents] Should DOM be modified before or after compositionupdate? edge/IE do one thing, chrome/saf/firefox do another? (#66) (Monday, 19 December)
• [w3c/uievents] InputEvent.data should be nullable (#128) (Friday, 16 December)
• [w3c/uievents] InputEvent.data should be nullable (#116) (Thursday, 15 December)

Chris Dumez

• Re: [whatwg/dom] cancelBubble legacy property (#211) (Friday, 16 December)

Chris Rebert

• Re: [w3c/uievents] MouseEvent.fromElement/toElement (#84) (Thursday, 29 December)
• [w3c/uievents] Serious typo in EventModifierInit.ctrlKey's description (#129) (Wednesday, 28 December)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Wednesday, 14 December)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Friday, 9 December)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Friday, 9 December)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Friday, 9 December)
• Re: [whatwg/dom] Add Event's cancelBubble attribute (#383) (Friday, 9 December)
• Re: [whatwg/dom] Inform event handler about the default action of an event (#382) (Thursday, 8 December)
• Re: [whatwg/dom] cancelBubble legacy property (#211) (Thursday, 8 December)
• Re: [whatwg/dom] Add Event's cancelBubble attribute (#383) (Thursday, 8 December)
• Re: [whatwg/dom] Add Event's cancelBubble attribute (#383) (Thursday, 8 December)
• Re: [whatwg/dom] Add Event's cancelBubble attribute (#383) (Wednesday, 7 December)
• Re: [whatwg/dom] Add Event's cancelBubble attribute (#383) (Wednesday, 7 December)
• Re: [whatwg/dom] Add Event's cancelBubble attribute (#383) (Wednesday, 7 December)

Corey Farwell

• [whatwg/url] Add a couple more links for scheme related concepts. (#168) (Saturday, 3 December)

cynthia

• Re: [w3c/gamepad] [Extensions] GamepadHapticActuator#pulse bugs (#50) (Tuesday, 27 December)
• Re: [w3c/touch-events] Initialize touchList in Chrome (#78) (Saturday, 10 December)

Dave Koston

• Re: [whatwg/fetch] fetch() doesn't properly handle errors from pre-flight responses with CORS (#443) (Wednesday, 28 December)
• Re: [whatwg/fetch] fetch() doesn't properly handle errors from pre-flight responses with CORS (#443) (Wednesday, 28 December)
• Re: [whatwg/fetch] fetch() doesn't properly handle errors from pre-flight responses with CORS (#443) (Tuesday, 27 December)
• Re: [whatwg/fetch] fetch() doesn't properly handle errors from pre-flight responses with CORS (#443) (Tuesday, 27 December)
• [whatwg/fetch] fetch() doesn't properly handle errors from pre-flight responses with CORS (#443) (Thursday, 22 December)

Dave Tapuska

• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Wednesday, 14 December)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Friday, 9 December)

David Reed

• Re: [whatwg/xhr] Dell Diagnosis IF Support Assistant installed THEN it stalls with several errors & warnings (#104) (Sunday, 18 December)
• [whatwg/xhr] Dell Diagnosis IF Support Assistant installed THEN it stalls with several errors & warnings (#104) (Sunday, 18 December)

Dima Voytenko

• Re: [whatwg/dom] Provide an opt-out for inputs overriding form DOM API (#388) (Thursday, 22 December)
• Re: [whatwg/dom] Provide an opt-out for inputs overriding form DOM API (#388) (Thursday, 22 December)
• Re: [whatwg/dom] Provide an opt-out for inputs overriding form DOM API (#388) (Thursday, 22 December)
• [whatwg/dom] Provide an opt-out for inputs overriding form DOM API (#388) (Wednesday, 21 December)

Diwank Singh Tomer

• Re: [whatwg/streams] Start work on a polyfill? (#630) (Monday, 19 December)
• Re: [whatwg/streams] Start work on a polyfill? (#630) (Monday, 19 December)
• [whatwg/streams] Start work on polyfill? (#630) (Wednesday, 14 December)

Domenic Denicola

• Re: [whatwg/url] internal class (or type) "URL" (#191) (Saturday, 31 December)
• Re: [whatwg/url] internal class (or type) "URL" (#191) (Saturday, 31 December)
• Re: [whatwg/url] internal class (or type) "URL" (#191) (Saturday, 31 December)
• Re: [whatwg/streams] Meta: add a service worker to the spec (#637) (Friday, 30 December)
• Re: [whatwg/streams] Meta: add a service worker to the spec (#637) (Friday, 30 December)
• Re: [whatwg/streams] Meta: add a service worker to the spec (#637) (Friday, 30 December)
• Re: [whatwg/url] Something is causing the </main> to be closed prematurely (#190) (Friday, 30 December)
• [whatwg/fetch] Editorial: let Infra define byte-lowercasing/uppercasing (#445) (Friday, 30 December)
• Re: [whatwg/streams] Meta: add a service worker to the spec (#637) (Friday, 30 December)
• [whatwg/url] Something is causing the </main> to be closed prematurely (#190) (Thursday, 29 December)
• Re: [whatwg/streams] Meta: add a service worker to the spec (#637) (Thursday, 29 December)
• Re: [whatwg/streams] Meta: add a service worker to the spec (#637) (Thursday, 29 December)
• Re: [whatwg/streams] Meta: add a service worker to the spec (#637) (Thursday, 29 December)
• [whatwg/streams] Meta: add a service worker to the spec (#637) (Thursday, 29 December)
• Re: [whatwg/url] Add non-special-URL hosts (#185) (Thursday, 29 December)
• Re: [whatwg/url] Add non-special-URL hosts (#185) (Thursday, 29 December)
• Re: [whatwg/url] No need for null passwords (#186) (Thursday, 29 December)
• Re: [whatwg/url] URLSearchParams delete and iterator ambiguity (#188) (Wednesday, 28 December)
• Re: [whatwg/url] Add non-special-URL hosts (#185) (Wednesday, 28 December)
• Re: [whatwg/url] Add non-special-URL hosts (#185) (Wednesday, 28 December)
• Re: [whatwg/url] No need for null passwords (#186) (Wednesday, 28 December)
• Re: [whatwg/url] empty auth vs no auth -- same? (#181) (Wednesday, 28 December)
• Re: [heycam/webidl] Consider simplifying serializers (#188) (Thursday, 22 December)
• Re: [heycam/webidl] Consider simplifying serializers (#188) (Wednesday, 21 December)
• Re: [whatwg/streams] don't invoke [[strategySize]] as method (#635) (Wednesday, 21 December)
• Re: [whatwg/streams] don't invoke [[strategySize]] as method (#635) (Wednesday, 21 December)
• Re: [whatwg/streams] Do not allow abort to happen when a close is about to happen (#634) (Wednesday, 21 December)
• Re: [whatwg/url] What to do with /reference-implementation/ (#162) (Tuesday, 20 December)
• Re: [heycam/webidl] Should mixins be able to add overloads? (#261) (Monday, 19 December)
• Re: [whatwg/streams] alert underlyingSink when [[strategySize]]() fails (#628) (Monday, 19 December)
• Re: [whatwg/streams] Define valid queuing strategy (#427) (Monday, 19 December)
• [whatwg/streams] Do not allow abort to happen when a close is about to happen (#634) (Monday, 19 December)
• Re: [heycam/webidl] Adding slots [initial braindump] (#258) (Monday, 19 December)
• Re: [w3c/clipboard-apis] Where would one get a DataTransfer to hand to the ClipboardEvent constructor? (#33) (Monday, 19 December)
• Re: [whatwg/url] Editorial: add some URL parsing examples (#177) (Monday, 19 December)
• Re: [whatwg/url] Editorial: add some URL parsing examples (#177) (Monday, 19 December)
• Re: [whatwg/url] Editorial: add some URL parsing examples (#177) (Monday, 19 December)
• Re: [w3c/clipboard-apis] Where would one get a DataTransfer to hand to the ClipboardEvent constructor? (#33) (Monday, 19 December)
• Re: [w3c/webcomponents] Can't reuse custom element constructors? (#618) (Monday, 19 December)
• Re: [whatwg/url] Editorial: add some URL parsing examples (#177) (Monday, 19 December)
• Re: [whatwg/url] Editorial: add some URL parsing examples (#177) (Monday, 19 December)
• Re: [whatwg/url] Editorial: clarify the "shorten a path" algorithm (#174) (Monday, 19 December)
• Re: [whatwg/url] Editorial: clarify the "shorten a path" algorithm (#174) (Monday, 19 December)
• Re: [whatwg/url] Editorial: add some URL parsing examples (#177) (Monday, 19 December)
• Re: [w3c/clipboard-apis] Where would one get a DataTransfer to hand to the ClipboardEvent constructor? (#33) (Monday, 19 December)
• [whatwg/url] Editorial: clarify the "shorten a path" algorithm (#174) (Monday, 19 December)
• [whatwg/url] Editorial: extra "and" in IPv4 parser (#173) (Sunday, 18 December)
• [whatwg/streams] Consolidate "closing" state and [[pendingClosePromise]]? (#633) (Friday, 16 December)
• [whatwg/streams] Do not allow abort() to interrupt a closing writable stream? (#632) (Friday, 16 December)
• [whatwg/streams] Remove fallback from underlying sink abort to close (#631) (Friday, 16 December)
• Re: [whatwg/streams] alert underlyingSink when [[strategySize]]() fails (#628) (Friday, 16 December)
• Re: [whatwg/streams] Start work on a polyfill? (#630) (Friday, 16 December)
• Re: [whatwg/streams] Specify WritableStream.[[Transfer]] (#629) (Friday, 16 December)
• Re: [whatwg/streams] skip WPT dir if not present (#608) (Friday, 16 December)
• Re: [whatwg/streams] skip WPT dir if not present (#608) (Friday, 16 December)
• Re: [whatwg/streams] Fix missing comma in example (#627) (Friday, 16 December)
• Re: [whatwg/streams] Fix missing comma in example (#627) (Friday, 16 December)
• Re: [whatwg/streams] Make run-web-platform-tests.js take glob patterns to filter tests (#625) (Friday, 16 December)
• [w3c/ServiceWorker] Why are only a subset of JS mime types allowed? (#1033) (Friday, 16 December)
• Re: [w3c/ServiceWorker] Content-Type requirement of service worker importScripts() (#1032) (Friday, 16 December)
• Re: [whatwg/dom] Point to IndexedDB for DOMStringList (#385) (Friday, 16 December)
• Re: [w3c/IndexedDB] DOMStringList should have [Exposed=(Window,Worker)] (#118) (Thursday, 15 December)
• Re: [w3c/ServiceWorker] Include imported scripts to byte-check (#1023) (Thursday, 15 December)
• Re: [whatwg/dom] Point to IndexedDB for DOMStringList (#385) (Thursday, 15 December)
• Re: [heycam/webidl] Split DOMException back into IDL type and DFN. (#257) (Wednesday, 14 December)
• [heycam/webidl] "For `DOMExceptions`" (#255) (Tuesday, 13 December)
• Re: [whatwg/streams] Specify ReadableStream.[[Transfer]] (#623) (Tuesday, 13 December)
• Re: [w3c/webcomponents] CE reaction queue's not-really-sync behavior doesn't provide strong enough guarantees about when reactions occur (#616) (Monday, 12 December)
• Re: [heycam/webidl] Are operations on the `[[BackingMap]]` and `[[BackingSet]]` page-hookable? And if not, why not? (#254) (Monday, 12 December)
• Re: [heycam/webidl] Are operations on the `[[BackingMap]]` and `[[BackingSet]]` page-hookable? And if not, why not? (#254) (Monday, 12 December)
• Re: [heycam/webidl] Are operations on the `[[BackingMap]]` and `[[BackingSet]]` page-hookable? And if not, why not? (#254) (Monday, 12 December)
• Re: [heycam/webidl] Are operations on the `[[BackingMap]]` and `[[BackingSet]]` page-hookable? And if not, why not? (#254) (Monday, 12 December)
• Re: [heycam/webidl] Are operations on the `[[BackingMap]]` and `[[BackingSet]]` page-hookable? And if not, why not? (#254) (Monday, 12 December)
• Re: [whatwg/streams] Fix missing comma in example (#627) (Monday, 12 December)
• Re: [whatwg/streams] Fix missing comma in example (#627) (Monday, 12 December)
• Re: [w3c/webcomponents] How should autofill work for inputs generated inside shadow roots (#572) (Monday, 12 December)
• Re: [heycam/webidl] Exception cleanup (#250) (Friday, 9 December)
• Re: [heycam/webidl] Exception cleanup (#250) (Friday, 9 December)
• Re: [whatwg/streams] Specify ReadableStream.[[Transfer]] (#623) (Friday, 9 December)
• Re: [heycam/webidl] Exception cleanup (#250) (Friday, 9 December)
• [heycam/webidl] Clarify "The Type must not identify the same or another typedef." (#252) (Friday, 9 December)
• Re: [heycam/webidl] Exception cleanup (#250) (Thursday, 8 December)
• Re: [heycam/webidl] Exception cleanup (#250) (Thursday, 8 December)
• Re: [heycam/webidl] Exception cleanup (#250) (Thursday, 8 December)
• Re: [heycam/webidl] Add missing legacy error names. (#251) (Thursday, 8 December)
• Re: [heycam/webidl] Disallow nullable Promise types. (#248) (Thursday, 8 December)
• Re: [heycam/webidl] Disallow nullable Promise types. (#248) (Thursday, 8 December)
• Re: [heycam/webidl] Disallow nullable Promise types. (#248) (Thursday, 8 December)
• Re: [whatwg/streams] Specify ReadableStream.[[Transfer]] (#623) (Thursday, 8 December)
• Re: [whatwg/streams] Do not leak the closed promise on errored release (#626) (Thursday, 8 December)
• Re: [whatwg/streams] Do not leak the closed promise on errored release (#626) (Thursday, 8 December)
• [heycam/webidl] Change the recommended language for DOMExceptions (#247) (Thursday, 8 December)
• Re: [heycam/webidl] Deprecate InvalidAccessError. (#246) (Thursday, 8 December)
• Re: [w3c/webcomponents] How should autofill work for inputs generated inside shadow roots (#572) (Wednesday, 7 December)
• Re: [whatwg/storage] Error handling in estimate() (#38) (Wednesday, 7 December)
• Re: [w3c/IndexedDB] Add non-normative documentation for methods/properties. (#121) (Tuesday, 6 December)
• Re: [w3c/webcomponents] How should autofill work for inputs generated inside shadow roots (#572) (Tuesday, 6 December)
• Re: [w3c/webcomponents] How should autofill work for inputs generated inside shadow roots (#572) (Tuesday, 6 December)
• Re: [w3c/webcomponents] How should autofill work for inputs generated inside shadow roots (#572) (Tuesday, 6 December)
• Re: [w3c/webcomponents] How should autofill work for inputs generated inside shadow roots (#572) (Tuesday, 6 December)
• Re: [w3c/webcomponents] How should autofill work for inputs generated inside shadow roots (#572) (Tuesday, 6 December)
• Re: [w3c/ServiceWorker] ServiceWorker lifetime and respondWith() with a user-constructed ReadableStream (#882) (Tuesday, 6 December)
• Re: [w3c/ServiceWorker] DO NOT MERGE: using better link defaults (#995) (Tuesday, 6 December)
• Re: [w3c/ServiceWorker] DO NOT MERGE: using better link defaults (#995) (Tuesday, 6 December)
• Re: [whatwg/fetch] See if resource exists (#428) (Monday, 5 December)
• Re: [whatwg/streams] Remove ZERO WIDTH JOINER characters (#624) (Monday, 5 December)
• Re: [whatwg/streams] Reference defining "transforming [promise] by a fulfillment handler" ? (#622) (Saturday, 3 December)
• Re: [whatwg/streams] Aborting a stream should wait for pending writes (#619) (Saturday, 3 December)
• Re: [whatwg/streams] Why are [[writeRequests]] and [[queue]] separate? (#589) (Saturday, 3 December)
• Re: [w3c/IndexedDB] Reword DOMException throwing (#125) (Friday, 2 December)
• Re: [w3c/IndexedDB] Add non-normative documentation for methods/properties. (#121) (Friday, 2 December)
• Re: [w3c/IndexedDB] Add non-normative documentation for methods/properties. (#121) (Friday, 2 December)

Dominic Cooney

• Re: [w3c/webcomponents] Consider adding a childrenChangedCallback or something (#619) (Wednesday, 28 December)
• [w3c/webcomponents] Consider adding a childrenChangedCallback or something (#619) (Monday, 26 December)
• Re: [w3c/webcomponents] CE reaction queue's not-really-sync behavior doesn't provide strong enough guarantees about when reactions occur (#616) (Tuesday, 20 December)
• Re: [w3c/webcomponents] CE reaction queue's not-really-sync behavior doesn't provide strong enough guarantees about when reactions occur (#616) (Tuesday, 20 December)

Dominick Ng

• Re: [w3c/manifest] Is it possible to load the progressive web app manifest file from authenticated site? (#535) (Thursday, 8 December)
• Re: [w3c/manifest] Is it possible to load the progressive web app manifest file from authenticated site? (#535) (Thursday, 8 December)
• Re: [w3c/manifest] Is it possible to load the progressive web app manifest file from authenticated site? (#535) (Wednesday, 7 December)

Dominique Hazael-Massieux

• [w3ctag/spec-reviews] WebRTC Stats review (#148) (Tuesday, 20 December)
• Re: [w3c/manifest] [Explainer] Fix cralwers -> crawlers typo (#531) (#532) (Monday, 5 December)

Duan Yao

• Re: [whatwg/fullscreen] Allow fullscreen on initial load of a page (#36) (Friday, 16 December)
• Re: [whatwg/fullscreen] Allow fullscreen on initial load of a page (#36) (Friday, 16 December)
• Re: [whatwg/fullscreen] Allow fullscreen on initial load of a page (#36) (Friday, 16 December)
• Re: [whatwg/fullscreen] Allow fullscreen on initial load of a page (#36) (Friday, 16 December)
• Re: [w3c/manifest] Additional property to define a webapp to be single instance (single-tab) (#479) (Thursday, 15 December)
• Re: [whatwg/fullscreen] Allow fullscreen on initial load of a page (#36) (Thursday, 15 December)
• [whatwg/url] Encode percent(%)s that are not part of a percent-encoded byte when parsing a URL (#170) (Thursday, 8 December)

EduardoRFS

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

Eero Häkkinen

• Re: [whatwg/fetch] Clarify Body package data algorithm with multipart/form-data MIME type (#424) (Friday, 16 December)
• Re: [whatwg/fetch] Clarify Body package data algorithm with multipart/form-data MIME type (#424) (Friday, 9 December)
• Re: [whatwg/fetch] Clarify Body package data algorithm with multipart/form-data MIME type (#424) (Friday, 9 December)
• Re: [whatwg/fetch] Clarify Body package data algorithm with multipart/form-data MIME type (#424) (Monday, 5 December)
• Re: [whatwg/fetch] Clarify Body package data algorithm with multipart/form-data MIME type (#424) (Monday, 5 December)

Eric Bidelman

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

Erik Wilde

• Re: [w3c/manifest] Add info push notifications to extensions registry (#529) (Friday, 2 December)
• Re: [w3c/manifest] Add info push notifications to extensions registry (#529) (Thursday, 1 December)
• Re: [w3c/manifest] Add info push notifications to extensions registry (#529) (Thursday, 1 December)

Erin Dachtler

• [w3c/ServiceWorker] Wasted bandwidth when proxying media (#1044) (Saturday, 31 December)

Florian Rivoal

• Re: [w3c/editing] Should we propose "::caret" pseudo-element to CSS WG? (#158) (Thursday, 8 December)

Francois Marier

• Re: [whatwg/fetch] Should we send an Origin header for no-cors fetches? (#225) (Wednesday, 7 December)

François Daoust

• Re: [w3ctag/spec-reviews] Remote Playback API (#145) (Thursday, 1 December)

Galen-Yip

• Re: [whatwg/fetch] why not add an option of json (#430) (Thursday, 8 December)
• Re: [whatwg/fetch] why not add an option of json (#430) (Thursday, 8 December)
• Re: [whatwg/fetch] why not add an option of json (#430) (Thursday, 8 December)
• [whatwg/fetch] why not add an option of json (#430) (Wednesday, 7 December)

Gary Kacmarcik

• Re: [w3c/clipboard-apis] Pause automatic publication for now (#37) (Thursday, 22 December)
• Re: [w3c/clipboard-apis] Clarify the algorithm for setting target of a clipboard event in 7.2 Processing model for event dispatch (#29) (Tuesday, 20 December)
• Re: [w3c/clipboard-apis] What should happen when copying content with a CANVAS tag in? (#8) (Tuesday, 20 December)
• Re: [w3c/clipboard-apis] Wording around default actions needs updating (#14) (Tuesday, 20 December)
• Re: [w3c/clipboard-apis] Add SVG reference to 3.2 Graphics with built-in semantics (#23) (Tuesday, 20 December)
• Re: [w3c/clipboard-apis] Definition of editing host (#20) (Tuesday, 20 December)
• Re: [w3c/clipboard-apis] Definition of editing host (#20) (Tuesday, 20 December)
• [w3c/clipboard-apis] Clean up test cases (#34) (Tuesday, 20 December)
• Re: [w3c/uievents] Use U+ notation to refer to code points (#127) (Saturday, 17 December)
• Re: [w3c/uievents-key] i18n Issues common to main spec (#34) (Friday, 16 December)
• Re: [w3c/uievents-key] i18n Issues common to main spec (#34) (Friday, 16 December)
• Re: [w3c/uievents-code] i18n Issues common to main spec (#12) (Friday, 16 December)
• Re: [w3c/uievents-code] i18n Issues common to main spec (#12) (Friday, 16 December)
• [w3c/uievents-key] Printable control characters needs refinement (#37) (Friday, 16 December)
• [w3c/uievents-code] Printable control characters needs refinement (#15) (Friday, 16 December)
• [w3c/uievents-key] 'Key value' terminology is ambiguous and confusing (#36) (Friday, 16 December)
• [w3c/uievents-code] 'Key value' terminology is ambiguous and confusing (#14) (Friday, 16 December)
• [w3c/uievents-code] Use U+ notation to refer to code points (#13) (Friday, 16 December)
• [w3c/uievents-key] Use U+ notation to refer to code points (#35) (Friday, 16 December)
• Re: [w3c/clipboard-apis] Use <pre class=idl> for IDL blocks (#31) (Thursday, 1 December)

GrumpyMcGrumperson

• Re: [whatwg/streams] Review request on the ReadableStream API (#433) (Friday, 9 December)
• Re: [whatwg/streams] Review request on the ReadableStream API (#433) (Friday, 9 December)

guest271314

• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Monday, 19 December)
• Re: [whatwg/fetch] upload progress return response.json()? (#389) (Sunday, 18 December)
• [whatwg/fetch] Passing ReadableStream as Request.body to fetch (#439) (Sunday, 18 December)

HapLeo

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

Harald Alvestrand

• Re: [w3c/permissions] Define restrictions on "device-info" permission (from TPAC). (#131) (Friday, 9 December)

Hayato Ito

• Re: [w3c/webcomponents] Is the order of `slotchange` events along a slot chain across node trees defined? (#617) (Saturday, 17 December)
• Re: [w3c/webcomponents] Is the order of `slotchange` events along a slot chain across node trees defined? (#617) (Saturday, 17 December)
• Re: [w3c/webcomponents] How should autofill work for inputs generated inside shadow roots (#572) (Tuesday, 13 December)
• Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78) (Thursday, 8 December)
• Re: [w3c/webcomponents] How should autofill work for inputs generated inside shadow roots (#572) (Wednesday, 7 December)
• Re: [w3c/webcomponents] How should autofill work for inputs generated inside shadow roots (#572) (Wednesday, 7 December)
• Re: [w3c/webcomponents] How should autofill work for inputs generated inside shadow roots (#572) (Tuesday, 6 December)
• Re: [w3c/webcomponents] How should autofill work for inputs generated inside shadow roots (#572) (Tuesday, 6 December)
• Re: [w3c/webcomponents] How should autofill work for inputs generated inside shadow roots (#572) (Tuesday, 6 December)
• Re: [w3c/webcomponents] How should autofill work for inputs generated inside shadow roots (#572) (Tuesday, 6 December)
• Re: [w3c/webcomponents] How should autofill work for inputs generated inside shadow roots (#572) (Tuesday, 6 December)
• Re: [w3c/webcomponents] How should autofill work for inputs generated inside shadow roots (#572) (Tuesday, 6 December)
• Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354) (Tuesday, 6 December)
• Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354) (Tuesday, 6 December)
• Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Tuesday, 6 December)
• Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Tuesday, 6 December)
• Re: [w3c/webcomponents] Extend the slotting algorithm so that a slot can select an element which doesn't have slot attribute. (#343) (Tuesday, 6 December)
• Re: [w3c/webcomponents] Extend the slotting algorithm so that a slot can select an element which doesn't have slot attribute. (#343) (Tuesday, 6 December)
• Re: [w3c/webcomponents] Broken wikipedia link for "Green Eye" (#538) (Tuesday, 6 December)
• Re: [w3c/webcomponents] Broken wikipedia link for "Green Eye" (#538) (Tuesday, 6 December)
• Re: [w3c/webcomponents] [Shadow] Slotting indirect children (#574) (Tuesday, 6 December)
• Re: [w3c/webcomponents] [Shadow] Slotting indirect children (#574) (Tuesday, 6 December)
• Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Tuesday, 6 December)
• Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Tuesday, 6 December)
• Re: [w3c/webcomponents] Observe ShadowRoot attachment (#204) (Tuesday, 6 December)
• Re: [w3c/webcomponents] Observe ShadowRoot attachment (#204) (Tuesday, 6 December)
• Re: [w3c/webcomponents] DocumentOrShadowRoot.deepActiveElement (#104) (Tuesday, 6 December)
• Re: [w3c/webcomponents] DocumentOrShadowRoot.deepActiveElement (#104) (Tuesday, 6 December)
• Re: [w3c/webcomponents] How should autofill work for inputs generated inside shadow roots (#572) (Tuesday, 6 December)
• Re: [w3c/webcomponents] How should autofill work for inputs generated inside shadow roots (#572) (Tuesday, 6 December)
• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Tuesday, 6 December)
• Re: [w3c/webcomponents] Is <slot> a replaced element or not? (#564) (Tuesday, 6 December)
• Re: [w3c/webcomponents] Is <slot> a replaced element or not? (#564) (Tuesday, 6 December)
• Re: [w3c/webcomponents] [Idea] Distant ShadowDOM. (#576) (Tuesday, 6 December)
• Re: [w3c/webcomponents] [Idea] Distant ShadowDOM. (#576) (Tuesday, 6 December)
• Re: [w3c/webcomponents] Copying global `<style>` textContent into ShadowDOM roots is not ideal. (#609) (Tuesday, 6 December)
• Re: [w3c/webcomponents] Copying global `<style>` textContent into ShadowDOM roots is not ideal. (#609) (Tuesday, 6 December)
• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Tuesday, 6 December)
• Re: [w3c/webcomponents] [shadow-dom] [spec-bug] in asignedNodes description. (#612) (Monday, 5 December)

HE Shi-Jun

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

Henne2806

• [w3c/touch-events] Initialize touchList in Chrome (#78) (Thursday, 8 December)

Henrik Vendelbo

• [w3c/webcomponents] Further upgrade of custom elements (#620) (Thursday, 29 December)

Huang Xuan

• [w3c/manifest] Relationship between nestedly scoped web app manifests? (#539) (Friday, 23 December)

Ian Kilpatrick

• Re: [w3ctag/spec-reviews] Custom Paint API to CR (#140) (Monday, 19 December)

Ilya Grigorik

• Re: [whatwg/fetch] Add "fetch" as a destination for "connect-src" bound features (#442) (Thursday, 22 December)
• Re: [whatwg/fetch] Split up media into video, audio and track (#437) (Friday, 16 December)
• Re: [whatwg/fetch] Enforce limit on inflight keepalive bytes (#419) (Monday, 5 December)

isonmad

• [w3c/ServiceWorker] Link to v1 in README.md (#1043) (Saturday, 31 December)
• [w3c/ServiceWorker] unclear how Client.postMessage looks up its destination (#1042) (Saturday, 31 December)
• Re: [w3c/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Friday, 30 December)
• Re: [whatwg/streams] Meta: add a service worker to the spec (#637) (Friday, 30 December)
• Re: [w3c/manifest] Define how the manifest is fetched (#481) (Friday, 30 December)
• Re: [whatwg/streams] Specify WritableStream.[[Transfer]] (#629) (Wednesday, 21 December)
• [whatwg/streams] define semantics of {source,sink}.finally() (#636) (Wednesday, 21 December)
• [whatwg/streams] don't invoke [[strategySize]] as method (#635) (Wednesday, 21 December)
• Re: [whatwg/streams] alert underlyingSink when [[strategySize]]() fails (#628) (Friday, 16 December)
• Re: [whatwg/streams] alert underlyingSink when [[strategySize]]() fails (#628) (Tuesday, 13 December)
• Re: [whatwg/streams] Specify WritableStream.[[Transfer]] (#629) (Tuesday, 13 December)
• [whatwg/streams] Specify WritableStream.[[Transfer]] (#629) (Tuesday, 13 December)
• [whatwg/streams] alert underlyingSink when [[strategySize]]() fails (#628) (Tuesday, 13 December)
• Re: [whatwg/streams] Specify ReadableStream.[[Transfer]] (#623) (Tuesday, 13 December)
• Re: [whatwg/streams] Specify ReadableStream.[[Transfer]] (#623) (Tuesday, 13 December)
• Re: [whatwg/streams] Brainstorming a buffer-reusing version of writable streams (#495) (Saturday, 10 December)
• Re: [whatwg/streams] Specify ReadableStream.[[Transfer]] (#623) (Friday, 9 December)
• Re: [whatwg/streams] Specify ReadableStream.[[Transfer]] (#623) (Friday, 9 December)
• Re: [whatwg/streams] Specify ReadableStream.[[Transfer]] (#623) (Friday, 9 December)
• Re: [whatwg/streams] Specify ReadableStream.[[Transfer]] (#623) (Friday, 9 December)
• Re: [whatwg/streams] Specify ReadableStream.[[Transfer]] (#623) (Friday, 9 December)
• [whatwg/streams] Specify ReadableStream.[[Transfer]] (#623) (Sunday, 4 December)

Italo A. Casas

• [whatwg/url] Editorial: removing extra and in IPv4 parser (#180) (Tuesday, 20 December)

Jake Archibald

• Re: [w3c/ServiceWorker] Wasted bandwidth when proxying media (#1044) (Saturday, 31 December)
• Re: [whatwg/fetch] WIP: Changing skip-service-worker flag to use-service-workers enum (#435) (Tuesday, 20 December)
• Re: [w3c/ServiceWorker] reserved Client objects and redirected navigations (#1031) (Monday, 19 December)
• Re: [whatwg/fetch] Only specific APIs should skip the fetch event when called within a service worker (#303) (Friday, 16 December)
• Re: [w3c/ServiceWorker] Consider mechanisms to bypass the service worker for things that we know won't be in it's cache (#1026) (Friday, 16 December)
• Re: [w3c/ServiceWorker] Consider providing `navigation` event (#1028) (Friday, 16 December)
• Re: [w3c/ServiceWorker] (WIP) Navigation preload (#983) (Friday, 16 December)
• Re: [w3c/ServiceWorker] (WIP) Navigation preload (#983) (Friday, 16 December)
• Re: [w3c/ServiceWorker] (WIP) Navigation preload (#983) (Friday, 16 December)
• Re: [w3c/ServiceWorker] Opt cache.add/addAll and importScripts out of a local service worker (#1025) (Friday, 16 December)
• Re: [w3c/ServiceWorker] (WIP) Navigation preload (#983) (Friday, 16 December)
• Re: [whatwg/fetch] WIP: Changing skip-service-worker flag to use-service-workers enum (#435) (Friday, 16 December)
• Re: [whatwg/fetch] WIP: Changing skip-service-worker flag to use-service-workers enum (#435) (Friday, 16 December)
• Re: [whatwg/fetch] WIP: Changing skip-service-worker flag to use-service-workers enum (#435) (Friday, 16 December)
• Re: [w3c/ServiceWorker] Consider providing `navigation` event (#1028) (Friday, 16 December)
• Re: [w3c/ServiceWorker] Consider providing `navigation` event (#1028) (Friday, 16 December)
• Re: [w3c/ServiceWorker] Consider mechanisms to bypass the service worker for things that we know won't be in it's cache (#1026) (Friday, 16 December)
• Re: [whatwg/fetch] WIP: Making a skip-local-service-worker flag (#435) (Friday, 16 December)
• Re: [w3c/ServiceWorker] (WIP) Navigation preload (#983) (Friday, 16 December)
• Re: [w3c/ServiceWorker] (WIP) Navigation preload (#983) (Friday, 16 December)
• Re: [w3c/ServiceWorker] (WIP) Navigation preload (#983) (Friday, 16 December)
• Re: [w3c/ServiceWorker] (WIP) Navigation preload (#983) (Friday, 16 December)
• Re: [w3c/ServiceWorker] Opt cache.add/addAll and importScripts out of a local service worker (#1025) (Friday, 16 December)
• Re: [whatwg/fetch] Only specific APIs should skip the fetch event when called within a service worker (#303) (Friday, 16 December)
• Re: [whatwg/fetch] Aborting a fetch (#27) (Friday, 16 December)
• Re: [whatwg/fetch] Aborting a fetch (#27) (Friday, 16 December)
• Re: [whatwg/fetch] Only specific APIs should skip the fetch event when called within a service worker (#303) (Friday, 16 December)
• Re: [whatwg/fetch] Aborting a fetch (#27) (Thursday, 15 December)
• Re: [w3c/ServiceWorker] Opt cache.add/addAll and importScripts out of a local service worker (#1025) (Thursday, 15 December)
• Re: [whatwg/fetch] WIP: Making a skip-local-service-worker flag (#435) (Thursday, 15 December)
• Re: [w3c/ServiceWorker] activation of the Service Worker on an iframe context (#1029) (Thursday, 15 December)
• Re: [w3c/ServiceWorker] Opt cache.add/addAll and importScripts out of a local service worker (#1025) (Thursday, 15 December)
• Re: [w3c/ServiceWorker] Opt cache.add/addAll and importScripts out of a local service worker (#1025) (Thursday, 15 December)
• Re: [whatwg/fetch] WIP: Making a skip-local-service-worker flag (#435) (Thursday, 15 December)
• Re: [w3c/ServiceWorker] Opt cache.add/addAll and importScripts out of a local service worker (#1025) (Thursday, 15 December)
• Re: [w3c/ServiceWorker] (WIP) Navigation preload (#983) (Wednesday, 14 December)
• Re: [w3c/ServiceWorker] Include imported scripts to byte-check (#1023) (Wednesday, 14 December)
• Re: [w3c/ServiceWorker] Include imported scripts to byte-check (#1023) (Wednesday, 14 December)
• [w3c/ServiceWorker] Ensuring no-cache is set on module imported scripts (#1027) (Wednesday, 14 December)
• Re: [w3c/ServiceWorker] Include imported scripts to byte-check (#1023) (Wednesday, 14 December)
• Re: [w3c/ServiceWorker] Include imported scripts to byte-check (#1023) (Wednesday, 14 December)
• Re: [w3c/ServiceWorker] Include imported scripts to byte-check (#1023) (Wednesday, 14 December)
• Re: [w3c/ServiceWorker] Opt cache.add/addAll and importScripts out of a local service worker (#1025) (Tuesday, 13 December)
• Re: [whatwg/fetch] WIP: Making a skip-local-service-worker flag (#435) (Tuesday, 13 December)
• [w3c/ServiceWorker] Opt cache.add/addAll and importScripts out of a local service worker (#1025) (Tuesday, 13 December)
• Re: [whatwg/fetch] WIP: Making a skip-local-service-worker flag (#435) (Tuesday, 13 December)
• Re: [whatwg/fetch] WIP: Making a skip-local-service-worker flag (#435) (Tuesday, 13 December)
• [whatwg/fetch] WIP: Making a skip-local-service-worker flag (#435) (Tuesday, 13 December)
• Re: [w3c/ServiceWorker] Include imported scripts to byte-check (#1023) (Tuesday, 13 December)
• Re: [w3c/ServiceWorker] Include imported scripts to byte-check (#1023) (Tuesday, 13 December)
• Re: [w3c/ServiceWorker] Include imported scripts to byte-check (#1023) (Tuesday, 13 December)
• Re: [w3c/ServiceWorker] consider allowing static routing only for "foreign fetch" for anonymous requests (#1024) (Tuesday, 13 December)
• Re: [w3c/ServiceWorker] When should "imported scripts updated flag" be unset? (#1021) (Tuesday, 13 December)
• Re: [w3c/ServiceWorker] When should "imported scripts updated flag" be unset? (#1021) (Tuesday, 13 December)
• Re: [w3c/ServiceWorker] When should "imported scripts updated flag" be unset? (#1021) (Monday, 12 December)
• Re: [w3c/ServiceWorker] When should "imported scripts updated flag" be unset? (#1021) (Monday, 12 December)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Monday, 12 December)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Saturday, 10 December)
• Re: [whatwg/streams] Review request on the ReadableStream API (#433) (Friday, 9 December)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Friday, 9 December)
• Re: [w3c/ServiceWorker] When should "imported scripts updated flag" be unset? (#1021) (Friday, 9 December)
• Re: [w3c/ServiceWorker] Fetch service worker scripts with "no-cache" by default (#1020) (Friday, 9 December)
• Re: [w3c/ServiceWorker] Fetch service worker scripts with "no-cache" by default (#1020) (Friday, 9 December)
• Re: [w3c/ServiceWorker] Fetch service worker scripts with "no-cache" by default (#1020) (Thursday, 8 December)
• Re: [w3c/ServiceWorker] Fetch service worker scripts with "no-cache" by default (#1020) (Thursday, 8 December)
• Re: [w3c/ServiceWorker] Fetch service worker scripts with "no-cache" by default (#1020) (Thursday, 8 December)
• Re: [whatwg/fetch] why not add an option of json (#430) (Thursday, 8 December)
• Re: [w3c/ServiceWorker] When should "imported scripts updated flag" be unset? (#1021) (Thursday, 8 December)
• Re: [whatwg/fetch] why not add an option of json (#430) (Wednesday, 7 December)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Wednesday, 7 December)
• Re: [w3c/ServiceWorker] When should "imported scripts updated flag" be unset? (#1021) (Wednesday, 7 December)
• [w3c/ServiceWorker] When should "imported scripts updated flag" be unset? (#1021) (Wednesday, 7 December)
• Re: [w3c/ServiceWorker] Fetch service worker scripts with "no-cache" by default (#1020) (Tuesday, 6 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Monday, 5 December)
• Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920) (Friday, 2 December)
• [w3c/push-api] Reject if there's no active service worker (#230) (Friday, 2 December)
• Re: [w3c/ServiceWorker] (WIP) Navigation preload (#983) (Friday, 2 December)
• Re: [w3c/ServiceWorker] allow service worker produced resources to be marked as "cachable" (#962) (Friday, 2 December)
• Re: [w3c/ServiceWorker] clientId on ForeignFetchEvents (#1017) (Friday, 2 December)
• Re: [w3c/ServiceWorker] Lots of bikeshed usage issues (#965) (Friday, 2 December)
• Re: [w3c/ServiceWorker] Lots of bikeshed usage issues (#965) (Friday, 2 December)
• Re: [w3c/ServiceWorker] Add client.type (#1018) (Friday, 2 December)
• Re: [w3c/ServiceWorker] Change behavior of skipWaiting() (#1019) (Friday, 2 December)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Thursday, 1 December)
• Re: [w3c/ServiceWorker] (WIP) Bikeshed cleanup (#1014) (Thursday, 1 December)

James M Snell

• Re: [whatwg/url] URLSearchParams delete and iterator ambiguity (#188) (Wednesday, 28 December)
• Re: [whatwg/url] URLSearchParams delete and iterator ambiguity (#188) (Wednesday, 28 December)
• Re: [whatwg/url] URLSearchParams delete and iterator ambiguity (#188) (Wednesday, 28 December)
• [whatwg/url] URLSearchParams delete and iterator ambiguity (#188) (Wednesday, 28 December)

jan-ivar

• Re: [heycam/webidl] Consider simplifying serializers (#188) (Wednesday, 21 December)
• Re: [w3c/permissions] Drop .request() (#83) (Monday, 12 December)

Johannes Wilm

• Re: [w3c/editing] Should we propose "::caret" pseudo-element to CSS WG? (#158) (Friday, 9 December)

John-David Dalton

• Re: [whatwg/fetch] Make Request constructor more forgiving (#377) (Thursday, 15 December)

Joseph Orbegoso Pea

• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Saturday, 24 December)
• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Saturday, 24 December)
• Re: [w3c/webcomponents] Is the order of `slotchange` events along a slot chain across node trees defined? (#617) (Saturday, 17 December)
• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Saturday, 17 December)
• Re: [w3c/webcomponents] Is the order of `slotchange` events along a slot chain across node trees defined? (#617) (Friday, 16 December)
• [w3c/webcomponents] Is the order of `slotchange` events along a slot chain across node trees defined? (#617) (Friday, 16 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 14 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 12 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 12 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 11 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Friday, 9 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 8 December)
• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Tuesday, 6 December)
• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Tuesday, 6 December)
• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Tuesday, 6 December)
• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Tuesday, 6 December)
• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Tuesday, 6 December)
• Re: [w3c/webcomponents] [shadow-dom] [spec-bug] in asignedNodes description. (#612) (Sunday, 4 December)
• Re: [w3c/webcomponents] defining and instantiating customized built‐in elements as if they were autonomous custom elements (#613) (Sunday, 4 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 4 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 4 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 4 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 4 December)
• Re: [w3c/webcomponents] [idea] [shadow-dom] Provide a version number on shadow roots so they can be distinguished. (#610) (Sunday, 4 December)
• Re: [w3c/webcomponents] [idea] [shadow-dom] Provide a version number on shadow roots so they can be distinguished. (#610) (Friday, 2 December)
• Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Friday, 2 December)
• Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Thursday, 1 December)
• Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Thursday, 1 December)

Josh Matthews

• Re: [whatwg/fetch] Make Request constructor more forgiving (#377) (Thursday, 15 December)
• Re: [whatwg/fetch] Make Request constructor more forgiving (#377) (Thursday, 15 December)

Joshua Bell

• Re: [w3c/IndexedDB] Specify timing of transaction deactivation more precisely (#87) (Friday, 30 December)
• Re: [w3c/IndexedDB] Negative counts have inconsistent behavior in getAll()/getAllKeys() (#131) (Friday, 23 December)
• Re: [w3c/IndexedDB] Negative counts have inconsistent behavior in getAll()/getAllKeys() (#131) (Friday, 23 December)
• Re: [w3c/IndexedDB] transaction should either take DOMStringList or DOMStringList needs to be iterable (#85) (Tuesday, 20 December)
• Re: [w3c/IndexedDB] transaction should either take DOMStringList or DOMStringList needs to be iterable (#85) (Sunday, 18 December)
• Re: [w3c/IndexedDB] Clarify the conditions for running create/deleteObjectStore() (#129) (Friday, 16 December)
• Re: [w3c/IndexedDB] Clarify the conditions for running create/deleteObjectStore() (#129) (Friday, 16 December)
• [w3c/IndexedDB] Clarify the conditions for running create/deleteObjectStore() (#129) (Friday, 16 December)
• Re: [w3c/IndexedDB] Specify timing of transaction deactivation more precisely (#87) (Thursday, 15 December)
• Re: [w3c/IndexedDB] DOMStringList should have [Exposed=(Window,Worker)] (#118) (Thursday, 15 December)
• Re: [w3c/IndexedDB] transaction should either take DOMStringList or DOMStringList needs to be iterable (#85) (Thursday, 15 December)
• Re: [w3c/IndexedDB] DOMStringList should have [Exposed=(Window,Worker)] (#118) (Thursday, 15 December)
• Re: [w3c/IndexedDB] DOMStringList has been removed from DOM (#28) (Wednesday, 14 December)
• Re: [w3c/IndexedDB] Remove DOMStringList (#128) (Tuesday, 13 December)
• Re: [w3c/IndexedDB] Remove DOMStringList (#128) (Tuesday, 13 December)
• Re: [whatwg/xhr] Make FormData a cloneable object (#55) (Monday, 12 December)
• Re: [w3c/IndexedDB] Add non-normative documentation for methods/properties. Resolves #110 (61ad40a) (Tuesday, 6 December)
• Re: [w3c/IndexedDB] Reword DOMException throwing (#125) (Tuesday, 6 December)
• Re: [w3c/IndexedDB] Reword DOMException throwing (#124) (Tuesday, 6 December)
• Re: [w3c/IndexedDB] Add non-normative documentation for methods/properties. (#121) (Tuesday, 6 December)
• Re: [w3c/IndexedDB] Add non-normative docs for APIs (#110) (Tuesday, 6 December)
• Re: [w3c/IndexedDB] Add non-normative documentation for methods/properties. (#121) (Tuesday, 6 December)
• Re: [w3c/IndexedDB] Parity between key retrieval steps and type conversions (#122) (Tuesday, 6 December)
• Re: [w3c/IndexedDB] Parity between single and multiple key retrieval steps (converting key to a value) (#107) (Tuesday, 6 December)
• Re: [w3c/IndexedDB] Add travis-ci config (#127) (Tuesday, 6 December)
• Re: [w3c/IndexedDB] Add travis-ci config (#127) (Tuesday, 6 December)
• Re: [w3c/IndexedDB] Add travis-ci config (#127) (Tuesday, 6 December)
• Re: [w3c/IndexedDB] Add travis-ci config (#127) (Tuesday, 6 December)
• [w3c/IndexedDB] Add travis-ci config (#127) (Tuesday, 6 December)
• Re: [w3c/IndexedDB] Parity between key retrieval steps and type conversions (#122) (Tuesday, 6 December)
• Re: [w3c/IndexedDB] Parity between key retrieval steps and type conversions (#122) (Tuesday, 6 December)
• Re: [w3c/IndexedDB] Add support for async update or another way to prepopulate the databade (#126) (Monday, 5 December)
• Re: [w3c/IndexedDB] Add support for async update or another way to prepopulate the databade (#126) (Monday, 5 December)
• Re: [w3c/IndexedDB] Add support for async update or another way to prepopulate the databade (#126) (Monday, 5 December)
• [w3c/IndexedDB] Reword DOMException throwing (#125) (Friday, 2 December)
• [w3c/IndexedDB] Reword DOMException throwing (#124) (Friday, 2 December)
• Re: [w3c/IndexedDB] Add non-normative documentation for methods/properties. (#121) (Friday, 2 December)
• Re: [w3c/IndexedDB] Add non-normative documentation for methods/properties. (#121) (Friday, 2 December)
• Re: [w3c/IndexedDB] Add non-normative documentation for methods/properties. (#121) (Friday, 2 December)
• Re: [w3c/IndexedDB] Tiny grammar mistake (#123) (Friday, 2 December)
• Re: [w3c/IndexedDB] Add non-normative documentation for methods/properties. (#121) (Friday, 2 December)
• Re: [w3c/IndexedDB] TLS is the new SSL (#119) (Friday, 2 December)
• Re: [w3c/IndexedDB] Change SSL references to TLS (#120) (Friday, 2 December)
• Re: [w3c/IndexedDB] Parity between key retrieval steps and type conversions (#122) (Friday, 2 December)
• Re: [w3c/IndexedDB] Parity between key retrieval steps and type conversions (#122) (Friday, 2 December)
• [w3c/IndexedDB] Parity between key retrieval steps and type conversions (#122) (Friday, 2 December)
• [w3c/IndexedDB] Add non-normative documentation for methods/properties. (#121) (Friday, 2 December)
• Re: [w3c/IndexedDB] Change SSL references to TLS (#120) (Friday, 2 December)
• Re: [w3c/IndexedDB] TLS is the new SSL (#119) (Thursday, 1 December)
• [w3c/IndexedDB] Change SSL references to TLS (#120) (Thursday, 1 December)

Jungkee Song

• Re: [w3c/ServiceWorker] async waitUntil() does not allow extension on final promise resolution? (#1039) (Friday, 23 December)
• Re: [w3c/ServiceWorker] reserved Client objects and redirected navigations (#1031) (Thursday, 22 December)
• Re: [w3c/ServiceWorker] reserved Client objects and redirected navigations (#1031) (Wednesday, 21 December)
• Re: [w3c/ServiceWorker] what should Client.url return for a reserved Worker Client? (#1034) (Wednesday, 21 December)
• Re: [w3c/ServiceWorker] what should Client.url return for a reserved Worker Client? (#1034) (Tuesday, 20 December)
• Re: [w3c/ServiceWorker] reserved Client objects and redirected navigations (#1031) (Tuesday, 20 December)
• [w3c/ServiceWorker] postMessage() to a reserved client throws (#1035) (Monday, 19 December)
• Re: [w3c/ServiceWorker] reserved Client objects and redirected navigations (#1031) (Monday, 19 December)
• Re: [w3c/ServiceWorker] what should Client.url return for a reserved Worker Client? (#1034) (Monday, 19 December)
• Re: [w3c/ServiceWorker] what should Client.url return for a reserved Worker Client? (#1034) (Monday, 19 December)
• Re: [w3c/ServiceWorker] what should Client.url return for a reserved Worker Client? (#1034) (Monday, 19 December)
• Re: [w3c/ServiceWorker] reserved Client objects and redirected navigations (#1031) (Monday, 19 December)
• Re: [w3c/ServiceWorker] what should Client.url return for a reserved Worker Client? (#1034) (Monday, 19 December)
• Re: [w3c/ServiceWorker] Client.reserved references wrong context state? (#1030) (Monday, 19 December)
• Re: [w3c/ServiceWorker] what should Client.url return for a reserved Worker Client? (#1034) (Monday, 19 December)
• Re: [w3c/ServiceWorker] Navigation preload (#983) (Friday, 16 December)
• Re: [w3c/ServiceWorker] (WIP) Navigation preload (#983) (Friday, 16 December)
• Re: [w3c/ServiceWorker] (WIP) Navigation preload (#983) (Friday, 16 December)
• Re: [w3c/ServiceWorker] (WIP) Navigation preload (#983) (Friday, 16 December)
• Re: [w3c/ServiceWorker] (WIP) Navigation preload (#983) (Friday, 16 December)
• Re: [w3c/ServiceWorker] (WIP) Navigation preload (#983) (Friday, 16 December)
• Re: [w3c/ServiceWorker] (WIP) Navigation preload (#983) (Friday, 16 December)
• Re: [w3c/ServiceWorker] Include imported scripts to byte-check (#1023) (Friday, 16 December)
• Re: [whatwg/fetch] Only specific APIs should skip the fetch event when called within a service worker (#303) (Friday, 16 December)
• Re: [w3c/ServiceWorker] (WIP) Navigation preload (#983) (Friday, 16 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Thursday, 15 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Thursday, 15 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Thursday, 15 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Thursday, 15 December)
• Re: [w3c/ServiceWorker] (WIP) Navigation preload (#983) (Thursday, 15 December)
• Re: [w3c/ServiceWorker] Opt cache.add/addAll and importScripts out of a local service worker (#1025) (Thursday, 15 December)
• Re: [w3c/ServiceWorker] Opt cache.add/addAll and importScripts out of a local service worker (#1025) (Thursday, 15 December)
• Re: [w3c/ServiceWorker] Opt cache.add/addAll and importScripts out of a local service worker (#1025) (Thursday, 15 December)
• Re: [w3c/ServiceWorker] Opt cache.add/addAll and importScripts out of a local service worker (#1025) (Thursday, 15 December)
• Re: [w3c/ServiceWorker] Ensuring no-cache is set on module imported scripts (#1027) (Thursday, 15 December)
• Re: [w3c/ServiceWorker] Ensuring no-cache is set on module imported scripts (#1027) (Thursday, 15 December)
• Re: [w3c/ServiceWorker] Include imported scripts to byte-check (#1023) (Thursday, 15 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 14 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 14 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 14 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 14 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 14 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 14 December)
• Re: [w3c/ServiceWorker] Include imported scripts to byte-check (#1023) (Wednesday, 14 December)
• Re: [w3c/ServiceWorker] Include imported scripts to byte-check (#1023) (Wednesday, 14 December)
• Re: [w3c/ServiceWorker] Include imported scripts to byte-check (#1023) (Wednesday, 14 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 14 December)
• Re: [w3c/ServiceWorker] Include imported scripts to byte-check (#1023) (Wednesday, 14 December)
• Re: [w3c/ServiceWorker] Include imported scripts to byte-check (#1023) (Wednesday, 14 December)
• Re: [w3c/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Tuesday, 13 December)
• Re: [w3c/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Tuesday, 13 December)
• Re: [w3c/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Tuesday, 13 December)
• Re: [w3c/ServiceWorker] Sort out settings object for service worker module scripts (#1013) (Tuesday, 13 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Tuesday, 13 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Tuesday, 13 December)
• Re: [w3c/ServiceWorker] When should "imported scripts updated flag" be unset? (#1021) (Tuesday, 13 December)
• Re: [w3c/ServiceWorker] When should "imported scripts updated flag" be unset? (#1021) (Tuesday, 13 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Tuesday, 13 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Tuesday, 13 December)
• Re: [w3c/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Tuesday, 13 December)
• Re: [w3c/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Tuesday, 13 December)
• Re: [w3c/ServiceWorker] When should "imported scripts updated flag" be unset? (#1021) (Monday, 12 December)
• [w3c/ServiceWorker] Include imported scripts to byte-check (#1023) (Monday, 12 December)
• Re: [w3c/ServiceWorker] Include imported scripts to byte-check (#1023) (Monday, 12 December)
• Re: [w3c/ServiceWorker] potential http cache issues with importScripts() (#894) (Monday, 12 December)
• Re: [w3c/ServiceWorker] potential http cache issues with importScripts() (#894) (Monday, 12 December)
• Re: [w3c/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Monday, 12 December)
• Re: [w3c/ServiceWorker] Fetch service worker scripts with "no-cache" by default (#1020) (Monday, 12 December)
• Re: [w3c/ServiceWorker] When should "imported scripts updated flag" be unset? (#1021) (Monday, 12 December)
• Re: [w3c/ServiceWorker] Fetch service worker scripts with "no-cache" by default (#1020) (Friday, 9 December)
• Re: [w3c/ServiceWorker] Fetch service worker scripts with "no-cache" by default (#1020) (Friday, 9 December)
• Re: [w3c/ServiceWorker] Fetch service worker scripts with "no-cache" by default (#1020) (Friday, 9 December)
• Re: [w3c/ServiceWorker] Fetch service worker scripts with "no-cache" by default (#1020) (Thursday, 8 December)
• Re: [w3c/ServiceWorker] Fetch service worker scripts with "no-cache" by default (#1020) (Thursday, 8 December)
• Re: [w3c/ServiceWorker] Fetch service worker scripts with "no-cache" by default (#1020) (Thursday, 8 December)
• Re: [w3c/ServiceWorker] When should "imported scripts updated flag" be unset? (#1021) (Thursday, 8 December)
• Re: [w3c/ServiceWorker] potential http cache issues with importScripts() (#894) (Tuesday, 6 December)
• Re: [w3c/ServiceWorker] Fetch service worker scripts with "no-cache" by default (#1020) (Tuesday, 6 December)
• Re: [w3c/ServiceWorker] Fetch service worker scripts with "no-cache" by default (#1020) (Tuesday, 6 December)
• [w3c/ServiceWorker] Fetch service worker scripts with "no-cache" by default (#1020) (Tuesday, 6 December)
• Re: [w3c/ServiceWorker] potential http cache issues with importScripts() (#894) (Monday, 5 December)
• Re: [w3c/ServiceWorker] potential http cache issues with importScripts() (#894) (Monday, 5 December)
• Re: [w3c/ServiceWorker] Change behavior of skipWaiting() (#1019) (Friday, 2 December)
• Re: [w3c/ServiceWorker] consider exposing a type attribute on Client (#1005) (Friday, 2 December)
• Re: [w3c/ServiceWorker] Add client.type (#1018) (Friday, 2 December)
• Re: [w3c/ServiceWorker] Change behavior of skipWaiting() (#1019) (Friday, 2 December)
• [w3c/ServiceWorker] Change behavior of skipWaiting() (#1019) (Friday, 2 December)
• [w3c/ServiceWorker] Add client.type (#1018) (Friday, 2 December)

Justin Ridgewell

• [w3c/ServiceWorker] clientId on ForeignFetchEvents (#1017) (Friday, 2 December)

Kenneth Rohde Christiansen

• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 28 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 28 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 28 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 28 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 28 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 28 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 28 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 28 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 28 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 28 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 28 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 28 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 28 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 28 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 28 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 28 December)
• Re: [w3c/manifest] The list of known Web Manifest platform values is confusing (#538) (Monday, 19 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Thursday, 15 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Thursday, 15 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Thursday, 15 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Thursday, 15 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Thursday, 15 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Thursday, 15 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Thursday, 15 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Thursday, 15 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 14 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 14 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 14 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 14 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Tuesday, 13 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Tuesday, 13 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Tuesday, 13 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Monday, 12 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Monday, 12 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Monday, 12 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Monday, 12 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Monday, 12 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Monday, 12 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Monday, 12 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Monday, 12 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Thursday, 8 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Tuesday, 6 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Tuesday, 6 December)
• Re: [w3c/manifest] [Explainer] Fix cralwers -> crawlers typo (#531) (#532) (Monday, 5 December)
• Re: [w3c/manifest] Add Optional Opt-In for UA Default Transition (#504) (Thursday, 1 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Thursday, 1 December)

Khaledrahat

• Re: [whatwg/url] empty auth vs no auth -- same? (#181) (Friday, 23 December)
• Re: [whatwg/url] empty auth vs no auth -- same? (#181) (Friday, 23 December)

Kit Cambridge

• Re: [w3c/push-api] Properly define the pushsubscriptionchange event (#234) (Friday, 30 December)
• Re: [w3c/push-api] Properly define the pushsubscriptionchange event (#234) (Friday, 30 December)
• Re: [w3c/push-api] Properly define the pushsubscriptionchange event (#234) (Thursday, 29 December)
• Re: [w3c/push-api] Properly define the pushsubscriptionchange event (#234) (Thursday, 29 December)

L. David Baron

• Re: [w3ctag/spec-reviews] PaymentRequest.canMakeActivePayment() (#146) (Thursday, 1 December)

leolux

• Re: [w3c/manifest] Additional property to define a webapp to be single instance (single-tab) (#479) (Tuesday, 20 December)

lichenhao

• Re: [w3c/editing] How can I send the return value when I bind an copy/cut event with propagation stoped (#157) (Saturday, 3 December)
• Re: [w3c/editing] How can I send the return value when I bind an copy/cut event with propagation stoped (#157) (Saturday, 3 December)
• [w3c/editing] How can I send the return value after I bind an copy/cut event after propagation stoped (#157) (Saturday, 3 December)

Léonie Watson

• Re: [w3c/WebPlatformWG] Meetings: Fix a typo ("ediging") (#84) (Thursday, 22 December)
• Re: [w3c/WebPlatformWG] Meetings: Fix a typo ("ediging") (#84) (Thursday, 22 December)

Manish Goregaokar

• Re: [whatwg/url] SIngle quotes in queries should be percent encoded? (#172) (Thursday, 29 December)
• Re: [whatwg/url] SIngle quotes in queries should be percent encoded? (#172) (Thursday, 29 December)
• Re: [whatwg/url] SIngle quotes in queries should be percent encoded? (#172) (Saturday, 17 December)
• Re: [whatwg/url] SIngle quotes in queries should be percent encoded? (#172) (Saturday, 17 December)
• Re: [whatwg/url] SIngle quotes in queries should be percent encoded? (#172) (Saturday, 17 December)
• Re: [whatwg/url] SIngle quotes in queries should be percent encoded? (#172) (Saturday, 17 December)
• [whatwg/url] SIngle quotes in queries should be percent encoded? (#172) (Saturday, 17 December)

Marc G.

• Re: [whatwg/fetch] Allow * for Access-Control-Expose-Headers (#252) (Sunday, 25 December)
• Re: [whatwg/fetch] Allow * for Access-Control-Expose-Headers (#252) (Sunday, 25 December)

Marcos Cáceres

• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 28 December)
• Re: [whatwg/url] URLSearchParams: calling .set() and .append() should return itself (#90) (Tuesday, 20 December)
• Re: [whatwg/url] URLSearchParams: calling .set() and .append() should return itself (#90) (Tuesday, 20 December)
• Re: [w3c/manifest] Additional property to define a webapp to be single instance (single-tab) (#479) (Tuesday, 20 December)
• Re: [whatwg/url] URLSearchParams: calling .set() and .append() should return itself (#90) (Tuesday, 20 December)
• Re: [whatwg/url] URLSearchParams: calling .set() and .append() should return itself (#90) (Tuesday, 20 December)
• Re: [whatwg/url] URLSearchParams: calling .set() and .append() should return itself (#90) (Tuesday, 20 December)
• Re: [w3c/manifest] The list of known Web Manifest platform values is confusing (#538) (Monday, 19 December)
• Re: [w3c/manifest] [Explainer] Hyperlink icon purpose section to spec (#537) (Monday, 12 December)
• Re: [w3c/manifest] [Explainer] Hyperlink icon purpose section to spec (#537) (Monday, 12 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Friday, 9 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Friday, 9 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Friday, 9 December)
• Re: [w3c/clipboard-apis] Use <pre class=idl> for IDL blocks (#31) (Thursday, 8 December)
• Re: [w3c/clipboard-apis] chore: use new school WebIDL (closes #31) (#32) (Thursday, 8 December)
• [w3c/clipboard-apis] chore: use new school WebIDL (closes #31) (#32) (Thursday, 8 December)
• Re: [w3c/manifest] Allow for multiple scopes (#449) (Thursday, 8 December)
• Re: [w3c/manifest] Is it possible to load the progressive web app manifest file from authenticated site? (#535) (Thursday, 8 December)
• Re: [w3c/push-api] chore: use new school WebIDL (#231) (Wednesday, 7 December)
• Re: [w3c/push-api] chore: use new school WebIDL (#231) (Wednesday, 7 December)
• [w3c/push-api] chore: use new school WebIDL (#231) (Wednesday, 7 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 7 December)
• Re: [w3c/push-api] Switching to contiguous webidl (#229) (Wednesday, 7 December)
• Re: [w3c/push-api] Switching to contiguous webidl (#229) (Tuesday, 6 December)
• Re: [w3c/manifest] [Explainer] Add very simple manifest example (#533) (Tuesday, 6 December)
• Re: [w3c/manifest] [Explainer] Add very simple manifest example (#533) (Tuesday, 6 December)
• [w3c/selection-api] chore: use new school WebIDL (closes #76) (#77) (Tuesday, 6 December)
• Re: [w3c/gamepad] Spec broken because of use of "old school" WebIDL mode (#47) (Tuesday, 6 December)
• Re: [w3c/gamepad] Spec broken because of use of "old school" WebIDL mode (#47) (Tuesday, 6 December)
• Re: [w3c/pointerlock] chore: use new school WebIDL (closes #13) (#14) (Tuesday, 6 December)
• Re: [w3c/manifest] The new explainer ties the manifest with the concept of install ability (#536) (Tuesday, 6 December)
• Re: [w3c/manifest] The new explainer ties the manifest with the concept of install ability (#536) (Tuesday, 6 December)
• Re: [w3c/manifest] Is it possible for a progressive web app to embed web manifest into html page? (#534) (Tuesday, 6 December)
• Re: [w3c/manifest] Is it possible to load the progressive web app manifest file from authenticated site? (#535) (Tuesday, 6 December)
• Re: [w3c/manifest] Is it possible for a progressive web app to embed web manifest into html page? (#534) (Tuesday, 6 December)
• Re: [w3c/selection-api] Use <pre class=idl> for IDL blocks (#76) (Monday, 5 December)
• Re: [w3c/quota-api] WebIDL syntax issues (#5) (Monday, 5 December)
• [w3c/quota-api] chore: use new school WebIDL (closes #5,#6) (#7) (Monday, 5 December)
• Re: [w3c/manifest] [Explainer] Fix cralwers -> crawlers typo (#531) (#532) (Monday, 5 December)
• Re: [w3c/manifest] [Explainer] Fix cralwers -> crawlers typo (#531) (#532) (Monday, 5 December)
• Re: [w3c/push-api] Switching to contiguous webidl (#229) (Monday, 5 December)
• Re: [w3c/pointerlock] chore: use new school WebIDL (closes #13) (#14) (Monday, 5 December)
• Re: [w3c/manifest] [Explainer] Fix cralwers -> crawlers typo (#531) (#532) (Monday, 5 December)
• Re: [w3c/manifest] [Explainer] Fix cralwers -> crawlers typo (#531) (#532) (Monday, 5 December)
• [w3c/pointerlock] chore: use new school WebIDL (closes #13) (#14) (Monday, 5 December)
• Re: [w3c/pointerlock] Use <pre class=idl> for IDL blocks (#13) (Monday, 5 December)
• Re: [w3c/gamepad] Use <pre class=idl> for IDL blocks (#48) (Friday, 2 December)
• Re: [w3c/gamepad] Use <pre class=idl> for IDL blocks (#48) (Friday, 2 December)
• Re: [w3c/gamepad] chore: convert to newschool idl (#49) (Friday, 2 December)
• [w3c/gamepad] chore: convert to newschool idl (#49) (Friday, 2 December)
• Re: [w3c/gamepad] Use <pre class=idl> for IDL blocks (#48) (Friday, 2 December)
• Re: [w3c/gamepad] Use <pre class=idl> for IDL blocks (#48) (Friday, 2 December)
• Re: [w3c/gamepad] Spec broken because of use of "old school" WebIDL mode (#47) (Friday, 2 December)
• Re: [w3c/gamepad] Use <pre class=idl> for IDL blocks (#48) (Friday, 2 December)
• Re: [w3c/manifest] Add info push notifications to extensions registry (#529) (Thursday, 1 December)
• Re: [w3c/manifest] Add info push notifications to extensions registry (#529) (Thursday, 1 December)

Marijn Kruisselbrink

• Re: [whatwg/fetch] WIP: Changing skip-service-worker flag to use-service-workers enum (#435) (Friday, 16 December)
• Re: [whatwg/fetch] WIP: Changing skip-service-worker flag to use-service-workers enum (#435) (Friday, 16 December)
• Re: [w3c/ServiceWorker] postMessage keeps service workers alive indefinitely (#980) (Tuesday, 13 December)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Monday, 12 December)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Monday, 12 December)
• Re: [w3c/FileAPI] Blob.close() has several problems (#10) (Wednesday, 7 December)
• Re: [w3c/FileAPI] Blob.close() has several problems (#10) (Wednesday, 7 December)
• Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303) (Wednesday, 7 December)
• Re: [w3c/FileAPI] Some simplifications/improvements in how bikeshed is utilized for links. (#55) (Tuesday, 6 December)
• [w3c/FileAPI] Some simplifications/improvements in how bikeshed is utilized for links. (#55) (Tuesday, 6 December)
• Re: [w3c/FileAPI] Blob.close() has several problems (#10) (Tuesday, 6 December)
• Re: [w3c/ServiceWorker] clientId on ForeignFetchEvents (#1017) (Friday, 2 December)

Marius Gundersen

• Re: [w3c/IndexedDB] Add support for async update or another way to prepopulate the databade (#126) (Monday, 5 December)
• Re: [w3c/IndexedDB] Add support for async update or another way to prepopulate the databade (#126) (Monday, 5 December)
• Re: [w3c/IndexedDB] Add support for async update or another way to prepopulate the databade (#126) (Monday, 5 December)
• [w3c/IndexedDB] Add support for async update or another way to prepopulate the databade (#126) (Sunday, 4 December)

Martin Thomson

• Re: [w3c/push-api] Properly define the pushsubscriptionchange event (#234) (Tuesday, 20 December)
• Re: [w3c/push-api] Ergonomics of VAPID key (#226) (Wednesday, 14 December)
• Re: [w3c/push-api] Allow passing a base64url-encoded value to `applicationServerKey` (#227) (Wednesday, 14 December)
• Re: [w3c/push-api] Allow passing a base64url-encoded value to `applicationServerKey` (#227) (Wednesday, 14 December)
• [w3c/push-api] Final IDL cleanup (#232) (Wednesday, 14 December)
• Re: [w3c/push-api] chore: use new school WebIDL (#231) (Wednesday, 14 December)
• Re: [w3c/push-api] chore: use new school WebIDL (#231) (Wednesday, 14 December)
• Re: [w3c/push-api] Reject if there's no active service worker (#230) (Wednesday, 14 December)

Martin Ždila

• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Friday, 9 December)
• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Thursday, 8 December)
• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Wednesday, 7 December)

Matt Falkenhagen

• [w3c/ServiceWorker] Handling duplicate importScripts() (#1041) (Wednesday, 28 December)
• Re: [w3c/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Monday, 19 December)
• Re: [w3c/ServiceWorker] activation of the Service Worker on an iframe context (#1029) (Friday, 16 December)
• Re: [w3c/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Tuesday, 13 December)

Matt Giuca

• Re: [w3c/manifest] Should appinstalled / beforeinstallprompt fire on native app installation? (#514) (Thursday, 15 December)
• Re: [w3c/manifest] Should appinstalled / beforeinstallprompt fire on native app installation? (#514) (Thursday, 15 December)

Matthew Hartz

• Re: [whatwg/fetch] CORS Preflight status 307 (#429) (Tuesday, 6 December)
• Re: [whatwg/fetch] CORS Preflight status 307 (#429) (Tuesday, 6 December)
• [whatwg/fetch] CORS Preflight status 307 (#429) (Tuesday, 6 December)
• Re: [whatwg/fetch] Redirect on preflighted CORS requests generally impossible (#204) (Tuesday, 6 December)

Matthew Phillips

• Re: [w3c/webcomponents] Consider adding a childrenChangedCallback or something (#619) (Tuesday, 27 December)
• Re: [w3c/webcomponents] [idea] [shadow-dom] Provide a version number on shadow roots so they can be distinguished. (#610) (Saturday, 3 December)

matthewburnell

• [whatwg/dom] 3603108154 (#386) (Tuesday, 20 December)

MattTreichelYeah

• Re: [w3c/gamepad] Only 4 Gamepads? (#52) (Wednesday, 21 December)
• [w3c/gamepad] Only 4 Gamepads? (#52) (Tuesday, 20 December)

Michael[tm] Smith

• [whatwg/fetch] Meta: Give Travis the full path to the java binary (#427) (Friday, 2 December)
• Re: [whatwg/dom] Meta: run output through the HTML checker (#381) (Friday, 2 December)

Mike West

• Re: [whatwg/fetch] Should we send an Origin header for no-cors fetches? (#225) (Thursday, 8 December)

Milan Raj

• Re: [w3c/webcomponents] ES5 consideration for custom elements (#423) (Thursday, 22 December)

Ms2ger

• Re: [heycam/webidl] Adding slots [initial braindump] (#258) (Wednesday, 28 December)
• Re: [heycam/webidl] Adding slots [initial braindump] (#258) (Monday, 19 December)
• Re: [whatwg/fetch] Link directly to the concept-settings-object-referrer-policy anchor. (#432) (Monday, 19 December)
• Re: [w3c/IndexedDB] Remove DOMStringList (#128) (Tuesday, 13 December)
• [w3c/IndexedDB] Remove DOMStringList (#128) (Tuesday, 13 December)
• [whatwg/fetch] Access-Control-Expose-Headers parsing failure not handled in main fetch (#433) (Friday, 9 December)
• [whatwg/fetch] Link directly to the concept-settings-object-referrer-policy anchor. (#432) (Thursday, 8 December)
• Re: [w3c/DOM-Parsing] Define the origin of the documents returned from DOMParser (#24) (Wednesday, 7 December)
• Re: [whatwg/dom] cancelBubble legacy property (#211) (Thursday, 1 December)

Nathan Schloss

• Re: [w3c/ServiceWorker] Consider mechanisms to bypass the service worker for things that we know won't be in it's cache (#1026) (Friday, 16 December)
• [w3c/ServiceWorker] Consider mechanisms to bypass the service worker for things that we know won't be in it's cache (#1026) (Tuesday, 13 December)

newschapmj1

• [w3c/manifest] Minor typo in explainer.md (#531) (Friday, 2 December)

Nicholas Shanks

• [whatwg/fetch] "3.3. `X-Content-Type-Options` header" (#444) (Thursday, 29 December)

Nicolas Le Gall

• Re: [whatwg/streams] Define valid queuing strategy (#427) (Saturday, 17 December)
• Re: [whatwg/streams] Start work on a polyfill? (#630) (Saturday, 17 December)

Nigel Megitt

• Re: [w3ctag/spec-reviews] Timed Text Markup Language 2 (TTML2) (#138) (Tuesday, 6 December)

Noah Levitt

• Re: [whatwg/url] IPv4 number parser on "0x0a" (#167) (Friday, 9 December)
• Re: [whatwg/url] IPv4 number parser on "0x0a" (#167) (Friday, 9 December)
• Re: [whatwg/url] Parsing an empty host (#79) (Friday, 2 December)
• Re: [whatwg/url] IPv4 number parser on "0x0a" (#167) (Thursday, 1 December)
• Re: [whatwg/url] IPv4 number parser on "0x0a" (#167) (Thursday, 1 December)
• [whatwg/url] IPv4 number parser on "0x0a" (#167) (Thursday, 1 December)

Nolan Lawson

• [w3c/IndexedDB] Negative counts have inconsistent behavior in getAll()/getAllKeys() (#131) (Friday, 23 December)
• [w3c/IndexedDB] Add descending order for getAll() and getAllKeys() (#130) (Friday, 23 December)

Ole Ersoy

• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 28 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 15 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 14 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 14 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 13 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 13 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 13 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 12 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 12 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 12 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 12 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 12 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 12 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 12 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 12 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 12 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 12 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 11 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 10 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 10 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 10 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Friday, 9 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 8 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 8 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 8 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 8 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 8 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 8 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 8 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 8 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 8 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 8 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 7 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 7 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 7 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 6 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 6 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 6 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 6 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 6 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 6 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 6 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 6 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 6 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 6 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 6 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 6 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 5 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 5 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 5 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 5 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 5 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 5 December)
• Re: [w3c/webcomponents] defining and instantiating customized built‐in elements as if they were autonomous custom elements (#613) (Saturday, 3 December)
• Re: [w3c/webcomponents] defining and instantiating customized built‐in elements as if they were autonomous custom elements (#613) (Friday, 2 December)

Ole Martin Handeland

• [w3c/ServiceWorker] Inconsistent behaviour when client-side certificates are required (#1022) (Sunday, 11 December)

OvermindDL1

• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 8 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 8 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 8 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 8 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 7 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 6 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 5 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 5 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 5 December)

Patrick H. Lauke

• Re: [w3c/touch-events] Specify what browsers do on non-touch devices (#64) (Wednesday, 14 December)
• Re: [w3c/touch-events] Specify what browsers do on non-touch devices (#64) (Tuesday, 13 December)

Patrick McManus

• Re: [whatwg/fetch] consider exposing and allowing script to set Request priority (#436) (Thursday, 15 December)

Peter Beverloo

• [w3c/push-api] Properly define the pushsubscriptionchange event (#234) (Tuesday, 20 December)
• [w3c/push-api] Need to define where the EventHandler type comes from (#233) (Monday, 19 December)
• Re: [w3c/push-api] Allow passing a base64url-encoded value to `applicationServerKey` (#227) (Wednesday, 7 December)
• Re: [w3c/push-api] Please use Contiguous IDL instead (#216) (Wednesday, 7 December)
• Re: [w3c/push-api] Switching to contiguous webidl (#229) (Wednesday, 7 December)
• Re: [w3c/push-api] Switching to contiguous webidl (#229) (Wednesday, 7 December)

Peter Rushforth

• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 12 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 12 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 12 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 12 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 12 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 12 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 10 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Friday, 9 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Friday, 9 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 8 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 8 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 8 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 8 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 6 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 6 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 6 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 6 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 6 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 6 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 6 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 5 December)

Philip Jägenstedt

• Re: [whatwg/fullscreen] Reject exitFullscreen() in inactive documents (#68) (Monday, 19 December)
• Re: [whatwg/fullscreen] Reject exitFullscreen() in inactive documents (#68) (Monday, 19 December)
• [whatwg/fullscreen] Introduce document.exitFullscreen({ fully: true })? (#70) (Monday, 19 December)
• Re: [w3c/clipboard-apis] Where would one get a DataTransfer to hand to the ClipboardEvent constructor? (#33) (Friday, 16 December)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Friday, 16 December)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Friday, 16 December)
• Re: [whatwg/fullscreen] Reject exitFullscreen() in inactive documents (#68) (Friday, 16 December)
• Re: [whatwg/fullscreen] Reject exitFullscreen() in inactive documents (#68) (Friday, 16 December)
• Re: [whatwg/fullscreen] Reject exitFullscreen() in inactive documents (#68) (Friday, 16 December)
• Re: [whatwg/fullscreen] Editorial: resolve promises, don't fulfill them (#69) (Friday, 16 December)
• Re: [whatwg/fullscreen] Check the fullscreen element in the animation frame task for exit (#66) (Friday, 16 December)
• Re: [whatwg/fullscreen] Check the fullscreen element in the animation frame task for exit (#66) (Friday, 16 December)
• Re: [whatwg/fullscreen] Check the fullscreen element in the animation frame task for exit (#66) (Friday, 16 December)
• [whatwg/fullscreen] Editorial: resolve promises, don't fulfill them (#69) (Friday, 16 December)
• Re: [whatwg/fullscreen] Check the fullscreen element in the animation frame task for exit (#66) (Friday, 16 December)
• Re: [whatwg/dom] cancelBubble legacy property (#211) (Friday, 16 December)
• Re: [whatwg/fullscreen] Define fully exit fullscreen in terms of exitFullscreen({ fully: true }) (#65) (Friday, 16 December)
• Re: [whatwg/fullscreen] Define fully exit fullscreen in terms of exitFullscreen({ fully: true }) (#65) (Friday, 16 December)
• Re: [whatwg/fullscreen] Define fully exit fullscreen in terms of exitFullscreen({ fully: true }) (#65) (Friday, 16 December)
• Re: [whatwg/fullscreen] Reject exitFullscreen() in inactive documents (#68) (Thursday, 15 December)
• [whatwg/fullscreen] Reject exitFullscreen() in inactive documents (#68) (Thursday, 15 December)
• Re: [whatwg/fullscreen] Define what happens with requestFullscreen() and exitFullscreen() in inactive document (#67) (Thursday, 15 December)
• Re: [whatwg/fullscreen] Define what happens with requestFullscreen() and exitFullscreen() in inactive document (#67) (Thursday, 15 December)
• [whatwg/fullscreen] Define what happens with requestFullscreen() and exitFullscreen() in inactive document (#67) (Thursday, 15 December)
• Re: [whatwg/fullscreen] Check the fullscreen element in the animation frame task for exit (#66) (Wednesday, 14 December)
• [whatwg/fullscreen] Check the fullscreen element in the animation frame task for exit (#66) (Wednesday, 14 December)
• Re: [whatwg/fullscreen] Define fully exit fullscreen in terms of exitFullscreen({ fully: true }) (#65) (Wednesday, 14 December)
• [whatwg/fullscreen] Define fully exit fullscreen in terms of exitFullscreen({ fully: true }) (#65) (Wednesday, 14 December)
• Re: [w3c/gamepad] Add missing type argument to the GamepadEvent constructor (#51) (Tuesday, 13 December)
• [w3c/gamepad] Add missing type argument to the GamepadEvent constructor (#51) (Tuesday, 13 December)
• [whatwg/dom] Editorial: remove stray : from Mixin Slotable (#384) (Monday, 12 December)
• Re: [w3c/clipboard-apis] Use <pre class=idl> for IDL blocks (#31) (Friday, 2 December)
• Re: [w3c/gamepad] Use <pre class=idl> for IDL blocks (#48) (Friday, 2 December)
• Re: [w3c/gamepad] Use <pre class=idl> for IDL blocks (#48) (Friday, 2 December)
• [w3c/quota-api] Use <pre class=idl> for IDL blocks (#6) (Thursday, 1 December)
• Re: [w3c/quota-api] WebIDL syntax issues (#5) (Thursday, 1 December)
• [w3c/pointerlock] Use <pre class=idl> for IDL blocks (#13) (Thursday, 1 December)
• [w3c/gamepad] Use <pre class=idl> for IDL blocks (#48) (Thursday, 1 December)
• [w3c/clipboard-apis] Use <pre class=idl> for IDL blocks (#31) (Thursday, 1 December)
• [w3c/selection-api] Use <pre class=idl> for IDL blocks (#76) (Thursday, 1 December)
• Re: [w3c/push-api] Please use Contiguous IDL instead (#216) (Thursday, 1 December)

pkotwicz

• Re: [w3c/manifest] The list of known Web Manifest platform values is confusing (#538) (Monday, 19 December)
• [w3c/manifest] The list of known Web Manifest platform values is confusing (#538) (Friday, 16 December)

r12a

• [w3c/uievents-code] i18n Issues common to main spec (#12) (Friday, 16 December)
• [w3c/uievents-key] Issues common to main spec (#34) (Friday, 16 December)
• [w3c/uievents-key] Ed: Unicode character encodings are shown (#33) (Friday, 16 December)
• [w3c/uievents-key] Faulty references (#32) (Friday, 16 December)
• [w3c/uievents-code] Ed: Include more international keyboard examples (#11) (Friday, 16 December)
• [w3c/uievents] Use U+ notation to refer to code points (#127) (Friday, 16 December)
• [w3c/uievents-key] Supplementary characters in ES6 can use code point values (#31) (Friday, 16 December)
• [w3c/uievents] Are Shift or AltGr fallbacks sufficient? (#126) (Friday, 16 December)
• [w3c/uievents] Ed: Use webfonts for Kanji and Serbian characters (#125) (Friday, 16 December)
• [w3c/uievents] Ed: MAY may not be appropriate (#124) (Friday, 16 December)
• [w3c/uievents] Editorial: Capital letter equivalents for bicameral scripts (#123) (Friday, 16 December)
• [w3c/uievents] Editorial: Use Serbian for key code example (#122) (Friday, 16 December)
• [w3c/uievents] Printable control characters needs refinement (#121) (Friday, 16 December)
• [w3c/uievents] Dead keys and unsupported base characters (#120) (Friday, 16 December)
• [w3c/uievents] What is an 'appropriate' Unicode code point? (#119) (Friday, 16 December)
• [w3c/uievents] Typos (#118) (Friday, 16 December)
• [w3c/uievents] 'Key value' terminology is ambiguous and confusing (#117) (Friday, 16 December)

Raphael Kubo da Costa

• Re: [w3c/WebPlatformWG] Meetings: Fix a typo ("ediging") (#84) (Thursday, 22 December)
• [w3c/WebPlatformWG] Meetings: Fix a typo ("ediging") (#84) (Tuesday, 20 December)

rektide

• Re: [whatwg/fetch] See if resource exists (#428) (Friday, 30 December)
• [w3c/gamepad] Background gamepads (#53) (Saturday, 24 December)
• [whatwg/fetch] See if resource exists (#428) (Monday, 5 December)

Rick Byers

• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Wednesday, 21 December)
• Re: [w3c/manifest] The list of known Web Manifest platform values is confusing (#538) (Friday, 16 December)
• Re: [w3c/manifest] The list of known Web Manifest platform values is confusing (#538) (Friday, 16 December)
• Re: [w3c/clipboard-apis] Where would one get a DataTransfer to hand to the ClipboardEvent constructor? (#33) (Friday, 16 December)
• Re: [w3c/clipboard-apis] Where would one get a DataTransfer to hand to the ClipboardEvent constructor? (#33) (Friday, 16 December)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Friday, 9 December)

Ricky Miller

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

Rob Dolin

• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Monday, 5 December)

Rob Dolin (MSFT)

• [w3c/manifest] [Explainer] Hyperlink icon purpose section to spec (#537) (Saturday, 10 December)
• Re: [w3c/manifest] Proposal: Add Optional Member for IARC Rating (#523) (Wednesday, 7 December)
• Re: [w3c/manifest] Minor typo in explainer.md (#531) (Wednesday, 7 December)
• Re: [w3c/manifest] Minor typo in explainer.md (#531) (Wednesday, 7 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Wednesday, 7 December)
• Re: [w3c/manifest] Is it possible for a progressive web app to embed web manifest into html page? (#534) (Tuesday, 6 December)
• Re: [w3c/manifest] Is it possible to load the progressive web app manifest file from authenticated site? (#535) (Tuesday, 6 December)
• Re: [w3c/manifest] The new explainer ties the manifest with the concept of install ability (#536) (Tuesday, 6 December)
• Re: [w3c/manifest] Allow for multiple scopes (#449) (Tuesday, 6 December)
• Re: [w3c/manifest] Is it possible for a progressive web app to embed web manifest into html page? (#534) (Tuesday, 6 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Tuesday, 6 December)
• Re: [w3c/manifest] [Explainer] Fix cralwers -> crawlers typo (#531) (#532) (Tuesday, 6 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Monday, 5 December)
• Re: [w3c/manifest] [Explainer] Add very simple manifest example (#533) (Monday, 5 December)
• [w3c/manifest] [Explainer] Add very simple manifest example (#533) (Friday, 2 December)
• Re: [w3c/manifest] [Explainer] Fix cralwers -> crawlers typo (#531) (#532) (Friday, 2 December)
• Re: [w3c/manifest] Minor typo in explainer.md (#531) (Friday, 2 December)
• [w3c/manifest] [Explainer] Fix cralwers -> crawlers typo (#531) (#532) (Friday, 2 December)
• Re: [w3c/manifest] Update references to W3C if available (#526) (Thursday, 1 December)
• Re: [w3c/manifest] Add Optional Opt-In for UA Default Transition (#504) (Thursday, 1 December)
• Re: [w3c/manifest] Allow for multiple scopes (#449) (Thursday, 1 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Thursday, 1 December)
• Re: [w3c/manifest] Add info push notifications to extensions registry (#529) (Thursday, 1 December)
• Re: [w3c/manifest] Proposal: Add Optional Member for IARC Rating (#523) (Thursday, 1 December)

Russell Bicknell

• Re: [w3c/webcomponents] Can't reuse custom element constructors? (#618) (Tuesday, 20 December)
• Re: [w3c/webcomponents] Can't reuse custom element constructors? (#618) (Tuesday, 20 December)
• Re: [w3c/webcomponents] Can't reuse custom element constructors? (#618) (Tuesday, 20 December)
• [w3c/webcomponents] Can't reuse custom element constructors? (#618) (Monday, 19 December)
• Re: [w3c/webcomponents] CE reaction queue's not-really-sync behavior doesn't provide strong enough guarantees about when reactions occur (#616) (Saturday, 10 December)
• [w3c/webcomponents] CE reaction queue's not-really-sync behavior doesn't provide strong enough guarantees about when reactions occur (#616) (Saturday, 10 December)

Ryosuke Niwa

• Re: [w3c/webcomponents] Can't reuse custom element constructors? (#618) (Wednesday, 21 December)
• Re: [w3c/webcomponents] CE reaction queue's not-really-sync behavior doesn't provide strong enough guarantees about when reactions occur (#616) (Tuesday, 20 December)
• Re: [w3c/webcomponents] Can't reuse custom element constructors? (#618) (Tuesday, 20 December)
• Re: [w3c/webcomponents] Can't reuse custom element constructors? (#618) (Tuesday, 20 December)
• Re: [w3c/webcomponents] Is the order of `slotchange` events along a slot chain across node trees defined? (#617) (Friday, 16 December)
• Re: [w3c/webcomponents] CE reaction queue's not-really-sync behavior doesn't provide strong enough guarantees about when reactions occur (#616) (Tuesday, 13 December)
• Re: [w3c/webcomponents] HTMLElement.prototype.offsetParent leaks a node inside a shadow tree (#497) (Saturday, 10 December)
• Re: [w3c/webcomponents] HTMLElement.prototype.offsetParent leaks a node inside a shadow tree (#497) (Saturday, 10 December)
• Re: [w3c/webcomponents] CE reaction queue's not-really-sync behavior doesn't provide strong enough guarantees about when reactions occur (#616) (Saturday, 10 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 10 December)
• Re: [w3c/webcomponents] fullscreenchange should be dispatched on each ancestor shadow root (#614) (Friday, 9 December)
• Re: [w3c/webcomponents] fullscreenchange should be dispatched on each ancestor shadow root (#614) (Friday, 9 December)
• [w3c/webcomponents] fullscreenchange should be dispatched on each ancestor shadow root (#614) (Thursday, 8 December)
• Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78) (Thursday, 8 December)
• Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78) (Wednesday, 7 December)
• Re: [w3c/webcomponents] How should autofill work for inputs generated inside shadow roots (#572) (Wednesday, 7 December)
• Re: [w3c/selection-api] Use <pre class=idl> for IDL blocks (#76) (Tuesday, 6 December)
• Re: [w3c/selection-api] chore: use new school WebIDL (closes #76) (#77) (Tuesday, 6 December)
• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Tuesday, 6 December)
• Re: [w3c/webcomponents] How should autofill work for inputs generated inside shadow roots (#572) (Tuesday, 6 December)
• Re: [w3c/webcomponents] How should autofill work for inputs generated inside shadow roots (#572) (Tuesday, 6 December)
• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Tuesday, 6 December)
• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Tuesday, 6 December)
• Re: [w3c/webcomponents] How should autofill work for inputs generated inside shadow roots (#572) (Tuesday, 6 December)
• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Tuesday, 6 December)
• Re: [w3c/webcomponents] How should autofill work for inputs generated inside shadow roots (#572) (Tuesday, 6 December)
• Re: [w3c/webcomponents] How should autofill work for inputs generated inside shadow roots (#572) (Tuesday, 6 December)
• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Tuesday, 6 December)
• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Monday, 5 December)
• Re: [w3c/webcomponents] Method for detecting finally-distributed nodes. (#611) (Monday, 5 December)
• Re: [w3c/webcomponents] Copying global `<style>` textContent into ShadowDOM roots is not ideal. (#609) (Monday, 5 December)

Salvador de la Puente González

• Re: [w3c/ServiceWorker] Consider providing `navigation` event (#1028) (Monday, 19 December)
• Re: [w3c/ServiceWorker] Consider providing `navigation` event (#1028) (Friday, 16 December)
• Re: [w3c/ServiceWorker] Consider providing `navigation` event (#1028) (Friday, 16 December)
• Re: [w3c/ServiceWorker] Consider providing `navigation` event (#1028) (Friday, 16 December)
• Re: [w3c/manifest] Should appinstalled / beforeinstallprompt fire on native app installation? (#514) (Thursday, 15 December)
• Re: [w3c/manifest] Allow for multiple scopes (#449) (Wednesday, 14 December)
• Re: [w3c/ServiceWorker] Consider providing `navigation` event (#1028) (Wednesday, 14 December)
• Re: [w3c/ServiceWorker] Consider providing `navigation` event (#1028) (Wednesday, 14 December)
• Re: [w3c/manifest] Additional property to define a webapp to be single instance (single-tab) (#479) (Wednesday, 14 December)
• [w3c/ServiceWorker] Provide `navigation` event (#1028) (Wednesday, 14 December)
• Re: [w3c/manifest] purpose: badge should be defined as default badge for Notifications API (#508) (Wednesday, 14 December)
• Re: [w3c/manifest] Add splashscreen as a `purpose` (#510) (Wednesday, 14 December)
• Re: [w3c/manifest] Should appinstalled / beforeinstallprompt fire on native app installation? (#514) (Wednesday, 14 December)
• Re: [w3c/manifest] Proposal: Add Optional Member for IARC Rating (#523) (Wednesday, 14 December)
• Re: [w3c/manifest] The new explainer ties the manifest with the concept of install ability (#536) (Tuesday, 6 December)
• Re: [w3c/manifest] The new explainer ties the manifest with the concept of install ability (#536) (Tuesday, 6 December)
• Re: [w3c/manifest] The new explainer ties the manifest with the concept of install ability (#536) (Tuesday, 6 December)
• [w3c/manifest] The new explainer ties the manifest with the concept of install ability (#536) (Tuesday, 6 December)

Samer Masterson

• Re: [w3c/ServiceWorker] allow service worker produced resources to be marked as "cachable" (#962) (Thursday, 1 December)

Scott Graham

• Re: [w3c/gamepad] chore: convert to newschool idl (#49) (Friday, 2 December)
• Re: [w3c/gamepad] chore: convert to newschool idl (#49) (Friday, 2 December)

Serge van den Oever

• Re: [w3c/manifest] Is it possible to load the progressive web app manifest file from authenticated site? (#535) (Sunday, 11 December)
• Re: [w3c/manifest] Is it possible for a progressive web app to embed web manifest into html page? (#534) (Wednesday, 7 December)
• Re: [w3c/manifest] Is it possible to load the progressive web app manifest file from authenticated site? (#535) (Wednesday, 7 December)
• Re: [w3c/manifest] Is it possible for a progressive web app to embed web manifest into html page? (#534) (Tuesday, 6 December)
• Re: [w3c/manifest] Is it possible for a progressive web app to embed web manifest into html page? (#534) (Tuesday, 6 December)
• [w3c/manifest] Is it possible to load the progressive web app manifest file from authenticated site? (#535) (Tuesday, 6 December)
• [w3c/manifest] Is it possible for a progressive web app to embed web manifest into html page? (#534) (Tuesday, 6 December)

Shahar Or

• Re: [w3c/webcomponents] "is" attribute for autonomous custom elements (#603) (Thursday, 22 December)

Shawn Huang

• Re: [whatwg/storage] Check PermissionState instead of PermissionStatus (#39) (Monday, 19 December)
• Re: [whatwg/storage] Check PermissionState instead of PermissionStatus (#39) (Friday, 16 December)
• Re: [whatwg/storage] Check PermissionState instead of PermissionStatus (#39) (Friday, 16 December)
• Re: [whatwg/storage] Check PermissionState instead of PermissionStatus (#39) (Friday, 16 December)
• [whatwg/storage] Check PermissionState instead of PermissionStatus (#39) (Wednesday, 14 December)

Shiino Yuki

• Re: [heycam/webidl] Are operations on the `[[BackingMap]]` and `[[BackingSet]]` page-hookable? And if not, why not? (#254) (Thursday, 15 December)

Simon Pieters

• Re: [whatwg/fetch] Only use nosniff for "script" and "style" (#438) (Monday, 19 December)
• Re: [whatwg/fullscreen] Reject exitFullscreen() in inactive documents (#68) (Friday, 16 December)
• Re: [whatwg/fullscreen] Reject exitFullscreen() in inactive documents (#68) (Thursday, 15 December)
• Re: [whatwg/fullscreen] Define what happens with requestFullscreen() and exitFullscreen() in inactive document (#67) (Thursday, 15 December)
• Re: [whatwg/fullscreen] Define what happens with requestFullscreen() and exitFullscreen() in inactive document (#67) (Thursday, 15 December)
• Re: [whatwg/fullscreen] Define what happens with requestFullscreen() and exitFullscreen() in inactive document (#67) (Thursday, 15 December)
• Re: [w3c/IndexedDB] DOMStringList has been removed from DOM (#28) (Thursday, 15 December)
• [whatwg/dom] Point to IndexedDB for DOMStringList (#385) (Thursday, 15 December)
• Re: [whatwg/dom] cancelBubble legacy property (#211) (Monday, 12 December)
• Re: [whatwg/url] unicode fragments (#150) (Thursday, 8 December)
• Re: [heycam/webidl] Should perform security check for constructors (#249) (Thursday, 8 December)
• Re: [heycam/webidl] Should perform security check for constructors (#249) (Thursday, 8 December)
• [heycam/webidl] Should perform security check for constructors (#249) (Thursday, 8 December)
• Re: [whatwg/dom] Copy the origin pointer when cloning a document (#380) (Thursday, 1 December)

sleevi

• Re: [whatwg/url] URLSearchParams delete and iterator ambiguity (#188) (Wednesday, 28 December)
• Re: [whatwg/url] Trailing dot and origin compuation (#132) (Tuesday, 20 December)
• Re: [whatwg/fetch] Only specific APIs should skip the fetch event when called within a service worker (#303) (Friday, 16 December)
• Re: [whatwg/fetch] Only specific APIs should skip the fetch event when called within a service worker (#303) (Friday, 16 December)
• Re: [whatwg/fetch] consider exposing and allowing script to set Request priority (#436) (Thursday, 15 December)

smaug----

• Re: [w3c/IndexedDB] Specify timing of transaction deactivation more precisely (#87) (Saturday, 31 December)
• Re: [w3c/IndexedDB] Specify timing of transaction deactivation more precisely (#87) (Thursday, 29 December)
• Re: [w3c/IndexedDB] Specify timing of transaction deactivation more precisely (#87) (Thursday, 29 December)
• Re: [w3c/IndexedDB] Specify timing of transaction deactivation more precisely (#87) (Thursday, 29 December)
• Re: [w3c/IndexedDB] Specify timing of transaction deactivation more precisely (#87) (Wednesday, 28 December)
• Re: [w3c/clipboard-apis] Where would one get a DataTransfer to hand to the ClipboardEvent constructor? (#33) (Monday, 19 December)
• Re: [w3c/clipboard-apis] Where would one get a DataTransfer to hand to the ClipboardEvent constructor? (#33) (Monday, 19 December)
• Re: [w3c/clipboard-apis] Where would one get a DataTransfer to hand to the ClipboardEvent constructor? (#33) (Monday, 19 December)
• Re: [whatwg/dom] cancelBubble legacy property (#211) (Friday, 16 December)
• Re: [w3c/FileAPI] Document BlobPropertyBag "endings", or keep pushing to remove? (#46) (Thursday, 1 December)

Spongman

• Re: [w3c/ServiceWorker] notification of cancelled download? (#957) (Wednesday, 21 December)

staktrace

• Re: [w3c/touch-events] Specify what browsers do on non-touch devices (#64) (Tuesday, 13 December)
• Re: [w3c/touch-events] Specify what browsers do on non-touch devices (#64) (Tuesday, 13 December)

stefan hakansson

• Re: [w3c/ServiceWorker] clarify that manually constructed ExtendableEvent objects may not extend lifetime via waitUntil() (#1040) (Friday, 23 December)
• Re: [w3c/ServiceWorker] async waitUntil() does not allow extension on final promise resolution? (#1039) (Friday, 23 December)

Steve Orvell

• Re: [w3c/webcomponents] CE reaction queue's not-really-sync behavior doesn't provide strong enough guarantees about when reactions occur (#616) (Saturday, 10 December)

Steven Vachon

• Re: [whatwg/url] internal class (or type) "URL" (#191) (Saturday, 31 December)
• Re: [whatwg/url] internal class (or type) "URL" (#191) (Saturday, 31 December)
• [whatwg/url] internal class (or type) "URL" (#191) (Saturday, 31 December)
• Re: [whatwg/url] remove need for "//" after protocol? (#182) (Wednesday, 28 December)
• Re: [whatwg/url] remove need for "//" after protocol? (#182) (Wednesday, 28 December)
• Re: [whatwg/url] remove need for "//" after protocol? (#182) (Wednesday, 28 December)
• Re: [whatwg/url] remove need for "//" after protocol? (#182) (Wednesday, 28 December)
• Re: [whatwg/url] Splicing URLSearchParams? (#183) (Wednesday, 28 December)
• Re: [whatwg/url] remove need for "//" after protocol? (#182) (Wednesday, 28 December)
• Re: [whatwg/url] Splicing URLSearchParams? (#183) (Wednesday, 28 December)
• Re: [whatwg/url] Weird URLSearchParams delete issue (#184) (Wednesday, 28 December)
• [whatwg/url] Weird URLSearchParams delete issue (#184) (Wednesday, 28 December)
• [whatwg/url] Splicing URLSearchParams? (#183) (Wednesday, 28 December)
• Re: [whatwg/url] empty auth vs no auth -- same? (#181) (Wednesday, 28 December)
• Re: [whatwg/url] empty auth vs no auth -- same? (#181) (Tuesday, 27 December)
• [whatwg/url] remove need for "//" after protocol? (#182) (Tuesday, 27 December)
• [whatwg/url] empty auth vs no auth -- same? (#181) (Thursday, 22 December)

Stuart P. Bentley

• Re: [whatwg/fetch] Aborting a fetch (#27) (Friday, 16 December)
• Re: [whatwg/fetch] Aborting a fetch (#27) (Thursday, 15 December)

Tab Atkins Jr.

• Re: [whatwg/url] Consider railroad diagrams in syntax sections to aid understanding (#67) (Thursday, 22 December)
• Re: [heycam/webidl] Exception cleanup (#250) (Tuesday, 13 December)

Takayoshi Kochi

• Re: [w3c/webcomponents] fullscreenchange should be dispatched on each ancestor shadow root (#614) (Friday, 9 December)
• Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78) (Friday, 2 December)

Takeshi Yoshino

• Re: [whatwg/fetch] Handle null and failure for Access-Control-Expose-Headers (#434) (Friday, 9 December)
• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Thursday, 8 December)
• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Thursday, 8 December)
• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Thursday, 8 December)
• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Thursday, 8 December)
• [whatwg/streams] Add a pattern parameter to run-web-platform-tests.js (#625) (Monday, 5 December)

TAMURA, Kent

• Re: [whatwg/dom] cancelBubble legacy property (#211) (Monday, 19 December)

Tanguy Krotoff

• Re: [whatwg/streams] Fix missing comma in example (#627) (Monday, 12 December)
• Re: [whatwg/streams] Fix missing comma in example (#627) (Monday, 12 December)
• [whatwg/streams] Fix missing comma in example (#627) (Sunday, 11 December)

Tapan Anand

• Re: [w3c/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Friday, 9 December)

Ted Dinklocker

• Re: [w3c/touch-events] Specify what browsers do on non-touch devices (#64) (Wednesday, 14 December)

Ted Mielczarek

• Re: [w3c/gamepad] Only 4 Gamepads? (#52) (Wednesday, 21 December)
• Re: [w3c/gamepad] Use <pre class=idl> for IDL blocks (#48) (Thursday, 1 December)

Teflo

• [w3c/gamepad] [Extensions] GamepadHapticActuator#pulse bugs (#50) (Wednesday, 7 December)

Tim Ruffles

• Re: [whatwg/url] Convenience method for serializing URLSearchParams (#142) (Monday, 19 December)

Timothy Guan-tin Chien

• Re: [whatwg/url] Trailing dot and origin compuation (#132) (Tuesday, 20 December)
• Re: [whatwg/url] Trailing dot and origin compuation (#132) (Tuesday, 20 December)

tnikolai2

• Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Monday, 26 December)
• Re: [w3c/webcomponents] Consider adding a childrenChangedCallback or something (#619) (Monday, 26 December)
• Re: [w3c/webcomponents] components v1 native implementation - inner components problem (#615) (Saturday, 10 December)
• [w3c/webcomponents] components v1 native implementation - inner components problem (#615) (Friday, 9 December)

Tobie Langel

• [heycam/webidl] Serializable types should include records (#262) (Wednesday, 28 December)
• Re: [heycam/webidl] Consider simplifying serializers (#188) (Friday, 23 December)
• Re: [heycam/webidl] Serialized value should allow any string type (#259) (Thursday, 22 December)
• Re: [heycam/webidl] Consider simplifying serializers (#188) (Thursday, 22 December)
• Re: [heycam/webidl] Serialized value should allow any string type (#259) (Thursday, 22 December)
• Re: [heycam/webidl] Consider simplifying serializers (#188) (Wednesday, 21 December)
• Re: [heycam/webidl] Consider simplifying serializers (#188) (Wednesday, 21 December)
• Re: [heycam/webidl] Consider simplifying serializers (#188) (Wednesday, 21 December)
• Re: [heycam/webidl] Consider simplifying serializers (#188) (Tuesday, 20 December)
• Re: [heycam/webidl] Consider simplifying serializers (#188) (Tuesday, 20 December)
• Re: [heycam/webidl] Adding slots [initial braindump] (#258) (Sunday, 18 December)
• [heycam/webidl] Adding slots [initial braindump] (#258) (Sunday, 18 December)
• Re: [heycam/webidl] Split DOMException back into IDL type and DFN. (#257) (Wednesday, 14 December)
• [heycam/webidl] Split DOMException back into IDL type and DFN. (#257) (Wednesday, 14 December)
• Re: [heycam/webidl] "For `DOMExceptions`" (#255) (Wednesday, 14 December)
• Re: [heycam/webidl] "For `DOMExceptions`" (#255) (Wednesday, 14 December)
• Re: [heycam/webidl] "For `DOMExceptions`" (#255) (Wednesday, 14 December)
• Re: [heycam/webidl] Meta: fix "throw" dfns (#256) (Tuesday, 13 December)
• [heycam/webidl] Meta: fix "throw" dfns (#256) (Tuesday, 13 December)
• Re: [heycam/webidl] Exception cleanup (#250) (Tuesday, 13 December)
• Re: [heycam/webidl] Change the recommended language for DOMExceptions (#247) (Tuesday, 13 December)
• Re: [heycam/webidl] Exception cleanup (#250) (Tuesday, 13 December)
• Re: [heycam/webidl] Exception cleanup (#250) (Tuesday, 13 December)
• Re: [heycam/webidl] Exception cleanup (#250) (Sunday, 11 December)
• Re: [heycam/webidl] Exception cleanup (#250) (Sunday, 11 December)
• Re: [heycam/webidl] Exception cleanup (#250) (Friday, 9 December)
• Re: [heycam/webidl] Exception cleanup (#250) (Friday, 9 December)
• Re: [heycam/webidl] Clarify "The Type must not identify the same or another typedef." (#252) (Friday, 9 December)
• Re: [heycam/webidl] Clarify "The Type must not identify the same or another typedef." (#252) (Friday, 9 December)
• Re: [heycam/webidl] Editorial: clarify typedef aliasing limitations. (#253) (Friday, 9 December)
• [heycam/webidl] Editorial: clarify typedef aliasing limitations. (#253) (Friday, 9 December)
• Re: [heycam/webidl] Disallow nullable Promise types. (#248) (Friday, 9 December)
• Re: [heycam/webidl] Exception cleanup (#250) (Friday, 9 December)
• Re: [heycam/webidl] Add missing legacy error names. (#251) (Friday, 9 December)
• Re: [heycam/webidl] Add missing legacy error names. (#251) (Friday, 9 December)
• Re: [heycam/webidl] Add missing legacy error names. (#251) (Friday, 9 December)
• Re: [heycam/webidl] Should perform security check for constructors (#249) (Thursday, 8 December)
• Re: [heycam/webidl] Exception cleanup (#250) (Thursday, 8 December)
• Re: [heycam/webidl] Exception cleanup (#250) (Thursday, 8 December)
• Re: [heycam/webidl] Exception cleanup (#250) (Thursday, 8 December)
• [heycam/webidl] Add missing legacy error names. (#251) (Thursday, 8 December)
• Re: [heycam/webidl] Should perform security check for constructors (#249) (Thursday, 8 December)
• [heycam/webidl] Exception cleanup (#250) (Thursday, 8 December)
• Re: [heycam/webidl] Disallow nullable Promise types. (#248) (Thursday, 8 December)
• [heycam/webidl] Disallow nullable Promise types. (#248) (Thursday, 8 December)
• Re: [heycam/webidl] Deprecate InvalidAccessError. (#246) (Thursday, 8 December)
• Re: [heycam/webidl] Deprecate InvalidAccessError. (#246) (Thursday, 8 December)
• Re: [heycam/webidl] Deprecate InvalidAccessError. (#246) (Thursday, 8 December)
• Re: [heycam/webidl] Deprecate InvalidAccessError. (#246) (Thursday, 8 December)
• [heycam/webidl] Deprecate InvalidAccessError. (#246) (Wednesday, 7 December)
• Re: [heycam/webidl] Meta: remove sequence<T> as Bikeshed definition (#245) (Thursday, 1 December)

Tomek Wytrębowicz

• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 12 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 12 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 12 December)
• Re: [w3c/webcomponents] Copying global `<style>` textContent into ShadowDOM roots is not ideal. (#609) (Monday, 5 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 5 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 5 December)
• Re: [w3c/webcomponents] Copying global `<style>` textContent into ShadowDOM roots is not ideal. (#609) (Monday, 5 December)

Trey Shugart

• Re: [w3c/webcomponents] Consider adding a childrenChangedCallback or something (#619) (Wednesday, 28 December)
• Re: [w3c/webcomponents] Consider adding a childrenChangedCallback or something (#619) (Wednesday, 28 December)
• Re: [w3c/webcomponents] Can't reuse custom element constructors? (#618) (Wednesday, 21 December)
• Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Friday, 2 December)

tripu

• [w3c/clipboard-apis] Pause automatic publication for now (#37) (Thursday, 22 December)
• Re: [w3c/clipboard-apis] Import and set up ReSpec (#36) (Tuesday, 20 December)
• [w3c/clipboard-apis] Import and set up ReSpec (#36) (Tuesday, 20 December)
• [w3c/clipboard-apis] Remove file “ECHIDNA” (#35) (Tuesday, 20 December)
• Re: [w3c/WebPlatformWG] [WIP] Use Apiary to show updated info on home page (#83) (Wednesday, 7 December)
• [w3c/WebPlatformWG] [WIP] Use Apiary to show updated info on home page (#83) (Wednesday, 7 December)
• Re: [w3c/WebPlatformWG] Add Chong Zhang to attendees (#74) (Wednesday, 7 December)
• Re: [w3c/WebPlatformWG] spell fix (#73) (Wednesday, 7 December)
• Re: [w3c/WebPlatformWG] Update TPAC Editing meeting agenda (#77) (Wednesday, 7 December)

Valentin Gosu

• Re: [whatwg/url] unicode fragments (#150) (Thursday, 8 December)
• Re: [whatwg/url] unicode fragments (#150) (Thursday, 8 December)

Victor Costan

• Re: [w3c/IndexedDB] Clarify the conditions for running create/deleteObjectStore() (#129) (Friday, 16 December)
• [w3c/IndexedDB] Tiny grammar mistake (#123) (Friday, 2 December)

Vincent Scheib

• Re: [w3c/pointerlock] Use <pre class=idl> for IDL blocks (#13) (Monday, 5 December)
• Re: [w3c/pointerlock] chore: use new school WebIDL (closes #13) (#14) (Monday, 5 December)
• Re: [w3c/pointerlock] chore: use new school WebIDL (closes #13) (#14) (Monday, 5 December)

Walter

• Re: [w3c/webcomponents] Extend the slotting algorithm so that a slot can select an element which doesn't have slot attribute. (#343) (Thursday, 29 December)

Wendy Seltzer

• Re: [w3c/IndexedDB] TLS is the new SSL (#119) (Friday, 2 December)
• Re: [w3c/IndexedDB] Change SSL references to TLS (#120) (Friday, 2 December)
• Re: [w3c/IndexedDB] Change SSL references to TLS (#120) (Friday, 2 December)
• [w3c/IndexedDB] TLS is the new SSL (#119) (Thursday, 1 December)
• [w3c/screen-orientation] Lacks a privacy and security consideration section (#96) (Thursday, 1 December)

wisniewskit

• Re: [whatwg/xhr] Make FormData a cloneable object (#55) (Saturday, 10 December)

Xiaoqian Wu

• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Tuesday, 6 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Tuesday, 6 December)
• Re: [w3c/manifest] Add support for 'serviceworkers' member (#507) (Tuesday, 6 December)
• Re: [w3c/IndexedDB] Parity between key retrieval steps and type conversions (#122) (Saturday, 3 December)
• Re: [w3c/IndexedDB] Repository website (#115) (Thursday, 1 December)
• Re: [w3c/IndexedDB] Repository website (#115) (Thursday, 1 December)

Xidorn Quan

• Re: [whatwg/fullscreen] Define fully exit fullscreen in terms of exitFullscreen({ fully: true }) (#65) (Monday, 19 December)
• Re: [whatwg/fullscreen] Allow fullscreen on initial load of a page (#36) (Friday, 16 December)
• Re: [whatwg/fullscreen] Allow fullscreen on initial load of a page (#36) (Friday, 16 December)
• Re: [whatwg/fullscreen] Allow fullscreen on initial load of a page (#36) (Friday, 16 December)
• Re: [whatwg/fullscreen] Allow fullscreen on initial load of a page (#36) (Thursday, 15 December)
• Re: [whatwg/fullscreen] Allow fullscreen on initial load of a page (#36) (Thursday, 8 December)
• [whatwg/dom] Inform event handler about the default action of an event (#382) (Saturday, 3 December)

Yoav Weiss

• [whatwg/fetch] Add "fetch" as a destination for "connect-src" bound features (#442) (Thursday, 22 December)
• [whatwg/fetch] Split up media into video, audio and track (#437) (Friday, 16 December)
• Re: [whatwg/fetch] consider exposing and allowing script to set Request priority (#436) (Thursday, 15 December)

yosin

• [w3c/editing] Should we propose "::caret" pseudo-element to CSS WG? (#158) (Thursday, 8 December)

youennf

• Re: [whatwg/fetch] Should we send an Origin header for no-cors fetches? (#225) (Friday, 9 December)
• Re: [whatwg/fetch] Should we send an Origin header for no-cors fetches? (#225) (Thursday, 8 December)

Yutaka Hirano

• Re: [whatwg/fetch] Define "to read a request" more specifically (#441) (Tuesday, 20 December)
• Re: [whatwg/fetch] Define "to read a request" more specifically (#441) (Tuesday, 20 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Tuesday, 20 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Tuesday, 20 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Tuesday, 20 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Tuesday, 20 December)
• Re: [whatwg/fetch] Define "to read a request" more specifically (#441) (Tuesday, 20 December)
• [whatwg/fetch] Define "to read a request" more specifically (#441) (Tuesday, 20 December)
• Re: [whatwg/fetch] Remove an obsolete not for ReadableStream type (#440) (Tuesday, 20 December)
• [whatwg/fetch] Remove an obsolete not for ReadableStream type (#440) (Tuesday, 20 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Monday, 19 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Monday, 19 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Monday, 19 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Monday, 19 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Monday, 19 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Monday, 19 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Friday, 16 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Friday, 9 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Friday, 9 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Friday, 9 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Friday, 9 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Friday, 9 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Friday, 9 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Friday, 9 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Friday, 9 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Friday, 9 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Monday, 5 December)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Monday, 5 December)

Yves Lafon

• Re: [w3c/ServiceWorker] Link to v1 in README.md (#1043) (Saturday, 31 December)

Zambonifofex

• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 14 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 13 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 13 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 11 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 11 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 10 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 5 December)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 4 December)
• [w3c/webcomponents] defining and instantiating customized built‐in elements as if they were autonomous custom elements (#613) (Thursday, 1 December)

Иван К

• Re: [whatwg/fetch] Aborting a fetch (#27) (Thursday, 15 December)
• Re: [whatwg/fetch] Aborting a fetch (#27) (Thursday, 15 December)

Last message date: Saturday, 31 December 2016 20:02:10 UTC