public-webapps-github@w3.org from May 2017 by author

=JeffH

• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Thursday, 4 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Thursday, 4 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Thursday, 4 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Thursday, 4 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Thursday, 4 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Thursday, 4 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Thursday, 4 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Thursday, 4 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Thursday, 4 May)

Aaron Gustafson

• Re: [w3c/manifest] Add (optional) "category" member (#569) (Wednesday, 3 May)
• Re: [w3c/manifest] Add (optional) "category" member (#569) (Tuesday, 2 May)
• Re: [w3c/manifest] Add (optional) "category" member (#569) (Tuesday, 2 May)

achristensen07

• Re: [whatwg/url] Record whether the URL parser removed newlines. (#284) (Thursday, 25 May)
• Re: [whatwg/url] Record whether the URL parser removed newlines. (#284) (Wednesday, 24 May)
• Re: [whatwg/url] Record whether the URL parser removed newlines. (#284) (Wednesday, 24 May)
• Re: [whatwg/url] Record whether the URL parser removed newlines. (#284) (Wednesday, 24 May)
• Re: [whatwg/url] Record whether the URL parser removed newlines. (#284) (Tuesday, 23 May)
• Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) (Tuesday, 23 May)
• Re: [whatwg/url] Record whether the URL parser removed newlines. (#284) (Tuesday, 23 May)
• Re: [whatwg/url] Specify window.webkitURL as an alias to URL (#312) (Tuesday, 23 May)
• Re: [whatwg/url] Record whether the URL parser removed newlines. (#284) (Monday, 22 May)

Adam Klein

• Re: [heycam/webidl] Only install @@toStringTag on the prototype (#357) (Wednesday, 3 May)

Adam Rice

• Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Tuesday, 30 May)
• Re: [whatwg/streams] pipeTo should return a cancelable promise (#446) (Monday, 22 May)
• Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Monday, 22 May)
• Re: [whatwg/streams] ReadableStreamDefaultController seems redundant (#743) (Wednesday, 10 May)

Addison Phillips

• Re: [w3ctag/design-reviews] Serialization of natural language in data formats such as JSON [I18N] (#178) (Thursday, 18 May)
• [w3ctag/design-reviews] Serialization of natural language in data formats such as JSON [I18N] (#178) (Thursday, 18 May)
• Re: [whatwg/encoding] Half-width Katakana should be representable in ISO-2022-JP (#105) (Sunday, 7 May)
• Re: [whatwg/encoding] Half-width Katakana should be representable in ISO-2022-JP (#105) (Friday, 5 May)
• Re: [whatwg/encoding] Half-width Katakana should be representable in ISO-2022-JP (#105) (Friday, 5 May)

Agniva De Sarker

• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Tuesday, 30 May)

albertsylvester

• Re: [w3c/ServiceWorker] Service Worker makes AJAX Progress Listener not Working (#1141) (Tuesday, 16 May)
• Re: [w3c/ServiceWorker] Service Worker makes AJAX Progress Listener not Working (#1141) (Tuesday, 16 May)
• Re: [w3c/ServiceWorker] Service Worker makes AJAX Progress Listener not Working (#1141) (Tuesday, 16 May)
• Re: [w3c/ServiceWorker] Service Worker makes AJAX Progress Listener not Working (#1141) (Tuesday, 16 May)
• [w3c/ServiceWorker] Service Worker makes AJAX Progress Listener not Working (#1141) (Tuesday, 16 May)

Alexander Shalamov

• [w3c/screen-orientation] Orientation angle to orientation type mapping for 2-in-1 devices (#101) (Tuesday, 2 May)
• [w3c/screen-orientation] Steps for updating orientation information are misleading (#100) (Tuesday, 2 May)
• [w3c/screen-orientation] Orientation angle cannot be precisely mapped to orientation type for devices with 1:1 screen size ratio (#99) (Tuesday, 2 May)

alexelias

• Re: [whatwg/encoding] Amount of bytes to sniff for encoding detection (#102) (Tuesday, 23 May)
• Re: [whatwg/encoding] Amount of bytes to sniff for encoding detection (#102) (Friday, 19 May)
• Re: [whatwg/encoding] Amount of bytes to sniff for encoding detection (#102) (Friday, 19 May)
• Re: [whatwg/encoding] Amount of bytes to sniff for encoding detection (#102) (Tuesday, 9 May)
• Re: [whatwg/encoding] Amount of bytes to sniff for encoding detection (#102) (Monday, 8 May)

Alwin Blok

• Re: [whatwg/url] Why is the host dropped if the path contains a Windows drive letter? (#302) (Thursday, 4 May)

amn

• Re: [whatwg/fetch] Developer-controlled streams for request/response (#88) (Wednesday, 10 May)

Andrea Giammarchi

• Re: [whatwg/dom] Consider boolean interface for properties (#461) (Tuesday, 23 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 22 May)
• Re: [whatwg/dom] Consider boolean interface for properties (#461) (Monday, 22 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 22 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 22 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 22 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 22 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 22 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 21 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 21 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 20 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 20 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 18 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 18 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 17 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 17 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 14 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 9 May)

Andrea Marchesini

• Re: [whatwg/url] Let webkitURL be an alias of the URL constructor (#135) (Wednesday, 31 May)

Andy Earnshaw

• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Monday, 22 May)
• Re: [whatwg/dom] Make EventTarget subclassable (#441) (Tuesday, 16 May)
• Re: [whatwg/dom] Make EventTarget subclassable (#441) (Monday, 15 May)

Anne van Kesteren

• Re: [whatwg/url] Address several IDNA issues (#309) (Wednesday, 24 May)
• Re: [whatwg/url] Address several IDNA issues (#309) (Wednesday, 24 May)
• Re: [whatwg/fetch] access-conrol-allow-origin: * can be interpreted in two ways (#548) (Wednesday, 24 May)
• Re: [whatwg/url] IDNA / UTS #46 "should" requirements (Bidi and Joiners) (#110) (Wednesday, 24 May)
• Re: [whatwg/fetch] access-conrol-allow-origin: * can be interpreted in two ways (#548) (Wednesday, 24 May)
• Re: [whatwg/url] Address several IDNA issues (#309) (Wednesday, 24 May)
• Re: [whatwg/url] IDNA (#53) (Wednesday, 24 May)
• Re: [whatwg/url] Address several IDNA issues (#309) (Wednesday, 24 May)
• Re: [whatwg/url] IDNA (#53) (Wednesday, 24 May)
• [whatwg/url] IDNA: realign once UTS46 revision 18 is final (#313) (Wednesday, 24 May)
• Re: [whatwg/url] Refactor IPv6 in terms of lists (#286) (Wednesday, 24 May)
• Re: [whatwg/url] Refactor IPv6 in terms of lists (#286) (Wednesday, 24 May)
• Re: [whatwg/url] Refactor IPv6 in terms of lists (#286) (Wednesday, 24 May)
• Re: [whatwg/encoding] For your information: Illegal UTF-8 proposal (#112) (Wednesday, 24 May)
• Re: [whatwg/fetch] Add potential destination. (#547) (Wednesday, 24 May)
• Re: [whatwg/fetch] Add potential destination. (#547) (Wednesday, 24 May)
• Re: [whatwg/fetch] Add potential destination. (#547) (Wednesday, 24 May)
• Re: [whatwg/fetch] Add potential destination. (#547) (Wednesday, 24 May)
• Re: [whatwg/dom] DOMTokenList.remove() can add an attribute (#462) (Wednesday, 24 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Wednesday, 24 May)
• Re: [whatwg/encoding] Meta: retry HTML checker by curl, suppress warnings (#109) (Tuesday, 23 May)
• Re: [whatwg/fetch] Add potential destination. (#547) (Tuesday, 23 May)
• Re: [whatwg/encoding] Meta: retry HTML checker by curl, suppress warnings (#109) (Tuesday, 23 May)
• Re: [whatwg/fetch] Add potential destination. (#547) (Tuesday, 23 May)
• Re: [whatwg/url] Record whether the URL parser removed newlines. (#284) (Tuesday, 23 May)
• Re: [whatwg/fetch] Add potential destination. (#547) (Tuesday, 23 May)
• Re: [whatwg/encoding] Amount of bytes to sniff for encoding detection (#102) (Tuesday, 23 May)
• Re: [whatwg/url] Record whether the URL parser removed newlines. (#284) (Tuesday, 23 May)
• Re: [whatwg/fetch] Block requests for suspected dangling markup. (#519) (Tuesday, 23 May)
• Re: [whatwg/dom] DOMTokenList.remove() can add an attribute (#462) (Tuesday, 23 May)
• Re: [whatwg/url] Record whether the URL parser removed newlines. (#284) (Tuesday, 23 May)
• Re: [whatwg/dom] Consider boolean interface for properties (#461) (Tuesday, 23 May)
• Re: [whatwg/fetch] Prevent requests to HTTP(S) URLs containing raw `\n` and `<`. (#546) (Tuesday, 23 May)
• Re: [whatwg/url] Specify window.webkitURL as an alias to URL (#312) (Monday, 22 May)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Monday, 22 May)
• Re: [whatwg/storage] UI and origins <> origin groups (#34) (Monday, 22 May)
• Re: [whatwg/xhr] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience (#140) (Monday, 22 May)
• Re: [whatwg/xhr] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience (#140) (Monday, 22 May)
• Re: [whatwg/xhr] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience (#140) (Monday, 22 May)
• Re: [whatwg/url] Specify window.webkitURL as an alias to URL (#312) (Monday, 22 May)
• Re: [whatwg/fullscreen] Fire events at elements by default, falling back to documents (#90) (Monday, 22 May)
• Re: [whatwg/url] Let webkitURL be an alias of the URL constructor (#135) (Monday, 22 May)
• Re: [whatwg/encoding] Amount of bytes to sniff for encoding detection (#102) (Monday, 22 May)
• Re: [whatwg/fetch] Prevent requests to URLs containing raw `\n` and `<`. (#546) (Monday, 22 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Monday, 22 May)
• Re: [whatwg/encoding] Amount of bytes to sniff for encoding detection (#102) (Saturday, 20 May)
• Re: [whatwg/url] Clearly indicate a known issue with ToASCII (#309) (Saturday, 20 May)
• Re: [whatwg/url] Refactor IPv6 in terms of lists (#286) (Friday, 19 May)
• Re: [whatwg/url] Refactor IPv6 in terms of lists (#286) (Friday, 19 May)
• Re: [whatwg/url] Expose origin as ASCII or Unicode (#297) (Friday, 19 May)
• Re: [whatwg/url] Make URL's origin return solely ASCII code points (#311) (Friday, 19 May)
• Re: [whatwg/url] IDNA / UTS #46 "should" requirements (#110) (Friday, 19 May)
• Re: [whatwg/url] IDNA / UTS #46 "should" requirements (#110) (Friday, 19 May)
• Re: [whatwg/url] Clearly indicate a known issue with ToASCII (#309) (Friday, 19 May)
• Re: [whatwg/url] Clearly indicate a known issue with ToASCII (#309) (Friday, 19 May)
• Re: [whatwg/fullscreen] Fire fullscreenchange at elements by default, documents if necessary (#90) (Friday, 19 May)
• Re: [whatwg/fetch] should Response.blob() type include parameters like charset? (#540) (Friday, 19 May)
• Re: [whatwg/fetch] should Response.blob() type include parameters like charset? (#540) (Friday, 19 May)
• Re: [whatwg/fetch] should Response.blob() type include parameters like charset? (#540) (Friday, 19 May)
• Re: [w3c/ServiceWorker] Fix fetchEvent.request initialization (#1147) (Friday, 19 May)
• Re: [whatwg/fullscreen] Fire fullscreenchange at elements by default, documents if necessary (#90) (Friday, 19 May)
• Re: [whatwg/fetch] should Response.blob() type include parameters like charset? (#540) (Friday, 19 May)
• Re: [whatwg/fetch] Add domintro explanations for web developers (#543) (Friday, 19 May)
• Re: [whatwg/encoding] Amount of bytes to sniff for encoding detection (#102) (Friday, 19 May)
• Re: [whatwg/fetch] Small cors typo (#545) (Friday, 19 May)
• Re: [whatwg/fetch] Small cors typo (#545) (Friday, 19 May)
• Re: [whatwg/url] Perhaps do not apply ToASCII for ASCII-only input (#267) (Friday, 19 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Friday, 19 May)
• Re: [whatwg/xhr] jquery.js:9615 [Deprecation] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/. (#139) (Friday, 19 May)
• Re: [whatwg/xhr] jquery.js:9615 [Deprecation] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/. (#139) (Friday, 19 May)
• Re: [whatwg/dom] Abort controller (#437) (Thursday, 18 May)
• Re: [whatwg/fetch] WIP: Cancelation (#523) (Thursday, 18 May)
• Re: [whatwg/fetch] WIP: Cancelation (#523) (Thursday, 18 May)
• Re: [whatwg/fullscreen] Fire fullscreenchange at elements by default, documents if necessary (#90) (Thursday, 18 May)
• Re: [whatwg/url] Perhaps do not apply ToASCII for ASCII-only input (#267) (Thursday, 18 May)
• Re: [whatwg/url] IDNA / UTS #46 "should" requirements (#110) (Thursday, 18 May)
• Re: [whatwg/url] IDNA / UTS #46 "should" requirements (#110) (Thursday, 18 May)
• Re: [whatwg/dom] Abort controller (#437) (Thursday, 18 May)
• Re: [whatwg/url] Expose origin as ASCII or Unicode (#297) (Thursday, 18 May)
• Re: [whatwg/url] Perhaps do not apply ToASCII for ASCII-only input (#267) (Thursday, 18 May)
• Re: [whatwg/url] Make URL's origin return solely ASCII code points (#311) (Thursday, 18 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Thursday, 18 May)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Thursday, 18 May)
• Re: [whatwg/dom] Abort controller (#437) (Wednesday, 17 May)
• Re: [whatwg/dom] Abort controller (#437) (Wednesday, 17 May)
• Re: [whatwg/dom] Abort controller (#437) (Wednesday, 17 May)
• Re: [whatwg/dom] Abort controller (#437) (Wednesday, 17 May)
• Re: [whatwg/dom] Abort controller (#437) (Wednesday, 17 May)
• Re: [whatwg/url] Clearly indicate a known issue with ToASCII (#309) (Wednesday, 17 May)
• [w3c/ServiceWorker] Use ASCII serialization for origins (#1142) (Wednesday, 17 May)
• Re: [whatwg/url] Make URL's origin return solely ASCII code points (#311) (Wednesday, 17 May)
• Re: [whatwg/dom] Abort controller (#437) (Wednesday, 17 May)
• Re: [whatwg/dom] Abort controller (#437) (Wednesday, 17 May)
• Re: [whatwg/dom] Abort controller (#437) (Wednesday, 17 May)
• Re: [whatwg/dom] Abort controller (#437) (Wednesday, 17 May)
• Re: [whatwg/dom] Abort controller (#437) (Wednesday, 17 May)
• Re: [whatwg/dom] Don't set a suppress signaling flag when a slot is inserted (#459) (Wednesday, 17 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Wednesday, 17 May)
• Re: [whatwg/dom] Abort controller design (#438) (Wednesday, 17 May)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Wednesday, 17 May)
• Re: [heycam/webidl] How to do aliases of legacy interfaces (HTMLDocument, WebKitCSSMatrix...) (#362) (Wednesday, 17 May)
• Re: [heycam/webidl] How to do aliases of legacy interfaces (HTMLDocument, WebKitCSSMatrix...) (#362) (Tuesday, 16 May)
• Re: [heycam/webidl] How to do aliases of legacy interfaces (HTMLDocument, WebKitCSSMatrix...) (#362) (Tuesday, 16 May)
• [whatwg/url] Make URL's origin return solely ASCII code points (#311) (Tuesday, 16 May)
• Re: [heycam/webidl] How to do aliases of legacy interfaces (HTMLDocument, WebKitCSSMatrix...) (#362) (Tuesday, 16 May)
• Re: [whatwg/fullscreen] In requestFullscreen(), handle the pending element moving (#87) (Tuesday, 16 May)
• Re: [heycam/webidl] How to do aliases of legacy interfaces (HTMLDocument, WebKitCSSMatrix...) (#362) (Tuesday, 16 May)
• Re: [whatwg/dom] Abort controller design (#438) (Tuesday, 16 May)
• Re: [whatwg/streams] Allow aborting an ongoing pipe operation using AbortSignals (#744) (Tuesday, 16 May)
• Re: [whatwg/dom] Abort controller (#437) (Tuesday, 16 May)
• Re: [whatwg/dom] Abort controller (#437) (Tuesday, 16 May)
• Re: [whatwg/dom] Abort controller design (#438) (Tuesday, 16 May)
• Re: [heycam/webidl] Designing mixins (#363) (Tuesday, 16 May)
• Re: [whatwg/fetch] "With Credentials" flag possibly inconsistent with web architecture (#517) (Tuesday, 16 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Tuesday, 16 May)
• Re: [whatwg/dom] Abort controller (#437) (Monday, 15 May)
• Re: [whatwg/dom] Abort controller design (#438) (Monday, 15 May)
• Re: [whatwg/dom] Abort controller (#437) (Monday, 15 May)
• Re: [whatwg/dom] Abort controller (#437) (Monday, 15 May)
• Re: [whatwg/dom] Abort controller (#437) (Monday, 15 May)
• Re: [whatwg/dom] Abort controller (#437) (Monday, 15 May)
• Re: [whatwg/dom] Abort controller (#437) (Monday, 15 May)
• Re: [whatwg/dom] Define a 'CancelationController' and 'CancelationSignal' interface. (#434) (Monday, 15 May)
• Re: [whatwg/dom] Define a 'CancelationController' and 'CancelationSignal' interface. (#434) (Monday, 15 May)
• Re: [whatwg/dom] Abort controller (#437) (Monday, 15 May)
• Re: [whatwg/dom] Abort controller (#437) (Monday, 15 May)
• Re: [whatwg/dom] Abort controller (#437) (Monday, 15 May)
• Re: [whatwg/fetch] "With Credentials" flag possibly inconsistent with web architecture (#517) (Monday, 15 May)
• Re: [whatwg/encoding] Should not prepend gb18030 second and third when range decode fails upon fourth (#110) (Monday, 15 May)
• Re: [whatwg/encoding] gb18030 decoder: unwind from fourth byte when it's not a digit (#111) (Monday, 15 May)
• Re: [whatwg/url] Clearly indicate a known issue with ToASCII (#309) (Monday, 15 May)
• Re: [whatwg/url] Clearly indicate a known issue with ToASCII (#309) (Monday, 15 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Monday, 15 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Monday, 15 May)
• Re: [w3c/ServiceWorker] Service worker MessageEvents set the "origin" property, but Worker MessageEvents do not. (#1122) (Monday, 15 May)
• Re: [whatwg/fetch] Consider adding SMB to port blacklist (#544) (Sunday, 14 May)
• Re: [whatwg/url] new URL('file://').origin is 'null' (#310) (Sunday, 14 May)
• Re: [whatwg/url] new URL('file://').origin is 'null' (#310) (Sunday, 14 May)
• Re: [whatwg/url] new URL('file://').origin is 'null' (#310) (Sunday, 14 May)
• Re: [whatwg/fetch] Consider adding SMB to port blacklist (#544) (Sunday, 14 May)
• Re: [whatwg/fetch] Add support for federated token binding to fetch (#30) (Saturday, 13 May)
• Re: [whatwg/fetch] Add support for federated token binding to fetch (#30) (Saturday, 13 May)
• Re: [heycam/webidl] Figure-out what supporting Array-subclassing implies (#345) (Saturday, 13 May)
• Re: [heycam/webidl] Consider flipping the [Unscopable] design (#361) (Friday, 12 May)
• Re: [heycam/webidl] Consider flipping the [Unscopable] design (#361) (Friday, 12 May)
• Re: [whatwg/fetch] Add domintro explanations for web developers (#543) (Friday, 12 May)
• Re: [w3c/ServiceWorker] Assert same-origin for registration matching (#1138) (Friday, 12 May)
• Re: [w3c/ServiceWorker] Assert same-origin for registration matching (#1138) (Friday, 12 May)
• Re: [heycam/webidl] How to do aliases of legacy interfaces (HTMLDocument, WebKitCSSMatrix...) (#362) (Friday, 12 May)
• Re: [w3c/ServiceWorker] Assert same-origin for registration matching (#1138) (Friday, 12 May)
• Re: [w3c/ServiceWorker] Assert same-origin for registration matching (#1138) (Friday, 12 May)
• Re: [heycam/webidl] How to do aliases of legacy interfaces (HTMLDocument, WebKitCSSMatrix...) (#362) (Friday, 12 May)
• Re: [w3c/ServiceWorker] Assert same-origin for registration matching (#1138) (Friday, 12 May)
• Re: [whatwg/fullscreen] Require that the document is fully active in requestFullscreen() (#85) (Friday, 12 May)
• Re: [whatwg/fullscreen] Require that the document is fully active in requestFullscreen() (#85) (Friday, 12 May)
• Re: [whatwg/fullscreen] Require that the document is fully active in requestFullscreen() (#85) (Friday, 12 May)
• Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) (Friday, 12 May)
• Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) (Friday, 12 May)
• Re: [whatwg/url] Clearly indicate a known issue with ToASCII (#309) (Friday, 12 May)
• [heycam/webidl] Consider flipping the [Unscopable] design (#361) (Friday, 12 May)
• Re: [whatwg/fullscreen] Add [Unscopable] to Document.prototype.fullscreen (#84) (Friday, 12 May)
• [whatwg/fullscreen] Add [Unscopable] to Document.prototype.fullscreen (#84) (Friday, 12 May)
• Re: [whatwg/url] Clearly indicate a known issue with ToASCII (#309) (Friday, 12 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Friday, 12 May)
• [whatwg/url] Clearly indicate a known issue with ToASCII (#309) (Friday, 12 May)
• Re: [whatwg/fetch] Remove null origin issue (#542) (Friday, 12 May)
• Re: [whatwg/fetch] Remove null origin issue (#542) (Friday, 12 May)
• Re: [whatwg/fetch] Remove null origin issue (#542) (Thursday, 11 May)
• Re: [whatwg/fetch] Remove null origin issue (#542) (Thursday, 11 May)
• Re: [whatwg/fetch] Remove null origin issue (#542) (Thursday, 11 May)
• Re: [whatwg/url] IDNA (#53) (Thursday, 11 May)
• Re: [whatwg/fullscreen] Editorial: use Infra's break to clarify requestFullscreen() iteration (#83) (Thursday, 11 May)
• Re: [w3c/FileAPI] Replace RFC1738 with RFC4266 (gopher) (#81) (Thursday, 11 May)
• Re: [w3c/FileAPI] Fix link to "that repository" in README.md (#80) (Thursday, 11 May)
• Re: [whatwg/fullscreen] Problems with the "unloading document cleanup steps" (#82) (Thursday, 11 May)
• Re: [whatwg/fullscreen] Editorial: use Infra's break to clarify requestFullscreen() iteration (#83) (Thursday, 11 May)
• Re: [whatwg/fullscreen] Editorial: use Infra's break to clarify requestFullscreen() iteration (#83) (Thursday, 11 May)
• Re: [whatwg/fullscreen] Editorial: use Infra's break to clarify requestFullscreen() iteration (#83) (Thursday, 11 May)
• Re: [whatwg/fullscreen] Problems with the "unloading document cleanup steps" (#82) (Thursday, 11 May)
• Re: [whatwg/encoding] gb18030 decoder: unwind from fourth byte when it's not a digit (#111) (Thursday, 11 May)
• Re: [whatwg/encoding] gb18030 decoder: unwind from fourth byte when it's not a digit (#111) (Thursday, 11 May)
• Re: [whatwg/encoding] Editorial: ensure various bits link properly (#104) (Thursday, 11 May)
• [whatwg/encoding] gb18030 encoder: unwind from fourth byte when it's not a digit (#111) (Thursday, 11 May)
• Re: [whatwg/encoding] Should not prepend gb18030 second and third when range decode fails upon fourth (#110) (Thursday, 11 May)
• Re: [whatwg/encoding] Should not prepend gb18030 second and third when range decode fails upon fourth (#110) (Thursday, 11 May)
• Re: [whatwg/url] IDNA (#53) (Thursday, 11 May)
• Re: [w3c/ServiceWorker] Match Service Worker Registration should assert same-origin? (#1118) (Thursday, 11 May)
• Re: [whatwg/dom] Details missing on (lack of) namespace support in Element.match (#458) (Thursday, 11 May)
• Re: [heycam/webidl] Figure-out what supporting Array-subclassing implies (#345) (Thursday, 11 May)
• Re: [heycam/webidl] [EnforceRange] should normatively specify RangeError (#359) (Thursday, 11 May)
• Re: [whatwg/url] Provide means to "strip query" (#247) (Thursday, 11 May)
• Re: [whatwg/fetch] Developer-controlled streams for request/response (#88) (Wednesday, 10 May)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Wednesday, 10 May)
• Re: [whatwg/fullscreen] Clarify what "collect documents to unfullscreen" returns (#81) (Wednesday, 10 May)
• Re: [whatwg/fullscreen] Editorial: update variable name in removing steps (#80) (Wednesday, 10 May)
• Re: [whatwg/fullscreen] Meta: use infra for lists and sets (#79) (Wednesday, 10 May)
• Re: [w3ctag/design-reviews] SharedArrayBuffer + Atomics (#165) (Wednesday, 10 May)
• Re: [whatwg/dom] "The value attribute’s getter must return the va..." (#456) (Wednesday, 10 May)
• Re: [whatwg/dom] Node Tree section should probably include Attr (#457) (Wednesday, 10 May)
• Re: [whatwg/dom] "The value attribute’s getter must return the va..." (#456) (Wednesday, 10 May)
• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Wednesday, 10 May)
• Re: [heycam/webidl] Figure-out what supporting Array-subclassing implies (#345) (Wednesday, 10 May)
• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Tuesday, 9 May)
• Re: [whatwg/fullscreen] Meta: use infra for lists and sets (#79) (Tuesday, 9 May)
• Re: [whatwg/url] javascript: URL parsing (#307) (Tuesday, 9 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Tuesday, 9 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Tuesday, 9 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Tuesday, 9 May)
• Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) (Tuesday, 9 May)
• Re: [whatwg/fetch] Is a missing HeadersInit treated differently from an empty one? (#479) (Tuesday, 9 May)
• Re: [whatwg/fetch] Is a missing HeadersInit treated differently from an empty one? (#479) (Tuesday, 9 May)
• Re: [whatwg/encoding] Editorial: ensure various bits link properly (#104) (Tuesday, 9 May)
• Re: [whatwg/encoding] Editorial: ensure various bits link properly (#104) (Tuesday, 9 May)
• Re: [whatwg/fetch] .pr-preview file lists h1 as "URL", not "Fetch" (#539) (Tuesday, 9 May)
• Re: [whatwg/fetch] .pr-preview file lists h1 as "URL", not "Fetch" (#539) (Tuesday, 9 May)
• Re: [whatwg/fetch] Request body streams that cannot be retried (#538) (Monday, 8 May)
• Re: [whatwg/fetch] Request body streams that cannot be retried (#538) (Monday, 8 May)
• Re: [whatwg/fetch] Request body streams that cannot be retried (#538) (Monday, 8 May)
• [whatwg/fetch] Request body streams that cannot be retried (#538) (Monday, 8 May)
• Re: [w3c/FileAPI] Export "Blob URL Store" definition (#77) (Monday, 8 May)
• Re: [whatwg/encoding] ISO-2022-JP encoder: convert halfwidth Katakana to fullwidth (#106) (Monday, 8 May)
• Re: [whatwg/encoding] Half-width Katakana should be representable in ISO-2022-JP (#105) (Monday, 8 May)
• Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) (Monday, 8 May)
• Re: [whatwg/encoding] ISO-2022-JP encoder: convert halfwidth Katakana to fullwidth (#106) (Sunday, 7 May)
• Re: [whatwg/encoding] ISO-2022-JP encoder: convert halfwidth Katakana to fullwidth (#106) (Sunday, 7 May)
• Re: [whatwg/encoding] ISO-2022-JP encoder: convert halfwidth Katakana to fullwidth (#106) (Sunday, 7 May)
• Re: [whatwg/encoding] Half-width Katakana should be representable in ISO-2022-JP (#105) (Sunday, 7 May)
• Re: [whatwg/encoding] Half-width Katakana should be representable in ISO-2022-JP (#105) (Sunday, 7 May)
• Re: [whatwg/encoding] ISO-2022-JP encoder: convert halfwidth Katakana to fullwidth (#106) (Sunday, 7 May)
• Re: [whatwg/encoding] ISO-2022-JP encoder: convert halfwidth Katakana to fullwidth (#106) (Saturday, 6 May)
• Re: [whatwg/encoding] ISO-2022-JP encoder: convert halfwidth Katakana to fullwidth (#106) (Saturday, 6 May)
• Re: [whatwg/encoding] ISO-2022-JP encoder: convert halfwidth Katakana to fullwidth (#106) (Saturday, 6 May)
• Re: [whatwg/encoding] ISO-2022-JP encoder: convert halfwidth Katakana to fullwidth (#106) (Friday, 5 May)
• Re: [whatwg/encoding] Half-width Katakana should be representable in ISO-2022-JP (#105) (Friday, 5 May)
• Re: [w3c/FileAPI] Export "Blob URL Store" definition (#77) (Friday, 5 May)
• Re: [whatwg/encoding] ISO-2022-JP encoder: convert halfwidth Katakana to fullwidth (#106) (Friday, 5 May)
• Re: [whatwg/encoding] Half-width Katakana should be representable in ISO-2022-JP (#105) (Friday, 5 May)
• Re: [whatwg/encoding] Editorial: remove substeps as a concept (#108) (Friday, 5 May)
• Re: [whatwg/encoding] Editorial: check non-null before null (#107) (Friday, 5 May)
• Re: [whatwg/encoding] EUC-JP: only unwind ASCII bytes (#103) (Friday, 5 May)
• Re: [whatwg/encoding] Important warnings getting lost in the noise (#97) (Friday, 5 May)
• Re: [whatwg/encoding] Important warnings getting lost in the noise (#97) (Friday, 5 May)
• [whatwg/encoding] Editorial: remove substeps as a concept (#108) (Friday, 5 May)
• Re: [whatwg/encoding] EUC-JP: only unwind ASCII bytes (#103) (Friday, 5 May)
• [whatwg/encoding] Editorial: check non-null before null (#107) (Friday, 5 May)
• Re: [whatwg/encoding] EUC-JP: only unwind ASCII bytes (#103) (Friday, 5 May)
• Re: [whatwg/encoding] ISO-2022-JP encoder: convert halfwidth Katakana to fullwidth (#106) (Friday, 5 May)
• Re: [whatwg/encoding] ISO-2022-JP encoder: convert halfwidth Katakana to fullwidth (#106) (Friday, 5 May)
• Re: [whatwg/encoding] Editorial: ensure various bits link properly (#104) (Friday, 5 May)
• Re: [whatwg/encoding] ISO-2022-JP encoder: convert halfwidth Katakana to fullwidth (#106) (Friday, 5 May)
• Re: [whatwg/encoding] ISO-2022-JP encoder: convert halfwidth Katakana to fullwidth (#106) (Friday, 5 May)
• [whatwg/encoding] ISO-2022-JP encoder: convert halfwidth Katakana to fullwidth (#106) (Friday, 5 May)
• Re: [whatwg/encoding] Half-width Katakana should be representable in ISO-2022-JP (#105) (Friday, 5 May)
• Re: [whatwg/encoding] Half-width Katakana should be representable in ISO-2022-JP (#105) (Friday, 5 May)
• Re: [whatwg/encoding] Half-width Katakana should be representable in ISO-2022-JP (#105) (Friday, 5 May)
• Re: [whatwg/encoding] Half-width Katakana should be representable in ISO-2022-JP (#105) (Friday, 5 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Friday, 5 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Friday, 5 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Friday, 5 May)
• Re: [whatwg/fetch] Editorial: rename "basic fetch" to "scheme fetch" (#537) (Friday, 5 May)
• Re: [whatwg/fetch] Editorial: rename "basic fetch" to "scheme fetch" (#537) (Friday, 5 May)
• Re: [whatwg/url] Why is the host dropped if the path contains a Windows drive letter? (#302) (Friday, 5 May)
• Re: [whatwg/fetch] Editorial: rename "basic fetch" to "generic fetch" (#537) (Thursday, 4 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Thursday, 4 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Thursday, 4 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Thursday, 4 May)
• Re: [whatwg/dom] To investigate: do error events bubble to window? (#455) (Thursday, 4 May)
• [w3c/FileAPI] Don't update FileReader's result until "LOAD" (#79) (Thursday, 4 May)
• [whatwg/dom] Document's base URL needs to be cloned (#454) (Thursday, 4 May)
• Re: [whatwg/fullscreen] Fix Bikeshed error about SVG reference (#78) (Thursday, 4 May)
• Re: [whatwg/fullscreen] Fix Bikeshed error about SVG reference (#78) (Thursday, 4 May)
• Re: [whatwg/fullscreen] Use SVG2 for the <svg> element reference (#78) (Thursday, 4 May)
• Re: [whatwg/url] remaining variable ambiguity (#308) (Thursday, 4 May)
• Re: [whatwg/fullscreen] Use SVG2 for the <svg> element reference (#78) (Thursday, 4 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Thursday, 4 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Thursday, 4 May)
• Re: [heycam/webidl] Remove custom [[HasInstance]] behavior from interface objects (#356) (Thursday, 4 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Thursday, 4 May)
• Re: [whatwg/url] remaining variable ambiguity (#308) (Thursday, 4 May)
• Re: [whatwg/url] remaining variable ambiguity (#308) (Thursday, 4 May)
• Re: [heycam/webidl] Remove custom [[HasInstance]] behavior from interface objects (#356) (Thursday, 4 May)
• Re: [whatwg/url] javascript: URL parsing (#307) (Thursday, 4 May)
• Re: [whatwg/fetch] Editorial: rename "basic fetch" to "generic fetch" (#537) (Thursday, 4 May)
• Re: [whatwg/url] javascript: URL parsing (#307) (Wednesday, 3 May)
• Re: [w3c/uievents] Click event is not fired when the node is removed and then added back (#141) (Wednesday, 3 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Wednesday, 3 May)
• Re: [whatwg/fetch] Odd format for fetch callbacks (#536) (Wednesday, 3 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Wednesday, 3 May)
• Re: [w3ctag/design-reviews] Review origin policy. (#127) (Wednesday, 3 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Wednesday, 3 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Wednesday, 3 May)
• Re: [whatwg/url] Fix windows drive letter handling in the file state (#305) (Wednesday, 3 May)
• Re: [whatwg/url] Fix windows drive letter handling in the file state (#305) (Wednesday, 3 May)
• Re: [whatwg/url] EOF after stand-alone drive-letter. (#304) (Wednesday, 3 May)
• Re: [whatwg/fetch] provide a way to construct a new Request from an old Request and an overriding URL (#129) (Wednesday, 3 May)
• Re: [w3c/webcomponents] Create op (#639) (Wednesday, 3 May)
• Re: [w3ctag/design-reviews] Review origin policy. (#127) (Wednesday, 3 May)
• Re: [whatwg/fetch] Odd format for fetch callbacks (#536) (Wednesday, 3 May)
• Re: [whatwg/fetch] Response filter escalation (#535) (Wednesday, 3 May)
• Re: [whatwg/fetch] Response filter escalation (#535) (Tuesday, 2 May)
• Re: [whatwg/fetch] Response filter escalation (#535) (Tuesday, 2 May)
• Re: [whatwg/fetch] Editorial: correct typo (#533) (Tuesday, 2 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Tuesday, 2 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Tuesday, 2 May)
• [whatwg/dom] Define "has event listener" operation (#453) (Tuesday, 2 May)
• Re: [whatwg/fetch] MK (#534) (Tuesday, 2 May)
• Re: [whatwg/url] Editorial: use Infra in a/x-www-form-urlencoded (#300) (Tuesday, 2 May)
• Re: [whatwg/url] Editorial: use Infra in a/x-www-form-urlencoded (#300) (Tuesday, 2 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Tuesday, 2 May)
• Re: [whatwg/fetch] "process request body" is gone (#495) (Tuesday, 2 May)
• Re: [whatwg/fetch] Queue "process request body" tasks during request body transmission (#532) (Tuesday, 2 May)
• Re: [whatwg/fetch] Queue "process request body" tasks during request body transmission (#532) (Tuesday, 2 May)
• Re: [heycam/webidl] "::" is used in comments but is not formally a part of webidl ? (#354) (Tuesday, 2 May)
• Re: [whatwg/fetch] Queue "process request body" tasks during request body transmission (#532) (Tuesday, 2 May)
• Re: [whatwg/url] Editorial: cleanup references (#299) (Tuesday, 2 May)
• Re: [whatwg/url] Fix windows drive letter handling in the file state (#305) (Tuesday, 2 May)
• Re: [whatwg/url] Editorial: use Infra in a/x-www-form-urlencoded (#300) (Tuesday, 2 May)
• Re: [whatwg/fetch] Editorial: correct typo (#533) (Tuesday, 2 May)
• Re: [heycam/webidl] "::" is used in comments but is not formally a part of webidl ? (#354) (Tuesday, 2 May)
• Re: [heycam/webidl] Remove custom [[HasInstance]] behavior from interface objects (#356) (Tuesday, 2 May)
• Re: [w3c/IndexedDB] Use HTML's StructuredSerializeForStorage (#198) (Tuesday, 2 May)

Anssi Kostiainen

• Re: [w3c/permissions] Link generic sensor permission revocation algorithm and fix note links (#146) (Wednesday, 31 May)
• [w3c/permissions] Link generic sensor permission revocation algorithm and fix note links (#146) (Wednesday, 31 May)
• Re: [w3c/manifest] Small markup issues (#572) (Wednesday, 3 May)
• Re: [w3c/manifest] Small markup issues (#572) (Wednesday, 3 May)
• Re: [w3c/manifest] Use data-cite (#574) (Wednesday, 3 May)
• Re: [w3c/manifest] Use data-cite (#574) (Wednesday, 3 May)
• [w3c/manifest] Use data-cite (#574) (Wednesday, 3 May)
• [w3c/manifest] Use data-cite for all references (#573) (Wednesday, 3 May)
• Re: [w3c/manifest] Small markup issues (#572) (Wednesday, 3 May)
• Re: [w3c/manifest] Fix typos in "Privacy consideration: start_url tracking" (#571) (Wednesday, 3 May)
• Re: [w3c/manifest] Fix typos in "Privacy consideration: start_url tracking" (#571) (Wednesday, 3 May)
• Re: [w3c/manifest] Use UTF-8 decode when obtaining a manifest (#570) (Wednesday, 3 May)
• Re: [w3c/manifest] Fix typos in "Privacy consideration: start_url tracking" (#571) (Tuesday, 2 May)
• Re: [w3c/manifest] It is not stated how to decode the bytes obtained (#565) (Tuesday, 2 May)
• [w3c/manifest] Use UTF-8 decode when obtaining a manifest (#570) (Tuesday, 2 May)

Arcadio Garcia Salvadores

• Re: [w3c/manifest] Extending the manifest with 'vendor-specific' properties (#560) (Monday, 1 May)

Arthur Stolyar

• Re: [w3c/push-api] Propose enabling background sync from `pushsubscriptionchange` events (#240) (Monday, 1 May)
• Re: [w3c/push-api] Pass removed subscriptions as a property of the `pushsubscriptionchange` event (#193) (Monday, 1 May)
• Re: [w3c/push-api] Pass removed subscriptions as a property of the `pushsubscriptionchange` event (#193) (Monday, 1 May)
• Re: [w3c/push-api] Propose enabling background sync from `pushsubscriptionchange` events (#240) (Monday, 1 May)
• Re: [w3c/push-api] Pass removed subscriptions as a property of the `pushsubscriptionchange` event (#193) (Monday, 1 May)
• Re: [w3c/push-api] Pass removed subscriptions as a property of the `pushsubscriptionchange` event (#193) (Monday, 1 May)

Bastien

• [w3c/manifest] Change platform android by play in exemple (#581) (Sunday, 21 May)

Ben Kelly

• Re: [w3c/ServiceWorker] "Unregister" operation may be interrupted by `ServiceWorker#postMessage` (#1146) (Wednesday, 31 May)
• Re: [w3c/ServiceWorker] Should update() called on an installing worker reject (as currently does?) (#1155) (Tuesday, 30 May)
• Re: [w3c/ServiceWorker] Should update() called on an installing worker reject (as currently does?) (#1155) (Monday, 29 May)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Monday, 22 May)
• Re: [whatwg/fetch] should Response.blob() type include parameters like charset? (#540) (Friday, 19 May)
• Re: [w3c/ServiceWorker] Service Worker makes AJAX Progress Listener not Working (#1141) (Tuesday, 16 May)
• Re: [w3c/ServiceWorker] Service Worker makes AJAX Progress Listener not Working (#1141) (Tuesday, 16 May)
• Re: [w3c/ServiceWorker] Service Worker makes AJAX Progress Listener not Working (#1141) (Tuesday, 16 May)
• Re: [w3c/ServiceWorker] Service Worker makes AJAX Progress Listener not Working (#1141) (Tuesday, 16 May)
• Re: [w3c/ServiceWorker] Service Worker makes AJAX Progress Listener not Working (#1141) (Tuesday, 16 May)
• Re: [w3c/ServiceWorker] Service Worker makes AJAX Progress Listener not Working (#1141) (Tuesday, 16 May)
• Re: [w3c/ServiceWorker] navigator.serviceWorker.ready remain resolved after unregister (#1139) (Monday, 15 May)
• Re: [w3c/ServiceWorker] navigator.serviceWorker.ready remain resolved after unregister (#1139) (Monday, 15 May)
• Re: [w3c/ServiceWorker] consider Client behavior for windows where initial about:blank is replaced with a loaded document (#1091) (Thursday, 11 May)
• [whatwg/fetch] should Response.blob() type include parameters like charset? (#540) (Tuesday, 9 May)
• Re: [w3c/ServiceWorker] consider Client behavior for windows where initial about:blank is replaced with a loaded document (#1091) (Monday, 8 May)
• Re: [w3c/ServiceWorker] consider Client behavior for windows where initial about:blank is replaced with a loaded document (#1091) (Monday, 8 May)
• Re: [whatwg/fetch] Request body streams that cannot be retried (#538) (Monday, 8 May)
• Re: [whatwg/fetch] Response filter escalation (#535) (Tuesday, 2 May)
• Re: [whatwg/fetch] Response filter escalation (#535) (Tuesday, 2 May)

Ben Smith

• Re: [w3ctag/design-reviews] SharedArrayBuffer + Atomics (#165) (Tuesday, 9 May)

Benjamin Gruenbaum

• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Wednesday, 10 May)
• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Wednesday, 10 May)

binary

• Re: [w3c/webcomponents] Create op (#639) (Wednesday, 3 May)
• [w3c/webcomponents] Create op (#639) (Wednesday, 3 May)

Binyamin Laukstein

• [w3c/ServiceWorker] Proposal: pass custom params in ServiceWorkerRegistration for future use (#1157) (Wednesday, 31 May)

bokand

• Re: [w3ctag/design-reviews] ViewportAPI naming Re-review (#172) (Tuesday, 16 May)

Boris Zbarsky

• Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Friday, 26 May)
• Re: [heycam/webidl] Do records (record<>s) purposefully throw on any object with an enumerable Symbol-named property? (#294) (Thursday, 18 May)
• Re: [heycam/webidl] Do records (record<>s) purposefully throw on any object with an enumerable Symbol-named property? (#294) (Thursday, 18 May)
• Re: [heycam/webidl] Do records (record<>s) purposefully throw on any object with an enumerable Symbol-named property? (#294) (Thursday, 18 May)
• Re: [heycam/webidl] Do records (record<>s) purposefully throw on any object with an enumerable Symbol-named property? (#294) (Thursday, 18 May)
• Re: [heycam/webidl] Do records (record<>s) purposefully throw on any object with an enumerable Symbol-named property? (#294) (Thursday, 18 May)
• Re: [heycam/webidl] Figure-out what supporting Array-subclassing implies (#345) (Thursday, 18 May)
• Re: [heycam/webidl] How to do aliases of legacy interfaces (HTMLDocument, WebKitCSSMatrix...) (#362) (Thursday, 18 May)
• Re: [heycam/webidl] How to do aliases of legacy interfaces (HTMLDocument, WebKitCSSMatrix...) (#362) (Tuesday, 16 May)
• Re: [heycam/webidl] How to do aliases of legacy interfaces (HTMLDocument, WebKitCSSMatrix...) (#362) (Tuesday, 16 May)
• Re: [heycam/webidl] The [SecureContext] text is unclear on exposure for interfaces (#119) (Monday, 15 May)
• Re: [heycam/webidl] Consider flipping the [Unscopable] design (#361) (Friday, 12 May)
• Re: [heycam/webidl] Consider flipping the [Unscopable] design (#361) (Friday, 12 May)
• Re: [heycam/webidl] Figure-out what supporting Array-subclassing implies (#345) (Thursday, 11 May)
• Re: [heycam/webidl] Figure-out what supporting Array-subclassing implies (#345) (Wednesday, 10 May)
• Re: [heycam/webidl] Remove custom [[HasInstance]] behavior from interface objects (#356) (Thursday, 4 May)
• Re: [heycam/webidl] Remove custom [[HasInstance]] behavior from interface objects (#356) (Thursday, 4 May)
• Re: [heycam/webidl] Only install @@toStringTag on the prototype (#357) (Wednesday, 3 May)
• Re: [heycam/webidl] Only install @@toStringTag on the prototype (#357) (Wednesday, 3 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Wednesday, 3 May)
• Re: [heycam/webidl] Only install @@toStringTag on the prototype (#357) (Tuesday, 2 May)
• Re: [heycam/webidl] Only install @@toStringTag on the prototype (#357) (Tuesday, 2 May)
• Re: [heycam/webidl] Add [AllowShared] to allow accepting SharedArrayBuffers (#353) (Monday, 1 May)
• Re: [heycam/webidl] Add [AllowShared] to allow accepting SharedArrayBuffers (#353) (Monday, 1 May)

Brad Nelson

• Re: [w3ctag/design-reviews] WebAssembly Response API / Web Embedding (#167) (Tuesday, 23 May)
• Re: [w3ctag/design-reviews] WebAssembly Response API / Web Embedding (#167) (Thursday, 18 May)

Brett Zamir

• Re: [w3c/IndexedDB] Set request result/done flag appropriately in open/delete (#202) (Tuesday, 16 May)
• Re: [w3c/IndexedDB] Set request result/done flag appropriately in open/delete (#202) (Tuesday, 16 May)
• Re: [w3c/IndexedDB] The done flag is never unset between upgradeneeded and success (#161) (Friday, 12 May)
• Re: [w3c/IndexedDB] Set request result/done flag appropriately in open/delete (#202) (Friday, 12 May)
• Re: [w3c/IndexedDB] Define db's associated upgrade tx to align with impls/tests (#201) (Friday, 12 May)
• Re: [w3c/IndexedDB] Define db's associated upgrade tx to align with impls/tests (#201) (Friday, 12 May)
• Re: [w3c/IndexedDB] Editorial: Remove use of 'substeps', simplify wording, add 'in parall… (#199) (Thursday, 11 May)
• Re: [w3c/IndexedDB] Editorial: Remove use of 'substeps', simplify wording, add 'in parall… (#199) (Monday, 8 May)
• Re: [w3c/IndexedDB] The done flag is never unset between upgradeneeded and success (#161) (Wednesday, 3 May)
• Re: [w3c/IndexedDB] JSON schema specification (#64) (Tuesday, 2 May)

Brian Kardell

• Re: [whatwg/dom] Consider boolean interface for properties (#461) (Monday, 22 May)
• Re: [whatwg/dom] Consider boolean interface for properties (#461) (Monday, 22 May)

BronislavKlucka

• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Monday, 22 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Sunday, 14 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Sunday, 14 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Sunday, 14 May)

chaals

• Re: [w3ctag/design-reviews] TAG Review of HTML 5.2 (previously 5.1) (#119) (Sunday, 28 May)
• Re: [w3ctag/design-reviews] TAG Review of HTML 5.2 (previously 5.1) (#119) (Friday, 26 May)
• Re: [w3ctag/design-reviews] TAG Review of HTML 5.2 (previously 5.1) (#119) (Friday, 26 May)
• Re: [w3ctag/design-reviews] TAG Review of HTML 5.2 (previously 5.1) (#119) (Friday, 26 May)
• Re: [w3ctag/design-reviews] TAG Review of HTML 5.2 (previously 5.1) (#119) (Friday, 26 May)
• Re: [w3ctag/design-reviews] TAG Review of HTML 5.2 (previously 5.1) (#119) (Friday, 26 May)
• Re: [w3ctag/design-reviews] TAG Review of HTML 5.2 (previously 5.1) (#119) (Friday, 26 May)
• Re: [w3c/charter-html] cleanup (743228d) (Tuesday, 23 May)
• Re: [w3c/charter-html] deliverable lists per Process 2017 (#143) (Tuesday, 23 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Tuesday, 23 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Tuesday, 23 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Tuesday, 23 May)
• Re: [w3c/charter-html] Change to the scope section not mentioned in the change sections (#142) (Tuesday, 23 May)
• Re: [w3c/charter-html] Change to the scope section not mentioned in the change sections (#142) (Tuesday, 23 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Tuesday, 23 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Tuesday, 23 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Monday, 22 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Monday, 22 May)
• Re: [w3c/ServiceWorker] Expose GeoLocation to workers (#745) (Monday, 22 May)
• Re: [w3c/charter-html] Relation with WICG (#141) (Tuesday, 16 May)
• Re: [w3c/charter-html] Incubation and new deliverables (#140) (Tuesday, 16 May)
• Re: [w3ctag/design-reviews] A spec style/structure checklist? (#136) (Tuesday, 9 May)
• Re: [w3c/manifest] Add (optional) "category" member (#569) (Wednesday, 3 May)

Chris Dumez

• Re: [whatwg/dom] DOMTokenList.remove() can add an attribute (#462) (Tuesday, 23 May)
• Re: [heycam/webidl] How to do aliases of legacy interfaces (HTMLDocument, WebKitCSSMatrix...) (#362) (Tuesday, 16 May)
• Re: [whatwg/dom] "The value attribute’s getter must return the va..." (#456) (Wednesday, 10 May)
• Re: [whatwg/dom] "The value attribute’s getter must return the va..." (#456) (Wednesday, 10 May)
• [whatwg/dom] Node Tree section should probably include Attr (#457) (Wednesday, 10 May)
• [whatwg/dom] "The value attribute’s getter must return the va..." (#456) (Wednesday, 10 May)
• Re: [heycam/webidl] Allow extended attributes to apply to types (#286) (Thursday, 4 May)
• Re: [heycam/webidl] Remove custom [[HasInstance]] behavior from interface objects (#356) (Tuesday, 2 May)

Chris Palmer

• Re: [w3c/ServiceWorker] Match Service Worker Registration should assert same-origin? (#1118) (Wednesday, 10 May)
• Re: [w3c/ServiceWorker] Match Service Worker Registration should assert same-origin? (#1118) (Tuesday, 2 May)

Chris Pearce

• Re: [whatwg/fullscreen] Fire events at elements by default, falling back to documents (#90) (Wednesday, 24 May)

chris van wiemeersch

• Re: [w3c/manifest] Provide VR display mode (#583) (Wednesday, 24 May)
• Re: [w3c/manifest] Provide VR display mode (#583) (Wednesday, 24 May)
• Re: [w3c/manifest] Provide VR display mode (#583) (Tuesday, 23 May)

Conrad Irwin

• Re: [w3c/uievents] Explain that mousedown focuses form controls (#81) (Friday, 5 May)

cynthia

• Re: [w3ctag/design-reviews] WICG Shape Detection API (#176) (Thursday, 25 May)
• Re: [w3ctag/design-reviews] WebAssembly Response API / Web Embedding (#167) (Tuesday, 23 May)
• Re: [w3ctag/design-reviews] Review Screen Orientation spec prior to CR-entry (#157) (Sunday, 21 May)
• Re: [w3ctag/design-reviews] README: fix links with spaces to use encoded spaces (#175) (Thursday, 4 May)
• Re: [w3ctag/design-reviews] README: fix links with spaces to use encoded spaces (#175) (Thursday, 4 May)

Cyril Auburtin

• Re: [whatwg/url] new URL('file://').origin is 'null' (#310) (Sunday, 14 May)
• [whatwg/url] new URL('file://').origin is 'null' (#310) (Saturday, 13 May)
• Re: [whatwg/url] "new URLSearchParams({key: "730d67"})" (#306) (Monday, 1 May)
• Re: [whatwg/url] "new URLSearchParams({key: "730d67"})" (#306) (Monday, 1 May)
• [whatwg/url] "new URLSearchParams({key: "730d67"})" (#306) (Monday, 1 May)

Daniel Appelquist

• Re: [w3ctag/design-reviews] Review origin policy. (#127) (Tuesday, 30 May)
• Re: [w3ctag/design-reviews] ViewportAPI naming Re-review (#172) (Tuesday, 16 May)
• Re: [w3ctag/design-reviews] ViewportAPI naming Re-review (#172) (Tuesday, 16 May)

Daniel Glazman

• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Wednesday, 24 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Tuesday, 23 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Tuesday, 23 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Monday, 22 May)

Dave Tapuska

• Re: [w3c/uievents] Click event is not fired when the node is removed and then added back (#141) (Wednesday, 3 May)

David Singer

• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Tuesday, 23 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Tuesday, 23 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Monday, 22 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Thursday, 18 May)
• Re: [w3c/charter-html] Relation with WICG (#141) (Tuesday, 16 May)
• Re: [w3c/charter-html] Relation with WICG (#141) (Tuesday, 16 May)

Devdatta Akhawe

• Re: [whatwg/fetch] Remove null origin issue (#542) (Thursday, 11 May)
• Re: [whatwg/fetch] Remove null origin issue (#542) (Thursday, 11 May)
• [whatwg/fetch] Remove null origin issue (#542) (Thursday, 11 May)

Dima Voytenko

• Re: [whatwg/fetch] Add flag to indicate delay-tolerant Request, to enable request coalescing. (#184) (Tuesday, 16 May)

Diwank Singh Tomer

• [whatwg/streams] RFC: Review pipes.js (a Highland.js inspired utility library for web streams) (#748) (Wednesday, 31 May)

Domenic Denicola

• Re: [whatwg/url] Address several IDNA issues (#309) (Wednesday, 31 May)
• Re: [heycam/webidl] [[Set]] algorithm for legacy platform objects does not seem to be compatible with the Storage interface (#366) (Wednesday, 31 May)
• Re: [heycam/webidl] [[Set]] algorithm for legacy platform objects does not seem to be compatible with the Storage interface (#366) (Wednesday, 31 May)
• Re: [whatwg/url] Address several IDNA issues (#309) (Wednesday, 31 May)
• Re: [whatwg/url] Should the legacy alias webkitURL be defined in the Compat Standard instead? (#314) (Wednesday, 31 May)
• Re: [w3c/webcomponents] Agenda for W3C TPAC 2017 (Web Components) (#641) (Wednesday, 31 May)
• Re: [w3c/webcomponents] Agenda for W3C TPAC 2017 (Web Components) (#641) (Wednesday, 31 May)
• Re: [w3c/ServiceWorker] Extend attribute ref with link to external spec (#1144) (Tuesday, 30 May)
• Re: [w3c/ServiceWorker] adding IANA considerations section (#1154) (Monday, 29 May)
• Re: [whatwg/url] Address several IDNA issues (#309) (Friday, 26 May)
• Re: [whatwg/url] Refactor IPv6 in terms of lists (#286) (Friday, 26 May)
• Re: [w3ctag/design-reviews] TAG Review of HTML 5.2 (previously 5.1) (#119) (Friday, 26 May)
• Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Thursday, 25 May)
• Re: [whatwg/url] Record whether the URL parser removed newlines. (#284) (Thursday, 25 May)
• Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Thursday, 25 May)
• Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Thursday, 25 May)
• Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Thursday, 25 May)
• Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Thursday, 25 May)
• Re: [whatwg/url] Record whether the URL parser removed newlines. (#284) (Tuesday, 23 May)
• Re: [whatwg/url] Record whether the URL parser removed newlines. (#284) (Tuesday, 23 May)
• Re: [whatwg/streams] Reference to CopyDataBlockBytes (#746) (Monday, 22 May)
• Re: [whatwg/streams] pipeTo should return a cancelable promise (#446) (Monday, 22 May)
• Re: [whatwg/dom] Consider boolean interface for properties (#461) (Monday, 22 May)
• Re: [heycam/webidl] Do records (record<>s) purposefully throw on any object with an enumerable Symbol-named property? (#294) (Monday, 22 May)
• Re: [whatwg/dom] Consider boolean interface for properties (#461) (Monday, 22 May)
• Re: [whatwg/url] Specify window.webkitURL as an alias to URL (#312) (Monday, 22 May)
• Re: [whatwg/dom] Can one get the "original" name of an element? (#460) (Monday, 22 May)
• Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Sunday, 21 May)
• Re: [w3c/ServiceWorker] event.waitUntil/respondWith vs return promise (#1148) (Saturday, 20 May)
• Re: [whatwg/xhr] Should send() throw if the XHR object's window's document is not fully active? (#65) (Saturday, 20 May)
• Re: [w3ctag/design-reviews] Serialization of natural language in data formats such as JSON [I18N] (#178) (Thursday, 18 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Thursday, 18 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Thursday, 18 May)
• Re: [whatwg/fetch] Add domintro explanations for web developers (#543) (Thursday, 18 May)
• Re: [heycam/webidl] Do records (record<>s) purposefully throw on any object with an enumerable Symbol-named property? (#294) (Thursday, 18 May)
• Re: [heycam/webidl] Do records (record<>s) purposefully throw on any object with an enumerable Symbol-named property? (#294) (Thursday, 18 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Wednesday, 17 May)
• Re: [whatwg/dom] Abort controller (#437) (Wednesday, 17 May)
• Re: [whatwg/dom] Abort controller (#437) (Wednesday, 17 May)
• Re: [whatwg/dom] Abort controller design (#438) (Wednesday, 17 May)
• Re: [whatwg/streams] Allow aborting an ongoing pipe operation using AbortSignals (#744) (Wednesday, 17 May)
• Re: [whatwg/dom] Abort controller (#437) (Wednesday, 17 May)
• Re: [whatwg/dom] Abort controller (#437) (Wednesday, 17 May)
• Re: [whatwg/dom] Abort controller (#437) (Wednesday, 17 May)
• Re: [whatwg/dom] Abort controller (#437) (Wednesday, 17 May)
• Re: [whatwg/dom] Abort controller (#437) (Wednesday, 17 May)
• Re: [w3c/ServiceWorker] Extend attribute ref with link to external spec (#1144) (Wednesday, 17 May)
• Re: [whatwg/dom] Abort controller (#437) (Tuesday, 16 May)
• Re: [whatwg/dom] Abort controller design (#438) (Tuesday, 16 May)
• Re: [heycam/webidl] Designing mixins (#363) (Tuesday, 16 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Tuesday, 16 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Monday, 15 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Monday, 15 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Monday, 15 May)
• [heycam/webidl] Designing mixins (#363) (Monday, 15 May)
• Re: [heycam/webidl] The [SecureContext] text is unclear on exposure for interfaces (#119) (Monday, 15 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Monday, 15 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Monday, 15 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Monday, 15 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Monday, 15 May)
• Re: [whatwg/dom] Abort controller design (#438) (Monday, 15 May)
• Re: [whatwg/dom] Abort controller (#437) (Monday, 15 May)
• [whatwg/streams] Allow aborting an ongoing pipe operation using AbortSignals (#744) (Monday, 15 May)
• Re: [whatwg/dom] Abort controller (#437) (Monday, 15 May)
• Re: [whatwg/dom] Abort controller (#437) (Monday, 15 May)
• Re: [whatwg/dom] Make EventTarget subclassable (#441) (Monday, 15 May)
• Re: [w3c/ServiceWorker] Adding a developer-provided name (#1121) (Monday, 15 May)
• Re: [w3c/ServiceWorker] Adding a developer-provided name (#1121) (Monday, 15 May)
• Re: [heycam/webidl] Consider flipping the [Unscopable] design (#361) (Friday, 12 May)
• Re: [heycam/webidl] Consider flipping the [Unscopable] design (#361) (Friday, 12 May)
• Re: [heycam/webidl] Consider flipping the [Unscopable] design (#361) (Friday, 12 May)
• [whatwg/fetch] Add domintro explanations for web developers (#543) (Friday, 12 May)
• Re: [whatwg/url] Clearly indicate a known issue with ToASCII (#309) (Friday, 12 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Thursday, 11 May)
• Re: [heycam/webidl] Figure-out what supporting Array-subclassing implies (#345) (Thursday, 11 May)
• Re: [heycam/webidl] Figure-out what supporting Array-subclassing implies (#345) (Thursday, 11 May)
• Re: [heycam/webidl] Figure-out what supporting Array-subclassing implies (#345) (Thursday, 11 May)
• Re: [heycam/webidl] provide clearer advice about USVString vs. DOMString (#84) (Thursday, 11 May)
• Re: [heycam/webidl] Do records (record<>s) purposefully throw on any object with an enumerable Symbol-named property? (#294) (Thursday, 11 May)
• Re: [heycam/webidl] Do records (record<>s) purposefully throw on any object with an enumerable Symbol-named property? (#294) (Thursday, 11 May)
• Re: [heycam/webidl] provide clearer advice about USVString vs. DOMString (#84) (Thursday, 11 May)
• Re: [whatwg/url] IDNA (#53) (Thursday, 11 May)
• Re: [whatwg/url] IDNA (#53) (Thursday, 11 May)
• Re: [whatwg/dom] Make element and attribute names behave like the HTML parser (#449) (Thursday, 11 May)
• Re: [heycam/webidl] Fix confusing wording in "extended attributes associated with" (#341) (Wednesday, 10 May)
• Re: [heycam/webidl] Clarify and add examples for "extended attributes associated with" (#355) (Wednesday, 10 May)
• Re: [heycam/webidl] Clarify and add examples for "extended attributes associated with" (#355) (Wednesday, 10 May)
• Re: [heycam/webidl] Throwing when converting detached ArrayBuffers is not what browsers do (#352) (Wednesday, 10 May)
• Re: [heycam/webidl] Throwing when converting detached ArrayBuffers is not what browsers do (#352) (Wednesday, 10 May)
• [heycam/webidl] Fix [TreatNullAs] usage in example (#360) (Wednesday, 10 May)
• Re: [heycam/webidl] [EnforceRange] should normatively specify RangeError (#359) (Wednesday, 10 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Tuesday, 9 May)
• Re: [whatwg/fetch] Request body streams that cannot be retried (#538) (Monday, 8 May)
• Re: [heycam/webidl] Allow extended attributes to apply to types (#286) (Thursday, 4 May)
• Re: [whatwg/dom] To investigate: do error events bubble to window? (#455) (Thursday, 4 May)
• Re: [whatwg/dom] To investigate: do error events bubble to window? (#455) (Thursday, 4 May)
• [whatwg/dom] To investigate: do error events bubble to window? (#455) (Thursday, 4 May)
• Re: [heycam/webidl] Remove custom [[HasInstance]] behavior from interface objects (#356) (Thursday, 4 May)
• Re: [heycam/webidl] Should probably spec a hasInstance for DOM interface objects (#129) (Thursday, 4 May)
• Re: [heycam/webidl] Remove custom [[HasInstance]] behavior from interface objects (#356) (Thursday, 4 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Thursday, 4 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Thursday, 4 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Thursday, 4 May)
• Re: [heycam/webidl] Remove custom [[HasInstance]] behavior from interface objects (#356) (Wednesday, 3 May)
• Re: [whatwg/url] javascript: URL parsing (#307) (Wednesday, 3 May)
• Re: [heycam/webidl] Add [AllowShared] to allow accepting SharedArrayBuffers (#353) (Wednesday, 3 May)
• Re: [heycam/webidl] Only install @@toStringTag on the prototype (#357) (Wednesday, 3 May)
• Re: [whatwg/url] javascript: URL parsing (#307) (Wednesday, 3 May)
• Re: [w3c/uievents] Click event is not fired when the node is removed and then added back (#141) (Wednesday, 3 May)
• [whatwg/url] javascript: URL parsing (#307) (Wednesday, 3 May)
• Re: [heycam/webidl] Add [AllowShared] to allow accepting SharedArrayBuffers (#353) (Tuesday, 2 May)
• Re: [heycam/webidl] Add [AllowShared] to allow accepting SharedArrayBuffers (#353) (Tuesday, 2 May)
• Re: [w3c/manifest] Use UTF-8 decode when obtaining a manifest (#570) (Tuesday, 2 May)
• Re: [heycam/webidl] Remove custom [[HasInstance]] behavior from interface objects (#356) (Tuesday, 2 May)
• Re: [heycam/webidl] Remove custom [[HasInstance]] behavior from interface objects (#356) (Tuesday, 2 May)
• Re: [heycam/webidl] Remove custom [[HasInstance]] behavior from interface objects (#356) (Tuesday, 2 May)
• Re: [heycam/webidl] Remove custom [[HasInstance]] behavior from interface objects (#356) (Tuesday, 2 May)
• Re: [heycam/webidl] Remove custom [[HasInstance]] behavior from interface objects (#356) (Tuesday, 2 May)
• Re: [whatwg/url] Fix windows drive letter handling in the file state (#305) (Tuesday, 2 May)
• Re: [heycam/webidl] Only install @@toStringTag on the prototype (#357) (Tuesday, 2 May)
• Re: [heycam/webidl] Only install @@toStringTag on the prototype (#357) (Tuesday, 2 May)
• [heycam/webidl] Only install @@toStringTag on the prototype (#357) (Monday, 1 May)
• [heycam/webidl] Remove custom [[HasInstance]] behavior from interface objects (#356) (Monday, 1 May)
• Re: [w3c/ServiceWorker] Handle deserialization failures in postMessage() (#1130) (Monday, 1 May)
• Re: [heycam/webidl] Add [AllowShared] to allow accepting SharedArrayBuffers (#353) (Monday, 1 May)
• Re: [heycam/webidl] Add [AllowShared] to allow accepting SharedArrayBuffers (#353) (Monday, 1 May)

Dominic Farolino

• Re: [whatwg/fetch] Add domintro explanations for web developers (#543) (Thursday, 18 May)
• Re: [whatwg/fetch] Small cors typo (#545) (Thursday, 18 May)
• [whatwg/fetch] Small cors typo (#545) (Thursday, 18 May)

Dominick Ng

• Re: [w3c/manifest] Add shortcuts (#575) (Tuesday, 9 May)

Duncan Munro

• Re: [w3c/webcomponents] [Custom]: Need callback for form submit data (bugzilla: 24603) (#187) (Tuesday, 2 May)

Dylan Barrell

• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Friday, 19 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Friday, 19 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Thursday, 18 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Friday, 12 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Friday, 12 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Thursday, 11 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Thursday, 11 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Wednesday, 10 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Wednesday, 10 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Tuesday, 9 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Monday, 8 May)

ekr

• Re: [whatwg/fetch] Request body streams that cannot be retried (#538) (Monday, 8 May)
• Re: [whatwg/fetch] Request body streams that cannot be retried (#538) (Monday, 8 May)
• Re: [whatwg/fetch] Request body streams that cannot be retried (#538) (Monday, 8 May)

Emily Stark

• Re: [w3c/ServiceWorker] Match Service Worker Registration should assert same-origin? (#1118) (Friday, 12 May)
• Re: [w3c/ServiceWorker] Match Service Worker Registration should assert same-origin? (#1118) (Thursday, 11 May)

Emmanuel T Odeke

• Re: [w3ctag/design-reviews] README: fix links with spaces to use encoded spaces (#175) (Thursday, 4 May)
• [w3ctag/design-reviews] README: fix links with spaces to use encoded spaces (#175) (Wednesday, 3 May)

Erik Wilde

• Re: [w3c/ServiceWorker] adding IANA considerations section (#1154) (Monday, 29 May)
• Re: [w3c/ServiceWorker] adding IANA considerations section (#1154) (Monday, 29 May)
• Re: [w3c/ServiceWorker] adding IANA considerations section (#1154) (Monday, 29 May)
• Re: [w3c/ServiceWorker] Register HTTP header fields with IANA (#1134) (Monday, 29 May)
• Re: [w3c/ServiceWorker] adding IANA considerations section (#1154) (Monday, 29 May)
• Re: [w3c/ServiceWorker] adding IANA considerations section (#1154) (Monday, 29 May)
• Re: [w3c/ServiceWorker] adding IANA considerations section (#1154) (Monday, 29 May)
• Re: [w3c/ServiceWorker] adding IANA considerations section (#1154) (Monday, 29 May)
• [w3c/ServiceWorker] adding IANA considerations section (#1154) (Monday, 29 May)
• Re: [w3c/ServiceWorker] Register HTTP header fields with IANA (#1134) (Thursday, 18 May)

falsandtru

• [w3c/IndexedDB] Expiry of databases (#205) (Monday, 29 May)

Felix Becker

• Re: [whatwg/url] Provide means to "strip query" (#247) (Thursday, 11 May)
• Re: [whatwg/url] Provide means to "strip query" (#247) (Thursday, 11 May)

Fernando Serboncini

• Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Thursday, 25 May)
• Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Thursday, 25 May)
• Re: [heycam/webidl] How to do aliases of legacy interfaces (HTMLDocument, WebKitCSSMatrix...) (#362) (Tuesday, 16 May)
• Re: [heycam/webidl] How to do aliases of legacy interfaces (HTMLDocument, WebKitCSSMatrix...) (#362) (Tuesday, 16 May)

Florian Rivoal

• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Wednesday, 24 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Wednesday, 24 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Tuesday, 23 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Tuesday, 23 May)
• [w3c/charter-html] Change to the scope section not mentioned in the change sections (#142) (Tuesday, 23 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Monday, 22 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Wednesday, 17 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Wednesday, 17 May)
• Re: [w3c/charter-html] Relation with WICG (#141) (Tuesday, 16 May)
• Re: [w3c/charter-html] Incubation and new deliverables (#140) (Tuesday, 16 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Tuesday, 16 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Tuesday, 16 May)
• [w3c/charter-html] Relation with WICG (#141) (Tuesday, 16 May)
• [w3c/charter-html] Incubation, WICG, etc (#140) (Tuesday, 16 May)
• [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Tuesday, 16 May)

Gary Kacmarcik

• Re: [w3c/uievents] Needs an option to make the <input> element readonly in "Keyboard Event Viewer" (#137) (Thursday, 25 May)
• Re: [w3c/uievents] Needs an option to make the <input> element readonly in "Keyboard Event Viewer" (#137) (Thursday, 25 May)
• Re: [w3c/uievents] 3.1. Event dispatch and DOM event flow - small typo (#143) (Thursday, 25 May)
• Re: [w3c/uievents] 3.1. Event dispatch and DOM event flow - small typo (#143) (Thursday, 25 May)
• [w3c/uievents] Need algorithm for how events are fired for key presses (#142) (Tuesday, 16 May)
• Re: [w3c/clipboard-apis] Add missing comma in navigator.clipboard IDL (#43) (Monday, 15 May)
• Re: [w3c/clipboard-apis] Add missing comma in navigator.clipboard IDL (#43) (Monday, 15 May)

Gordon P. Hemsley

• [whatwg/url] Clarify language around scheme state with state override in basic URL parser (#315) (Wednesday, 31 May)

Hayato Ito

• Re: [w3c/webcomponents] Agenda for W3C TPAC 2017 (Web Components) (#641) (Wednesday, 31 May)
• Re: [w3c/webcomponents] Agenda for W3C TPAC 2017 (Web Components) (#641) (Wednesday, 31 May)
• [w3c/webcomponents] Agenda for W3C TPAC 2017 (Web Components) (#641) (Wednesday, 31 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Thursday, 25 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Wednesday, 24 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Wednesday, 24 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Wednesday, 24 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Monday, 22 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Monday, 22 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Monday, 22 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Friday, 19 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Friday, 19 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Thursday, 18 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Thursday, 18 May)
• Re: [whatwg/dom] Don't set a suppress signaling flag when a slot is inserted (#459) (Thursday, 18 May)
• Re: [whatwg/dom] Don't set a suppress signaling flag when a slot is inserted (#459) (Wednesday, 17 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Monday, 15 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Monday, 15 May)
• Re: [whatwg/dom] Don't set a suppress signaling flag when a slot is inserted (#459) (Monday, 15 May)
• [whatwg/dom] Don't set a suppress signaling flag when a slot is inserted (#459) (Monday, 15 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Monday, 15 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Wednesday, 10 May)
• Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354) (Monday, 8 May)

HE Shi-Jun

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

hemanth.hm

• Re: [w3c/manifest] FR: Context menus on app icons. (#582) (Wednesday, 24 May)
• Re: [w3c/manifest] FR: Context menus on app icons. (#582) (Wednesday, 24 May)
• [w3c/manifest] FR: Context menus on app icons. (#582) (Tuesday, 23 May)

Henri Sivonen

• Re: [whatwg/encoding] Amount of bytes to sniff for encoding detection (#102) (Tuesday, 23 May)
• Re: [whatwg/encoding] For your information: Illegal UTF-8 proposal (#112) (Tuesday, 16 May)
• Re: [whatwg/encoding] For your information: Illegal UTF-8 proposal (#112) (Monday, 15 May)
• Re: [whatwg/encoding] gb18030 decoder: unwind from fourth byte when it's not a digit (#111) (Thursday, 11 May)
• Re: [whatwg/encoding] gb18030 decoder: unwind from fourth byte when it's not a digit (#111) (Thursday, 11 May)
• Re: [whatwg/encoding] Should not prepend gb18030 second and third when range decode fails upon fourth (#110) (Thursday, 11 May)
• Re: [whatwg/encoding] Should not prepend gb18030 second and third when range decode fails upon fourth (#110) (Thursday, 11 May)
• Re: [whatwg/encoding] Should not prepend gb18030 second and third when range decode fails upon fourth (#110) (Thursday, 11 May)
• [whatwg/encoding] Should not prepend gb18030 second and third when range decode fails upon fourth (#110) (Thursday, 11 May)
• Re: [whatwg/encoding] ISO-2022-JP encoder: convert halfwidth Katakana to fullwidth (#106) (Thursday, 11 May)
• Re: [whatwg/encoding] Amount of bytes to sniff for encoding detection (#102) (Tuesday, 9 May)
• Re: [whatwg/encoding] ISO-2022-JP encoder: convert halfwidth Katakana to fullwidth (#106) (Monday, 8 May)
• Re: [whatwg/encoding] ISO-2022-JP encoder: convert halfwidth Katakana to fullwidth (#106) (Saturday, 6 May)
• Re: [whatwg/encoding] ISO-2022-JP encoder: convert halfwidth Katakana to fullwidth (#106) (Friday, 5 May)
• Re: [whatwg/encoding] ISO-2022-JP encoder: convert halfwidth Katakana to fullwidth (#106) (Friday, 5 May)
• Re: [whatwg/encoding] EUC-JP: only unwind ASCII bytes (#103) (Friday, 5 May)
• Re: [whatwg/encoding] Amount of bytes to sniff for encoding detection (#102) (Friday, 5 May)
• [whatwg/encoding] Half-width Katakana should be representable in ISO-2022-JP (#105) (Friday, 5 May)

I-Maps

• Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Monday, 29 May)
• Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Monday, 29 May)
• Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Monday, 29 May)

Ilya Grigorik

• Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) (Friday, 12 May)

Jake Archibald

• Re: [w3c/ServiceWorker] event.waitUntil/respondWith vs return promise (#1148) (Sunday, 21 May)
• Re: [w3c/ServiceWorker] event.waitUntil/respondWith vs return promise (#1148) (Sunday, 21 May)
• Re: [w3c/ServiceWorker] event.waitUntil/respondWith vs return promise (#1148) (Saturday, 20 May)
• [w3c/ServiceWorker] Make object equality of service workers clearer (#1140) (Monday, 15 May)
• Re: [w3c/FileAPI] Don't update FileReader's result until "LOAD" (#79) (Thursday, 4 May)
• Re: [w3c/FileAPI] Don't update FileReader's result until "LOAD" (#79) (Thursday, 4 May)
• Re: [w3c/FileAPI] Don't update FileReader's result until "LOAD" (#79) (Thursday, 4 May)

Jan Miksovsky

• Re: [w3c/webcomponents] Agenda for W3C TPAC 2017 (Web Components) (#641) (Wednesday, 31 May)

jan-ivar

• Re: [w3c/permissions] Define restrictions on "device-info" permission (from TPAC). (#131) (Wednesday, 31 May)
• Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Friday, 26 May)

Jason Stewart

• Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Monday, 29 May)
• Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Sunday, 21 May)

jeffjaffe

• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Wednesday, 24 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Tuesday, 23 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Thursday, 18 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Wednesday, 17 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Wednesday, 17 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Tuesday, 16 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Tuesday, 16 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Tuesday, 16 May)

Jeffrey Yasskin

• Re: [heycam/webidl] The [SecureContext] text is unclear on exposure for interfaces (#119) (Monday, 15 May)
• Re: [whatwg/fetch] Odd format for fetch callbacks (#536) (Wednesday, 3 May)
• Re: [whatwg/fetch] Odd format for fetch callbacks (#536) (Wednesday, 3 May)
• [whatwg/fetch] Odd format for fetch callbacks (#536) (Tuesday, 2 May)
• Re: [w3c/permissions] Spec examples do not include `request()` (#144) (Monday, 1 May)

JinsukKim

• Re: [whatwg/encoding] Amount of bytes to sniff for encoding detection (#102) (Tuesday, 23 May)
• Re: [whatwg/encoding] Amount of bytes to sniff for encoding detection (#102) (Monday, 22 May)
• Re: [whatwg/encoding] Amount of bytes to sniff for encoding detection (#102) (Friday, 19 May)
• Re: [whatwg/encoding] Amount of bytes to sniff for encoding detection (#102) (Wednesday, 10 May)

jmuransky

• [w3c/ServiceWorker] Priority of requests (feature request) (#1137) (Wednesday, 10 May)

Johann

• Re: [w3c/ServiceWorker] navigator.serviceWorker.ready remain resolved after unregister (#1139) (Monday, 15 May)
• Re: [w3c/ServiceWorker] navigator.serviceWorker.ready remain resolved after unregister (#1139) (Monday, 15 May)
• Re: [w3c/ServiceWorker] navigator.serviceWorker.ready remain resolved after unregister (#1139) (Monday, 15 May)
• [w3c/ServiceWorker] navigator.serviceWorker.ready remain resolved after unregister (#1139) (Saturday, 13 May)

Jonathan Kingston

• [whatwg/dom] Consider boolean interface for properties (#461) (Monday, 22 May)

Jos van den Oever

• Re: [whatwg/dom] Details missing on (lack of) namespace support in Element.match (#458) (Thursday, 11 May)
• [whatwg/dom] Details missing on (lack of) namespace support in Element.match (#458) (Wednesday, 10 May)

Joseph Orbegoso Pea

• Re: [w3c/webcomponents] Should shadow host have `display: block` by default? (#426) (Thursday, 18 May)
• Re: [w3c/webcomponents] Should shadow host have `display: block` by default? (#426) (Thursday, 18 May)
• Re: [w3c/webcomponents] Should shadow host have `display: block` by default? (#426) (Thursday, 18 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 16 May)

Josh Habdas

• Re: [whatwg/fetch] should Response.blob() type include parameters like charset? (#540) (Friday, 19 May)
• Re: [whatwg/fetch] should Response.blob() type include parameters like charset? (#540) (Friday, 19 May)
• Re: [whatwg/fetch] should Response.blob() type include parameters like charset? (#540) (Friday, 19 May)
• Re: [whatwg/fetch] should Response.blob() type include parameters like charset? (#540) (Friday, 19 May)
• Re: [whatwg/fetch] should Response.blob() type include parameters like charset? (#540) (Thursday, 18 May)
• Re: [whatwg/fetch] should Response.blob() type include parameters like charset? (#540) (Wednesday, 10 May)
• Re: [whatwg/fetch] should Response.blob() type include parameters like charset? (#540) (Wednesday, 10 May)
• Re: [whatwg/fetch] should Response.blob() type include parameters like charset? (#540) (Wednesday, 10 May)
• Re: [whatwg/fetch] MK (#534) (Tuesday, 2 May)

Joshua Bell

• Re: [w3c/IndexedDB] Add caniuse panels (#159) (Monday, 22 May)
• Re: [w3c/IndexedDB] Set request result/done flag appropriately in open/delete (#202) (Wednesday, 17 May)
• Re: [w3c/IndexedDB] The done flag is never unset between upgradeneeded and success (#161) (Wednesday, 17 May)
• [w3c/IndexedDB] Custom index keys (#204) (Wednesday, 17 May)
• Re: [w3c/IndexedDB] Set request result/done flag appropriately in open/delete (#202) (Tuesday, 16 May)
• Re: [w3c/IndexedDB] Set request result/done flag appropriately in open/delete (#202) (Monday, 15 May)
• Re: [w3c/IndexedDB] Set request result/done flag appropriately in open/delete (#202) (Monday, 15 May)
• Re: [w3c/IndexedDB] Set request result/done flag appropriately in open/delete (#202) (Monday, 15 May)
• Re: [w3c/IndexedDB] create/deleteObjectStore: InvalidStateError logic does not match impls/tests (#192) (Friday, 12 May)
• Re: [w3c/IndexedDB] Define db's associated upgrade tx to align with impls/tests (#201) (Friday, 12 May)
• Re: [w3c/IndexedDB] Define db's associated upgrade tx to align with impls/tests (#201) (Friday, 12 May)
• Re: [w3c/IndexedDB] Examples have no language or direction (#180) (Friday, 12 May)
• Re: [w3c/IndexedDB] Examples have no language or direction (#180) (Friday, 12 May)
• Re: [w3c/IndexedDB] Where unique key goes (#181) (Friday, 12 May)
• Re: [w3c/IndexedDB] Where unique key goes (#181) (Friday, 12 May)
• Re: [w3c/IndexedDB] Nit about `deleteDatabase` error example (#196) (Friday, 12 May)
• Re: [w3c/IndexedDB] Nit about `deleteDatabase` error example (#196) (Friday, 12 May)
• Re: [w3c/IndexedDB] Update for structured cloning changes in HTML (#170) (Friday, 12 May)
• Re: [w3c/IndexedDB] Update for structured cloning changes in HTML (#170) (Friday, 12 May)
• [w3c/IndexedDB] Define storage operation of non-trivial StructuredSerializeForStorage records (e.g. Blob/File) (#203) (Friday, 12 May)
• Re: [w3c/IndexedDB] Set request result/done flag appropriately in open/delete (#202) (Friday, 12 May)
• Re: [w3c/IndexedDB] Editorial: Remove use of 'substeps', simplify wording, add 'in parall… (#199) (Thursday, 11 May)
• Re: [w3c/IndexedDB] Define db's associated upgrade tx to align with impls/tests (#201) (Thursday, 11 May)
• Re: [w3c/IndexedDB] Horizontal review… (#112) (Thursday, 11 May)
• Re: [w3c/IndexedDB] The done flag is never unset between upgradeneeded and success (#161) (Thursday, 11 May)
• [w3c/IndexedDB] Set request result/done flag appropriately in open/delete (#202) (Thursday, 11 May)
• Re: [w3c/IndexedDB] Define db's associated upgrade tx to align with impls/tests (#201) (Thursday, 11 May)
• [w3c/IndexedDB] Define db's associated upgrade tx to align with impls/tests. Resolves #192 (#201) (Thursday, 11 May)
• Re: [w3c/IndexedDB] Editorial: Remove use of 'substeps', simplify wording, add 'in parall… (#199) (Thursday, 11 May)
• Re: [w3c/IndexedDB] Ask for web-platform-tests in CONTRIBUTING.md (#200) (Thursday, 11 May)
• Re: [w3c/IndexedDB] Editorial: Remove use of 'substeps', simplify wording, add 'in parall… (#199) (Tuesday, 9 May)
• Re: [w3c/IndexedDB] Editorial: Remove use of 'substeps', simplify wording, add 'in parall… (#199) (Tuesday, 9 May)
• Re: [w3c/IndexedDB] Editorial: Remove use of 'substeps', simplify wording, add 'in parall… (#199) (Monday, 8 May)
• Re: [whatwg/encoding] ISO-2022-JP encoder: convert halfwidth Katakana to fullwidth (#106) (Friday, 5 May)
• [w3c/IndexedDB] Editorial: Remove use of 'substeps', simplify wording, add 'in parall… (#199) (Friday, 5 May)
• Re: [w3c/IndexedDB] SharedArrayBuffer integration (#152) (Tuesday, 2 May)
• Re: [w3c/IndexedDB] Use StructuredSerializeForStorage (#197) (Tuesday, 2 May)
• Re: [w3c/IndexedDB] Use HTML's StructuredSerializeForStorage (#198) (Tuesday, 2 May)
• [w3c/IndexedDB] Use HTML's StructuredSerializeForStorage (#198) (Monday, 1 May)

jugglinmike

• Re: [w3c/ServiceWorker] Extend attribute ref with link to external spec (#1144) (Tuesday, 30 May)
• [w3c/ServiceWorker] Dynamic Event Handler Registration (#1156) (Tuesday, 30 May)
• Re: [w3c/ServiceWorker] Extend attribute ref with link to external spec (#1144) (Tuesday, 30 May)
• [w3c/ServiceWorker] Editorial: correct method control flow (#1152) (Friday, 26 May)
• [w3c/ServiceWorker] Editorial: Correct value references (#1150) (Thursday, 25 May)
• Re: [w3c/ServiceWorker] Extend attribute ref with link to external spec (#1144) (Thursday, 25 May)
• Re: [w3c/ServiceWorker] Extend attribute ref with link to external spec (#1144) (Thursday, 25 May)
• [w3c/ServiceWorker] Editorial: correct typos in <link> element example (#1149) (Monday, 22 May)
• Re: [w3c/ServiceWorker] Editorial: Correct grammar of informative note (#1145) (Monday, 22 May)
• Re: [w3c/ServiceWorker] Editorial: Correct grammar of informative note (#1145) (Monday, 22 May)
• [w3c/ServiceWorker] "Unregister" operation may be interrupted by `ServiceWorker#postMessage` (#1146) (Thursday, 18 May)
• [w3c/ServiceWorker] Editorial: Correct grammar of informative note (#1145) (Thursday, 18 May)
• Re: [w3c/ServiceWorker] Extend attribute ref with link to external spec (#1144) (Wednesday, 17 May)
• Re: [w3c/ServiceWorker] Extend attribute ref with link to external spec (#1144) (Wednesday, 17 May)
• [w3c/ServiceWorker] Extend attribute ref with link to external spec (#1144) (Wednesday, 17 May)
• Re: [w3c/ServiceWorker] Remove unused flag (#1143) (Wednesday, 17 May)
• Re: [w3c/ServiceWorker] Remove unused flag (#1143) (Wednesday, 17 May)
• [w3c/ServiceWorker] Remove unused flag (#1143) (Wednesday, 17 May)
• Re: [whatwg/fetch] Editorial: rename "basic fetch" to "scheme fetch" (#537) (Saturday, 6 May)
• [w3c/ServiceWorker] Editorial: Simplify `ready` (#1136) (Friday, 5 May)
• Re: [whatwg/fetch] Editorial: rename "basic fetch" to "generic fetch" (#537) (Thursday, 4 May)
• Re: [whatwg/fetch] Editorial: rename "basic fetch" to "generic fetch" (#537) (Thursday, 4 May)
• [whatwg/fetch] Editorial: rename "basic fetch" to "generic fetch" (#537) (Wednesday, 3 May)
• Re: [whatwg/fetch] Response filter escalation (#535) (Tuesday, 2 May)
• Re: [whatwg/fetch] Response filter escalation (#535) (Tuesday, 2 May)
• [whatwg/fetch] Response filter escalation (#535) (Tuesday, 2 May)
• Re: [whatwg/fetch] Editorial: correct typo (#533) (Tuesday, 2 May)
• Re: [whatwg/fetch] Editorial: correct typo (#533) (Tuesday, 2 May)
• [whatwg/fetch] Editorial: correct typo (#533) (Monday, 1 May)

Jungkee Song

• Re: [w3c/ServiceWorker] "Unregister" operation may be interrupted by `ServiceWorker#postMessage` (#1146) (Wednesday, 31 May)
• Re: [w3c/ServiceWorker] update() method algorithm needs correction (#1153) (Wednesday, 31 May)
• Re: [w3c/ServiceWorker] update() method algorithm needs correction (#1153) (Wednesday, 31 May)
• Re: [w3c/ServiceWorker] Dynamic Event Handler Registration (#1156) (Wednesday, 31 May)
• Re: [w3c/ServiceWorker] Should update() called on an installing worker reject (as currently does?) (#1155) (Wednesday, 31 May)
• Re: [w3c/ServiceWorker] Should update() called on an installing worker reject (as currently does?) (#1155) (Tuesday, 30 May)
• Re: [w3c/ServiceWorker] Should update() called on an installing worker reject (as currently does?) (#1155) (Tuesday, 30 May)
• Re: [w3c/ServiceWorker] adding IANA considerations section (#1154) (Tuesday, 30 May)
• Re: [w3c/ServiceWorker] adding IANA considerations section (#1154) (Monday, 29 May)
• Re: [w3c/ServiceWorker] adding IANA considerations section (#1154) (Monday, 29 May)
• Re: [w3c/ServiceWorker] adding IANA considerations section (#1154) (Monday, 29 May)
• Re: [w3c/ServiceWorker] adding IANA considerations section (#1154) (Monday, 29 May)
• [w3c/ServiceWorker] Should update() called on an installing worker reject (as currently does?) (#1155) (Monday, 29 May)
• [w3c/ServiceWorker] update() method algorithm needs correction (#1153) (Monday, 29 May)
• Re: [w3c/ServiceWorker] Editorial: correct method control flow (#1152) (Monday, 29 May)
• Re: [w3c/ServiceWorker] Editorial: correct method control flow (#1152) (Monday, 29 May)
• Re: [w3c/ServiceWorker] Editorial: correct method control flow (#1152) (Monday, 29 May)
• Re: [w3c/ServiceWorker] Editorial: Correct value references (#1150) (Monday, 29 May)
• Re: [w3c/ServiceWorker] Editorial: Correct value references (#1150) (Monday, 29 May)
• Re: [w3c/ServiceWorker] Use ASCII serialization for origins (#1151) (Friday, 26 May)
• Re: [w3c/ServiceWorker] Use ASCII serialization for origins (#1151) (Friday, 26 May)
• [w3c/ServiceWorker] Use ASCII serialization for origins (#1151) (Friday, 26 May)
• Re: [w3c/ServiceWorker] Editorial: Correct grammar of informative note (#1145) (Friday, 26 May)
• Re: [w3c/ServiceWorker] Editorial: Correct grammar of informative note (#1145) (Friday, 26 May)
• Re: [w3c/ServiceWorker] Editorial: Correct grammar of informative note (#1145) (Monday, 22 May)
• Re: [w3c/ServiceWorker] Fix fetchEvent.request initialization (#1147) (Friday, 19 May)
• Re: [w3c/ServiceWorker] Handle Fetch creates JavaScript objects too early (and other feedback) (#951) (Friday, 19 May)
• Re: [w3c/ServiceWorker] Fix fetchEvent.request initialization (#1147) (Friday, 19 May)
• Re: [w3c/ServiceWorker] Fix fetchEvent.request initialization (#1147) (Friday, 19 May)
• [w3c/ServiceWorker] Fix fetchEvent.request initialization (#1147) (Friday, 19 May)
• Re: [w3c/ServiceWorker] Changing useCache boolean to updateViaCache enum (#1107) (Monday, 15 May)
• Re: [w3c/ServiceWorker] Changing useCache boolean to updateViaCache enum (#1107) (Monday, 15 May)
• Re: [w3c/ServiceWorker] Changing useCache boolean to updateViaCache enum (#1107) (Monday, 15 May)
• Re: [w3c/ServiceWorker] Changing useCache boolean to updateViaCache enum (#1107) (Monday, 15 May)
• Re: [w3c/ServiceWorker] Changing useCache boolean to updateViaCache enum (#1107) (Monday, 15 May)
• Re: [w3c/ServiceWorker] Adding a developer-provided name (#1121) (Monday, 15 May)
• Re: [w3c/ServiceWorker] Service worker MessageEvents set the "origin" property, but Worker MessageEvents do not. (#1122) (Monday, 15 May)
• Re: [w3c/ServiceWorker] Register HTTP header fields with IANA (#1134) (Monday, 15 May)
• Re: [w3c/ServiceWorker] Priority of requests (feature request) (#1137) (Monday, 15 May)
• Re: [w3c/ServiceWorker] navigator.serviceWorker.ready remain resolved after unregister (#1139) (Monday, 15 May)
• Re: [w3c/ServiceWorker] Assert same-origin for registration matching (#1138) (Friday, 12 May)
• Re: [w3c/ServiceWorker] Assert same-origin for registration matching (#1138) (Friday, 12 May)
• Re: [w3c/ServiceWorker] Assert same-origin for registration matching (#1138) (Friday, 12 May)
• Re: [w3c/ServiceWorker] Assert same-origin for registration matching (#1138) (Friday, 12 May)
• Re: [w3c/ServiceWorker] Assert same-origin for registration matching (#1138) (Friday, 12 May)
• Re: [w3c/ServiceWorker] Match Service Worker Registration should assert same-origin? (#1118) (Friday, 12 May)
• Re: [w3c/ServiceWorker] Assert same-origin for registration matching (#1138) (Friday, 12 May)
• Re: [w3c/ServiceWorker] Assert same-origin for registration matching (#1138) (Friday, 12 May)
• Re: [w3c/ServiceWorker] Assert same-origin for registration matching (#1138) (Friday, 12 May)
• Re: [w3c/ServiceWorker] Assert same-origin for registration matching (#1138) (Friday, 12 May)
• [w3c/ServiceWorker] Assert same-origin for registration matching (#1138) (Friday, 12 May)
• Re: [w3c/ServiceWorker] Match Service Worker Registration should assert same-origin? (#1118) (Friday, 12 May)
• Re: [w3c/ServiceWorker] Match Service Worker Registration should assert same-origin? (#1118) (Thursday, 11 May)
• Re: [w3c/ServiceWorker] Match Service Worker Registration should assert same-origin? (#1118) (Thursday, 11 May)
• Re: [w3c/ServiceWorker] Match Service Worker Registration should assert same-origin? (#1118) (Thursday, 11 May)
• Re: [w3c/ServiceWorker] Match Service Worker Registration should assert same-origin? (#1118) (Wednesday, 10 May)
• Re: [w3c/ServiceWorker] Editorial: Simplify `ready` (#1136) (Wednesday, 10 May)
• Re: [w3c/ServiceWorker] Editorial: Simplify `ready` (#1136) (Wednesday, 10 May)
• Re: [w3c/ServiceWorker] Match Service Worker Registration should assert same-origin? (#1118) (Thursday, 4 May)
• Re: [w3c/ServiceWorker] Match Service Worker Registration should assert same-origin? (#1118) (Thursday, 4 May)
• Re: [w3c/ServiceWorker] Secure context language is redundant/contradicts secure context spec (#1125) (Thursday, 4 May)
• Re: [w3c/ServiceWorker] Use proper license in CONTRIBUTING (#1135) (Thursday, 4 May)

jungshik

• Re: [whatwg/encoding] Half-width Katakana should be representable in ISO-2022-JP (#105) (Sunday, 7 May)
• Re: [whatwg/encoding] ISO-2022-JP encoder: convert halfwidth Katakana to fullwidth (#106) (Saturday, 6 May)
• Re: [whatwg/encoding] Half-width Katakana should be representable in ISO-2022-JP (#105) (Saturday, 6 May)

Justin Novosad

• Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Thursday, 25 May)
• Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Thursday, 25 May)
• Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Thursday, 25 May)

Kagami Sascha Rosylight

• Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Sunday, 21 May)
• Re: [w3c/gamepad] IDL array[]s no longer exist (#28) (Thursday, 18 May)
• [w3c/selection-api] Specify when the selection collapsing happen on mouse click (#90) (Tuesday, 2 May)

Kenneth Rohde Christiansen

• Re: [w3ctag/design-reviews] Cross-spec device identification & association (#64) (Wednesday, 31 May)
• Re: [w3ctag/design-reviews] Cross-spec device identification & association (#64) (Wednesday, 31 May)
• Re: [w3c/manifest] Install prompts: Allow manual prompting but not automatic prompting (#576) (Wednesday, 10 May)
• Re: [w3c/manifest] Define how the manifest is fetched (#481) (Tuesday, 9 May)
• Re: [w3c/manifest] Add shortcuts (#575) (Tuesday, 9 May)
• Re: [w3c/manifest] feat: Add splashscreens member + purpose (closes #510) (#530) (Friday, 5 May)
• Re: [w3c/manifest] Use UTF-8 decode when obtaining a manifest (#570) (Tuesday, 2 May)
• Re: [w3c/manifest] It is not stated how to decode the bytes obtained (#565) (Tuesday, 2 May)
• Re: [w3c/manifest] Fix typos in "Privacy consideration: start_url tracking" (#571) (Tuesday, 2 May)
• Re: [w3c/manifest] Fix typos in "Privacy consideration: start_url tracking" (#571) (Tuesday, 2 May)
• Re: [w3c/manifest] feat: Add splashscreens member + purpose (closes #510) (#530) (Tuesday, 2 May)
• Re: [w3c/manifest] Status section has misleading info on filing bugs (#489) (Tuesday, 2 May)
• Re: [w3c/manifest] Is it possible for a progressive web app to embed web manifest into html page? (#534) (Tuesday, 2 May)
• Re: [w3c/manifest] purpose: badge should be defined as default badge for Notifications API (#508) (Tuesday, 2 May)
• Re: [w3c/manifest] The list of known Web Manifest platform values is confusing (#538) (Tuesday, 2 May)
• Re: [w3c/manifest] Define how the manifest is fetched (#481) (Tuesday, 2 May)
• Re: [w3c/manifest] Should the spec include a link to the Explainer? (#512) (Tuesday, 2 May)
• Re: [w3c/manifest] Extending the manifest with 'vendor-specific' properties (#560) (Tuesday, 2 May)
• Re: [w3c/manifest] scope="../" should be invalid (#551) (Tuesday, 2 May)
• Re: [w3c/manifest] Allow app to load in parallel to splash screen (#559) (Tuesday, 2 May)
• Re: [w3c/manifest] Add (optional) "category" member (#569) (Tuesday, 2 May)
• Re: [w3c/manifest] feat: add iarc_rating_id member (resolves #523) (#567) (Tuesday, 2 May)
• Re: [w3c/manifest] feat: add iarc_rating_id member (resolves #523) (#567) (Tuesday, 2 May)
• Re: [w3c/manifest] feat: add iarc_rating_id member (resolves #523) (#567) (Tuesday, 2 May)
• Re: [w3c/manifest] feat: add iarc_rating_id member (resolves #523) (#567) (Tuesday, 2 May)
• Re: [w3c/manifest] feat: add iarc_rating_id member (resolves #523) (#567) (Tuesday, 2 May)

Kenton Varda

• Re: [whatwg/streams] ReadableStreamDefaultController seems redundant (#743) (Wednesday, 10 May)
• [whatwg/streams] ReadableStreamDefaultController seems redundant (#743) (Wednesday, 10 May)
• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Tuesday, 9 May)
• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Tuesday, 9 May)

kepengli

• Re: [w3c/push-api] Issue: Change Source of Push Service and Privacy Issues (#258) (Friday, 12 May)

Kit Cambridge

• Re: [w3c/push-api] Propose enabling background sync from `pushsubscriptionchange` events (#240) (Monday, 1 May)

Kizilaslan

• [whatwg/fetch] MK (#534) (Tuesday, 2 May)

L. David Baron

• Re: [w3ctag/design-reviews] Web Share API (#179) (Wednesday, 31 May)
• Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141) (Tuesday, 30 May)
• Re: [w3ctag/design-reviews] TAG Review of HTML 5.2 (previously 5.1) (#119) (Friday, 26 May)
• Re: [w3ctag/design-reviews] Web payment method manifest (#162) (Tuesday, 23 May)
• Re: [w3ctag/design-reviews] ViewportAPI naming Re-review (#172) (Tuesday, 16 May)
• Re: [w3ctag/design-reviews] Web payment method manifest (#162) (Tuesday, 16 May)
• Re: [w3ctag/design-reviews] SharedArrayBuffer + Atomics (#165) (Wednesday, 10 May)
• Re: [w3ctag/design-reviews] SharedArrayBuffer + Atomics (#165) (Tuesday, 9 May)

Lars T Hansen

• Re: [w3ctag/design-reviews] SharedArrayBuffer + Atomics (#165) (Wednesday, 10 May)

Lea Verou

• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Wednesday, 10 May)

Léonie Watson

• Re: [w3c/charter-html] Drop High Level User Events (#137) (Wednesday, 24 May)
• Re: [w3c/charter-html] Drop High Level User Events (#137) (Wednesday, 24 May)
• Re: [w3c/charter-html] Incubation and new deliverables (#140) (Wednesday, 24 May)
• Re: [w3c/charter-html] Relation with WICG (#141) (Wednesday, 24 May)
• Re: [w3c/charter-html] Relation with WICG (#141) (Wednesday, 24 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Wednesday, 24 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Wednesday, 24 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Tuesday, 23 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Tuesday, 23 May)
• [w3c/screen-orientation] Wide review tracker (#102) (Saturday, 20 May)
• Re: [w3ctag/design-reviews] Review Screen Orientation spec prior to CR-entry (#157) (Saturday, 20 May)
• Re: [w3c/IndexedDB] Horizontal review… (#112) (Saturday, 20 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Wednesday, 17 May)

Makoto Shimazu

• Re: [w3c/ServiceWorker] consider exposing a type attribute on Client (#1005) (Monday, 1 May)

Marcos Cáceres

• Re: [w3c/permissions] Define restrictions on "device-info" permission (from TPAC). (#131) (Wednesday, 31 May)
• Re: [w3c/manifest] Provide VR display mode (#583) (Monday, 29 May)
• Re: [w3c/manifest] Provide VR display mode (#583) (Thursday, 25 May)
• Re: [w3c/manifest] FR: Context menus on app icons. (#582) (Wednesday, 24 May)
• Re: [w3c/manifest] FR: Context menus on app icons. (#582) (Wednesday, 24 May)
• Re: [w3c/manifest] FR: Context menus on app icons. (#582) (Wednesday, 24 May)
• Re: [w3c/manifest] Provide VR display mode (#583) (Wednesday, 24 May)
• Re: [w3c/manifest] Provide VR display mode (#583) (Tuesday, 23 May)
• Re: [whatwg/dom] Can one get the "original" name of an element? (#460) (Monday, 22 May)
• Re: [whatwg/dom] Can one get the "original" name of an element? (#460) (Monday, 22 May)
• [whatwg/dom] Can one get the "original" name of an element (#460) (Monday, 22 May)
• Re: [w3c/manifest] Change platform android by play in exemple (#581) (Monday, 22 May)
• Re: [w3c/manifest] Change platform android by play in exemple (#581) (Monday, 22 May)
• Re: [w3c/manifest] Change platform android by play in exemple (#581) (Monday, 22 May)
• Re: [w3c/manifest] Which "platform" should I use for Windows 10 UWP apps? (#580) (Thursday, 18 May)
• Re: [w3c/manifest] beforeinstallprompt not fire (#579) (Wednesday, 17 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Tuesday, 16 May)
• Re: [w3c/manifest] Publishing icons for various UI sizes (DIPs) (#568) (Tuesday, 16 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Monday, 15 May)
• Re: [w3c/manifest] Install prompts: Allow manual prompting but not automatic prompting (#576) (Monday, 15 May)
• Re: [w3c/manifest] BeforeInstallPromptEvent: Should prompt() throw InvalidStateError if preventDefault not called? (#577) (Monday, 15 May)
• Re: [w3c/manifest] feat: add iarc_rating_id member (resolves #523) (#567) (Friday, 12 May)
• Re: [whatwg/url] Provide means to "strip query" (#247) (Thursday, 11 May)
• Re: [whatwg/url] Provide means to "strip query" (#247) (Thursday, 11 May)
• Re: [whatwg/url] Provide means to "strip query" (#247) (Thursday, 11 May)
• Re: [whatwg/url] Provide means to "strip query" (#247) (Thursday, 11 May)
• Re: [w3c/manifest] Define how the manifest is fetched (#481) (Tuesday, 9 May)
• Re: [w3c/manifest] Define how the manifest is fetched (#481) (Tuesday, 9 May)
• Re: [w3c/manifest] purpose: badge should be defined as default badge for Notifications API (#508) (Tuesday, 9 May)
• Re: [w3c/manifest] Is it possible for a progressive web app to embed web manifest into html page? (#534) (Tuesday, 9 May)
• Re: [w3c/manifest] Add installation prompt control flow (#417) (Tuesday, 9 May)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Tuesday, 9 May)
• Re: [w3c/manifest] Add shortcuts (#575) (Tuesday, 9 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Friday, 5 May)
• Re: [w3c/manifest] feat: Add splashscreens member + purpose (closes #510) (#530) (Friday, 5 May)
• Re: [w3c/manifest] Fix typos in "Privacy consideration: start_url tracking" (#571) (Friday, 5 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Thursday, 4 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Thursday, 4 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Thursday, 4 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Thursday, 4 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Thursday, 4 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Thursday, 4 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Thursday, 4 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Thursday, 4 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Thursday, 4 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Thursday, 4 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Wednesday, 3 May)
• Re: [w3c/manifest] Small markup issues (#572) (Wednesday, 3 May)
• Re: [w3c/manifest] Use UTF-8 decode when obtaining a manifest (#570) (Wednesday, 3 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Wednesday, 3 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Wednesday, 3 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Wednesday, 3 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Wednesday, 3 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Wednesday, 3 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Wednesday, 3 May)
• [w3c/manifest] Small markup issues (#572) (Wednesday, 3 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Tuesday, 2 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Tuesday, 2 May)
• [heycam/webidl] WIP: add localizable dictionary (#358) (Tuesday, 2 May)
• Re: [w3c/manifest] feat: add iarc_rating_id member (resolves #523) (#567) (Tuesday, 2 May)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Tuesday, 2 May)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Tuesday, 2 May)
• Re: [w3c/manifest] Add iarc_rating_id (resolves #523) (#567) (Tuesday, 2 May)
• Re: [w3c/manifest] Add iarc_rating_id (resolves #523) (#567) (Tuesday, 2 May)
• Re: [w3c/manifest] feat: Add splashscreens member + purpose (closes #510) (#530) (Tuesday, 2 May)
• Re: [w3c/manifest] Add (optional) "category" member (#569) (Tuesday, 2 May)
• Re: [w3c/manifest] It is not stated how to decode the bytes obtained (#565) (Monday, 1 May)
• Re: [w3c/manifest] It is not stated how to decode the bytes obtained (#565) (Monday, 1 May)
• Re: [w3c/manifest] Publishing icons for various UI sizes (DIPs) (#568) (Monday, 1 May)
• Re: [w3c/manifest] Publishing icons for various UI sizes (DIPs) (#568) (Monday, 1 May)
• Re: [w3ctag/design-reviews] Review Accessibility Object Model (#134) (Monday, 1 May)
• Re: [w3c/screen-orientation] Add a link to web-platform-tests to the top of the spec (#98) (Monday, 1 May)
• Re: [w3c/screen-orientation] Add a link to web-platform-tests to the top of the spec (#98) (Monday, 1 May)

Marijn Kruisselbrink

• Re: [w3c/ServiceWorker] Editorial: correct typos in <link> element example (#1149) (Monday, 22 May)

Mark Nottingham

• Re: [w3c/ServiceWorker] adding IANA considerations section (#1154) (Tuesday, 30 May)
• Re: [w3c/ServiceWorker] Register HTTP header fields with IANA (#1134) (Thursday, 18 May)
• Re: [w3ctag/design-reviews] Review origin policy. (#127) (Wednesday, 3 May)
• Re: [w3ctag/design-reviews] Review origin policy. (#127) (Wednesday, 3 May)
• Re: [w3ctag/design-reviews] Review origin policy. (#127) (Monday, 1 May)

Martin Thomson

• Re: [w3c/push-api] Define exposure of the Push API interfaces (#255) (Wednesday, 3 May)
• Re: [w3c/push-api] Define exposure of the Push API interfaces (#255) (Wednesday, 3 May)
• Re: [w3c/push-api] Mention how applicationServerKey is used (#250) (Wednesday, 3 May)
• Re: [w3c/push-api] applicationServerKey is never used in subscribe() (#209) (Wednesday, 3 May)

mastiz

• Re: [w3c/manifest] Publishing icons for various UI sizes (DIPs) (#568) (Tuesday, 16 May)
• Re: [w3c/manifest] Publishing icons for various UI sizes (DIPs) (#568) (Monday, 15 May)
• Re: [w3c/manifest] Publishing icons for various UI sizes (DIPs) (#568) (Friday, 5 May)

Matt Falkenhagen

• Re: [w3c/ServiceWorker] Secure context language is redundant/contradicts secure context spec (#1125) (Tuesday, 2 May)
• Re: [whatwg/fetch] Preserve fragment in Request/Response URLs (#214) (Monday, 1 May)
• Re: [w3c/ServiceWorker] Access to fragment identifiers (#854) (Monday, 1 May)

Matt Giuca

• Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Tuesday, 30 May)
• Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Friday, 26 May)
• Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Thursday, 25 May)
• Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Thursday, 25 May)
• Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Thursday, 25 May)
• Re: [w3c/manifest] Install prompts: Allow manual prompting but not automatic prompting (#576) (Wednesday, 24 May)
• Re: [w3c/manifest] beforeinstallprompt not fire (#579) (Wednesday, 17 May)
• Re: [w3c/manifest] beforeinstallprompt not fire (#579) (Wednesday, 17 May)
• Re: [w3c/manifest] beforeinstallprompt not fire (#579) (Wednesday, 17 May)
• Re: [w3c/manifest] Install prompts: Allow manual prompting but not automatic prompting (#576) (Monday, 15 May)
• Re: [w3c/manifest] BeforeInstallPromptEvent: Should prompt() throw InvalidStateError if preventDefault not called? (#577) (Monday, 15 May)
• Re: [w3c/manifest] Provide a way to find out the result of the install prompt without prompt() (#578) (Wednesday, 10 May)
• [w3c/manifest] Provide a way to find out the result of the install prompt without prompt() (#578) (Wednesday, 10 May)
• [w3c/manifest] BeforeInstallPromptEvent: Should prompt throw InvalidStateError if preventDefault not called? (#577) (Wednesday, 10 May)
• Re: [w3c/manifest] Install prompts: Allow manual prompting but not automatic prompting (#576) (Wednesday, 10 May)
• [w3c/manifest] BeforeInstallPromptEvent: Allow manual prompting but not automatic prompting (#576) (Wednesday, 10 May)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Tuesday, 9 May)
• Re: [w3c/manifest] Feat(events): add BeforeInstallPromptEvent (#520) (Tuesday, 2 May)

Matthew Phillips

• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Friday, 12 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Wednesday, 10 May)

Matthew Ryan

• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Friday, 19 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Friday, 19 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Thursday, 18 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Wednesday, 17 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Tuesday, 16 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Sunday, 14 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Sunday, 14 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Sunday, 14 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Sunday, 14 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Saturday, 13 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Saturday, 13 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Friday, 12 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Friday, 12 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Friday, 12 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Friday, 12 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Friday, 12 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Friday, 12 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Tuesday, 9 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Monday, 8 May)
• Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354) (Monday, 8 May)
• [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Monday, 8 May)
• Re: [w3c/webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354) (Sunday, 7 May)

Max Baluev

• Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447) (Monday, 22 May)

maxpassion

• [w3c/push-api] Issue: Change Source of Push Service and Privacy Issues (#258) (Thursday, 11 May)

Mehrdad Reshadi

• Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Monday, 22 May)

Michael Champion

• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Tuesday, 23 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Monday, 22 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Wednesday, 17 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Tuesday, 16 May)

Michael Heuberger

• Re: [heycam/webidl] Need an error for "User refused permission" (#95) (Monday, 1 May)

Michael[tm] Smith

• Re: [whatwg/encoding] Meta: retry HTML checker by curl, suppress warnings (#109) (Wednesday, 24 May)
• Re: [whatwg/encoding] Meta: retry HTML checker by curl, suppress warnings (#109) (Tuesday, 23 May)
• Re: [whatwg/encoding] Meta: retry HTML checker by curl, suppress warnings (#109) (Tuesday, 23 May)
• Re: [whatwg/encoding] Meta: retry HTML checker by curl, suppress warnings (#109) (Tuesday, 23 May)
• Re: [whatwg/encoding] Meta: retry HTML checker by curl, suppress warnings (#109) (Tuesday, 23 May)
• Re: [whatwg/encoding] Meta: retry HTML checker by curl, suppress warnings (#109) (Tuesday, 23 May)
• Re: [whatwg/encoding] Meta: retry HTML checker by curl, suppress warnings (#109) (Tuesday, 23 May)
• Re: [whatwg/encoding] Meta: retry HTML checker by curl, suppress warnings (#109) (Tuesday, 23 May)
• Re: [whatwg/encoding] Meta: retry HTML checker by curl, suppress warnings (#109) (Tuesday, 23 May)
• Re: [whatwg/encoding] Meta: retry HTML checker by curl, suppress warnings (#109) (Tuesday, 23 May)
• Re: [whatwg/encoding] Meta: retry HTML checker by curl, suppress warnings (#109) (Tuesday, 23 May)
• Re: [whatwg/encoding] Meta: retry HTML checker by curl, suppress warnings (#109) (Tuesday, 23 May)
• Re: [whatwg/encoding] Meta: retry HTML checker by curl, suppress warnings (#109) (Tuesday, 23 May)
• Re: [whatwg/encoding] Meta: retry HTML checker by curl, suppress warnings (#109) (Tuesday, 23 May)
• Re: [whatwg/encoding] Meta: retry HTML checker by curl, suppress warnings (#109) (Tuesday, 23 May)
• Re: [whatwg/encoding] Meta: retry HTML checker by curl, suppress warnings (#109) (Tuesday, 23 May)
• Re: [whatwg/encoding] Meta: retry HTML checker by curl, suppress warnings (#109) (Tuesday, 23 May)
• Re: [whatwg/encoding] Meta: retry HTML checker by curl, suppress warnings (#109) (Tuesday, 23 May)
• Re: [whatwg/encoding] Meta: retry HTML checker by curl, suppress warnings (#109) (Tuesday, 23 May)
• Re: [whatwg/encoding] Meta: retry HTML checker by curl, suppress warnings (#109) (Tuesday, 23 May)
• Re: [whatwg/encoding] Meta: retry HTML checker by curl, suppress warnings (#109) (Tuesday, 23 May)
• Re: [whatwg/encoding] Important warnings getting lost in the noise (#97) (Sunday, 7 May)
• [whatwg/encoding] Meta: retry HTML checker by curl, suppress warnings (#109) (Sunday, 7 May)

Miguel Casas-Sanchez

• Re: [w3ctag/design-reviews] WICG Shape Detection API (#176) (Thursday, 25 May)
• [w3ctag/design-reviews] WICG Shape Detection API (#176) (Thursday, 11 May)

Mike Taylor

• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Wednesday, 17 May)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Tuesday, 16 May)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Tuesday, 9 May)

Mike West

• Re: [whatwg/fetch] Prevent requests to HTTP(S) URLs containing raw `\n` and `<`. (#546) (Wednesday, 31 May)
• Re: [whatwg/url] Record whether the URL parser removed newlines. (#284) (Saturday, 27 May)
• Re: [whatwg/url] Record whether the URL parser removed newlines. (#284) (Thursday, 25 May)
• Re: [whatwg/url] Record whether the URL parser removed newlines. (#284) (Thursday, 25 May)
• Re: [whatwg/url] Record whether the URL parser removed newlines. (#284) (Wednesday, 24 May)
• Re: [whatwg/url] Record whether the URL parser removed newlines. (#284) (Wednesday, 24 May)
• Re: [whatwg/url] Record whether the URL parser removed newlines. (#284) (Wednesday, 24 May)
• Re: [whatwg/url] Record whether the URL parser removed newlines. (#284) (Tuesday, 23 May)
• Re: [whatwg/url] Record whether the URL parser removed newlines. (#284) (Tuesday, 23 May)
• Re: [whatwg/fetch] Block requests for suspected dangling markup. (#519) (Tuesday, 23 May)
• Re: [whatwg/url] Record whether the URL parser removed newlines. (#284) (Tuesday, 23 May)
• Re: [whatwg/url] Record whether the URL parser removed newlines. (#284) (Tuesday, 23 May)
• Re: [whatwg/fetch] Block requests for suspected dangling markup. (#519) (Tuesday, 23 May)
• Re: [whatwg/url] Record whether the URL parser removed newlines. (#284) (Tuesday, 23 May)
• Re: [whatwg/url] Record whether the URL parser removed newlines. (#284) (Tuesday, 23 May)
• Re: [whatwg/fetch] Block requests for suspected dangling markup. (#519) (Tuesday, 23 May)
• Re: [whatwg/fetch] Prevent requests to HTTP(S) URLs containing raw `\n` and `<`. (#546) (Monday, 22 May)
• Re: [whatwg/url] Record whether the URL parser removed newlines. (#284) (Monday, 22 May)
• Re: [whatwg/fetch] Block requests for suspected dangling markup. (#519) (Monday, 22 May)
• Re: [whatwg/fetch] Block requests for suspected dangling markup. (#519) (Monday, 22 May)
• Re: [whatwg/url] Record whether the URL parser removed newlines. (#284) (Monday, 22 May)
• Re: [whatwg/fetch] Prevent requests to URLs containing raw `\n` and `<`. (#546) (Monday, 22 May)
• [whatwg/fetch] Prevent requests to URLs containing raw `\n` and `<`. (#546) (Monday, 22 May)
• Re: [whatwg/fetch] "With Credentials" flag possibly inconsistent with web architecture (#517) (Monday, 15 May)
• Re: [whatwg/fetch] Consider adding SMB to port blacklist (#544) (Sunday, 14 May)
• Re: [whatwg/fetch] Consider adding SMB to port blacklist (#544) (Sunday, 14 May)
• [whatwg/fetch] Update the CSP mappings for requests. (#541) (Wednesday, 10 May)
• Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) (Tuesday, 9 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Friday, 5 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Thursday, 4 May)
• Re: [heycam/webidl] "::" is used in comments but is not formally a part of webidl ? (#354) (Tuesday, 2 May)

Mislav Marohnić

• Re: [whatwg/fetch] provide a way to construct a new Request from an old Request and an overriding URL (#129) (Tuesday, 2 May)

Mounir Lamouri

• Re: [whatwg/fullscreen] document.fullscreenElement in scroll event after entering fullscreen matters for compat (#74) (Thursday, 18 May)
• [whatwg/fullscreen] `fullscreenchange` should behave like `webkitfullscreenchange` (#89) (Thursday, 18 May)

Mustaq Ahmed

• Re: [w3c/uievents] Standardize layerX/layerY on MouseEvent (#135) (Tuesday, 16 May)

Nathan Broadbent

• Re: [w3c/manifest] Which "platform" should I use for Windows 10 UWP apps? (#580) (Thursday, 18 May)
• [w3c/manifest] Which "platform" should I use for Windows 10 UWP apps? (#580) (Thursday, 18 May)

Navid Zolghadr

• Re: [w3c/uievents] Click event is not fired when the node is removed and then added back (#141) (Tuesday, 2 May)
• [w3c/uievents] Click event when the node is removed and then added back is not fired (#141) (Tuesday, 2 May)

Nic Jansma

• Re: [whatwg/fetch] Observer API for fetch groups (#65) (Wednesday, 3 May)

Nicolaie Constantinescu

• Re: [w3c/uievents] 3.1. Event dispatch and DOM event flow - small typo (#143) (Thursday, 25 May)
• [w3c/uievents] 3.1. Event dispatch and DOM event flow - small typo (#143) (Thursday, 25 May)

Nicolas HENRY

• Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Monday, 29 May)
• Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Monday, 29 May)

Ole Ersoy

• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 23 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 22 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 22 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 22 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 22 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 21 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 21 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 20 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 20 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 18 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 18 May)

Oliver Hoff

• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 22 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 22 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 22 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 22 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 21 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Friday, 19 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 18 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 18 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 17 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 17 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 16 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 16 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 15 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 14 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Sunday, 14 May)

OvermindDL1

• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 22 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 22 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Monday, 22 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Thursday, 18 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 17 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 16 May)

Owen Campbell-Moore

• [w3ctag/design-reviews] Web Share API (#179) (Wednesday, 31 May)

Pat Mächler

• Re: [w3c/manifest] Fix typos in "Privacy consideration: start_url tracking" (#571) (Wednesday, 3 May)
• Re: [w3c/manifest] Fix typos in "Privacy consideration: start_url tracking" (#571) (Tuesday, 2 May)
• Re: [w3c/manifest] Fix typos in "Privacy consideration: start_url tracking" (#571) (Tuesday, 2 May)
• [w3c/manifest] Fix typos in "Privacy consideration: start_url tracking" (#571) (Tuesday, 2 May)

Patrick H. Lauke

• Re: [w3c/touch-events] Add touchType, altitudeAngle, azimuthAngle (Safari iOS 10.3 extensions for stylus) (#81) (Sunday, 7 May)
• Re: [w3c/touch-events] Add touchType, altitudeAngle, azimuthAngle (Safari iOS 10.3 extensions for stylus) (#81) (Thursday, 4 May)

Paul Cotton

• Re: [w3c/charter-html] Relation with WICG (#141) (Tuesday, 16 May)

Pedram Emrouznejad

• Re: [w3c/ServiceWorker] event.waitUntil/respondWith vs return promise (#1148) (Sunday, 21 May)
• Re: [w3c/ServiceWorker] event.waitUntil/respondWith vs return promise (#1148) (Sunday, 21 May)
• Re: [w3c/ServiceWorker] event.waitUntil/respondWith vs return promise (#1148) (Saturday, 20 May)
• [w3c/ServiceWorker] event.waitUntil/respondWith vs return promise (#1148) (Saturday, 20 May)

Peter Beverloo

• Re: [w3ctag/design-reviews] Budget API (especially reserve() method) (#169) (Wednesday, 24 May)
• Re: [w3c/push-api] Issue: Change Source of Push Service and Privacy Issues (#258) (Tuesday, 16 May)
• Re: [w3c/push-api] Issue: Change Source of Push Service and Privacy Issues (#258) (Thursday, 11 May)
• Re: [w3c/push-api] User preference for timing (#257) (Wednesday, 10 May)
• Re: [w3c/push-api] Fix three reference errors (#256) (Monday, 8 May)
• [w3c/push-api] Fix three reference errors (#256) (Friday, 5 May)
• Re: [w3c/push-api] Define exposure of the Push API interfaces (#255) (Wednesday, 3 May)
• [w3c/push-api] Define exposure of the Push API interfaces (#255) (Wednesday, 3 May)
• Re: [w3c/push-api] Mention how applicationServerKey is used (#250) (Wednesday, 3 May)

Peter Linss

• Re: [w3ctag/design-reviews] TAG Review of HTML 5.2 (previously 5.1) (#119) (Friday, 26 May)
• Re: [w3ctag/design-reviews] SharedArrayBuffer + Atomics (#165) (Tuesday, 23 May)
• Re: [w3ctag/design-reviews] Review request for Feature Policy (#159) (Tuesday, 23 May)
• Re: [w3ctag/design-reviews] Review request for Feature Policy (#159) (Tuesday, 23 May)
• Re: [w3ctag/design-reviews] Review origin policy. (#127) (Tuesday, 23 May)

Peter Occil

• [whatwg/encoding] For your information: Illegal UTF-8 proposal (#112) (Friday, 12 May)

Philip Jägenstedt

• Re: [w3ctag/design-reviews] WebUSB (#108) (Wednesday, 31 May)
• Re: [whatwg/fullscreen] Fullscreen/unfullscreen ASAP; fire events in animation frame tasks (#92) (Wednesday, 31 May)
• Re: [whatwg/fullscreen] Fullscreen/unfullscreen ASAP; fire events in animation frame tasks (#92) (Wednesday, 31 May)
• [whatwg/fullscreen] Fullscreen/unfullscreen ASAP; fire events in animation frame tasks (#92) (Wednesday, 31 May)
• Re: [whatwg/fullscreen] `fullscreenchange` should behave like `webkitfullscreenchange` (#89) (Wednesday, 31 May)
• Re: [whatwg/fullscreen] Fire events at elements by default, falling back to documents (#90) (Wednesday, 31 May)
• Re: [whatwg/fullscreen] Fire events at elements by default, falling back to documents (#90) (Wednesday, 31 May)
• Re: [whatwg/url] Let webkitURL be an alias of the URL constructor (#135) (Monday, 29 May)
• Re: [w3c/uievents] Standardize layerX/layerY on MouseEvent (#135) (Monday, 29 May)
• Re: [whatwg/fullscreen] Give "exit fullscreen" a fully flag and define "fully exit fullscreen" using it (#65) (Wednesday, 24 May)
• Re: [whatwg/fullscreen] Reinstate the hierarchy restrictions (#91) (Wednesday, 24 May)
• Re: [whatwg/fullscreen] Reinstate the hierarchy restrictions (#91) (Wednesday, 24 May)
• Re: [whatwg/fullscreen] Fire events at elements by default, falling back to documents (#90) (Wednesday, 24 May)
• Re: [whatwg/fullscreen] Fire events at elements by default, falling back to documents (#90) (Tuesday, 23 May)
• Re: [whatwg/fullscreen] Reinstate the hierarchy restrictions (#91) (Tuesday, 23 May)
• Re: [whatwg/fullscreen] Reinstate the hierarchy restrictions (#91) (Tuesday, 23 May)
• Re: [whatwg/fullscreen] Reinstate the hierarchy restrictions (#91) (Tuesday, 23 May)
• Re: [whatwg/fullscreen] Reinstate the hierarchy restrictions (#91) (Tuesday, 23 May)
• Re: [whatwg/fullscreen] Reinstate the hierarchy restrictions (#91) (Tuesday, 23 May)
• Re: [whatwg/fullscreen] Reinstate the hierarchy restrictions (#91) (Tuesday, 23 May)
• Re: [whatwg/fullscreen] Fire events at elements by default, falling back to documents (#90) (Monday, 22 May)
• Re: [whatwg/storage] UI and origins <> origin groups (#34) (Monday, 22 May)
• Re: [whatwg/fullscreen] Reinstate the hierarchy restrictions (#91) (Monday, 22 May)
• [whatwg/fullscreen] Reinstate the hierarchy restrictions (#91) (Monday, 22 May)
• Re: [whatwg/fullscreen] Fire events at elements by default, falling back to documents (#90) (Monday, 22 May)
• Re: [whatwg/fullscreen] Fire events at elements by default, falling back to documents (#90) (Monday, 22 May)
• Re: [whatwg/storage] UI and origins <> origin groups (#34) (Monday, 22 May)
• Re: [whatwg/fullscreen] Fire events at elements by default, falling back to documents (#90) (Monday, 22 May)
• Re: [whatwg/fullscreen] Fire events at elements by default, falling back to documents (#90) (Monday, 22 May)
• Re: [whatwg/fullscreen] Fire events at elements by default, falling back to documents (#90) (Friday, 19 May)
• Re: [whatwg/fullscreen] Fire fullscreenchange at elements by default, documents if necessary (#90) (Friday, 19 May)
• Re: [whatwg/fullscreen] Fire fullscreenchange at elements by default, documents if necessary (#90) (Thursday, 18 May)
• Re: [whatwg/fullscreen] `fullscreenchange` should behave like `webkitfullscreenchange` (#89) (Thursday, 18 May)
• Re: [whatwg/fullscreen] `fullscreenchange` should behave like `webkitfullscreenchange` (#89) (Thursday, 18 May)
• Re: [whatwg/fullscreen] `fullscreenchange` should behave like `webkitfullscreenchange` (#89) (Thursday, 18 May)
• [whatwg/fullscreen] Fire fullscreenchange at elements by default, documents if necessary (#90) (Thursday, 18 May)
• Re: [whatwg/fullscreen] document.fullscreenElement in scroll event after entering fullscreen matters for compat (#74) (Thursday, 18 May)
• Re: [whatwg/fullscreen] document.fullscreenElement in scroll event after entering fullscreen matters for compat (#74) (Thursday, 18 May)
• Re: [whatwg/fullscreen] `fullscreenchange` should behave like `webkitfullscreenchange` (#89) (Thursday, 18 May)
• Re: [whatwg/dom] Abort controller (#437) (Thursday, 18 May)
• Re: [whatwg/fullscreen] Decide whether to resize synchronously in requestFullscreen() (#64) (Wednesday, 17 May)
• Re: [whatwg/fullscreen] requestFullscreen() + moving pending element can fire fullscreenerror but leave browser in fullscreen (#88) (Wednesday, 17 May)
• Re: [whatwg/fullscreen] requestFullscreen() + moving pending element can fire fullscreenerror but leave browser in fullscreen (#88) (Wednesday, 17 May)
• Re: [whatwg/fullscreen] requestFullscreen() + moving pending element can fire fullscreenerror but leave browser in fullscreen (#88) (Tuesday, 16 May)
• Re: [heycam/webidl] How to do aliases of legacy interfaces (HTMLDocument, WebKitCSSMatrix...) (#362) (Tuesday, 16 May)
• Re: [whatwg/fullscreen] In requestFullscreen(), handle the pending element moving (#87) (Tuesday, 16 May)
• [whatwg/fullscreen] requestFullscreen() + moving pending element can fire fullscreenerror but leave browser in fullscreen (#88) (Tuesday, 16 May)
• Re: [whatwg/fullscreen] In requestFullscreen(), handle the pending element moving (#87) (Tuesday, 16 May)
• Re: [whatwg/fullscreen] What should happen if an element is moved to another document right after requestFullscreen (#33) (Tuesday, 16 May)
• Re: [whatwg/fullscreen] In requestFullscreen(), handle the pending element moving (#87) (Tuesday, 16 May)
• Re: [whatwg/fullscreen] In requestFullscreen(), handle the pending element moving (#87) (Tuesday, 16 May)
• [whatwg/fullscreen] In requestFullscreen(), handle the pending element moving (#87) (Tuesday, 16 May)
• [w3c/pointerlock] Ask for web-platform-tests in CONTRIBUTING.md (#20) (Tuesday, 16 May)
• Re: [w3c/clipboard-apis] Add missing comma in navigator.clipboard IDL (#43) (Monday, 15 May)
• [w3c/clipboard-apis] Add missing comma in navigator.clipboard IDL (#43) (Monday, 15 May)
• Re: [whatwg/fullscreen] Require that the document is fully active in requestFullscreen() (#85) (Monday, 15 May)
• Re: [whatwg/fullscreen] Animation frame tasks (#86) (Friday, 12 May)
• Re: [whatwg/fullscreen] Animation frame tasks (#86) (Friday, 12 May)
• [whatwg/fullscreen] Animation frame tasks (#86) (Friday, 12 May)
• Re: [whatwg/fullscreen] Add [Unscopable] to Document.prototype.fullscreen (#84) (Friday, 12 May)
• Re: [whatwg/fullscreen] Add [Unscopable] to Document.prototype.fullscreen (#84) (Friday, 12 May)
• Re: [whatwg/fullscreen] Add [Unscopable] to Document.prototype.fullscreen (#84) (Friday, 12 May)
• Re: [whatwg/fullscreen] Require that the document is fully active in requestFullscreen() (#85) (Friday, 12 May)
• Re: [whatwg/fullscreen] Require that the document is fully active in requestFullscreen() (#85) (Friday, 12 May)
• [whatwg/fullscreen] Require that the document is fully active in requestFullscreen() (#85) (Friday, 12 May)
• Re: [whatwg/fullscreen] Add [Unscopable] to Document.prototype.fullscreen (#84) (Friday, 12 May)
• Re: [whatwg/fullscreen] Add [Unscopable] to Document.prototype.fullscreen (#84) (Friday, 12 May)
• [w3c/IndexedDB] Ask for web-platform-tests in CONTRIBUTING.md (#200) (Thursday, 11 May)
• Re: [whatwg/fullscreen] Editorial: use Infra's break to clarify requestFullscreen() iteration (#83) (Thursday, 11 May)
• Re: [w3c/FileAPI] Replace RFC1738 with RFC4266 (gopher) (#81) (Thursday, 11 May)
• [w3c/FileAPI] Replace RFC1738 with RFC4266 (gopher) (#81) (Thursday, 11 May)
• [w3c/FileAPI] Fix link to "that repository" in README.md (#80) (Thursday, 11 May)
• Re: [whatwg/fullscreen] Problems with the "unloading document cleanup steps" (#82) (Thursday, 11 May)
• Re: [whatwg/fullscreen] Editorial: use Infra's break to clarify requestFullscreen() iteration (#83) (Thursday, 11 May)
• [whatwg/fullscreen] Editorial: use Infra's break to clarify requestFullscreen() iteration (#83) (Thursday, 11 May)
• Re: [whatwg/fullscreen] Give "exit fullscreen" a fully flag and define "fully exit fullscreen" using it (#65) (Thursday, 11 May)
• [whatwg/fullscreen] Problems with the "unloading document cleanup steps" (#82) (Thursday, 11 May)
• Re: [whatwg/fullscreen] Give "exit fullscreen" a fully flag and define "fully exit fullscreen" using it (#65) (Thursday, 11 May)
• Re: [whatwg/fullscreen] Clarify what "collect documents to unfullscreen" returns (#81) (Thursday, 11 May)
• Re: [whatwg/fullscreen] Clarify what "collect documents to unfullscreen" returns (#81) (Thursday, 11 May)
• Re: [whatwg/fullscreen] Clarify what "collect documents to unfullscreen" returns (#81) (Thursday, 11 May)
• Re: [whatwg/fullscreen] Give "exit fullscreen" a fully flag and define "fully exit fullscreen" using it (#65) (Wednesday, 10 May)
• Re: [whatwg/fullscreen] Give "exit fullscreen" a fully flag and define "fully exit fullscreen" using it (#65) (Wednesday, 10 May)
• Re: [whatwg/fullscreen] Give "exit fullscreen" a fully flag and define "fully exit fullscreen" using it (#65) (Wednesday, 10 May)
• Re: [whatwg/fullscreen] Give "exit fullscreen" a fully flag and define "fully exit fullscreen" using it (#65) (Wednesday, 10 May)
• Re: [whatwg/fullscreen] Clarify what "collect documents to unfullscreen" returns (#81) (Wednesday, 10 May)
• [whatwg/fullscreen] Clarify what "collect documents to unfullscreen" returns (#81) (Wednesday, 10 May)
• [whatwg/fullscreen] Editorial: update variable name in removing steps (#80) (Wednesday, 10 May)
• Re: [whatwg/fullscreen] Meta: use infra for lists and sets (#79) (Wednesday, 10 May)
• Re: [whatwg/fullscreen] Meta: use infra for lists and sets (#79) (Wednesday, 10 May)
• Re: [whatwg/fullscreen] Meta: use infra for lists and sets (#79) (Wednesday, 10 May)
• Re: [whatwg/fullscreen] Meta: use infra for lists and sets (#79) (Wednesday, 10 May)
• Re: [whatwg/fullscreen] Meta: use infra for lists and sets (#79) (Wednesday, 10 May)
• Re: [whatwg/fullscreen] Meta: use infra for lists and sets (#79) (Wednesday, 10 May)
• Re: [whatwg/fullscreen] Meta: use infra for lists and sets (#79) (Wednesday, 10 May)
• [whatwg/fullscreen] Meta: use infra for lists and sets (#79) (Tuesday, 9 May)
• Re: [heycam/webidl] Given [Constructor, Constructor(DOMString x)], new C(undefined) picks the second (#351) (Friday, 5 May)
• Re: [whatwg/fullscreen] Fix Bikeshed error about SVG reference (#78) (Thursday, 4 May)
• Re: [whatwg/fullscreen] Use SVG2 for the <svg> element reference (#78) (Thursday, 4 May)
• [whatwg/fullscreen] Use SVG2 for the <svg> element reference (#78) (Thursday, 4 May)
• Re: [whatwg/fullscreen] Deny request on invisible document (#60) (Wednesday, 3 May)
• Re: [w3c/uievents] Add a link to web-platform-tests to the top of the spec (#140) (Tuesday, 2 May)
• Re: [heycam/webidl] Allow [TreatNullAs=EmptyString] for USVString? (#340) (Tuesday, 2 May)
• Re: [whatwg/fullscreen] Deny request on invisible document (#60) (Tuesday, 2 May)

Philip Rogers

• Re: [whatwg/fetch] Prevent requests to HTTP(S) URLs containing raw `\n` and `<`. (#546) (Monday, 22 May)

Philippe Le Hegaret

• Re: [w3c/selection-api] Throw exception for removeRange on range that's not in selection (#87) (Tuesday, 9 May)
• [w3c/ServiceWorker] Use proper license in CONTRIBUTING (#1135) (Wednesday, 3 May)

PhistucK

• Re: [whatwg/dom] [Proposal] Add EventTarget.getEventListeners() (#412) (Thursday, 11 May)

Pierre-Anthony Lemieux

• Re: [w3ctag/design-reviews] Timed Text Markup Language 2 (TTML2) (#138) (Tuesday, 16 May)

Pieter

• Re: [w3c/ServiceWorker] Expose GeoLocation to workers (#745) (Monday, 22 May)

pkotwicz

• Re: [w3c/manifest] scope="../" should be invalid (#551) (Tuesday, 2 May)

r12a

• Re: [w3ctag/design-reviews] Serialization of natural language in data formats such as JSON [I18N] (#178) (Thursday, 18 May)

Raphael Kubo da Costa

• Re: [heycam/webidl] Do records (record<>s) purposefully throw on any object with an enumerable Symbol-named property? (#294) (Friday, 19 May)
• Re: [heycam/webidl] Do records (record<>s) purposefully throw on any object with an enumerable Symbol-named property? (#294) (Friday, 19 May)

RccnMarius

• [w3c/manifest] Add shortcuts (#575) (Monday, 8 May)
• Re: [w3c/manifest] Add (optional) "category" member (#569) (Tuesday, 2 May)

Rheetuparna Sarmah

• [whatwg/xhr] jquery.js:9615 [Deprecation] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/. (#139) (Friday, 19 May)

Richard Maher

• Re: [w3c/ServiceWorker] Expose GeoLocation to workers (#745) (Wednesday, 31 May)
• Re: [w3c/ServiceWorker] Expose GeoLocation to workers (#745) (Sunday, 28 May)
• Re: [w3c/ServiceWorker] Expose GeoLocation to workers (#745) (Friday, 26 May)
• Re: [w3c/ServiceWorker] Expose GeoLocation to workers (#745) (Friday, 26 May)
• Re: [w3c/ServiceWorker] Expose GeoLocation to workers (#745) (Friday, 26 May)

Rick Byers

• Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Thursday, 25 May)
• Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Thursday, 25 May)
• Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Thursday, 25 May)
• Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Thursday, 25 May)
• Re: [w3c/touch-events] Add touchType, altitudeAngle, azimuthAngle (Safari iOS 10.3 extensions for stylus) (#81) (Monday, 1 May)

Rick Waldron

• Re: [heycam/webidl] [EnforceRange] should normatively specify RangeError (#359) (Wednesday, 10 May)
• Re: [heycam/webidl] [EnforceRange] should normatively specify RangeError (#359) (Wednesday, 10 May)
• [heycam/webidl] [EnforceRange] should normatively specify RangeError (#359) (Wednesday, 10 May)

Rimas Misevičius

• Re: [whatwg/url] Address several IDNA issues (#309) (Friday, 26 May)
• Re: [whatwg/url] Address several IDNA issues (#309) (Wednesday, 24 May)
• Re: [whatwg/url] Refactor IPv6 in terms of lists (#286) (Wednesday, 24 May)
• Re: [whatwg/url] Refactor IPv6 in terms of lists (#286) (Sunday, 21 May)
• Re: [whatwg/url] Clearly indicate a known issue with ToASCII (#309) (Wednesday, 17 May)
• Re: [whatwg/url] Clearly indicate a known issue with ToASCII (#309) (Monday, 15 May)
• Re: [whatwg/url] Clearly indicate a known issue with ToASCII (#309) (Monday, 15 May)
• Re: [whatwg/url] new URL('file://').origin is 'null' (#310) (Sunday, 14 May)
• Re: [whatwg/url] remaining variable ambiguity (#308) (Thursday, 4 May)

Rob Dolin (MSFT)

• Re: [w3c/manifest] Add (optional) "category" member (#569) (Tuesday, 2 May)
• Re: [w3c/manifest] Fix typos in "Privacy consideration: start_url tracking" (#571) (Tuesday, 2 May)
• Re: [w3c/manifest] Fix typos in "Privacy consideration: start_url tracking" (#571) (Tuesday, 2 May)
• Re: [w3c/manifest] Fix typos in "Privacy consideration: start_url tracking" (#571) (Tuesday, 2 May)
• Re: [w3c/manifest] Status section has misleading info on filing bugs (#489) (Tuesday, 2 May)
• Re: [w3c/manifest] Should the spec include a link to the Explainer? (#512) (Tuesday, 2 May)
• Re: [w3c/manifest] Should the spec include a link to the Explainer? (#512) (Tuesday, 2 May)
• Re: [w3c/manifest] feat: Add splashscreens member + purpose (closes #510) (#530) (Tuesday, 2 May)
• [w3c/manifest] Add (optional) "category" member (#569) (Monday, 1 May)
• Re: [w3c/manifest] feat: Add splashscreens member + purpose (closes #510) (#530) (Monday, 1 May)
• Re: [w3c/manifest] Add info push notifications to extensions registry (#529) (Monday, 1 May)
• Re: [w3c/manifest] Extending the manifest with 'vendor-specific' properties (#560) (Monday, 1 May)
• Re: [w3c/manifest] Add iarc_rating_id (resolves #523) (#567) (Monday, 1 May)

Robert Bradford

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

rocallahan

• Re: [whatwg/fullscreen] Fire events at elements by default, falling back to documents (#90) (Monday, 22 May)

Romain

• Re: [whatwg/streams] Reference to CopyDataBlockBytes (#746) (Tuesday, 23 May)
• [whatwg/streams] Fix arguments order in CopyDataBlockBytes (#747) (Tuesday, 23 May)
• [whatwg/streams] Reference to CopyDataBlockBytes (#746) (Monday, 22 May)
• [whatwg/streams] Define generic operation for GetDesiredSize? (#745) (Wednesday, 17 May)

Russell Bicknell

• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Monday, 22 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Saturday, 20 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Monday, 15 May)

Ryosuke Niwa

• Re: [w3c/webcomponents] Agenda for W3C TPAC 2017 (Web Components) (#641) (Wednesday, 31 May)
• Re: [w3c/webcomponents] Agenda for W3C TPAC 2017 (Web Components) (#641) (Wednesday, 31 May)
• Re: [w3c/webcomponents] Agenda for W3C TPAC 2017 (Web Components) (#641) (Wednesday, 31 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Thursday, 25 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Tuesday, 23 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Friday, 19 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Friday, 19 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Friday, 19 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Friday, 19 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Thursday, 18 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Wednesday, 17 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Wednesday, 17 May)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Wednesday, 17 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Tuesday, 16 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Tuesday, 16 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Monday, 15 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Monday, 15 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Saturday, 13 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Friday, 12 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Friday, 12 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Friday, 12 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Friday, 12 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Friday, 12 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Friday, 12 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Friday, 12 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Thursday, 11 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Wednesday, 10 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Wednesday, 10 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Wednesday, 10 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Wednesday, 10 May)
• Re: [w3c/selection-api] Throw correct exceptions from collapse/selectAllChildren on detached doctypes (#86) (Tuesday, 9 May)
• Re: [w3c/selection-api] Throw exception for removeRange on range that's not in selection (#87) (Tuesday, 9 May)
• Re: [w3c/selection-api] Throw exception for removeRange on range that's not in selection (#87) (Tuesday, 9 May)
• Re: [w3c/selection-api] Add a link to web-platform-tests to the top of the spec (#89) (Tuesday, 9 May)
• Re: [w3c/webcomponents] [Custom]: Need callback for form submit data (bugzilla: 24603) (#187) (Tuesday, 9 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Tuesday, 9 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Tuesday, 9 May)

S.A.N

• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Tuesday, 16 May)

Salvador de la Puente González

• Re: [w3c/manifest] Install prompts: Allow manual prompting but not automatic prompting (#576) (Wednesday, 24 May)
• Re: [w3c/manifest] Provide VR display mode (#583) (Wednesday, 24 May)
• [w3c/manifest] Provide VR display mode (#583) (Tuesday, 23 May)
• Re: [w3c/manifest] Install prompts: Allow manual prompting but not automatic prompting (#576) (Tuesday, 23 May)

samweinig

• [heycam/webidl] [[Set]] algorithm for legacy platform objects does not seem to be compatible with the Storage interface (#366) (Wednesday, 31 May)

Sebastian Mayr

• Re: [whatwg/url] IDNA (#53) (Friday, 26 May)

Shiino Yuki

• Re: [heycam/webidl] Do records (record<>s) purposefully throw on any object with an enumerable Symbol-named property? (#294) (Tuesday, 23 May)
• Re: [heycam/webidl] Do records (record<>s) purposefully throw on any object with an enumerable Symbol-named property? (#294) (Monday, 22 May)

shitalsunilsulakhe

• Re: [whatwg/xhr] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience (#140) (Monday, 22 May)
• [whatwg/xhr] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience (#140) (Monday, 22 May)

Simon Fraser

• Re: [w3c/webcomponents] Should shadow host have `display: block` by default? (#426) (Thursday, 18 May)

Simon Pieters

• Re: [whatwg/url] Specify window.webkitURL as an alias to URL (#312) (Wednesday, 31 May)
• Re: [whatwg/url] Let webkitURL be an alias of the URL constructor (#135) (Wednesday, 31 May)
• Re: [whatwg/url] Let webkitURL be an alias of the URL constructor (#135) (Wednesday, 31 May)
• Re: [whatwg/url] Let webkitURL be an alias of the URL constructor (#135) (Monday, 29 May)
• Re: [whatwg/url] Specify window.webkitURL as an alias to URL (#312) (Tuesday, 23 May)
• Re: [whatwg/url] Specify window.webkitURL as an alias to URL (#312) (Tuesday, 23 May)
• Re: [whatwg/url] Specify window.webkitURL as an alias to URL (#312) (Monday, 22 May)
• Re: [whatwg/url] Let webkitURL be an alias of the URL constructor (#135) (Monday, 22 May)
• Re: [whatwg/url] Specify window.webkitURL as an alias to URL (#312) (Monday, 22 May)
• [whatwg/url] Specify window.webkitURL as an alias to URL (#312) (Monday, 22 May)
• Re: [whatwg/url] Let webkitURL be an alias of the URL constructor (#135) (Monday, 22 May)
• Re: [heycam/webidl] Add [LegacyWindowAlias] extended attribute for WebKitCSSMatrix et al (#364) (Thursday, 18 May)
• Re: [heycam/webidl] Add [LegacyWindowAlias] extended attribute for WebKitCSSMatrix et al (#364) (Thursday, 18 May)
• Re: [heycam/webidl] Add [LegacyWindowAlias] extended attribute for WebKitCSSMatrix et al (#364) (Thursday, 18 May)
• Re: [heycam/webidl] Add [LegacyWindowAlias] extended attribute for WebKitCSSMatrix et al (#364) (Thursday, 18 May)
• Re: [heycam/webidl] Add [LegacyWindowAlias] extended attribute for WebKitCSSMatrix et al (#364) (Wednesday, 17 May)
• Re: [heycam/webidl] Add [LegacyWindowAlias] extended attribute for WebKitCSSMatrix et al (#364) (Wednesday, 17 May)
• Re: [whatwg/url] Make URL's origin return solely ASCII code points (#311) (Wednesday, 17 May)
• Re: [whatwg/url] Make URL's origin return solely ASCII code points (#311) (Wednesday, 17 May)
• Re: [heycam/webidl] Add [LegacyWindowAlias] extended attribute for WebKitCSSMatrix et al (#364) (Wednesday, 17 May)
• Re: [heycam/webidl] Add [LegacyWindowAlias] extended attribute for WebKitCSSMatrix et al (#364) (Wednesday, 17 May)
• Re: [heycam/webidl] Add [LegacyWindowAlias] extended attribute for WebKitCSSMatrix et al (#364) (Wednesday, 17 May)
• Re: [heycam/webidl] How to do aliases of legacy interfaces (HTMLDocument, WebKitCSSMatrix...) (#362) (Tuesday, 16 May)
• Re: [heycam/webidl] How to do aliases of legacy interfaces (HTMLDocument, WebKitCSSMatrix...) (#362) (Tuesday, 16 May)
• Re: [heycam/webidl] How to do aliases of legacy interfaces (HTMLDocument, WebKitCSSMatrix...) (#362) (Tuesday, 16 May)
• Re: [heycam/webidl] How to do aliases of legacy interfaces (HTMLDocument, WebKitCSSMatrix...) (#362) (Tuesday, 16 May)
• [heycam/webidl] Add [LegacyWindowAlias] extended attribute for WebKitCSSMatrix et al (#364) (Tuesday, 16 May)
• Re: [heycam/webidl] How to do aliases of legacy interfaces (HTMLDocument, WebKitCSSMatrix...) (#362) (Tuesday, 16 May)
• Re: [heycam/webidl] How to do aliases of legacy interfaces (HTMLDocument, WebKitCSSMatrix...) (#362) (Tuesday, 16 May)
• Re: [heycam/webidl] How to do aliases of legacy interfaces (HTMLDocument, WebKitCSSMatrix...) (#362) (Tuesday, 16 May)
• Re: [heycam/webidl] How to do aliases of legacy interfaces (HTMLDocument, WebKitCSSMatrix...) (#362) (Tuesday, 16 May)
• Re: [heycam/webidl] How to do aliases of legacy interfaces (HTMLDocument, WebKitCSSMatrix...) (#362) (Tuesday, 16 May)
• Re: [heycam/webidl] How to do aliases of legacy interfaces (HTMLDocument, WebKitCSSMatrix...) (#362) (Friday, 12 May)
• Re: [heycam/webidl] How to do aliases of legacy interfaces (HTMLDocument, WebKitCSSMatrix...) (#362) (Friday, 12 May)
• Re: [heycam/webidl] How to do aliases of legacy interfaces (HTMLDocument, WebKitCSSMatrix...) (#362) (Friday, 12 May)
• [heycam/webidl] How to do aliases of legacy interfaces (HTMLDocument, WebKitCSSMatrix...) (#362) (Friday, 12 May)
• Re: [whatwg/url] javascript: URL parsing (#307) (Tuesday, 9 May)
• Re: [whatwg/url] javascript: URL parsing (#307) (Tuesday, 9 May)

Simon Sapin

• Re: [heycam/webidl] provide clearer advice about USVString vs. DOMString (#84) (Thursday, 11 May)
• Re: [heycam/webidl] provide clearer advice about USVString vs. DOMString (#84) (Thursday, 11 May)

sleevi

• Re: [whatwg/fetch] Add support for federated token binding to fetch (#30) (Saturday, 13 May)

smaug----

• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Tuesday, 9 May)
• Re: [whatwg/dom] To investigate: do error events bubble to window? (#455) (Thursday, 4 May)
• Re: [heycam/webidl] Only install @@toStringTag on the prototype (#357) (Wednesday, 3 May)
• Re: [w3c/uievents] Click event is not fired when the node is removed and then added back (#141) (Tuesday, 2 May)

spanicker

• [w3ctag/design-reviews] Request to review First Paint Timing (#177) (Thursday, 11 May)

Stef Busking

• [whatwg/dom] Clarify insert-node's record's previousSibling (#464) (Wednesday, 31 May)

Steve Orvell

• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Wednesday, 10 May)

stevefaulkner

• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Monday, 22 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Tuesday, 16 May)

Steven Vachon

• Re: [whatwg/url] Investigate aligning application/x-www-form-urlencoded with URL's query (#18) (Wednesday, 10 May)

Surma

• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Wednesday, 24 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Monday, 22 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Monday, 22 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Friday, 19 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Thursday, 18 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Thursday, 18 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Saturday, 13 May)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Wednesday, 10 May)

Sven-S. Porst

• Re: [whatwg/fetch] Block subresource requests whose URLs include credentials. (#465) (Sunday, 14 May)

Tab Atkins Jr.

• Re: [w3c/ServiceWorker] Extend attribute ref with link to external spec (#1144) (Tuesday, 30 May)
• Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Tuesday, 30 May)
• Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Friday, 26 May)
• Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Friday, 26 May)
• Re: [heycam/webidl] Figure-out what supporting Array-subclassing implies (#345) (Thursday, 18 May)
• Re: [heycam/webidl] Figure-out what supporting Array-subclassing implies (#345) (Saturday, 13 May)
• Re: [heycam/webidl] Figure-out what supporting Array-subclassing implies (#345) (Thursday, 11 May)
• Re: [heycam/webidl] Figure-out what supporting Array-subclassing implies (#345) (Thursday, 11 May)
• Re: [heycam/webidl] Figure-out what supporting Array-subclassing implies (#345) (Thursday, 11 May)
• Re: [heycam/webidl] Figure-out what supporting Array-subclassing implies (#345) (Tuesday, 9 May)
• [whatwg/fetch] .pr-preview file lists h1 as "URL", not "Fetch" (#539) (Tuesday, 9 May)
• Re: [whatwg/encoding] Editorial: ensure various bits link properly (#104) (Monday, 8 May)
• Re: [whatwg/encoding] Editorial: ensure various bits link properly (#104) (Monday, 8 May)

Takayoshi Kochi

• [whatwg/dom] Match querySelector for pseudo elements (::slotted()) (#463) (Wednesday, 31 May)

Takeshi Yoshino

• Re: [whatwg/fetch] Add flag to indicate delay-tolerant Request, to enable request coalescing. (#184) (Thursday, 25 May)
• Re: [whatwg/streams] ReadableStreamDefaultController seems redundant (#743) (Wednesday, 24 May)
• Re: [whatwg/streams] ReadableStreamDefaultController seems redundant (#743) (Wednesday, 24 May)
• Re: [whatwg/streams] ReadableStreamDefaultController seems redundant (#743) (Wednesday, 24 May)
• Re: [whatwg/streams] "At this point in time the division of work betw..." (#741) (Wednesday, 24 May)
• Re: [whatwg/streams] Reference to CopyDataBlockBytes (#746) (Wednesday, 24 May)
• Re: [whatwg/streams] Reference to CopyDataBlockBytes (#746) (Wednesday, 24 May)
• Re: [whatwg/streams] Fix arguments order in CopyDataBlockBytes (#747) (Wednesday, 24 May)
• Re: [whatwg/streams] Fix arguments order in CopyDataBlockBytes (#747) (Wednesday, 24 May)
• Re: [whatwg/streams] Fix arguments order in CopyDataBlockBytes (#747) (Wednesday, 24 May)
• Re: [whatwg/streams] pipeTo should return a cancelable promise (#446) (Monday, 22 May)
• Re: [whatwg/streams] Define generic operation for GetDesiredSize? (#745) (Monday, 22 May)
• Re: [whatwg/fetch] Request body streams that cannot be retried (#538) (Wednesday, 10 May)
• Re: [whatwg/streams] do chunk boundaries have to be preserved through to underlying sink? (#739) (Monday, 1 May)

TAMURA, Kent

• Re: [whatwg/dom] DOMTokenList.remove() can add an attribute (#462) (Wednesday, 24 May)
• [whatwg/dom] DOMTokenList.remove() can add an attribute (#462) (Monday, 22 May)

Tantek Çelik

• Re: [w3c/charter-html] Relation with WICG (#141) (Tuesday, 16 May)
• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Tuesday, 16 May)

Taylor Hunt

• Re: [whatwg/fetch] Prevent requests to HTTP(S) URLs containing raw `\n` and `<`. (#546) (Tuesday, 23 May)
• Re: [whatwg/fetch] Prevent requests to URLs containing raw `\n` and `<`. (#546) (Monday, 22 May)

Ted Drake

• [w3c/push-api] User preference for timing (#257) (Wednesday, 10 May)

Timothy Gu

• Re: [whatwg/url] Address several IDNA issues (#309) (Wednesday, 31 May)
• Re: [whatwg/url] Address several IDNA issues (#309) (Wednesday, 31 May)
• Re: [whatwg/url] Clearly indicate a known issue with ToASCII (#309) (Saturday, 20 May)
• Re: [whatwg/url] Perhaps do not apply ToASCII for ASCII-only input (#267) (Thursday, 18 May)
• Re: [whatwg/url] new URL('file://').origin is 'null' (#310) (Sunday, 14 May)
• Re: [whatwg/url] IDNA (#53) (Thursday, 11 May)
• Re: [whatwg/fetch] Is a missing HeadersInit treated differently from an empty one? (#479) (Monday, 8 May)
• [whatwg/url] remaining variable ambiguity (#308) (Thursday, 4 May)
• Re: [whatwg/url] Editorial: use Infra in a/x-www-form-urlencoded (#300) (Tuesday, 2 May)
• Re: [whatwg/url] Editorial: cleanup references (#299) (Tuesday, 2 May)

Tobie Langel

• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Friday, 19 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Thursday, 18 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Thursday, 18 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Thursday, 18 May)
• Re: [heycam/webidl] Add [LegacyWindowAlias] extended attribute for WebKitCSSMatrix et al (#364) (Thursday, 18 May)
• Re: [heycam/webidl] How to do aliases of legacy interfaces (HTMLDocument, WebKitCSSMatrix...) (#362) (Thursday, 18 May)
• Re: [heycam/webidl] Add [LegacyWindowAlias] extended attribute for WebKitCSSMatrix et al (#364) (Thursday, 18 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Thursday, 18 May)
• Re: [heycam/webidl] Add [LegacyWindowAlias] extended attribute for WebKitCSSMatrix et al (#364) (Thursday, 18 May)
• Re: [heycam/webidl] Add [LegacyWindowAlias] extended attribute for WebKitCSSMatrix et al (#364) (Thursday, 18 May)
• Re: [heycam/webidl] Add [LegacyWindowAlias] extended attribute for WebKitCSSMatrix et al (#364) (Thursday, 18 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Thursday, 18 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Wednesday, 17 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Wednesday, 17 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Wednesday, 17 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Wednesday, 17 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Wednesday, 17 May)
• Re: [heycam/webidl] Add [LegacyWindowAlias] extended attribute for WebKitCSSMatrix et al (#364) (Wednesday, 17 May)
• Re: [heycam/webidl] How to do aliases of legacy interfaces (HTMLDocument, WebKitCSSMatrix...) (#362) (Wednesday, 17 May)
• Re: [heycam/webidl] Investigate removing [PrimaryGlobal] and requiring [Exposed] (#365) (Wednesday, 17 May)
• Re: [heycam/webidl] Add [LegacyWindowAlias] extended attribute for WebKitCSSMatrix et al (#364) (Wednesday, 17 May)
• [heycam/webidl] Investigate removing [PrimaryGlobal] and requiring [Exposed] (#365) (Wednesday, 17 May)
• Re: [heycam/webidl] Add [LegacyWindowAlias] extended attribute for WebKitCSSMatrix et al (#364) (Tuesday, 16 May)
• Re: [heycam/webidl] Designing mixins (#363) (Tuesday, 16 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Tuesday, 16 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Tuesday, 16 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Tuesday, 16 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Tuesday, 16 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Tuesday, 16 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Tuesday, 16 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Monday, 15 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Monday, 15 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Monday, 15 May)
• Re: [heycam/webidl] The [SecureContext] text is unclear on exposure for interfaces (#119) (Monday, 15 May)
• Re: [heycam/webidl] The [SecureContext] text is unclear on exposure for interfaces (#119) (Monday, 15 May)
• Re: [heycam/webidl] The [SecureContext] text is unclear on exposure for interfaces (#119) (Monday, 15 May)
• Re: [heycam/webidl] The [SecureContext] text is unclear on exposure for interfaces (#119) (Monday, 15 May)
• Re: [heycam/webidl] Mark legacy content as deprecated. (#332) (Monday, 15 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Monday, 15 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Monday, 15 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Monday, 15 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Monday, 15 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Monday, 15 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Monday, 15 May)
• Re: [heycam/webidl] Should we x-link base concepts to the Infra Standard? (#242) (Friday, 12 May)
• Re: [heycam/webidl] Should we x-link base concepts to the Infra Standard? (#242) (Friday, 12 May)
• Re: [heycam/webidl] Add algorithm blocks around all algorithms (#185) (Friday, 12 May)
• Re: [heycam/webidl] Add algorithm blocks around all algorithms (#185) (Friday, 12 May)
• Re: [heycam/webidl] Consider flipping the [Unscopable] design (#361) (Friday, 12 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Thursday, 11 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Thursday, 11 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Thursday, 11 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Thursday, 11 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Thursday, 11 May)
• Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323) (Thursday, 11 May)
• Re: [heycam/webidl] Fix [TreatNullAs] usage in example (#360) (Wednesday, 10 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Tuesday, 9 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Tuesday, 9 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Thursday, 4 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Wednesday, 3 May)
• Re: [heycam/webidl] Remove custom [[HasInstance]] behavior from interface objects (#356) (Tuesday, 2 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Tuesday, 2 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Tuesday, 2 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Tuesday, 2 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Tuesday, 2 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Tuesday, 2 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Tuesday, 2 May)
• Re: [heycam/webidl] WIP: add localizable dictionary (#358) (Tuesday, 2 May)
• Re: [heycam/webidl] Add [AllowShared] to allow accepting SharedArrayBuffers (#353) (Tuesday, 2 May)
• Re: [heycam/webidl] "::" is used in comments but is not formally a part of webidl ? (#354) (Tuesday, 2 May)
• Re: [heycam/webidl] "::" is used in comments but is not formally a part of webidl ? (#354) (Tuesday, 2 May)
• Re: [heycam/webidl] "::" is used in comments but is not formally a part of webidl ? (#354) (Tuesday, 2 May)
• Re: [heycam/webidl] "::" is used in comments but is not formally a part of webidl ? (#354) (Tuesday, 2 May)
• Re: [heycam/webidl] Clarify and add examples for "extended attributes associated with" (#355) (Tuesday, 2 May)
• Re: [heycam/webidl] Remove custom [[HasInstance]] behavior from interface objects (#356) (Tuesday, 2 May)

Travis Leithead

• Re: [w3ctag/design-reviews] Cross-spec device identification & association (#64) (Wednesday, 31 May)
• Re: [w3ctag/design-reviews] Cross-spec device identification & association (#64) (Tuesday, 30 May)
• Re: [w3ctag/design-reviews] Cross-spec device identification & association (#64) (Monday, 22 May)
• Re: [w3ctag/design-reviews] WebRTC Stats review (#148) (Tuesday, 9 May)
• Re: [w3ctag/design-reviews] WebRTC Stats review (#148) (Tuesday, 9 May)
• Re: [w3ctag/design-reviews] WebRTC Stats review (#148) (Tuesday, 9 May)
• Re: [w3ctag/design-reviews] WebRTC Stats review (#148) (Tuesday, 9 May)
• Re: [w3ctag/design-reviews] WebRTC Stats review (#148) (Tuesday, 9 May)
• Re: [w3ctag/design-reviews] WebRTC Stats review (#148) (Tuesday, 9 May)
• Re: [w3ctag/design-reviews] WebRTC Stats review (#148) (Tuesday, 9 May)

Trey Shugart

• Re: [w3c/webcomponents] Agenda for W3C TPAC 2017 (Web Components) (#641) (Wednesday, 31 May)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Wednesday, 17 May)
• Re: [w3c/webcomponents] [Custom]: Need callback for form submit data (bugzilla: 24603) (#187) (Tuesday, 2 May)

tripu

• Re: [w3c/FileAPI] Export "Blob URL Store" definition (#77) (Monday, 8 May)
• Re: [w3c/FileAPI] Export "Blob URL Store" definition (#77) (Friday, 5 May)

vanupam

• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 13 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 13 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 13 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 13 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 13 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 13 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 13 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 13 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 13 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 13 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 13 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 13 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Saturday, 13 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Thursday, 11 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Thursday, 11 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Thursday, 11 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Thursday, 11 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Thursday, 11 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Thursday, 11 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Thursday, 11 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Friday, 5 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Friday, 5 May)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Friday, 5 May)

Viktor

• Re: [w3c/editing] INPUT/TEXTAREA should support subset of execCommand (#160) (Friday, 26 May)

Vincent Scheib

• Re: [whatwg/fullscreen] Fire events at elements by default, falling back to documents (#90) (Wednesday, 31 May)
• [w3c/pointerlock] Dispatch pointerlockchange and pointerlockerror events to target element, falling back to document. (#21) (Wednesday, 31 May)
• Re: [w3c/pointerlock] Ask for web-platform-tests in CONTRIBUTING.md (#20) (Tuesday, 16 May)
• Re: [w3c/pointerlock] Ask for web-platform-tests in CONTRIBUTING.md (#20) (Tuesday, 16 May)

vsuperator

• [w3c/manifest] beforeinstallprompt not fire (#579) (Tuesday, 16 May)

vyv03354

• Re: [whatwg/encoding] ISO-2022-JP encoder: convert halfwidth Katakana to fullwidth (#106) (Sunday, 7 May)
• Re: [whatwg/encoding] ISO-2022-JP encoder: convert halfwidth Katakana to fullwidth (#106) (Saturday, 6 May)
• Re: [whatwg/encoding] Half-width Katakana should be representable in ISO-2022-JP (#105) (Friday, 5 May)

Web Low-level Language

• Re: [w3ctag/design-reviews] WebAssembly Response API / Web Embedding (#167) (Tuesday, 23 May)
• Re: [w3ctag/design-reviews] WebAssembly Response API / Web Embedding (#167) (Thursday, 18 May)

Wendy Seltzer

• Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139) (Tuesday, 23 May)
• Re: [w3c/charter-html] Remove interaction domain logo (#138) (Friday, 12 May)
• [w3c/charter-html] Remove interaction domain logo (#138) (Friday, 12 May)

Xiaoqian Wu

• [w3c/uievents-key] Broken link to ANSI-CTA-2014-B (#43) (Tuesday, 30 May)
• Re: [w3c/IndexedDB] Horizontal review… (#112) (Monday, 22 May)

Xidorn Quan

• Re: [w3c/pointerlock] Dispatch pointerlockchange and pointerlockerror events to target element, falling back to document. (#21) (Wednesday, 31 May)
• Re: [whatwg/fullscreen] Fire events at elements by default, falling back to documents (#90) (Friday, 26 May)
• Re: [whatwg/fullscreen] Fire events at elements by default, falling back to documents (#90) (Wednesday, 24 May)
• Re: [whatwg/fullscreen] Reinstate the hierarchy restrictions (#91) (Wednesday, 24 May)
• Re: [whatwg/fullscreen] Reinstate the hierarchy restrictions (#91) (Tuesday, 23 May)
• Re: [whatwg/fullscreen] Reinstate the hierarchy restrictions (#91) (Tuesday, 23 May)
• Re: [whatwg/fullscreen] Reinstate the hierarchy restrictions (#91) (Tuesday, 23 May)
• Re: [whatwg/fullscreen] Fire events at elements by default, falling back to documents (#90) (Monday, 22 May)
• Re: [whatwg/fullscreen] `fullscreenchange` should behave like `webkitfullscreenchange` (#89) (Thursday, 18 May)
• Re: [whatwg/fullscreen] `fullscreenchange` should behave like `webkitfullscreenchange` (#89) (Thursday, 18 May)
• Re: [whatwg/fullscreen] document.fullscreenElement in scroll event after entering fullscreen matters for compat (#74) (Thursday, 18 May)
• Re: [whatwg/fullscreen] requestFullscreen() + moving pending element can fire fullscreenerror but leave browser in fullscreen (#88) (Tuesday, 16 May)
• Re: [whatwg/fullscreen] In requestFullscreen(), handle the pending element moving (#87) (Tuesday, 16 May)
• Re: [whatwg/fullscreen] In requestFullscreen(), handle the pending element moving (#87) (Tuesday, 16 May)
• Re: [whatwg/fullscreen] Require that the document is fully active in requestFullscreen() (#85) (Sunday, 14 May)
• Re: [whatwg/fullscreen] Clarify what "collect documents to unfullscreen" returns (#81) (Thursday, 11 May)
• Re: [whatwg/fullscreen] Deny request on invisible document (#60) (Tuesday, 2 May)

Yoav Weiss

• [whatwg/fetch] Make sure that potential destination is not the empty string (#549) (Friday, 26 May)
• Re: [whatwg/fetch] Add potential destination. (#547) (Wednesday, 24 May)
• Re: [whatwg/fetch] Add potential destination. (#547) (Wednesday, 24 May)
• Re: [whatwg/fetch] Add potential destination. (#547) (Tuesday, 23 May)
• Re: [whatwg/fetch] Add potential destination. (#547) (Tuesday, 23 May)
• Re: [whatwg/fetch] Add potential destination. (#547) (Tuesday, 23 May)
• Re: [whatwg/fetch] Add potential destination. (#547) (Tuesday, 23 May)
• Re: [whatwg/fetch] Add potential destination. (#547) (Tuesday, 23 May)
• Re: [whatwg/fetch] Add potential destination. (#547) (Tuesday, 23 May)
• Re: [whatwg/fetch] Add potential destination. (#547) (Tuesday, 23 May)
• Re: [whatwg/fetch] Add potential destination. (#547) (Tuesday, 23 May)
• Re: [whatwg/fetch] Add potential destination. (#547) (Tuesday, 23 May)
• Re: [whatwg/fetch] Add potential destination. (#547) (Tuesday, 23 May)
• Re: [whatwg/fetch] Add potential destination. (#547) (Tuesday, 23 May)
• Re: [whatwg/fetch] Add potential destination. (#547) (Tuesday, 23 May)
• Re: [whatwg/fetch] Add potential destination. (#547) (Tuesday, 23 May)
• Re: [whatwg/fetch] Add "fetch" as a destination for "connect-src" bound features (#442) (Tuesday, 23 May)
• Re: [whatwg/fetch] Add "fetch" as a destination for "connect-src" bound features (#442) (Tuesday, 23 May)
• Re: [whatwg/fetch] Add potential destination. (#547) (Tuesday, 23 May)
• Re: [whatwg/fetch] Add potential destination. (#547) (Tuesday, 23 May)
• Re: [whatwg/fetch] Add potential destination. (#547) (Tuesday, 23 May)
• [whatwg/fetch] Add potential destination. (#547) (Tuesday, 23 May)
• Re: [whatwg/fetch] Allow connection reuse for request without credentials when TLS client auth is not in use (#341) (Friday, 12 May)

youennf

• Re: [whatwg/fetch] should Response.blob() type include parameters like charset? (#540) (Friday, 19 May)

Yutaka Hirano

• Re: [whatwg/fetch] access-conrol-allow-origin: * can be interpreted in two ways (#548) (Wednesday, 24 May)
• [whatwg/fetch] access-conrol-allow-origin: * can be interpreted in two ways (#548) (Wednesday, 24 May)
• Re: [whatwg/fetch] Request body streams that cannot be retried (#538) (Monday, 8 May)
• Re: [whatwg/fetch] Queue "process request body" tasks during request body transmission (#532) (Tuesday, 2 May)
• Re: [whatwg/fetch] Queue "process request body" tasks during request body transmission (#532) (Tuesday, 2 May)
• Re: [whatwg/fetch] Queue "process request body" tasks during request body transmission (#532) (Tuesday, 2 May)
• Re: [whatwg/fetch] Queue "process request body" tasks during request body transmission (#532) (Tuesday, 2 May)
• Re: [whatwg/fetch] Queue "process request body" tasks during request body transmission (#532) (Monday, 1 May)
• Re: [whatwg/fetch] Queue "process request body" tasks during request body transmission (#532) (Monday, 1 May)
• Re: [whatwg/fetch] Queue "process request body" tasks during request body transmission (#532) (Monday, 1 May)

Yves Lafon

• Re: [w3c/ServiceWorker] adding IANA considerations section (#1154) (Monday, 29 May)
• Re: [w3c/ServiceWorker] Editorial: correct method control flow (#1152) (Saturday, 27 May)
• Re: [w3c/ServiceWorker] Editorial: Correct value references (#1150) (Saturday, 27 May)
• [w3c/charter-html] deliverable lists per Process 2017 (#143) (Tuesday, 23 May)
• Re: [w3c/ServiceWorker] Editorial: correct typos in <link> element example (#1149) (Monday, 22 May)
• Re: [w3c/ServiceWorker] Editorial: Correct grammar of informative note (#1145) (Friday, 19 May)
• Re: [w3c/ServiceWorker] Extend attribute ref with link to external spec (#1144) (Wednesday, 17 May)
• Re: [w3c/ServiceWorker] Remove unused flag (#1143) (Wednesday, 17 May)
• Re: [whatwg/fetch] "With Credentials" flag possibly inconsistent with web architecture (#517) (Monday, 15 May)
• Re: [whatwg/fetch] "With Credentials" flag possibly inconsistent with web architecture (#517) (Monday, 15 May)
• Re: [w3c/ServiceWorker] Editorial: Simplify `ready` (#1136) (Friday, 5 May)

Zach Koch

• Re: [w3ctag/design-reviews] Web payment method manifest (#162) (Tuesday, 23 May)

Zack Weinberg

• Re: [whatwg/fetch] Consider adding SMB to port blacklist (#544) (Sunday, 14 May)
• [whatwg/fetch] Consider adding SMB to port blacklist (#544) (Saturday, 13 May)

Zhang, Xiaofeng

• Re: [w3c/ServiceWorker] clarify Clients.matchAll() focus order for nested frames (#1080) (Wednesday, 24 May)

Šime Vidas

• Re: [whatwg/url] Should the legacy alias webkitURL be defined in the Compat Standard instead? (#314) (Wednesday, 31 May)
• Re: [whatwg/url] Should the legacy alias webkitURL be defined in the Compat Standard instead? (#314) (Wednesday, 31 May)
• [whatwg/url] Should the legacy alias webkitURL be defined in the Compat Standard instead? (#314) (Wednesday, 31 May)

Last message date: Wednesday, 31 May 2017 23:41:52 UTC