public-webapps-github@w3.org from March 2019 by author

Aaron

• Re: [whatwg/fetch] More CORB-protected MIME types - safelist-based approach (#721) (Wednesday, 6 March)

Aaron Gustafson

• Re: [w3c/manifest] App shortcuts / actions (#582) (Friday, 29 March)
• Re: [w3c/manifest] App shortcuts / actions (#582) (Tuesday, 26 March)
• Re: [w3c/manifest] App shortcuts / actions (#582) (Tuesday, 26 March)
• Re: [w3c/manifest] App shortcuts / actions (#582) (Tuesday, 26 March)
• Re: [w3c/manifest] Add a `color_scheme` member to `ImageResource` (#758) (Friday, 22 March)
• Re: [w3c/manifest] Add a `color_scheme` member to `ImageResource` (#758) (Friday, 22 March)
• Re: [w3c/manifest] Add a `color_scheme` member to `ImageResource` (#758) (Friday, 22 March)
• [w3c/manifest] Add a `color_scheme` member to `ImageResource` (#758) (Thursday, 21 March)
• Re: [w3c/manifest] App shortcuts / actions (#582) (Thursday, 21 March)
• Re: [w3c/manifest] App shortcuts / actions (#582) (Thursday, 21 March)
• Re: [w3c/manifest] Add optional `translations` member (#676) (Wednesday, 6 March)
• Re: [w3c/manifest] Add optional `translations` member (#676) (Wednesday, 6 March)

Abdón Rodríguez Davila

• Re: [w3c/webcomponents] Spring 2019 F2F Agenda (#802) (Thursday, 14 March)

Ackermann Yuriy

• Re: [heycam/webidl] Conversion from specification values to IDL values to ECMAScript values (#674) (Saturday, 2 March)

Adam Rice

• Re: [whatwg/streams] Constructor specification is unclear (#965) (Tuesday, 12 March)
• Re: [whatwg/streams] Remove extra arguments left over from forAuthorCode refactor (#998) (Monday, 11 March)
• Re: [whatwg/streams] Remove extra arguments left over from forAuthorCode refactor (#998) (Monday, 11 March)
• Re: [whatwg/streams] Treat forAuthorCode as an internal slot of reader object (#984) (Friday, 1 March)

akhtarzero

• [whatwg/dom] Brovo (#740) (Wednesday, 20 March)

alancutter

• Re: [w3c/manifest] What theme color should be used when a PWA window is out of scope? (#755) (Monday, 4 March)
• [w3c/manifest] What theme color should be used when a PWA window is out of scope? (#755) (Monday, 4 March)

Alex Russell

• Re: [w3ctag/design-reviews] Pointerevent extension (#346) (Thursday, 14 March)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Tuesday, 12 March)

aliams

• Re: [w3c/IndexedDB] cursor.request (#255) (Wednesday, 6 March)

Alice

• Re: [w3ctag/design-reviews] Alternative Text for CSS Generated Content (#351) (Saturday, 30 March)
• Re: [w3ctag/design-reviews] Alternative Text for CSS Generated Content (#351) (Friday, 29 March)
• Re: [w3ctag/design-reviews] Alternative Text for CSS Generated Content (#351) (Thursday, 28 March)
• Re: [w3ctag/design-reviews] Alternative Text for CSS Generated Content (#351) (Thursday, 28 March)
• Re: [w3ctag/design-reviews] User Activation Delegation through postMessages (#347) (Tuesday, 26 March)
• Re: [w3ctag/design-reviews] JavaScript WeakRefs (#321) (Tuesday, 12 March)
• Re: [w3ctag/design-reviews] JavaScript WeakRefs (#321) (Tuesday, 12 March)

Andrea Giammarchi

• Re: [w3c/webcomponents] [templates] Ensure that template instantiation actually improves the platform (#704) (Monday, 25 March)
• Re: [w3c/webcomponents] [templates] Ensure that template instantiation actually improves the platform (#704) (Sunday, 24 March)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Tuesday, 19 March)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Tuesday, 12 March)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Tuesday, 12 March)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Monday, 11 March)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Monday, 11 March)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Sunday, 10 March)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed onse inserted (#736) (Thursday, 7 March)
• [whatwg/dom] Proposal: Node.DOCUMENT_LIVE_FRAGMENT_NODE (#736) (Thursday, 7 March)

Andreas

• Re: [w3c/webcomponents] Element Behaviors, and the has="" attribute. A useful alternative to Custom Elements in many cases! (#727) (Sunday, 10 March)
• Re: [w3c/webcomponents] appreciate your feedback for custom element diagram (#784) (Sunday, 3 March)
• Re: [w3c/webcomponents] appreciate your feedback for custom element diagram (#784) (Sunday, 3 March)

Andrew Sutherland

• Re: [w3c/ServiceWorker] provide a way to execute work after browser has consumed a response (#1397) (Friday, 29 March)
• Re: [w3c/ServiceWorker] provide a way to execute work after browser has consumed a response (#1397) (Friday, 29 March)
• Re: [w3c/IndexedDB] cursor.request (#255) (Tuesday, 19 March)
• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Friday, 15 March)
• Re: [w3c/IndexedDB] cursor.request (#255) (Wednesday, 6 March)

Andrey Lushnikov

• Re: [GoogleChrome/puppeteer] Query nodes within shadow roots (#858) (Friday, 15 March)

Anne van Kesteren

• Re: [w3ctag/design-reviews] TAG review of whether element.pseudo(":unknown") should return null or throw (#348) (Sunday, 31 March)
• Re: [whatwg/fetch] CORB should not block application/dash+xml videos (#886) (Saturday, 30 March)
• Re: [whatwg/fetch] Request with GET/HEAD method cannot have body. (#551) (Friday, 29 March)
• Re: [whatwg/fetch] Request with GET/HEAD method cannot have body. (#551) (Friday, 29 March)
• Re: [whatwg/fetch] Request with GET/HEAD method cannot have body. (#551) (Friday, 29 March)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Friday, 29 March)
• Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) (Thursday, 28 March)
• Re: [w3c/webcomponents] Shadow tree encapsulation and CSS (#804) (Thursday, 28 March)
• [w3c/webcomponents] Shadow tree encapsulation and CSS (#804) (Thursday, 28 March)
• Re: [w3ctag/design-reviews] Alternative Text for CSS Generated Content (#351) (Thursday, 28 March)
• Re: [w3ctag/design-reviews] User Activation Delegation through postMessages (#347) (Thursday, 28 March)
• Re: [w3ctag/design-reviews] Alternative Text for CSS Generated Content (#351) (Thursday, 28 March)
• Re: [whatwg/url] Define domain label (#435) (Thursday, 28 March)
• Re: [whatwg/dom] Composed and non bubbling event semantic dispatched in shadow tree (#742) (Wednesday, 27 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Wednesday, 27 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Wednesday, 27 March)
• [whatwg/url] Define domain label (#435) (Wednesday, 27 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Wednesday, 27 March)
• Re: [whatwg/fetch] CORS: arbitrary blocking of accept header based on length (#862) (Wednesday, 27 March)
• Re: [whatwg/dom] Composed and non bubbling event semantic dispatched in shadow tree (#742) (Wednesday, 27 March)
• Re: [whatwg/dom] Composed and non bubbling event semantic dispatched in shadow tree (#742) (Tuesday, 26 March)
• Re: [w3ctag/design-reviews] Pointerevent extension (#346) (Tuesday, 26 March)
• Re: [w3ctag/design-reviews] Pointerevent extension (#346) (Tuesday, 26 March)
• Re: [w3ctag/design-reviews] Pointerevent extension (#346) (Tuesday, 26 March)
• Re: [whatwg/dom] Create an abstraction for Element's textContent getter (#743) (Tuesday, 26 March)
• Re: [whatwg/dom] Create an abstraction for Element's textContent getter (#743) (Tuesday, 26 March)
• Re: [whatwg/dom] Create an abstraction for Element's textContent getter (#743) (Tuesday, 26 March)
• [whatwg/dom] Create an abstraction for Element's textContent getter (#743) (Tuesday, 26 March)
• Re: [whatwg/dom] Composed and non bubbling event semantic dispatched in shadow tree (#742) (Tuesday, 26 March)
• Re: [w3ctag/design-reviews] Pointerevent extension (#346) (Tuesday, 26 March)
• Re: [whatwg/fetch] Consider supporting Fetch Metadata. (#885) (Tuesday, 26 March)
• [whatwg/xhr] Do not fire upload progress events if the upload complete flag is set (#242) (Monday, 25 March)
• Re: [whatwg/fetch] Consider supporting Fetch Metadata. (#885) (Monday, 25 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Monday, 25 March)
• Re: [whatwg/xhr] surviv.io hacks need a new update (#241) (Monday, 25 March)
• Re: [heycam/webidl] [wip] First pass at adding internal slots (#495) (Monday, 25 March)
• Re: [whatwg/xhr] Clean up remaining MIME type usage (#175) (Sunday, 24 March)
• Re: [whatwg/xhr] Clean up remaining MIME type usage (#175) (Sunday, 24 March)
• Re: [whatwg/xhr] Blob name (#232) (Sunday, 24 March)
• Re: [whatwg/xhr] Remove substep usage (#228) (Sunday, 24 March)
• Re: [whatwg/xhr] Extract a MIME type no longer returns bytes (#227) (Sunday, 24 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Sunday, 24 March)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Sunday, 24 March)
• Re: [whatwg/fetch] Add three new client hint headers to the fetch spec: rtt, downlink, ect (#720) (Saturday, 23 March)
• Re: [whatwg/fetch] Add three new client hint headers to the fetch spec: rtt, downlink, ect (#720) (Saturday, 23 March)
• Re: [whatwg/fetch] Should the safelisted request header list still include `Downlink`? (#684) (Saturday, 23 March)
• Re: [whatwg/fetch] Should the safelisted request header list still include `Downlink`? (#684) (Saturday, 23 March)
• Re: [whatwg/fetch] Does Client Hints have multi vendor support? (#867) (Saturday, 23 March)
• Re: [whatwg/fetch] Remove Client Hints (#884) (Saturday, 23 March)
• Re: [whatwg/fetch] Remove Client Hints (#884) (Saturday, 23 March)
• [whatwg/fetch] Remove Client Hints (#884) (Saturday, 23 March)
• Re: [w3ctag/design-reviews] Pointerevent extension (#346) (Friday, 22 March)
• Re: [w3c/DOM-Parsing] Error thrown when resetting the default namespace to null on a prefixed element (#48) (Friday, 22 March)
• Re: [w3c/DOM-Parsing] Error thrown when resetting the default namespace to null on a prefixed element (#48) (Friday, 22 March)
• Re: [whatwg/dom] Dispatching slotchange within a compound microtask (#734) (Friday, 22 March)
• [whatwg/dom] Remove compound microtasks (#741) (Friday, 22 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Friday, 22 March)
• Re: [w3ctag/design-reviews] Pointerevent extension (#346) (Friday, 22 March)
• Re: [w3c/FileAPI] Add simpler reading methods to Blob interface. (#117) (Friday, 22 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Thursday, 21 March)
• Re: [whatwg/fetch] Safelist request headers starting with `Sec-` (#880) (Thursday, 21 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Thursday, 21 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Thursday, 21 March)
• Re: [whatwg/fetch] Add a speculative flag to `Request` as well as related processing (#881) (Thursday, 21 March)
• Re: [whatwg/fetch] Add a speculative flag to `Request` as well as related processing (#881) (Thursday, 21 March)
• Re: [whatwg/fetch] Handling of invalid Location header characters doesn't match browsers (#883) (Thursday, 21 March)
• Re: [whatwg/fetch] Handling of invalid Location header characters doesn't match browsers (#883) (Thursday, 21 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Thursday, 21 March)
• Re: [whatwg/fetch] Safelist request headers starting with `Sec-` (#880) (Thursday, 21 March)
• Re: [whatwg/fetch] Add a speculative flag to `Request` as well as related processing (#881) (Thursday, 21 March)
• Re: [whatwg/fetch] Add a speculative flag to `Request` as well as related processing (#881) (Thursday, 21 March)
• Re: [whatwg/fetch] Add a speculative flag to `Request` as well as related processing (#881) (Thursday, 21 March)
• Re: [whatwg/fetch] Handling of invalid Location header characters doesn't match browsers (#883) (Wednesday, 20 March)
• Re: [whatwg/fetch] Handling of invalid Location header characters doesn't match browsers (#883) (Wednesday, 20 March)
• Re: [whatwg/fetch] Handling of invalid Location header characters doesn't match browsers (#883) (Wednesday, 20 March)
• Re: [whatwg/fetch] Clarify the way CORB should be applied to beacons (#882) (Wednesday, 20 March)
• Re: [whatwg/dom] Brovo (#740) (Wednesday, 20 March)
• Re: [whatwg/dom] Wrong return type of Node::getRootNode() (#739) (Wednesday, 20 March)
• Re: [heycam/webidl] Arguments allow double extended attributes (#691) (Wednesday, 20 March)
• Re: [whatwg/fetch] Clarify the way CORB should be applied to beacons (#882) (Tuesday, 19 March)
• Re: [whatwg/fetch] Clarify the way CORB should be applied to beacons (#882) (Tuesday, 19 March)
• [heycam/webidl] Dealing with argument types for callback functions (#692) (Tuesday, 19 March)
• Re: [whatwg/fetch] Clarify the way CORB should be applied to beacons (#882) (Tuesday, 19 March)
• Re: [whatwg/fetch] Clarify the way CORB should be applied to beacons (#882) (Tuesday, 19 March)
• Re: [whatwg/dom] Dispatching slotchange within a compound microtask (#734) (Tuesday, 19 March)
• Re: [whatwg/dom] Dispatching slotchange within a compound microtask (#734) (Tuesday, 19 March)
• Re: [whatwg/fetch] Safelist request headers starting with `Sec-` (#880) (Tuesday, 19 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Tuesday, 19 March)
• Re: [heycam/webidl] Arguments allow double extended attributes (#691) (Tuesday, 19 March)
• Re: [heycam/webidl] Remove support for overloading callbacks (#690) (Tuesday, 19 March)
• Re: [w3ctag/design-reviews] TAG review: Async Clipboard - image/delayed content (#350) (Tuesday, 19 March)
• Re: [w3c/webcomponents] HTML module should require a new top level element (#752) (Tuesday, 19 March)
• Re: [w3c/ServiceWorker] Is respondWith(fetch(event.request)) always the same as not calling respondWith()? (#1395) (Tuesday, 19 March)
• Re: [whatwg/dom] Reference to struct in inner invoke (#738) (Tuesday, 19 March)
• Re: [w3c/FileAPI] Allow MediaSource, disallow any more extensions (#103) (Monday, 18 March)
• Re: [whatwg/fetch] Safelist request headers starting with `Sec-` (#880) (Monday, 18 March)
• Re: [whatwg/fetch] Safelist request headers starting with `Sec-` (#880) (Monday, 18 March)
• Re: [whatwg/fetch] Safelist request headers starting with `Sec-` (#880) (Monday, 18 March)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Monday, 18 March)
• Re: [whatwg/fetch] Safelist request headers starting with `Sec-` (#880) (Monday, 18 March)
• Re: [whatwg/fetch] Safelist request headers starting with `Sec-` (#880) (Monday, 18 March)
• Re: [heycam/webidl] Make the grammar check more robust. (#688) (Monday, 18 March)
• Re: [heycam/webidl] Make the grammar check more robust. (#688) (Monday, 18 March)
• Re: [w3c/webcomponents] Spring 2019 F2F Agenda (#802) (Monday, 18 March)
• Re: [w3c/webcomponents] HTML module should require a new top level element (#752) (Monday, 18 March)
• Re: [w3c/webcomponents] Spring 2019 F2F Agenda (#802) (Monday, 18 March)
• Re: [w3c/webcomponents] Provide an option which allows global CSSes to style elements inside a shadow tree (#769) (Saturday, 16 March)
• Re: [w3c/webcomponents] Provide an option which allows global CSSes to style elements inside a shadow tree (#769) (Saturday, 16 March)
• Re: [w3c/webcomponents] How to introduce global "css", such as "iconfont" font library (#757) (Saturday, 16 March)
• Re: [w3c/webcomponents] Cleaning up (undefining) custom elements? (#754) (Saturday, 16 March)
• Re: [w3c/webcomponents] Cleaning up (undefining) custom elements? (#754) (Saturday, 16 March)
• Re: [w3c/webcomponents] changing slot text node is overly verbose (#753) (Saturday, 16 March)
• Re: [w3c/webcomponents] changing slot text node is overly verbose (#753) (Saturday, 16 March)
• Re: [w3c/webcomponents] HTML module should require a new top level element (#752) (Saturday, 16 March)
• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Saturday, 16 March)
• Re: [w3c/FileAPI] Add simpler reading methods to Blob interface. (#117) (Saturday, 16 March)
• [w3c/FileAPI] Use [NewObject] for Blob's slice() and FileReaderSync (#121) (Saturday, 16 March)
• Re: [w3c/FileAPI] Add simpler reading methods to Blob interface. (#117) (Saturday, 16 March)
• Re: [whatwg/dom] Use a queue of deferred steps in the node insertion algorithm (#732) (Friday, 15 March)
• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Friday, 15 March)
• Re: [w3c/DOM-Parsing] XML null namespaces need to be preserved (#47) (Friday, 15 March)
• Re: [heycam/webidl] Is [AllowShared] an applicable-to-types attribute? (#687) (Friday, 15 March)
• Re: [heycam/webidl] Is [AllowShared] an applicable-to-types attribute? (#687) (Friday, 15 March)
• Re: [w3c/FileAPI] Rewrite FileReader definitions. (#118) (Thursday, 14 March)
• [w3c/FileAPI] Consider dispatching loadstart "synchronously" (similar to XMLHttpRequest) (#119) (Thursday, 14 March)
• Re: [w3c/FileAPI] Rewrite FileReader definitions. (#118) (Thursday, 14 March)
• Re: [heycam/webidl] Editorial: run platform algorithms on IDL objects (#666) (Thursday, 14 March)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Thursday, 14 March)
• Re: [w3ctag/design-reviews] Subresource prefetching+loading via Signed HTTP Exchange (#352) (Thursday, 14 March)
• Re: [w3ctag/design-reviews] TAG review: Async Clipboard - image/delayed content (#350) (Thursday, 14 March)
• [w3c/clipboard-apis] write() method assumes its passed Blob objects (#88) (Thursday, 14 March)
• [w3c/clipboard-apis] write() method incorrect (#87) (Thursday, 14 March)
• Re: [whatwg/fetch] Allow modifying the default referrer policy applied to certain fetches depending on engine-specific rules (#879) (Thursday, 14 March)
• Re: [w3c/webcomponents] Spring 2019 F2F Agenda (#802) (Thursday, 14 March)
• Re: [w3c/FileAPI] Rewrite FileReader definitions. (#118) (Thursday, 14 March)
• Re: [w3c/webcomponents] Spring 2019 F2F Agenda (#802) (Thursday, 14 March)
• Re: [whatwg/fetch] Tests do not always require Origin header when mode is "cors" (#871) (Wednesday, 13 March)
• Re: [w3c/FileAPI] Add simpler reading methods to Blob interface. (#117) (Wednesday, 13 March)
• Re: [w3c/FileAPI] Add simpler reading methods to Blob interface. (#117) (Wednesday, 13 March)
• Re: [w3c/FileAPI] Rewrite FileReader definitions. (#118) (Wednesday, 13 March)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Tuesday, 12 March)
• Re: [w3c/DOM-Parsing] XML null namespaces need to be preserved (#47) (Tuesday, 12 March)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Tuesday, 12 March)
• Re: [w3c/IndexedDB] Incoming link from HTML broken (#256) (Tuesday, 12 March)
• Re: [w3c/DOM-Parsing] XML null namespaces need to be preserved (#47) (Tuesday, 12 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Monday, 11 March)
• Re: [w3ctag/design-reviews] TAG review: Async Clipboard - image/delayed content (#350) (Monday, 11 March)
• Re: [w3c/FileAPI] Add simpler reading methods to Blob interface. (#117) (Monday, 11 March)
• Re: [w3c/FileAPI] Add simpler reading methods to Blob interface. (#117) (Monday, 11 March)
• Re: [heycam/webidl] "platform object" for ECMAScript vs. IDL values (#680) (Monday, 11 March)
• Re: [heycam/webidl] Unclear [Constructor] does the right thing for subclassing (#533) (Monday, 11 March)
• Re: [heycam/webidl] Unclear [Constructor] does the right thing for subclassing (#533) (Monday, 11 March)
• Re: [heycam/webidl] Disallow constants to be null (#686) (Monday, 11 March)
• [w3c/IndexedDB] Incoming link from HTML broken (#256) (Saturday, 9 March)
• Re: [whatwg/dom] isEqualNode and <template> (#737) (Friday, 8 March)
• Re: [whatwg/url] Snap be (#433) (Thursday, 7 March)
• Re: [heycam/webidl] Correct the 'indexed getter' cross-reference (#679) (Thursday, 7 March)
• Re: [whatwg/fetch] Image Accept: headers in the spec prevent conneg (#877) (Thursday, 7 March)
• Re: [whatwg/fetch] Generic Accept header value */* and Service Workers (#634) (Thursday, 7 March)
• Re: [whatwg/fetch] Generic Accept header value */* and Service Workers (#634) (Thursday, 7 March)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Thursday, 7 March)
• Re: [w3c/ServiceWorker] Add API for postMessage with PostMessageOptions (#1344) (Thursday, 7 March)
• Re: [w3c/FileAPI] Add simpler reading methods to Blob interface. (#117) (Thursday, 7 March)
• Re: [w3c/webcomponents] Add list of major open design questions to HTML Modules proposal doc (#801) (Thursday, 7 March)
• Re: [whatwg/fetch] More CORB-protected MIME types - safelist-based approach (#721) (Thursday, 7 March)
• Re: [whatwg/xhr] O- (#240) (Thursday, 7 March)
• Re: [whatwg/fetch] More CORB-protected MIME types - safelist-based approach (#721) (Wednesday, 6 March)
• Re: [heycam/webidl] Conversion from specification values to IDL values to ECMAScript values (#674) (Wednesday, 6 March)
• Re: [heycam/webidl] Conversion from specification values to IDL values to ECMAScript values (#674) (Wednesday, 6 March)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Wednesday, 6 March)
• Re: [whatwg/fetch] More CORB-protected MIME types - safelist-based approach (#721) (Tuesday, 5 March)
• Re: [whatwg/fetch] More CORB-protected MIME types - safelist-based approach (#721) (Tuesday, 5 March)
• Re: [whatwg/fetch] More CORB-protected MIME types - safelist-based approach (#721) (Tuesday, 5 March)
• Re: [w3c/webcomponents] Question: where to incubate HTML modules? (#794) (Tuesday, 5 March)
• Re: [whatwg/fetch] Should `Content-Disposition: attachment` implicitly opt into CORB and/or CORP? (#875) (Monday, 4 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Monday, 4 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Monday, 4 March)
• Re: [heycam/webidl] Enumeration order of interface members (#432) (Monday, 4 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Monday, 4 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Monday, 4 March)
• [heycam/webidl] Everything is a module (#676) (Monday, 4 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Monday, 4 March)
• Re: [w3c/webcomponents] JSON "modules" (#770) (Monday, 4 March)
• Re: [whatwg/dom] Capturing event listeners are called during bubbling phase for shadow hosts (#685) (Friday, 1 March)
• Re: [heycam/webidl] Editorial: fix some bikeshed link warnings (#672) (Friday, 1 March)
• Re: [heycam/webidl] Editorial: improve language around conversions to JS (#664) (Friday, 1 March)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Friday, 1 March)
• Re: [heycam/webidl] Editorial: improve language around conversions to JS (#664) (Friday, 1 March)
• [heycam/webidl] Conversion from specification values to IDL values to ECMAScript values (#674) (Friday, 1 March)
• Re: [heycam/webidl] Is a subclass still a platform object? (#540) (Friday, 1 March)
• Re: [heycam/webidl] Is a subclass still a platform object? (#540) (Friday, 1 March)
• Re: [heycam/webidl] Editorial: fix some bikeshed link warnings (#672) (Friday, 1 March)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Friday, 1 March)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Friday, 1 March)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Friday, 1 March)
• Re: [heycam/webidl] Deduplicate unforgeable member functions (#668) (Friday, 1 March)
• Re: [whatwg/dom] Capturing event listeners are called during bubbling phase for shadow hosts (#685) (Friday, 1 March)
• Re: [whatwg/dom] Fix event path iteration (#686) (Friday, 1 March)
• Re: [whatwg/dom] Capturing event listeners are called during bubbling phase for shadow hosts (#685) (Friday, 1 March)
• Re: [whatwg/dom] Fix event path iteration (#686) (Friday, 1 March)
• Re: [whatwg/fetch] More CORB-protected MIME types - safelist-based approach (#721) (Friday, 1 March)
• Re: [whatwg/xhr] madness (#239) (Friday, 1 March)
• Re: [whatwg/url] Consider adding support for fragment parameters (#389) (Friday, 1 March)

Anssi Kostiainen

• Re: [w3c/screen-orientation] Reliability of angle (#162) (Tuesday, 12 March)
• Re: [w3ctag/design-reviews] User Idle Detection (#336) (Monday, 11 March)

Arthur Stolyar

• Re: [w3c/ServiceWorker] Add cookie accessor/setter methods? (#707) (Saturday, 16 March)

arturjanc

• Re: [whatwg/fetch] Should `Content-Disposition: attachment` implicitly opt into CORB and/or CORP? (#875) (Sunday, 24 March)

Axel D.

• Re: [whatwg/dom] Wrong return type of Node::getRootNode() (#739) (Wednesday, 20 March)
• Re: [whatwg/dom] Wrong return type of Node::getRootNode() (#739) (Wednesday, 20 March)
• Re: [whatwg/dom] Wrong return type of Node::getRootNode() (#739) (Wednesday, 20 March)
• [whatwg/dom] Wrong return type of Node::getRootNode() (#739) (Wednesday, 20 March)
• Re: [w3c/selection-api] Add Selection/Range methods based on anchestor element (#102) (Tuesday, 5 March)
• Re: [w3c/selection-api] Add Selection/Range methods based on anchestor element (#102) (Tuesday, 5 March)
• Re: [w3c/selection-api] Add Selection/Range methods based on anchestor element (#102) (Monday, 4 March)
• Re: [w3c/selection-api] Add Selection/Range methods based on anchestor element (#102) (Monday, 4 March)
• Re: [w3c/selection-api] Add Selection/Range methods based on anchestor element (#102) (Friday, 1 March)
• Re: [w3c/selection-api] Add Selection/Range methods based on anchestor element (#102) (Friday, 1 March)

Becca Hughes

• [w3ctag/design-reviews] Autoplay Detection API (#356) (Monday, 25 March)

beidson

• Re: [w3c/IndexedDB] cursor.request (#255) (Wednesday, 6 March)

Ben Kelly

• Re: [w3c/ServiceWorker] provide a way to execute work after browser has consumed a response (#1397) (Friday, 29 March)
• Re: [w3c/ServiceWorker] provide a way to execute work after browser has consumed a response (#1397) (Friday, 29 March)
• [w3c/ServiceWorker] provide a way to execute work after browser has consumed a response (#1397) (Thursday, 28 March)
• [w3c/ServiceWorker] spec should document Cache API HEIST mitigations (#1396) (Tuesday, 26 March)
• Re: [w3c/ServiceWorker] Add cookie accessor/setter methods? (#707) (Sunday, 17 March)
• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Friday, 15 March)
• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Friday, 15 March)
• Re: [w3c/ServiceWorker] Can respondWith() be called from a microtask? (#1394) (Thursday, 14 March)
• Re: [w3c/ServiceWorker] Can respondWith() be called from a microtask? (#1394) (Thursday, 14 March)
• Re: [whatwg/fetch] Generic Accept header value */* and Service Workers (#634) (Thursday, 7 March)

BigBlueHat

• Re: [w3ctag/design-reviews] Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312) (Friday, 1 March)

Boris Zbarsky

• Re: [heycam/webidl] Update the requirement about the definition of a constructor (#697) (Tuesday, 26 March)
• Re: [heycam/webidl] Update the requirement about the definition of a constructor (#697) (Tuesday, 26 March)
• Re: [heycam/webidl] Define that interface objects are constructors (#698) (Tuesday, 26 March)
• Re: [heycam/webidl] Define that interface objects are constructors (#698) (Tuesday, 26 March)
• Re: [heycam/webidl] Define that interface objects are constructors (#698) (Tuesday, 26 March)
• Re: [heycam/webidl] Define that interface objects are constructors (#698) (Tuesday, 26 March)
• Re: [heycam/webidl] Define that interface objects are constructors (#698) (Tuesday, 26 March)
• Re: [heycam/webidl] Define that interface objects are constructors (#698) (Tuesday, 26 March)
• Re: [heycam/webidl] Absence of "record" token from Other production (#694) (Friday, 22 March)
• Re: [heycam/webidl] Arguments allow double extended attributes (#691) (Wednesday, 20 March)
• Re: [heycam/webidl] Arguments allow double extended attributes (#691) (Wednesday, 20 March)
• Re: [heycam/webidl] Arguments allow double extended attributes (#691) (Tuesday, 19 March)
• Re: [heycam/webidl] Arguments allow double extended attributes (#691) (Tuesday, 19 March)
• Re: [heycam/webidl] Remove support for overloading callbacks (#690) (Tuesday, 19 March)
• Re: [heycam/webidl] Remove support for overloading callbacks (#690) (Tuesday, 19 March)
• Re: [heycam/webidl] Remove support for overloading callbacks (#690) (Tuesday, 19 March)
• Re: [heycam/webidl] Remove support for overloading callbacks (#690) (Tuesday, 19 March)
• Re: [heycam/webidl] [Exposed] check for overloaded operations makes no sense (#689) (Monday, 18 March)
• Re: [heycam/webidl] [Exposed] check for overloaded operations makes no sense (#689) (Monday, 18 March)
• Re: [heycam/webidl] Disallow constants to be null (#686) (Friday, 15 March)
• Re: [heycam/webidl] "platform object" for ECMAScript vs. IDL values (#680) (Monday, 11 March)
• Re: [heycam/webidl] "platform object" for ECMAScript vs. IDL values (#680) (Thursday, 7 March)
• Re: [heycam/webidl] Conversion from specification values to IDL values to ECMAScript values (#674) (Wednesday, 6 March)
• Re: [heycam/webidl] Conversion from specification values to IDL values to ECMAScript values (#674) (Tuesday, 5 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Monday, 4 March)
• Re: [heycam/webidl] Enumeration order of interface members (#432) (Monday, 4 March)
• Re: [heycam/webidl] Deduplicate unforgeable member functions (#668) (Friday, 1 March)
• Re: [heycam/webidl] [[DefineOwnProperty]] for legacy objects should not force configurability (#669) (Friday, 1 March)
• Re: [heycam/webidl] Deduplicate unforgeable member functions (#668) (Friday, 1 March)

Brett Zamir

• [w3c/IndexedDB] Sp. (#259) (Thursday, 21 March)
• [w3c/IndexedDB] `abort()` to set transaction state to inactive (#258) (Thursday, 21 March)
• Re: [w3c/IndexedDB] Add IDBTransaction commit() method (#242) (Thursday, 21 March)

Brian Kardell

• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Saturday, 23 March)
• Re: [w3c/webcomponents] CSS encapsulation and common CSS rules (#800) (Friday, 1 March)

Bruce B. Anderson

• Re: [w3c/webcomponents] [templates] Ensure that template instantiation actually improves the platform (#704) (Sunday, 24 March)
• Re: [w3c/webcomponents] [templates] Ensure that template instantiation actually improves the platform (#704) (Thursday, 21 March)
• Re: [w3c/webcomponents] [templates] Ensure that template instantiation actually improves the platform (#704) (Thursday, 21 March)

Cameron McCormack

• Re: [heycam/webidl] Editorial: marking former editors as such (#685) (Sunday, 10 March)
• Re: [heycam/webidl] Editorial: marking former editors as such (#685) (Sunday, 10 March)

Caridy Patiño

• Re: [whatwg/dom] Composed and non bubbling event semantic dispatched in shadow tree (#742) (Wednesday, 27 March)
• Re: [whatwg/dom] Composed and non bubbling event semantic dispatched in shadow tree (#742) (Tuesday, 26 March)
• Re: [w3c/webcomponents] Spring 2019 F2F Agenda (#802) (Thursday, 14 March)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Saturday, 2 March)

Chris Rollins

• Re: [whatwg/fetch] Request with GET/HEAD method cannot have body. (#551) (Friday, 29 March)

Christopher Robert Van Wiemeersch

• Re: [w3c/gamepad] id field in gamepad might have a persistent identifier? (#73) (Tuesday, 5 March)

cynthia

• Re: [w3ctag/design-reviews] Web of Things (WoT) Thing Description (#357) (Tuesday, 26 March)
• Re: [w3ctag/design-reviews] Audiobooks (#345) (Tuesday, 26 March)

Dan Clark

• [w3c/webcomponents] Fix HTML Modules demo links (#803) (Tuesday, 26 March)
• [w3c/webcomponents] Add list of major open design questions to HTML Modules proposal doc (#801) (Wednesday, 6 March)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Friday, 1 March)

Daniel Appelquist

• Re: [w3ctag/design-reviews] Priority Hints API (#241) (Tuesday, 26 March)
• Re: [w3ctag/design-reviews] Priority Hints API (#241) (Tuesday, 26 March)
• Re: [w3ctag/design-reviews] User Activation Delegation through postMessages (#347) (Tuesday, 26 March)
• Re: [w3ctag/design-reviews] TAG review request: User Activation Delegation through postMessages (#347) (Tuesday, 19 March)
• Re: [w3ctag/design-reviews] User Idle Detection (#336) (Tuesday, 19 March)
• Re: [w3ctag/design-reviews] Web Share Target API (#221) (Tuesday, 12 March)
• Re: [w3ctag/design-reviews] ads.txt (#201) (Friday, 1 March)

Daniel Bates

• Re: [w3c/uievents] Should we dispatch a keypress event when spacebar is used to activate an element (#225) (Wednesday, 6 March)
• Re: [w3c/uievents] Should we dispatch a keypress event when spacebar is used to activate an element (#225) (Tuesday, 5 March)
• [w3c/uievents] Should we dispatch a keypress event when spacebar is used to activate an element (#225) (Tuesday, 5 March)

Daniel Burnett

• Re: [w3ctag/design-reviews] TAG review request: Verifiable Credentials Data Model 1.0 (#343) (Tuesday, 12 March)
• Re: [w3ctag/design-reviews] TAG review request: Verifiable Credentials Data Model 1.0 (#343) (Tuesday, 12 March)

Daniel Ehrenberg

• Re: [heycam/webidl] Stop using extended attributes for constructors (#636) (Monday, 25 March)
• Re: [heycam/webidl] Remove unused callback interface functionality (#696) (Monday, 25 March)
• Re: [w3c/webcomponents] Spring 2019 F2F Agenda (#802) (Wednesday, 20 March)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Monday, 18 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Friday, 15 March)
• Re: [heycam/webidl] Unclear [Constructor] does the right thing for subclassing (#533) (Sunday, 10 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Sunday, 10 March)
• Re: [heycam/webidl] Stop using extended attributes for constructors (#636) (Friday, 8 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Wednesday, 6 March)
• Re: [heycam/webidl] Declaring modules in WebIDL (#592) (Tuesday, 5 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Tuesday, 5 March)
• Re: [heycam/webidl] Editorial: Clarify that attributes and operations may be namespace members (#678) (Tuesday, 5 March)
• Re: [heycam/webidl] Attributes and operations can be namespace members as well (#677) (Tuesday, 5 March)
• Re: [heycam/webidl] Enumeration order of interface members (#432) (Monday, 4 March)
• Re: [heycam/webidl] Enumeration order of interface members (#432) (Monday, 4 March)
• [heycam/webidl] Editorial: Clarify that attributes and operations may be namespace members (#678) (Monday, 4 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Monday, 4 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Monday, 4 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Monday, 4 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Monday, 4 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Monday, 4 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Monday, 4 March)
• [heycam/webidl] Attributes and operations can be namespace members as well (#677) (Monday, 4 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Monday, 4 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Monday, 4 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Monday, 4 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Monday, 4 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Monday, 4 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Monday, 4 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Monday, 4 March)
• Re: [heycam/webidl] Enumeration order of interface members (#432) (Monday, 4 March)
• Re: [heycam/webidl] Everything is a module (#676) (Monday, 4 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Monday, 4 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Monday, 4 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Sunday, 3 March)
• [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Sunday, 3 March)
• Re: [heycam/webidl] Declaring modules in WebIDL (#592) (Saturday, 2 March)
• Re: [heycam/webidl] Disallow combining an indexed getter with a maplike/setlike (#671) (Friday, 1 March)

dannyjr894

• Re: [w3c/FileAPI] Allow MediaSource, disallow any more extensions (#103) (Friday, 22 March)

Darien Maillet Valentine

• [heycam/webidl] Absence of "record" token from Other production (#694) (Friday, 22 March)

Darwin Huang

• Re: [w3ctag/design-reviews] TAG review: Async Clipboard - image/delayed content (#350) (Tuesday, 12 March)

Dave Tapuska

• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Tuesday, 19 March)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Tuesday, 19 March)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Friday, 15 March)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Tuesday, 12 March)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Tuesday, 12 March)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Tuesday, 12 March)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Tuesday, 12 March)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Tuesday, 12 March)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Tuesday, 12 March)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Tuesday, 12 March)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Tuesday, 12 March)
• Re: [w3c/ServiceWorker] Add API for postMessage with PostMessageOptions (#1344) (Thursday, 7 March)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Wednesday, 6 March)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Wednesday, 6 March)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Wednesday, 6 March)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Wednesday, 6 March)

David Benjamin

• Re: [whatwg/fetch] Handling of invalid Location header characters doesn't match browsers (#883) (Saturday, 23 March)
• Re: [whatwg/fetch] Handling of invalid Location header characters doesn't match browsers (#883) (Thursday, 21 March)
• Re: [whatwg/fetch] Handling of invalid Location header characters doesn't match browsers (#883) (Wednesday, 20 March)
• Re: [whatwg/fetch] Handling of invalid Location header characters doesn't match browsers (#883) (Wednesday, 20 March)
• Re: [whatwg/fetch] Handling of invalid Location header characters doesn't match browsers (#883) (Wednesday, 20 March)
• [whatwg/fetch] Handling of invalid Location header characters doesn't match browsers (#883) (Tuesday, 19 March)

ddorwin

• [w3c/gamepad] Editorial: Fix a couple punctuation issues in "Remapping" (#91) (Monday, 25 March)

Denis Ah-Kang

• [w3c/screen-orientation] Fix description markup (#167) (Tuesday, 5 March)
• [w3c/screen-orientation] respec no longer supports the old ";" delimiter (#166) (Tuesday, 5 March)

Diego Ferreiro Val

• Re: [w3c/webcomponents] Spring 2019 F2F Agenda (#802) (Thursday, 14 March)

dmitriid

• Re: [w3c/webcomponents] [templates] Ensure that template instantiation actually improves the platform (#704) (Thursday, 21 March)
• Re: [w3c/webcomponents] [templates] Ensure that template instantiation actually improves the platform (#704) (Wednesday, 20 March)

Domenic Denicola

• Re: [whatwg/dom] Define mutation events (#305) (Friday, 29 March)
• Re: [whatwg/dom] Remove compound microtasks (#741) (Friday, 29 March)
• Re: [whatwg/dom] Dispatching slotchange within a compound microtask (#734) (Friday, 29 March)
• Re: [whatwg/dom] Remove compound microtasks (#741) (Friday, 29 March)
• Re: [heycam/webidl] Correct the effective overload set use for named constructors (#699) (Friday, 29 March)
• Re: [whatwg/streams] Make it clear that a chunk size has to be non-negative (#999) (Thursday, 28 March)
• Re: [whatwg/streams] Make it clear that a chunk size has to be non-negative (#999) (Thursday, 28 March)
• Re: [heycam/webidl] Remove unused callback interface functionality (#696) (Thursday, 28 March)
• Re: [w3ctag/design-reviews] Additional reading methods on Blob and File (#359) (Thursday, 28 March)
• Re: [whatwg/dom] Create an abstraction for Element's textContent getter (#743) (Tuesday, 26 March)
• Re: [heycam/webidl] Arguments allow double extended attributes (#691) (Wednesday, 20 March)
• Re: [whatwg/dom] Wrong return type of Node::getRootNode() (#739) (Wednesday, 20 March)
• Re: [whatwg/dom] Wrong return type of Node::getRootNode() (#739) (Wednesday, 20 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Tuesday, 19 March)
• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Monday, 18 March)
• Re: [w3c/webcomponents] Please revisit HTML Imports (#677) (Saturday, 16 March)
• Re: [w3c/webcomponents] Spring 2019 F2F Agenda (#802) (Friday, 15 March)
• Re: [heycam/webidl] Formalize the 'this' and 'given value' ambient values (#665) (Friday, 15 March)
• Re: [heycam/webidl] Formalize the 'this' and 'given value' ambient values (#665) (Thursday, 14 March)
• Re: [heycam/webidl] Properly call the imperative creation algorithms for prototypes (#684) (Thursday, 14 March)
• Re: [w3c/FileAPI] Rewrite FileReader definitions. (#118) (Thursday, 14 March)
• [w3c/FileAPI] Event handler content attributes are for HTML elements, not JS APIs (#120) (Thursday, 14 March)
• Re: [heycam/webidl] Disallow constants to be null (#686) (Monday, 11 March)
• Re: [heycam/webidl] Disallow constants to be null (#686) (Monday, 11 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Sunday, 10 March)
• Re: [w3c/FileAPI] Add simpler reading methods to Blob interface. (#117) (Friday, 8 March)
• Re: [heycam/webidl] Imperatively create the interface prototype objects (#684) (Friday, 8 March)
• Re: [heycam/webidl] Ensure that interface objects aren't used before they exist (#682) (Friday, 8 March)
• Re: [heycam/webidl] Stop using extended attributes for constructors (#636) (Friday, 8 March)
• Re: [heycam/webidl] Remove references to ECMAScript global environments (#681) (Thursday, 7 March)
• [heycam/webidl] "platform object" for ECMAScript vs. IDL values (#680) (Thursday, 7 March)
• Re: [w3c/webcomponents] CSS Modules (#759) (Wednesday, 6 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Tuesday, 5 March)
• Re: [w3ctag/design-reviews] User Idle Detection (#336) (Tuesday, 5 March)
• Re: [heycam/webidl] Declaring modules in WebIDL (#592) (Tuesday, 5 March)
• Re: [heycam/webidl] Declaring modules in WebIDL (#592) (Tuesday, 5 March)
• Re: [heycam/webidl] Enumeration order of interface members (#432) (Monday, 4 March)
• Re: [heycam/webidl] Enumeration order of interface members (#432) (Monday, 4 March)
• Re: [heycam/webidl] Should callback interfaces with more than one operation be supported? (#661) (Monday, 4 March)
• Re: [heycam/webidl] Clarify note about enum conversion exceptions (#673) (Friday, 1 March)

Dominick Ng

• Re: [w3c/manifest] Change the default value for start_url (#670) (Thursday, 21 March)
• Re: [w3c/manifest] What theme color should be used when a PWA window is out of scope? (#755) (Monday, 4 March)
• Re: [w3c/manifest] What theme color should be used when a PWA window is out of scope? (#755) (Monday, 4 March)

Ehsan Akhgari

• [whatwg/fetch] Allow modifying the default referrer policy applied to certain fetches depending on engine-specific rules (#879) (Friday, 8 March)

Ella Ge

• Re: [w3c/pointerlock] movementX/Y when zoom in/out (#23) (Thursday, 21 March)
• Re: [w3c/pointerlock] movementX/Y when zoom in/out (#23) (Thursday, 21 March)
• [w3c/pointerlock] movementX/Y coordinate space (#42) (Thursday, 21 March)
• Re: [w3ctag/design-reviews] Pointerevent extension (#346) (Thursday, 21 March)
• Re: [w3c/pointerlock] Warp on Exit (#41) (Wednesday, 13 March)

Emilio Cobos Álvarez

• Re: [w3c/webcomponents] Shadow tree encapsulation and CSS (#804) (Thursday, 28 March)
• Re: [w3c/webcomponents] Shadow tree encapsulation and CSS (#804) (Thursday, 28 March)
• Re: [w3c/webcomponents] Shadow tree encapsulation and CSS (#804) (Thursday, 28 March)
• Re: [w3c/webcomponents] Shadow tree encapsulation and CSS (#804) (Thursday, 28 March)
• Re: [w3c/webcomponents] Shadow tree encapsulation and CSS (#804) (Thursday, 28 March)

Emily Stark

• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Wednesday, 27 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Wednesday, 27 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Wednesday, 27 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Wednesday, 27 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Saturday, 23 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Saturday, 23 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Saturday, 23 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Friday, 22 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Friday, 22 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Friday, 22 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Thursday, 21 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Thursday, 21 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Thursday, 21 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Thursday, 21 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Thursday, 21 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Thursday, 21 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Thursday, 21 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Thursday, 21 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Thursday, 21 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Thursday, 21 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Thursday, 21 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Thursday, 21 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Thursday, 21 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Thursday, 21 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Thursday, 21 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Thursday, 21 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Wednesday, 20 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Wednesday, 20 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Wednesday, 20 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Wednesday, 20 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Wednesday, 20 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Wednesday, 20 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Wednesday, 20 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Wednesday, 20 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Wednesday, 20 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Friday, 15 March)
• [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Friday, 15 March)

Eugene Kashida

• Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) (Tuesday, 26 March)

Evan Wallace

• Re: [w3c/manifest] Add a "tabbed application" mode (#737) (Tuesday, 12 March)

ExE Boss

• Re: [w3c/webcomponents] HTML module should require a new top level element (#752) (Tuesday, 19 March)
• Re: [w3c/webcomponents] HTML module should require a new top level element (#752) (Saturday, 16 March)

François Beaufort

• Re: [whatwg/fullscreen] How :fullscreen CSS pseudo class works in shadow dom? (#149) (Wednesday, 20 March)
• Re: [whatwg/fullscreen] How :fullscreen CSS pseudo class works in shadow dom? (#149) (Wednesday, 20 March)
• [whatwg/fullscreen] How :fullscreen CSS pseudo class works in shadow dom? (#149) (Wednesday, 20 March)

Gary Kacmarcik

• Re: [w3ctag/design-reviews] TAG review: Async Clipboard - image/delayed content (#350) (Monday, 18 March)
• Re: [w3c/clipboard-apis] Request a TAG review for image/delayed-content-generation API (#60) (Saturday, 9 March)
• [w3ctag/design-reviews] TAG review: Async Clipboard - image/delayed content (#350) (Saturday, 9 March)

GerTHT

• [whatwg/xhr] surviv.io hacks need a new update (#241) (Sunday, 24 March)

Gijs

• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Monday, 25 March)

Giovanni Ortuño

• Re: [w3c/manifest] App shortcuts / actions (#582) (Sunday, 31 March)
• Re: [w3c/manifest] Support a way to update explicitly (#446) (Sunday, 24 March)
• Re: [w3c/manifest] Support a way to update explicitly (#446) (Sunday, 24 March)
• Re: [w3c/manifest] What theme color should be used when a PWA window is out of scope? (#755) (Monday, 4 March)

Goffert van Gool

• Re: [w3c/webcomponents] Spring 2019 F2F Agenda (#802) (Monday, 18 March)
• Re: [w3c/webcomponents] Spring 2019 F2F Agenda (#802) (Monday, 18 March)
• Re: [w3c/webcomponents] Spring 2019 F2F Agenda (#802) (Sunday, 17 March)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Sunday, 17 March)

Hayato Ito

• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Friday, 29 March)
• Re: [w3c/webcomponents] Shadow tree encapsulation and CSS (#804) (Friday, 29 March)
• Re: [w3c/webcomponents] Spring 2019 F2F Agenda (#802) (Wednesday, 13 March)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Wednesday, 6 March)
• Re: [w3c/webcomponents] CSS encapsulation and common CSS rules (#800) (Friday, 1 March)
• Re: [w3c/webcomponents] CSS encapsulation and common CSS rules (#800) (Friday, 1 March)
• Re: [w3c/webcomponents] CSS encapsulation and common CSS rules (#800) (Friday, 1 March)

Henri Sivonen

• Re: [whatwg/encoding] Make decode() and encodeInto() accept SharedArrayBuffer-backed views (#172) (Friday, 8 March)

hoangzenby92

• [w3c/screen-orientation] Locking orientation algorithm (#176) (Monday, 25 March)
• Re: [w3c/screen-orientation] Fix description markup (#175) (Sunday, 24 March)
• [w3c/screen-orientation] Fix description markup (#175) (Sunday, 24 March)

hober

• Re: [w3ctag/design-reviews] Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312) (Tuesday, 26 March)
• Re: [w3ctag/design-reviews] Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312) (Tuesday, 26 March)
• Re: [w3ctag/design-reviews] User Activation API (#300) (Wednesday, 13 March)
• Re: [w3ctag/design-reviews] User Activation API (#300) (Wednesday, 13 March)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Monday, 11 March)
• Re: [w3ctag/design-reviews] Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312) (Friday, 1 March)
• Re: [w3ctag/design-reviews] Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312) (Friday, 1 March)
• Re: [w3ctag/design-reviews] Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312) (Friday, 1 March)

Honza Bambas

• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Tuesday, 19 March)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Tuesday, 19 March)

Ivan Herman

• Re: [w3ctag/design-reviews] Audiobooks (#345) (Tuesday, 26 March)
• Re: [w3ctag/design-reviews] Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312) (Friday, 1 March)

Jake Archibald

• Re: [whatwg/dom] isEqualNode and <template> (#737) (Sunday, 31 March)
• Re: [whatwg/dom] isEqualNode and <template> (#737) (Saturday, 30 March)
• Re: [whatwg/fetch] Safelist request headers starting with `Sec-` (#880) (Tuesday, 19 March)
• Re: [w3c/IndexedDB] Add cursor.request (#257) (Thursday, 14 March)
• Re: [w3c/IndexedDB] Add cursor.request (#257) (Thursday, 14 March)
• Re: [w3c/IndexedDB] Add cursor.request (#257) (Thursday, 14 March)
• Re: [w3c/IndexedDB] Add cursor.request (#257) (Thursday, 14 March)
• Re: [w3c/IndexedDB] Add cursor.request (#257) (Thursday, 14 March)
• Re: [w3c/IndexedDB] Add cursor.request (#257) (Wednesday, 13 March)
• Re: [w3c/IndexedDB] Add cursor.request (#257) (Wednesday, 13 March)
• Re: [w3c/IndexedDB] Add cursor.request (#257) (Wednesday, 13 March)
• [w3c/IndexedDB] Add cursor.reques (#257) (Wednesday, 13 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Friday, 8 March)
• [whatwg/dom] isEqualNode and <template> (#737) (Friday, 8 March)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Thursday, 7 March)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Thursday, 7 March)
• Re: [whatwg/fetch] More CORB-protected MIME types - safelist-based approach (#721) (Thursday, 7 March)
• Re: [w3c/IndexedDB] cursor.request (#255) (Wednesday, 6 March)
• Re: [whatwg/fetch] More CORB-protected MIME types - safelist-based approach (#721) (Tuesday, 5 March)
• Re: [whatwg/fetch] More CORB-protected MIME types - safelist-based approach (#721) (Tuesday, 5 March)
• Re: [w3c/IndexedDB] cursor.request (#255) (Tuesday, 5 March)
• Re: [w3c/ServiceWorker] Don't fail update upon error fetching the incumbent worker's import s… (#1377) (Tuesday, 5 March)
• Re: [w3c/ServiceWorker] Don't fail update upon error fetching the incumbent worker's import s… (#1377) (Monday, 4 March)
• [w3c/IndexedDB] cursor.request (#255) (Monday, 4 March)

James Browning

• Re: [w3c/webcomponents] [templates] Ensure that template instantiation actually improves the platform (#704) (Monday, 25 March)
• Re: [w3c/FileAPI] Add simpler reading methods to Blob interface. (#117) (Friday, 22 March)

Jan Miksovsky

• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Friday, 8 March)

Jason Miller

• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Thursday, 7 March)

Jason Orendorff

• Re: [whatwg/streams] Treat forAuthorCode as an internal slot of reader object (#984) (Friday, 1 March)

Jeffrey Yasskin

• [w3ctag/design-reviews] Design questions for Signed Exchanges (#354) (Sunday, 24 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Friday, 22 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Friday, 22 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Wednesday, 20 March)

jfey

• Re: [w3c/manifest] Explicit requirements/capabilities section (#756) (Wednesday, 13 March)
• Re: [w3c/manifest] Explicit requirements/capabilities section (#756) (Wednesday, 13 March)
• [w3c/manifest] Explicit requirements/capabilities section (#756) (Tuesday, 12 March)

Joe Pea

• Re: [w3c/webcomponents] Is there a way to detect if a custom element was constructed during parsing? (#789) (Tuesday, 19 March)
• Re: [w3c/webcomponents] Is there a way to detect if a custom element was constructed during parsing? (#789) (Tuesday, 19 March)
• Re: [w3c/webcomponents] Is there a way to detect if a custom element was constructed during parsing? (#789) (Monday, 18 March)
• Re: [w3c/webcomponents] Is there a way to detect if a custom element was constructed during parsing? (#789) (Monday, 18 March)

Johan Sundström

• Re: [w3c/selection-api] Add Selection/Range methods based on anchestor element (#102) (Tuesday, 5 March)
• Re: [w3c/selection-api] Add Selection/Range methods based on anchestor element (#102) (Tuesday, 5 March)

Johanna

• [w3c/screen-orientation] Fix Respec warnings (#174) (Thursday, 14 March)
• Re: [w3c/screen-orientation] Locking orientation algorithm edits (#160) (Thursday, 14 March)
• Re: [w3c/screen-orientation] Change lock link in example 3 (#169) (Thursday, 14 March)
• Re: [w3c/screen-orientation] unlocking during event dispatching is undefined (#173) (Thursday, 14 March)
• Re: [w3c/screen-orientation] Change lock link in example 3 (#169) (Thursday, 14 March)
• Re: [w3c/screen-orientation] Edit to 5.3.1. Locking to the default orientation (#171) (Thursday, 14 March)
• Re: [w3c/screen-orientation] Edit to 5.3.1. Locking to the default orientation (#171) (Wednesday, 13 March)
• Re: [w3c/screen-orientation] Edit to 5.3.1. Locking to the default orientation (#171) (Wednesday, 13 March)
• Re: [w3c/screen-orientation] Expand default orientation definition (#172) (Wednesday, 13 March)
• Re: [w3c/screen-orientation] Expand default orientation definition (#172) (Wednesday, 13 March)
• Re: [w3c/screen-orientation] Edit to 5.3.1. Locking to the default orientation (#171) (Tuesday, 12 March)
• [w3c/screen-orientation] Expand default orientation definition (#172) (Tuesday, 12 March)
• Re: [w3c/screen-orientation] Section 3 edits (#170) (Tuesday, 12 March)
• [w3c/screen-orientation] Edit to 5.3.1. Locking to the default orientation (#171) (Monday, 11 March)
• [w3c/screen-orientation] Section 3 edits (#170) (Monday, 11 March)
• [w3c/screen-orientation] Change lock link in example 3 (#169) (Monday, 11 March)
• Re: [w3c/screen-orientation] Locking orientation algorithm edits (#160) (Wednesday, 6 March)
• Re: [w3c/screen-orientation] Locking orientation algorithm edits (#160) (Tuesday, 5 March)
• Re: [w3c/screen-orientation] Editorial: refactor to use in parallel (#165) (Tuesday, 5 March)
• Re: [w3c/screen-orientation] Deal with fragment navigation (#87) (Monday, 4 March)
• Re: [w3c/screen-orientation] Add test link to step 3 of updating orientation algorithm (#164) (Monday, 4 March)
• Re: [w3c/screen-orientation] Reliability of angle (#162) (Friday, 1 March)
• [w3c/screen-orientation] Add test link to step 3 of updating orientation algorithm (#164) (Friday, 1 March)
• Re: [w3c/screen-orientation] Locking orientation algorithm edits (#160) (Friday, 1 March)

Johannes Wilm

• Re: [w3c/editing] Disambiguate caret position at wrapped line boundaries (#189) (Friday, 22 March)
• Re: [w3c/editing] Disambiguate caret position at wrapped line boundaries (#189) (Friday, 22 March)

Josh Matthews

• Re: [whatwg/fetch] "typedef (sequence<sequence<ByteString>> or reco..." (#876) (Thursday, 7 March)

Joshua Bell

• Re: [w3c/FileAPI] Consider reserializing type attributes, not just parsing them. (#123) (Saturday, 30 March)
• Re: [w3c/IndexedDB] Prebuilt IndexedDB format (#224) (Friday, 29 March)
• Re: [w3c/IndexedDB] feature-request - add appendFile capability to overcome nedb performance-bottleneck (#260) (Thursday, 28 March)
• Re: [w3c/IndexedDB] feature-request - add appendFile capability to overcome nedb performance-bottleneck (#260) (Thursday, 28 March)
• Re: [w3c/IndexedDB] `abort()` to set transaction state to inactive (#258) (Thursday, 21 March)
• Re: [w3c/IndexedDB] `abort()` to set transaction state to inactive (#258) (Thursday, 21 March)
• Re: [w3c/IndexedDB] `abort()` to set transaction state to inactive (#258) (Thursday, 21 March)
• Re: [w3c/IndexedDB] `abort()` to set transaction state to inactive (#258) (Thursday, 21 March)
• Re: [w3c/IndexedDB] Sp. (#259) (Thursday, 21 March)
• Re: [w3c/IndexedDB] Sp. (#259) (Thursday, 21 March)
• Re: [w3c/IndexedDB] Sp. (#259) (Thursday, 21 March)
• Re: [w3c/IndexedDB] Add IDBTransaction commit() method (#242) (Thursday, 21 March)
• Re: [w3c/IndexedDB] cursor.request (#255) (Monday, 18 March)
• Re: [w3c/IndexedDB] cursor.request (#255) (Thursday, 14 March)
• Re: [w3c/IndexedDB] Add cursor.request (#257) (Thursday, 14 March)
• Re: [w3c/IndexedDB] Add cursor.request (#257) (Thursday, 14 March)
• Re: [w3c/IndexedDB] Add cursor.request (#257) (Thursday, 14 March)
• Re: [w3c/IndexedDB] Add cursor.request (#257) (Wednesday, 13 March)
• Re: [w3c/IndexedDB] Add cursor.request (#257) (Wednesday, 13 March)
• Re: [w3c/IndexedDB] Add cursor.request (#257) (Wednesday, 13 March)
• Re: [w3c/IndexedDB] Incoming link from HTML broken (#256) (Monday, 11 March)
• Re: [w3c/IndexedDB] Incoming link from HTML broken (#256) (Monday, 11 March)
• Re: [w3c/IndexedDB] Incoming link from HTML broken (#256) (Monday, 11 March)
• Re: [w3c/IndexedDB] cursor.request (#255) (Wednesday, 6 March)
• Re: [w3c/IndexedDB] cursor.request (#255) (Wednesday, 6 March)
• Re: [w3c/IndexedDB] cursor.request (#255) (Monday, 4 March)

Joshua Peek

• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Wednesday, 13 March)

Jungkee Song

• Re: [w3c/ServiceWorker] Add CR Plan for V1 (#1242) (Thursday, 14 March)

Justin Fagnani

• Re: [w3c/webcomponents] Spring 2019 F2F Agenda (#802) (Thursday, 14 March)
• Re: [w3c/webcomponents] Spring 2019 F2F Agenda (#802) (Wednesday, 13 March)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Thursday, 7 March)
• Re: [w3c/webcomponents] CSS Modules (#759) (Thursday, 7 March)
• Re: [w3c/webcomponents] CSS Modules (#759) (Wednesday, 6 March)
• Re: [w3c/webcomponents] CSS Modules (#759) (Wednesday, 6 March)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Friday, 1 March)

Jxck

• Re: [w3ctag/design-reviews] Alternative Text for CSS Generated Content (#351) (Saturday, 30 March)
• Re: [w3ctag/design-reviews] Alternative Text for CSS Generated Content (#351) (Saturday, 23 March)

Kagami Sascha Rosylight

• Re: [heycam/webidl] Arguments allow double extended attributes (#691) (Thursday, 21 March)
• Re: [heycam/webidl] Arguments allow double extended attributes (#691) (Wednesday, 20 March)
• [heycam/webidl] Extended attributes for arguments? (#691) (Tuesday, 19 March)
• Re: [heycam/webidl] Disallow constants to be null (#686) (Monday, 11 March)
• Re: [heycam/webidl] Disallow constants to be null (#686) (Monday, 11 March)
• Re: [heycam/webidl] Disallow constants to be null (#686) (Monday, 11 March)
• [heycam/webidl] Disallow constants to be null (#686) (Monday, 11 March)

kai zhu

• Re: [w3c/IndexedDB] Prebuilt IndexedDB format (#224) (Friday, 29 March)
• Re: [w3c/IndexedDB] Prebuilt IndexedDB format (#224) (Friday, 29 March)
• Re: [w3c/IndexedDB] feature-request - add appendFile capability to overcome nedb performance-bottleneck (#260) (Thursday, 28 March)
• [w3c/IndexedDB] add appendFile capability to overcome nedb performance-bottleneck (#260) (Thursday, 28 March)

Keith Rarick

• Re: [w3c/pointerlock] Warp on Exit (#41) (Sunday, 17 March)
• Re: [w3c/pointerlock] Warp on Exit (#41) (Sunday, 17 March)
• [w3c/pointerlock] Warp on Exit (#41) (Thursday, 7 March)

Ken

• Re: [whatwg/fetch] Consider to add "resolveAtIdleTime" to RequestInit (#821) (Saturday, 2 March)

Kenneth Rohde Christiansen

• Re: [w3c/manifest] App shortcuts / actions (#582) (Saturday, 30 March)
• Re: [w3c/manifest] App shortcuts / actions (#582) (Tuesday, 26 March)
• Re: [w3ctag/design-reviews] TAG review request: Additional reading methods on Blob and File (#359) (Tuesday, 26 March)
• Re: [w3ctag/design-reviews] TAG review request: MediaStream Image Capture API (Pan/Tilt feature) (#358) (Tuesday, 26 March)
• Re: [w3ctag/design-reviews] TAG review request: MediaStream Image Capture API (Pan/Tilt feature) (#358) (Tuesday, 26 March)
• Re: [w3ctag/design-reviews] TAG review request: MediaStream Image Capture API (Pan/Tilt feature) (#358) (Tuesday, 26 March)
• Re: [w3ctag/design-reviews] TAG review request: MediaStream Image Capture API (Pan/Tilt feature) (#358) (Tuesday, 26 March)
• Re: [w3ctag/design-reviews] User Idle Detection (#336) (Wednesday, 20 March)
• Re: [w3ctag/design-reviews] User Idle Detection (#336) (Monday, 11 March)
• Re: [w3ctag/design-reviews] User Idle Detection (#336) (Monday, 11 March)
• Re: [w3ctag/design-reviews] User Idle Detection (#336) (Monday, 11 March)
• Re: [w3ctag/design-reviews] User Idle Detection (#336) (Wednesday, 6 March)
• Re: [w3c/manifest] What theme color should be used when a PWA window is out of scope? (#755) (Monday, 4 March)
• Re: [w3c/manifest] What theme color should be used when a PWA window is out of scope? (#755) (Monday, 4 March)

Kerry

• [w3c/manifest] requests (#757) (Friday, 15 March)

Kevin Jahns

• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Friday, 15 March)

Khivar

• [w3c/ServiceWorker] Browsers should not consume the stream right away on ReadableStream responses with 'Content-Disposition: attachment' header. (#1398) (Saturday, 30 March)

Kinuko Yasuda

• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Friday, 8 March)

Kuzcoo

• Re: [w3c/webcomponents] Please revisit HTML Imports (#677) (Saturday, 16 March)
• Re: [w3c/webcomponents] Please revisit HTML Imports (#677) (Saturday, 16 March)
• Re: [w3c/webcomponents] Please revisit HTML Imports (#677) (Saturday, 16 March)

L. David Baron

• Re: [w3ctag/design-reviews] TAG review of whether element.pseudo(":unknown") should return null or throw (#348) (Sunday, 31 March)
• Re: [w3ctag/design-reviews] TAG review of whether element.pseudo(":unkown") should return null or throw (#348) (Friday, 29 March)
• Re: [w3ctag/design-reviews] IntersectionObserver V2 (#328) (Friday, 29 March)
• Re: [w3ctag/design-reviews] Feature policy control over sandbox features (#339) (Tuesday, 26 March)
• Re: [w3ctag/design-reviews] User Activation Delegation through postMessages (#347) (Tuesday, 26 March)
• Re: [w3ctag/design-reviews] Priority Hints API (#241) (Tuesday, 19 March)
• Re: [w3ctag/design-reviews] TAG review request: User Activation Delegation through postMessages (#347) (Tuesday, 19 March)
• Re: [w3ctag/design-reviews] TAG review request: User Activation Delegation through postMessages (#347) (Tuesday, 19 March)
• Re: [w3ctag/design-reviews] Web Publications review (#344) (Tuesday, 19 March)
• Re: [w3ctag/design-reviews] Portals (#331) (Wednesday, 13 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Saturday, 9 March)
• Re: [w3ctag/design-reviews] hrefTranslate attribute (#301) (Wednesday, 6 March)
• Re: [w3ctag/design-reviews] User Activation API (#300) (Wednesday, 6 March)
• Re: [w3ctag/design-reviews] First-Party Sets (#342) (Tuesday, 5 March)

Lukasz Anforowicz

• Re: [whatwg/fetch] CORB shouldn't block application/dash+xml videos. (#887) (Friday, 29 March)
• [whatwg/fetch] CORB shouldn't block application/dash+xml videos. (#887) (Friday, 29 March)
• [whatwg/fetch] CORB should not block application/dash+xml videos (#886) (Friday, 29 March)
• Re: [whatwg/fetch] More CORB-protected MIME types - safelist-based approach (#721) (Tuesday, 5 March)
• Re: [whatwg/fetch] More CORB-protected MIME types - safelist-based approach (#721) (Tuesday, 5 March)
• Re: [whatwg/fetch] More CORB-protected MIME types - safelist-based approach (#721) (Tuesday, 5 March)
• [whatwg/fetch] Should `Content-Disposition: attachment` implicitly opt into CORB and/or CORP? (#875) (Monday, 4 March)

Lukasz Olejnik

• Re: [w3ctag/design-reviews] TAG review request: Verifiable Credentials Data Model 1.0 (#343) (Tuesday, 12 March)
• Re: [w3ctag/design-reviews] TAG review request: Verifiable Credentials Data Model 1.0 (#343) (Tuesday, 12 March)

Majid Valipour

• [w3ctag/design-reviews] CSS Animation Worklet API (#349) (Friday, 8 March)

Makoto Shimazu

• Re: [w3c/ServiceWorker] Immediate Service Worker (#1389) (Wednesday, 6 March)

Marcel Dopita

• Re: [w3c/manifest] Support a way to update explicitly (#446) (Sunday, 24 March)
• Re: [w3c/manifest] Support a way to update explicitly (#446) (Friday, 22 March)

Marcos Cáceres

• Re: [w3c/gamepad] Editorial: Fix a couple punctuation issues in "Remapping" (#91) (Tuesday, 26 March)
• Re: [w3c/gamepad] Editorial: Fix a couple punctuation issues in "Remapping" (#91) (Tuesday, 26 March)
• Re: [w3c/gamepad] Editorial: Fix a couple punctuation issues in "Remapping" (#91) (Tuesday, 26 March)
• Re: [w3c/screen-orientation] Locking orientation algorithm (#176) (Tuesday, 26 March)
• Re: [heycam/webidl] [wip] First pass at adding internal slots (#495) (Monday, 25 March)
• Re: [heycam/webidl] [wip] First pass at adding internal slots (#495) (Monday, 25 March)
• Re: [heycam/webidl] Stop using extended attributes for constructors (#636) (Monday, 25 March)
• Re: [w3c/manifest] Add a `color_scheme` member to `ImageResource` (#758) (Friday, 22 March)
• Re: [w3c/manifest] requests (#757) (Friday, 15 March)
• Re: [w3c/gamepad] Move Ted to former editor (#90) (Friday, 15 March)
• [w3c/gamepad] Move Ted to former editor (#90) (Friday, 15 March)
• Re: [w3c/screen-orientation] Fix Respec warnings (#174) (Friday, 15 March)
• Re: [w3c/screen-orientation] Fix Respec warnings (#174) (Friday, 15 March)
• Re: [w3c/screen-orientation] Change lock link in example 3 (#169) (Thursday, 14 March)
• Re: [w3c/screen-orientation] Deal with fragment navigation (#87) (Thursday, 14 March)
• Re: [w3c/screen-orientation] Change lock link in example 3 (#169) (Thursday, 14 March)
• Re: [w3c/screen-orientation] Change lock link in example 3 (#169) (Thursday, 14 March)
• Re: [w3c/screen-orientation] Locking orientation algorithm edits (#160) (Thursday, 14 March)
• [w3c/screen-orientation] unlocking during event propagation is undefined (#173) (Thursday, 14 March)
• Re: [w3c/manifest] Explicit requirements/capabilities section (#756) (Thursday, 14 March)
• Re: [w3c/screen-orientation] Edit to 5.3.1. Locking to the default orientation (#171) (Wednesday, 13 March)
• Re: [w3c/manifest] Explicit requirements/capabilities section (#756) (Wednesday, 13 March)
• Re: [w3c/manifest] Explicit requirements/capabilities section (#756) (Wednesday, 13 March)
• Re: [w3c/manifest] Explicit requirements/capabilities section (#756) (Wednesday, 13 March)
• Re: [w3c/screen-orientation] Expand default orientation definition (#172) (Wednesday, 13 March)
• Re: [w3c/screen-orientation] Edit to 5.3.1. Locking to the default orientation (#171) (Wednesday, 13 March)
• Re: [w3c/screen-orientation] Face up and face down (#168) (Tuesday, 12 March)
• Re: [w3c/screen-orientation] Reliability of angle (#162) (Tuesday, 12 March)
• Re: [w3c/screen-orientation] Locking orientation algorithm edits (#160) (Tuesday, 12 March)
• Re: [w3c/screen-orientation] Locking orientation algorithm edits (#160) (Tuesday, 12 March)
• Re: [w3c/screen-orientation] Reliability of angle (#162) (Tuesday, 12 March)
• Re: [w3c/screen-orientation] Edit to 5.3.1. Locking to the default orientation (#171) (Tuesday, 12 March)
• Re: [w3c/screen-orientation] Edit to 5.3.1. Locking to the default orientation (#171) (Tuesday, 12 March)
• Re: [w3c/screen-orientation] Edit to 5.3.1. Locking to the default orientation (#171) (Tuesday, 12 March)
• Re: [w3c/screen-orientation] Section 3 edits (#170) (Monday, 11 March)
• [w3c/screen-orientation] Face up and face down (#168) (Monday, 11 March)
• Re: [w3c/uievents] Identify which of multiple keyboards an event came from (#226) (Thursday, 7 March)
• Re: [w3c/screen-orientation] Locking orientation algorithm edits (#160) (Wednesday, 6 March)
• Re: [w3c/screen-orientation] Locking orientation algorithm edits (#160) (Wednesday, 6 March)
• Re: [w3c/screen-orientation] Fix description markup (#167) (Tuesday, 5 March)
• Re: [w3c/screen-orientation] Fix description markup (#167) (Tuesday, 5 March)
• Re: [w3c/screen-orientation] respec no longer supports the old ";" delimiter (#166) (Tuesday, 5 March)
• Re: [w3c/screen-orientation] respec no longer supports the old ";" delimiter (#166) (Tuesday, 5 March)
• Re: [w3c/screen-orientation] Editorial: refactor to use in parallel (#165) (Tuesday, 5 March)
• Re: [w3c/screen-orientation] Deal with fragment navigation (#87) (Monday, 4 March)
• [w3c/screen-orientation] Editorial: refactor to us in parallel (#165) (Monday, 4 March)
• Re: [w3c/screen-orientation] Add test link to step 3 of updating orientation algorithm (#164) (Saturday, 2 March)

Marijn Kruisselbrink

• Re: [w3c/FileAPI] Add simpler reading methods to Blob interface. (#117) (Tuesday, 26 March)
• [w3ctag/design-reviews] TAG review request: Additional reading methods on Blob and File (#359) (Tuesday, 26 March)
• Re: [w3c/FileAPI] Add simpler reading methods to Blob interface. (#117) (Tuesday, 26 March)
• Re: [w3c/FileAPI] Allow MediaSource, disallow any more extensions (#103) (Monday, 18 March)
• Re: [w3c/FileAPI] Add simpler reading methods to Blob interface. (#117) (Friday, 15 March)
• Re: [w3c/FileAPI] Add simpler reading methods to Blob interface. (#117) (Friday, 15 March)
• Re: [w3c/FileAPI] Don't update FileReader's result until "LOAD" (#79) (Friday, 15 March)
• Re: [w3c/FileAPI] Rewrite FileReader definitions. (#118) (Friday, 15 March)
• Re: [w3c/FileAPI] Rewrite FileReader definitions. (#118) (Thursday, 14 March)
• Re: [w3c/FileAPI] Rewrite FileReader definitions. (#118) (Thursday, 14 March)
• Re: [w3c/FileAPI] Rewrite FileReader definitions. (#118) (Thursday, 14 March)
• Re: [w3c/FileAPI] Rewrite FileReader definitions. (#118) (Thursday, 14 March)
• Re: [w3c/FileAPI] Rewrite FileReader definitions. (#118) (Thursday, 14 March)
• Re: [w3c/FileAPI] Rewrite FileReader definitions. (#118) (Wednesday, 13 March)
• Re: [w3c/FileAPI] Rewrite FileReader definitions. (#118) (Wednesday, 13 March)
• Re: [w3c/FileAPI] Rewrite FileReader definitions. (#118) (Wednesday, 13 March)
• Re: [w3c/FileAPI] Add simpler reading methods to Blob interface. (#117) (Tuesday, 12 March)
• Re: [w3c/FileAPI] Rewrite FileReader definitions. (#118) (Tuesday, 12 March)
• Re: [w3c/FileAPI] Add simpler reading methods to Blob interface. (#117) (Tuesday, 12 March)
• Re: [w3c/FileAPI] Add simpler reading methods to Blob interface. (#117) (Tuesday, 12 March)
• [w3c/FileAPI] Rewrite FileReader definitions. (#118) (Tuesday, 12 March)
• Re: [w3c/FileAPI] Add simpler reading methods to Blob interface. (#117) (Friday, 8 March)
• Re: [w3c/FileAPI] Add simpler reading methods to Blob interface. (#117) (Friday, 8 March)
• Re: [w3c/FileAPI] Add simpler reading methods to Blob interface. (#117) (Thursday, 7 March)
• Re: [w3c/FileAPI] Add simpler reading methods to Blob interface. (#117) (Thursday, 7 March)
• [w3c/FileAPI] Add simpler reading methods to Blob interface. (#117) (Thursday, 7 March)

Mark Kennedy

• Re: [w3c/webcomponents] Question: where to incubate HTML modules? (#794) (Monday, 4 March)

Masayuki Nakano

• Re: [w3c/uievents] onbeforeinput (#218) (Friday, 29 March)
• Re: [w3c/uievents] onbeforeinput (#218) (Friday, 29 March)
• Re: [w3c/uievents] Should we dispatch a keypress event when spacebar is used to activate an element (#225) (Wednesday, 6 March)
• Re: [w3c/uievents] Event order between "compositionend" and "input" (#202) (Monday, 4 March)

Mason Freed

• Re: [w3ctag/design-reviews] Backdrop Filter (#353) (Friday, 29 March)
• [w3ctag/design-reviews] TAG Review Request: Backdrop Filter (#353) (Tuesday, 12 March)

Matt Falkenhagen

• Re: [w3c/ServiceWorker] Fully inline (.js + json manifest) service worker (#1392) (Tuesday, 19 March)
• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Tuesday, 19 March)
• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Tuesday, 19 March)
• [w3c/ServiceWorker] Is respondWith(fetch(event.request)) always the same as not calling respondWith()? (#1395) (Tuesday, 19 March)
• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Friday, 15 March)
• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Friday, 15 March)
• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Friday, 15 March)
• Re: [w3c/ServiceWorker] Can respondWith() be called from a microtask? (#1394) (Friday, 15 March)
• Re: [w3c/ServiceWorker] Can respondWith() be called from a microtask? (#1394) (Friday, 15 March)
• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Friday, 15 March)
• Re: [w3c/ServiceWorker] Can respondWith() be called from a microtask? (#1394) (Thursday, 14 March)
• Re: [w3c/ServiceWorker] Can respondWith() be called from a microtask? (#1394) (Thursday, 14 March)
• [w3c/ServiceWorker] Can respondWith() be called from a microtask? (#1394) (Thursday, 14 March)
• Re: [w3c/ServiceWorker] Fix the perform the fetch steps in Update algorithm (#1175) (Wednesday, 13 March)
• Re: [w3c/ServiceWorker] Fix the perform the fetch steps in Update algorithm (#1175) (Wednesday, 13 March)
• Re: [w3c/ServiceWorker] Add CR Plan for V1 (#1242) (Wednesday, 13 March)
• [w3c/ServiceWorker] Add WPT for an in-scope iframe inside a data URL iframe. (#1393) (Friday, 8 March)
• Re: [w3c/ServiceWorker] Add API for postMessage with PostMessageOptions (3b31974) (Friday, 8 March)
• Re: [w3c/ServiceWorker] Add API for postMessage with PostMessageOptions (#1344) (Friday, 8 March)
• Re: [w3c/ServiceWorker] Add API for postMessage with PostMessageOptions (#1344) (Friday, 8 March)
• Re: [w3c/ServiceWorker] Add API for postMessage with PostMessageOptions (#1344) (Thursday, 7 March)
• Re: [w3c/ServiceWorker] Minor Readme format changes (#1376) (Thursday, 7 March)
• Re: [w3c/ServiceWorker] Minor Readme format changes (#1376) (Thursday, 7 March)
• Re: [w3c/ServiceWorker] Don't fail update upon error fetching the incumbent worker's import s… (#1377) (Tuesday, 5 March)
• Re: [w3c/ServiceWorker] Update shouldn't fail due to MIME check or 404 for the incumbent's worker scripts (#1374) (Tuesday, 5 March)
• Re: [w3c/ServiceWorker] Update shouldn't fail due to MIME check or 404 for the incumbent's worker scripts (#1374) (Tuesday, 5 March)
• Re: [w3c/ServiceWorker] Don't fail update upon error fetching the incumbent worker's import s… (#1377) (Tuesday, 5 March)
• Re: [w3c/ServiceWorker] Don't fail update upon error fetching the incumbent worker's import s… (#1377) (Tuesday, 5 March)
• Re: [w3c/ServiceWorker] Don't fail update upon error fetching the incumbent worker's import s… (#1377) (Tuesday, 5 March)

Matt Giuca

• Re: [w3c/manifest] App shortcuts / actions (#582) (Tuesday, 26 March)

Matt Menke

• Re: [whatwg/fetch] Handling of invalid Location header characters doesn't match browsers (#883) (Saturday, 23 March)
• Re: [whatwg/fetch] Handling of invalid Location header characters doesn't match browsers (#883) (Saturday, 23 March)

Matthew Dean

• Re: [w3c/webcomponents] Please revisit HTML Imports (#677) (Saturday, 16 March)

Matthew Phillips

• Re: [w3c/webcomponents] Please revisit HTML Imports (#677) (Saturday, 16 March)
• Re: [w3c/webcomponents] Add list of major open design questions to HTML Modules proposal doc (#801) (Wednesday, 6 March)
• Re: [w3c/webcomponents] Add list of major open design questions to HTML Modules proposal doc (#801) (Wednesday, 6 March)

Mattias Buelens

• Re: [whatwg/streams] ReadableStreamTee: do not read when already pulling (#997) (Sunday, 31 March)
• Re: [whatwg/streams] Make it clear that a chunk size has to be non-negative (#999) (Sunday, 24 March)
• Re: [whatwg/streams] Make it clear that a chunk size has to be non-negative (#999) (Saturday, 23 March)
• [whatwg/streams] Remove extra arguments left over from forAuthorCode refactor (#998) (Sunday, 10 March)
• Re: [whatwg/streams] ReadableStreamTee: do not read when already pulling (#997) (Saturday, 2 March)

Meredith

• Re: [w3ctag/design-reviews] Alternative Text for CSS Generated Content (#351) (Thursday, 28 March)
• [w3ctag/design-reviews] Alternative Text for CSS Generated Content (#351) (Monday, 11 March)

Michael McCool

• Re: [w3ctag/design-reviews] Web of Things (WoT) Architecture (#355) (Thursday, 28 March)
• Re: [w3ctag/design-reviews] Web of Things (WoT) Thing Description (#357) (Wednesday, 27 March)
• [w3ctag/design-reviews] Web of Things (WoT) Thing Description (#357) (Tuesday, 26 March)
• [w3ctag/design-reviews] Web of Things (WoT) Architecture (#355) (Monday, 25 March)

Michael Stramel

• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Monday, 18 March)
• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Monday, 18 March)

Michael[tm] Smith

• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Wednesday, 27 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Wednesday, 27 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Monday, 25 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Monday, 25 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Thursday, 21 March)

Miguel Casas-Sanchez

• Re: [w3ctag/design-reviews] TAG review request: MediaStream Image Capture API (Pan/Tilt feature) (#358) (Tuesday, 26 March)

Mike Bostock

• Re: [w3c/webcomponents] Cleaning up (undefining) custom elements? (#754) (Saturday, 16 March)

Mike Sidorov

• Re: [whatwg/fetch] Clarify the way CORB should be applied to beacons (#882) (Wednesday, 20 March)
• Re: [whatwg/fetch] Clarify the way CORB should be applied to beacons (#882) (Tuesday, 19 March)
• Re: [whatwg/fetch] Clarify the way CORB should be applied to beacons (#882) (Tuesday, 19 March)
• Re: [whatwg/fetch] Clarify the way CORB should be applied to beacons (#882) (Tuesday, 19 March)
• [whatwg/fetch] Clarify the way CORB should be applied to beacons (#882) (Tuesday, 19 March)

Mike West

• Re: [w3ctag/design-reviews] HTTP State Tokens (#297) (Thursday, 28 March)
• Re: [w3ctag/design-reviews] Harmonize permissions and similar mechanisms (#360) (Wednesday, 27 March)
• Re: [whatwg/fetch] Consider supporting Fetch Metadata. (#885) (Monday, 25 March)
• [whatwg/fetch] Consider supporting Fetch Metadata. (#885) (Sunday, 24 March)
• Re: [whatwg/fetch] Consider splitting `document` into `document` and `nested-document`. (#755) (Thursday, 14 March)
• Re: [whatwg/fetch] Consider splitting `document` into `document` and `nested-document`. (#755) (Thursday, 14 March)
• Re: [whatwg/fetch] Consider splitting `document` into `document` and `nested-document`. (#755) (Thursday, 14 March)
• Re: [w3ctag/design-reviews] First-Party Sets (#342) (Wednesday, 13 March)

Moonchild

• Re: [whatwg/fetch] Image Accept: headers in the spec prevent conneg (#877) (Thursday, 7 March)
• [whatwg/fetch] Image Accept: headers in the spec prevent conneg (#877) (Thursday, 7 March)

Ms2ger

• [heycam/webidl] Stop using extended attributes for constructors (#700) (Friday, 29 March)
• [heycam/webidl] Correct the effective overload set use for named constructors (#699) (Friday, 29 March)
• Re: [heycam/webidl] Remove unused callback interface functionality (#696) (Friday, 29 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Wednesday, 27 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Tuesday, 26 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Tuesday, 26 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Tuesday, 26 March)
• [heycam/webidl] Define that interface objects are constructors (#698) (Tuesday, 26 March)
• [heycam/webidl] Update the requirement about the definition of a constructor (#697) (Tuesday, 26 March)
• Re: [heycam/webidl] Remove unused callback interface functionality (#696) (Monday, 25 March)
• [heycam/webidl] Remove unused callback interface functionality (#696) (Monday, 25 March)
• [heycam/webidl] Fix a grammar mistake in the 'partial interface' definition (#693) (Wednesday, 20 March)
• [heycam/webidl] Remove support for overloading callbacks (#690) (Tuesday, 19 March)
• [heycam/webidl] [Exposed] check for overloaded operations makes no sense (#689) (Monday, 18 March)
• Re: [w3c/FileAPI] Allow MediaSource, disallow any more extensions (#103) (Monday, 18 March)
• Re: [heycam/webidl] Formalize the 'this' and 'given value' ambient values (#665) (Monday, 18 March)
• Re: [heycam/webidl] Make the grammar check more robust (#688) (Monday, 18 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Friday, 15 March)
• Re: [heycam/webidl] Ensure that interface objects aren't used before they exist (#682) (Friday, 15 March)
• [heycam/webidl] Make the grammar check more robust. (#688) (Friday, 15 March)
• Re: [heycam/webidl] Formalize the 'this' and 'given value' ambient values (#665) (Friday, 15 March)
• Re: [heycam/webidl] Investigate removing nullables from allowed constant types (#448) (Friday, 15 March)
• Re: [heycam/webidl] Disallow constants to be null (#686) (Friday, 15 March)
• Re: [heycam/webidl] Properly call the imperative creation algorithms for prototypes (#684) (Friday, 15 March)
• Re: [heycam/webidl] Formalize the 'this' and 'given value' ambient values (#665) (Thursday, 14 March)
• Re: [heycam/webidl] Editorial: run platform algorithms on IDL objects (#666) (Thursday, 14 March)
• Re: [whatwg/streams] Constructor specification is unclear (#965) (Tuesday, 12 March)
• Re: [heycam/webidl] Disallow constants to be null (#686) (Monday, 11 March)
• Re: [heycam/webidl] Imperatively create the interface prototype objects (#684) (Monday, 11 March)
• Re: [heycam/webidl] Disallow constants to be null (#686) (Monday, 11 March)
• Re: [whatwg/streams] Constructor specification is unclear (#965) (Monday, 11 March)
• Re: [heycam/webidl] Correct the 'indexed getter' cross-reference (#679) (Monday, 11 March)
• Re: [heycam/webidl] Correct the 'indexed getter' cross-reference (#679) (Monday, 11 March)
• [heycam/webidl] Imperatively create the interface prototype objects (#684) (Friday, 8 March)
• [heycam/webidl] Enumeration order of properties on the global object (#683) (Friday, 8 March)
• [heycam/webidl] Ensure that interface objects aren't used before they exist (#682) (Friday, 8 March)
• Re: [heycam/webidl] Remove references to ECMAScript global environments (#681) (Friday, 8 March)
• Re: [heycam/webidl] Investigate/file bugs on named constructor prototype chain (#276) (Friday, 8 March)
• Re: [heycam/webidl] Investigate/file bugs on named constructor prototype chain (#276) (Friday, 8 March)
• Re: [heycam/webidl] Remove references to ECMAScript global environments (#681) (Friday, 8 March)
• Re: [heycam/webidl] Stop using extended attributes for constructors (#636) (Friday, 8 March)
• Re: [heycam/webidl] Remove references to ECMAScript global environments (#681) (Friday, 8 March)
• Re: [heycam/webidl] Remove references to ECMAScript global environments (#681) (Friday, 8 March)
• [heycam/webidl] Remove references to ECMAScript global environments (#681) (Thursday, 7 March)
• Re: [heycam/webidl] Correct the 'indexed getter' cross-reference (#679) (Thursday, 7 March)
• [heycam/webidl] Correct the 'indexed getter' cross-reference (#679) (Thursday, 7 March)
• Re: [heycam/webidl] Editorial: run platform algorithms on IDL objects (#666) (Thursday, 7 March)
• Re: [heycam/webidl] Deduplicate unforgeable member functions (#668) (Thursday, 7 March)
• Re: [heycam/webidl] Disallow combining an indexed getter with a maplike/setlike (#671) (Thursday, 7 March)
• Re: [heycam/webidl] Enumeration order of interface members (#432) (Monday, 4 March)
• Re: [heycam/webidl] Should callback interfaces with more than one operation be supported? (#661) (Monday, 4 March)
• Re: [heycam/webidl] Enumeration order of interface members (#432) (Monday, 4 March)
• Re: [heycam/webidl] Editorial: Clarify that attributes and operations may be namespace members (#678) (Monday, 4 March)
• Re: [heycam/webidl] Should callback interfaces with more than one operation be supported? (#661) (Monday, 4 March)
• Re: [heycam/webidl] Remove the 'user object' concept. (#662) (Monday, 4 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Monday, 4 March)
• Re: [heycam/webidl] [WIP] Define Web IDL Modules (#675) (Monday, 4 March)
• Re: [heycam/webidl] Editorial: fix some bikeshed link warnings (#672) (Monday, 4 March)
• Re: [heycam/webidl] Editorial: improve language around conversions to JS (#664) (Monday, 4 March)
• Re: [heycam/webidl] Editorial: improve language around conversions to JS (#664) (Friday, 1 March)
• Re: [heycam/webidl] Clarify note about enum conversion exceptions (#673) (Friday, 1 March)
• Re: [heycam/webidl] Editorial: remove redundant requirement for existence of 'length' (#667) (Friday, 1 March)
• Re: [heycam/webidl] Deduplicate unforgeable member functions (#668) (Friday, 1 March)
• Re: [heycam/webidl] Editorial: fix some bikeshed link warnings (#672) (Friday, 1 March)
• [heycam/webidl] Clarify note about enum conversion exceptions (#673) (Friday, 1 March)
• Re: [heycam/webidl] Can we use ObjectCreate in object creation? + other editorial tweaks (#655) (Friday, 1 March)
• Re: [heycam/webidl] Clean up some parts of object creation (#663) (Friday, 1 March)
• Re: [heycam/webidl] Is a subclass still a platform object? (#540) (Friday, 1 March)
• Re: [heycam/webidl] Editorial: improve language around conversions to JS (#664) (Friday, 1 March)
• [heycam/webidl] Editorial: fix some bikeshed link warnings (#672) (Friday, 1 March)
• Re: [heycam/webidl] Deduplicate unforgeable member functions (#668) (Friday, 1 March)
• Re: [heycam/webidl] [[DefineOwnProperty]] for legacy objects should not force configurability (#669) (Friday, 1 March)
• [heycam/webidl] Disallow combining an indexed getter with a maplike/setlike (#671) (Friday, 1 March)

Mu-An 慕安

• Re: [w3c/webcomponents] Spring 2019 F2F Agenda (#802) (Thursday, 28 March)

Mustaq Ahmed

• Re: [w3ctag/design-reviews] User Activation Delegation through postMessages (#347) (Friday, 29 March)
• Re: [w3c/pointerlock] movementX/Y coordinate space (#42) (Monday, 25 March)
• Re: [w3c/pointerlock] movementX/Y coordinate space (#42) (Monday, 25 March)
• Re: [w3ctag/design-reviews] TAG review request: User Activation Delegation through postMessages (#347) (Wednesday, 20 March)
• Re: [w3ctag/design-reviews] TAG review request: User Activation Delegation through postMessages (#347) (Friday, 1 March)

Myles Borins

• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Tuesday, 26 March)

Narongrit Pilantasnarat

• Re: [whatwg/fetch] "typedef (sequence<sequence<ByteString>> or reco..." (#876) (Thursday, 7 March)
• Re: [whatwg/fetch] "typedef (sequence<sequence<ByteString>> or reco..." (#876) (Thursday, 7 March)
• [whatwg/fetch] "typedef (sequence<sequence<ByteString>> or reco..." (#876) (Thursday, 7 March)

Navid Zolghadr

• Re: [w3ctag/design-reviews] Pointerevent extension (#346) (Tuesday, 26 March)
• Re: [w3ctag/design-reviews] Pointerevent extension (#346) (Tuesday, 26 March)
• Re: [w3ctag/design-reviews] Pointerevent extension (#346) (Tuesday, 26 March)
• Re: [w3ctag/design-reviews] Pointerevent extension (#346) (Monday, 25 March)
• Re: [w3c/pointerlock] movementX/Y coordinate space (#42) (Monday, 25 March)
• Re: [w3ctag/design-reviews] Pointerevent extension (#346) (Friday, 22 March)
• Re: [w3ctag/design-reviews] Pointerevent extension (#346) (Thursday, 14 March)

Nicolas Cordier

• Re: [whatwg/fetch] Request with GET/HEAD method cannot have body. (#551) (Thursday, 28 March)

npm1

• Re: [w3ctag/design-reviews] Element Timing API for img (#326) (Tuesday, 19 March)

peria

• [heycam/webidl] Add [AllowShared] in the list of applicable-to-types (#695) (Monday, 25 March)
• Re: [heycam/webidl] Is [AllowShared] an applicable-to-types attribute? (#687) (Friday, 15 March)
• Re: [heycam/webidl] Is [AllowShared] an applicable-to-types attribute? (#687) (Friday, 15 March)
• [heycam/webidl] Is [AllowShared] an applicable-to-types attribute? (#687) (Friday, 15 March)

Peter Linss

• Re: [w3ctag/design-reviews] User Activation Delegation through postMessages (#347) (Friday, 29 March)
• Re: [w3ctag/design-reviews] HTTP State Tokens (#297) (Thursday, 28 March)
• Re: [w3ctag/design-reviews] User Activation Delegation through postMessages (#347) (Wednesday, 27 March)
• [w3ctag/design-reviews] Harmonize permissions and similar mechanisms (#360) (Wednesday, 27 March)

Philip Jägenstedt

• Re: [whatwg/fullscreen] How :fullscreen CSS pseudo class works in shadow dom? (#149) (Wednesday, 20 March)
• Re: [whatwg/fullscreen] How :fullscreen CSS pseudo class works in shadow dom? (#149) (Wednesday, 20 March)
• Re: [w3c/screen-orientation] Deal with fragment navigation (#87) (Thursday, 14 March)

phurunbit

• Re: [whatwg/fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) (Friday, 15 March)

Pierre-Marie Dartus

• Re: [whatwg/dom] Composed and non bubbling event semantic dispatched in shadow tree (#742) (Tuesday, 26 March)
• [whatwg/dom] Composed and non bubbling event semantic dispatched in shadow tree (#742) (Tuesday, 26 March)

Pieter Colpaert

• Re: [whatwg/fetch] CORS: arbitrary blocking of accept header based on length (#862) (Wednesday, 27 March)
• Re: [whatwg/fetch] CORS: arbitrary blocking of accept header based on length (#862) (Wednesday, 27 March)
• Re: [whatwg/fetch] CORS: arbitrary blocking of accept header based on length (#862) (Wednesday, 27 March)
• Re: [whatwg/fetch] CORS: arbitrary blocking of accept header based on length (#862) (Wednesday, 27 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)
• Re: [whatwg/fetch] CORS: arbitrary blocking of accept header based on length (#862) (Friday, 8 March)
• Re: [whatwg/fetch] CORS: arbitrary blocking of accept header based on length (#862) (Friday, 8 March)

port25

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

Randall Leeds

• Re: [w3c/selection-api] Add Selection/Range methods based on anchestor element (#102) (Friday, 1 March)

raymeskhoury

• Re: [w3c/manifest] App shortcuts / actions (#582) (Friday, 22 March)

Reilly Grant

• Re: [w3c/manifest] Explicit requirements/capabilities section (#756) (Tuesday, 12 March)

Rich Harris

• Re: [w3c/webcomponents] CSS Modules (#759) (Wednesday, 6 March)

Richard Bushell

• Re: [whatwg/fullscreen] Introduce document.exitFullscreen({ fully: true })? (#70) (Thursday, 7 March)
• Re: [whatwg/fullscreen] Introduce document.exitFullscreen({ fully: true })? (#70) (Thursday, 7 March)
• Re: [whatwg/fullscreen] Introduce document.exitFullscreen({ fully: true })? (#70) (Sunday, 3 March)
• Re: [whatwg/fullscreen] Introduce document.exitFullscreen({ fully: true })? (#70) (Sunday, 3 March)
• Re: [whatwg/fullscreen] Introduce document.exitFullscreen({ fully: true })? (#70) (Sunday, 3 March)
• Re: [whatwg/fullscreen] MDN Cross-Reference Docs Clarification on fullscreenchange (#148) (Sunday, 3 March)
• Re: [whatwg/fullscreen] MDN Cross-Reference Docs Clarification on fullscreenchange (#148) (Sunday, 3 March)
• Re: [whatwg/fullscreen] MDN Cross-Reference Docs Clarification on fullscreenchange (#148) (Sunday, 3 March)
• Re: [whatwg/fullscreen] Introduce document.exitFullscreen({ fully: true })? (#70) (Sunday, 3 March)
• [whatwg/fullscreen] MDN Cross-Reference Docs Clarification on fullscreenchange (#148) (Saturday, 2 March)

Rijubrata Bhaumik

• Re: [w3ctag/design-reviews] TAG review request: MediaStream Image Capture API (Pan/Tilt feature) (#358) (Tuesday, 26 March)
• Re: [w3ctag/design-reviews] TAG review request: MediaStream Image Capture API (Pan/Tilt feature) (#358) (Tuesday, 26 March)
• Re: [w3ctag/design-reviews] TAG review request: MediaStream Image Capture API (Pan/Tilt feature) (#358) (Tuesday, 26 March)
• [w3ctag/design-reviews] TAG review request: MediaStream Image Capture API (Pan/Tilt feature) (#358) (Tuesday, 26 March)

Rob Sanderson

• Re: [w3ctag/design-reviews] Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312) (Friday, 1 March)

Rob Wormald

• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Thursday, 28 March)

Robat Williams

• Re: [w3c/uievents] Identify which of multiple keyboards an event came from (#226) (Saturday, 9 March)
• Re: [w3c/uievents] Identify which of multiple keyboards an event came from (#226) (Thursday, 7 March)
• [w3c/uievents] Identify which of multiple keyboards an event came from (#226) (Thursday, 7 March)

Robert Wlaschin

• Re: [whatwg/fetch] Request with GET/HEAD method cannot have body. (#551) (Friday, 29 March)

Rodriguez2014

• Re: [whatwg/dom] Allow removing event listeners by group (#469) (Monday, 4 March)

Ruben Verborgh

• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Monday, 11 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Saturday, 9 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)
• Re: [whatwg/fetch] CORS: arbitrary blocking of accept header based on length (#862) (Friday, 8 March)
• Re: [whatwg/fetch] Allow servers to take full responsibility of cross-origin resource protection (#865) (Friday, 8 March)
• Re: [whatwg/fetch] Allow servers to take full responsibility of cross-origin resource protection (#865) (Friday, 8 March)
• [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)

Ryan

• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Tuesday, 19 March)

Ryosuke Niwa

• Re: [whatwg/dom] isEqualNode and <template> (#737) (Sunday, 31 March)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Saturday, 30 March)
• Re: [whatwg/dom] isEqualNode and <template> (#737) (Saturday, 30 March)
• Re: [whatwg/dom] Don't allow adopting DocumentFragment of a template element (#744) (Saturday, 30 March)
• [whatwg/dom] Don't allow adopting DocumentFragment of a template element (#744) (Saturday, 30 March)
• Re: [whatwg/dom] isEqualNode and <template> (#737) (Saturday, 30 March)
• Re: [w3c/webcomponents] Spring 2019 F2F Agenda (#802) (Thursday, 28 March)
• Re: [whatwg/dom] Composed and non bubbling event semantic dispatched in shadow tree (#742) (Wednesday, 27 March)
• Re: [w3c/webcomponents] Spring 2019 F2F Agenda (#802) (Wednesday, 27 March)
• Re: [w3c/webcomponents] Spring 2019 F2F Agenda (#802) (Wednesday, 27 March)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Tuesday, 26 March)
• Re: [whatwg/dom] Composed and non bubbling event semantic dispatched in shadow tree (#742) (Tuesday, 26 March)
• Re: [w3c/webcomponents] Fix HTML Modules demo links (#803) (Tuesday, 26 March)
• Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) (Tuesday, 26 March)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Saturday, 23 March)
• Re: [w3c/webcomponents] Spring 2019 F2F Agenda (#802) (Saturday, 23 March)
• Re: [w3c/selection-api] Expose with which bidi-level caret is affiliated as well as API to set it (#57) (Saturday, 23 March)
• Re: [w3c/webcomponents] Is there a way to detect if a custom element was constructed during parsing? (#789) (Tuesday, 19 March)
• Re: [w3c/webcomponents] Is there a way to detect if a custom element was constructed during parsing? (#789) (Tuesday, 19 March)
• Re: [w3c/webcomponents] Is there a way to detect if a custom element was constructed during parsing? (#789) (Tuesday, 19 March)
• Re: [w3c/webcomponents] Is there a way to detect if a custom element was constructed during parsing? (#789) (Tuesday, 19 March)
• Re: [w3c/webcomponents] Spring 2019 F2F Agenda (#802) (Monday, 18 March)
• Re: [w3c/webcomponents] Is there a way to detect if a custom element was constructed during parsing? (#789) (Monday, 18 March)
• Re: [w3c/webcomponents] Is there a way to detect if a custom element was constructed during parsing? (#789) (Monday, 18 March)
• Re: [w3c/webcomponents] Spring 2019 F2F Agenda (#802) (Friday, 15 March)
• Re: [whatwg/dom] Dispatching slotchange within a compound microtask (#734) (Friday, 15 March)
• Re: [w3c/webcomponents] Spring 2019 F2F Agenda (#802) (Friday, 15 March)
• Re: [w3c/webcomponents] Spring 2019 F2F Agenda (#802) (Thursday, 14 March)
• Re: [w3c/webcomponents] Spring 2019 F2F Agenda (#802) (Thursday, 14 March)
• Re: [w3c/webcomponents] Spring 2019 F2F Agenda (#802) (Wednesday, 13 March)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Wednesday, 13 March)
• [w3c/webcomponents] Spring 2019 F2F Agenda (#802) (Wednesday, 13 March)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Monday, 11 March)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Monday, 11 March)
• Re: [w3c/webcomponents] SVG use element can't reference an element within the same shadow tree (#772) (Sunday, 10 March)
• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Sunday, 10 March)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Wednesday, 6 March)
• Re: [w3c/selection-api] Add Selection/Range methods based on anchestor element (#102) (Monday, 4 March)
• Re: [w3c/selection-api] Add Selection/Range methods based on anchestor element (#102) (Monday, 4 March)
• Re: [w3c/webcomponents] Question: where to incubate HTML modules? (#794) (Monday, 4 March)
• Re: [whatwg/dom] Capturing event listeners are called during bubbling phase for shadow hosts (#685) (Friday, 1 March)
• Re: [w3c/selection-api] Add Selection/Range methods based on anchestor element (#102) (Friday, 1 March)
• Re: [whatwg/dom] Capturing event listeners are called during bubbling phase for shadow hosts (#685) (Friday, 1 March)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Friday, 1 March)

S.A.N

• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Friday, 15 March)

sam goto

• Re: [w3ctag/design-reviews] User Idle Detection (#336) (Wednesday, 20 March)
• Re: [w3ctag/design-reviews] User Idle Detection (#336) (Thursday, 7 March)
• Re: [w3ctag/design-reviews] User Idle Detection (#336) (Thursday, 7 March)
• Re: [w3ctag/design-reviews] User Idle Detection (#336) (Monday, 4 March)

Sebastian Müller

• Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) (Thursday, 28 March)

sebastiankb

• Re: [w3ctag/design-reviews] Web of Things (WoT) Thing Description (#357) (Tuesday, 26 March)

shahnad

• [whatwg/xhr] O- (#240) (Wednesday, 6 March)

Shiino Yuki

• Re: [heycam/webidl] Stop using extended attributes for constructors (#636) (Monday, 11 March)
• Re: [heycam/webidl] Stop using extended attributes for constructors (#636) (Friday, 8 March)
• Re: [heycam/webidl] Stop using extended attributes for constructors (#636) (Friday, 8 March)

Shrey Banga

• Re: [w3c/editing] Disambiguate caret position at wrapped line boundaries (#189) (Friday, 22 March)

simon

• Re: [w3ctag/design-reviews] Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312) (Friday, 1 March)

sleevi

• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Thursday, 21 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)
• Re: [whatwg/fetch] Proposal: Allow servers to take full responsibility for cross-origin access protection (#878) (Friday, 8 March)

smaug----

• Re: [w3ctag/design-reviews] Pointerevent extension (#346) (Friday, 29 March)
• Re: [whatwg/dom] Dispatching slotchange within a compound microtask (#734) (Tuesday, 19 March)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Friday, 1 March)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Friday, 1 March)

Stef Busking

• Re: [w3c/DOM-Parsing] Error thrown when resetting the default namespace to null on a prefixed element (#48) (Friday, 22 March)
• [w3c/DOM-Parsing] Do not forbid resetting the default namespace… (#49) (Friday, 22 March)
• Re: [w3c/DOM-Parsing] Error thrown when resetting the default namespace to null on a prefixed element (#48) (Friday, 22 March)
• [w3c/DOM-Parsing] Error thrown when resetting the default namespace to null on a prefixed element (#48) (Friday, 22 March)

Sultan Tarimo

• Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736) (Monday, 11 March)

Surma

• Re: [whatwg/streams] Make it clear that a chunk size has to be non-negative (#999) (Sunday, 24 March)
• [whatwg/streams] Make it clear that a chunk size has to be non-negative (#999) (Saturday, 23 March)

Tab Atkins Jr.

• Re: [w3c/webcomponents] Shadow tree encapsulation and CSS (#804) (Thursday, 28 March)
• Re: [w3c/webcomponents] Shadow tree encapsulation and CSS (#804) (Thursday, 28 March)
• Re: [w3c/webcomponents] Shadow tree encapsulation and CSS (#804) (Thursday, 28 March)
• Re: [w3c/webcomponents] Shadow tree encapsulation and CSS (#804) (Thursday, 28 March)
• Re: [w3c/webcomponents] Shadow tree encapsulation and CSS (#804) (Thursday, 28 March)
• Re: [heycam/webidl] Correct the 'indexed getter' cross-reference (#679) (Monday, 11 March)
• Re: [heycam/webidl] Correct the 'indexed getter' cross-reference (#679) (Friday, 8 March)

Takashi Toyoshima

• Re: [whatwg/fetch] Safelist request headers starting with `Sec-` (#880) (Monday, 18 March)
• Re: [whatwg/fetch] Safelist request headers starting with `Sec-` (#880) (Monday, 18 March)

TAMURA, Kent

• Re: [w3c/webcomponents] Spring 2019 F2F Agenda (#802) (Friday, 15 March)
• Re: [w3c/DOM-Parsing] XML null namespaces need to be preserved (#47) (Friday, 15 March)
• Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Friday, 15 March)
• Re: [w3c/DOM-Parsing] XML null namespaces need to be preserved (#47) (Thursday, 14 March)
• Re: [w3c/webcomponents] Spring 2019 F2F Agenda (#802) (Wednesday, 13 March)
• Re: [w3c/DOM-Parsing] XML null namespaces need to be preserved (#47) (Tuesday, 12 March)
• Re: [w3c/DOM-Parsing] XML null namespaces need to be preserved (#47) (Tuesday, 12 March)
• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Friday, 8 March)

Theo

• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Friday, 1 March)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Friday, 1 March)
• Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713) (Friday, 1 March)

Thomas Allmer

• Re: [w3c/webcomponents] appreciate your feedback for custom element diagram (#784) (Sunday, 3 March)
• Re: [w3c/webcomponents] appreciate your feedback for custom element diagram (#784) (Sunday, 3 March)

Thomas Steiner

• Re: [w3c/manifest] App shortcuts / actions (#582) (Saturday, 30 March)
• Re: [w3c/manifest] Support a way to update explicitly (#446) (Friday, 22 March)
• Re: [w3c/manifest] Add a `color_scheme` member to `ImageResource` (#758) (Friday, 22 March)
• Re: [w3c/manifest] Add a `color_scheme` member to `ImageResource` (#758) (Friday, 22 March)
• [w3c/permissions] Semantic Permission Bundles (#191) (Thursday, 14 March)
• Re: [w3ctag/design-reviews] User Idle Detection (#336) (Wednesday, 6 March)

Thomas Wisniewski

• [w3c/FileAPI] Consider reserializing type attributes, not just parsing them. (#123) (Saturday, 30 March)
• [w3c/FileAPI] Consider dropping lowercasing requirement for the type attribute (#122) (Saturday, 30 March)

Timothy Gu

• Re: [whatwg/url] Define domain label (#435) (Thursday, 28 March)
• Re: [whatwg/url] Restructure URL rendering section and add additional guidance (#434) (Monday, 25 March)
• Re: [heycam/webidl] Disallow combining an indexed getter with a maplike/setlike (#671) (Tuesday, 5 March)

Tobie Langel

• Re: [w3ctag/design-reviews] User Idle Detection (#336) (Monday, 11 March)
• Re: [heycam/webidl] Editorial: marking former editors as such (#685) (Sunday, 10 March)
• [heycam/webidl] Editorial: marking former editors as such (#685) (Sunday, 10 March)

Tomek Wytrębowicz

• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Monday, 25 March)

Travis Leithead

• Re: [w3ctag/design-reviews] Verifiable Credentials Data Model 1.0 (#343) (Wednesday, 27 March)
• Re: [w3c/webcomponents] Spring 2019 F2F Agenda (#802) (Wednesday, 13 March)
• Re: [w3c/webcomponents] Question: where to incubate HTML modules? (#794) (Thursday, 7 March)
• Re: [w3c/webcomponents] Add list of major open design questions to HTML Modules proposal doc (#801) (Wednesday, 6 March)
• Re: [w3c/webcomponents] Add list of major open design questions to HTML Modules proposal doc (#801) (Wednesday, 6 March)
• Re: [w3c/webcomponents] Add list of major open design questions to HTML Modules proposal doc (#801) (Wednesday, 6 March)
• Re: [w3c/webcomponents] Question: where to incubate HTML modules? (#794) (Wednesday, 6 March)
• Re: [w3c/uievents] Should we dispatch a keypress event when spacebar is used to activate an element (#225) (Wednesday, 6 March)
• Re: [heycam/webidl] Conversion from specification values to IDL values to ECMAScript values (#674) (Tuesday, 5 March)
• Re: [heycam/webidl] Conversion from specification values to IDL values to ECMAScript values (#674) (Tuesday, 5 March)
• Re: [w3c/webcomponents] Question: where to incubate HTML modules? (#794) (Monday, 4 March)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Friday, 1 March)
• Re: [w3c/webcomponents] Move HTML Module Record definition from ES spec to HTML5 spec (#796) (Friday, 1 March)

triple-underscore

• Re: [heycam/webidl] Disallow combining an indexed getter with a maplike/setlike (#671) (Thursday, 7 March)

Tsuyoshi Horo

• Re: [w3ctag/design-reviews] Subresource prefetching+loading via Signed HTTP Exchange (#352) (Friday, 15 March)
• [w3ctag/design-reviews] Signed Exchange subresource prefetching (#352) (Tuesday, 12 March)

Victor Costan

• Re: [w3c/IndexedDB] feature-request - add appendFile capability to overcome nedb performance-bottleneck (#260) (Thursday, 28 March)

Vincent Weevers

• Re: [w3c/IndexedDB] feature-request - add appendFile capability to overcome nedb performance-bottleneck (#260) (Thursday, 28 March)

Wendy Seltzer

• Re: [w3ctag/design-reviews] ads.txt (#201) (Wednesday, 6 March)

William J. Edney

• Re: [w3c/DOM-Parsing] XML null namespaces need to be preserved (#47) (Thursday, 14 March)
• Re: [w3c/DOM-Parsing] XML null namespaces need to be preserved (#47) (Tuesday, 12 March)
• Re: [w3c/DOM-Parsing] XML null namespaces need to be preserved (#47) (Tuesday, 12 March)
• Re: [w3c/DOM-Parsing] XML null namespaces need to be preserved (#47) (Tuesday, 12 March)
• Re: [w3c/DOM-Parsing] XML null namespaces need to be preserved (#47) (Tuesday, 12 March)
• [w3c/DOM-Parsing] XML null namespaces are not preserved (#47) (Monday, 11 March)

Xidorn Quan

• Re: [whatwg/fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) (Saturday, 16 March)
• Re: [whatwg/fullscreen] Introduce document.exitFullscreen({ fully: true })? (#70) (Thursday, 7 March)
• Re: [whatwg/fullscreen] Introduce document.exitFullscreen({ fully: true })? (#70) (Thursday, 7 March)
• Re: [whatwg/fullscreen] Introduce document.exitFullscreen({ fully: true })? (#70) (Sunday, 3 March)
• Re: [whatwg/fullscreen] Introduce document.exitFullscreen({ fully: true })? (#70) (Sunday, 3 March)
• Re: [whatwg/fullscreen] MDN Cross-Reference Docs Clarification on fullscreenchange (#148) (Sunday, 3 March)
• Re: [whatwg/fullscreen] MDN Cross-Reference Docs Clarification on fullscreenchange (#148) (Sunday, 3 March)
• Re: [whatwg/fullscreen] Introduce document.exitFullscreen({ fully: true })? (#70) (Sunday, 3 March)
• Re: [whatwg/fullscreen] Introduce document.exitFullscreen({ fully: true })? (#70) (Sunday, 3 March)

Yoav Weiss

• Re: [whatwg/fetch] Remove Client Hints (#884) (Saturday, 23 March)
• Re: [whatwg/fetch] Remove Client Hints (#884) (Saturday, 23 March)
• Re: [whatwg/fetch] Add a speculative flag to `Request` as well as related processing (#881) (Friday, 22 March)
• Re: [whatwg/fetch] Add a speculative flag to `Request` as well as related processing (#881) (Thursday, 21 March)
• Re: [whatwg/fetch] Safelist request headers starting with `Sec-` (#880) (Thursday, 21 March)
• Re: [whatwg/fetch] Add a speculative flag to `Request` as well as related processing (#881) (Thursday, 21 March)
• Re: [whatwg/fetch] Add a speculative flag to `Request` as well as related processing (#881) (Thursday, 21 March)
• Re: [whatwg/fetch] Add a speculative flag to `Request` as well as related processing (#881) (Thursday, 21 March)
• Re: [whatwg/fetch] Add a speculative flag to `Request` as well as related processing (#881) (Thursday, 21 March)
• Re: [whatwg/fetch] Add a speculative flag to `Request` as well as related processing (#881) (Thursday, 21 March)
• Re: [whatwg/fetch] Add a speculative flag to `Request` as well as related processing (#881) (Thursday, 21 March)
• Re: [whatwg/fetch] Safelist request headers starting with `Sec-` (#880) (Thursday, 21 March)
• Re: [whatwg/fetch] Safelist request headers starting with `Sec-` (#880) (Thursday, 21 March)
• Re: [w3ctag/design-reviews] Priority Hints API (#241) (Wednesday, 20 March)
• Re: [whatwg/fetch] Add a speculative flag to `Reqeust` as well as related processing (#881) (Tuesday, 19 March)
• Re: [whatwg/fetch] Add a speculative flag to `Reqeust` as well as related processing (#881) (Tuesday, 19 March)
• [whatwg/fetch] Add a speculative flag to `Reqeust` as well as related processing (#881) (Tuesday, 19 March)
• Re: [whatwg/fetch] Align CH processing model with implementation and HTML#3774 (#773) (Monday, 18 March)
• Re: [whatwg/fetch] Safelist request headers starting with `Sec-` (#880) (Monday, 18 March)
• Re: [whatwg/fetch] Safelist request headers starting with `Sec-` (#880) (Monday, 18 March)
• Re: [whatwg/fetch] Safelist request headers starting with `Sec-` (#880) (Monday, 18 March)
• Re: [whatwg/fetch] Safelist request headers starting with `Sec-` (#880) (Monday, 18 March)
• Re: [whatwg/fetch] Safelist request headers starting with `Sec-` (#880) (Monday, 18 March)
• Re: [whatwg/fetch] Safelist request headers starting with `Sec-` (#880) (Monday, 18 March)
• [whatwg/fetch] Safelist request headers starting with `Sec-` (#880) (Monday, 18 March)
• Re: [whatwg/fetch] Consider splitting `document` into `document` and `nested-document`. (#755) (Thursday, 14 March)
• Re: [whatwg/fetch] Consider splitting `document` into `document` and `nested-document`. (#755) (Thursday, 14 March)
• Re: [whatwg/fetch] Consider splitting `document` into `document` and `nested-document`. (#755) (Thursday, 14 March)
• Re: [whatwg/fetch] Consider splitting `document` into `document` and `nested-document`. (#755) (Thursday, 14 March)

youennf

• Re: [whatwg/fetch] Add a speculative flag to `Request` as well as related processing (#881) (Friday, 22 March)

Yutaka Hirano

• Re: [whatwg/fetch] Tests do not always require Origin header when mode is "cors" (#871) (Wednesday, 13 March)
• Re: [whatwg/fetch] Tests do not always require Origin header when mode is "cors" (#871) (Wednesday, 13 March)

Yves Lafon

• Re: [w3ctag/design-reviews] hrefTranslate attribute (#301) (Thursday, 7 March)

zafar4u

• Re: [whatwg/url] Review Draft Publication: February 2019 (c4f729a) (Thursday, 7 March)
• Re: [whatwg/url] Snap be (#433) (Thursday, 7 March)
• [whatwg/url] Snap be (#433) (Thursday, 7 March)

Zamralik

• Re: [whatwg/fetch] Request with GET/HEAD method cannot have body. (#551) (Friday, 29 March)
• Re: [whatwg/fetch] Request with GET/HEAD method cannot have body. (#551) (Friday, 29 March)

Zirro

• [whatwg/dom] Reference to struct in inner invoke (#738) (Tuesday, 19 March)

慕安

• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Friday, 1 March)

Last message date: Sunday, 31 March 2019 23:28:39 UTC