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

aaronsn

• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Wednesday, 2 January)

achristensen07

• Re: [whatwg/url] searchParams.set("param", undefined) should not stringify as param=undefined (#427) (Tuesday, 29 January)

Adam Rice

• [whatwg/streams] "npm run coverage" is no longer working (#981) (Thursday, 31 January)
• Re: [whatwg/streams] Switching to Web IDL (#963) (Thursday, 31 January)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Wednesday, 30 January)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Wednesday, 30 January)
• Re: [whatwg/streams] ReadableStream should be an async iterable (#778) (Tuesday, 29 January)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Tuesday, 29 January)
• Re: [whatwg/streams] add @@asyncIterator to ReadableStream (#954) (Thursday, 24 January)
• Re: [whatwg/streams] add @@asyncIterator to ReadableStream (#954) (Thursday, 24 January)
• Re: [whatwg/streams] add @@asyncIterator to ReadableStream (#954) (Tuesday, 22 January)
• Re: [whatwg/encoding] Editorial: less than or equal to (#170) (Wednesday, 9 January)
• Re: [whatwg/encoding] Define encodeInto() API (#166) (Tuesday, 8 January)
• Re: [whatwg/streams] Editorial changes to transferable streams explainer (#977) (Tuesday, 8 January)
• Re: [whatwg/streams] Editorial changes to transferable streams explainer (#977) (Tuesday, 8 January)

Addison Phillips

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

ajeeshc

• [w3c/ServiceWorker] Service worker not intercepting the call intiated for CSS from JS files “ css:”css/custom.css" (#1386) (Monday, 28 January)

Alex Inkin

• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Tuesday, 29 January)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Tuesday, 29 January)
• Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) (Monday, 14 January)

Alex Russell

• Re: [w3ctag/design-reviews] TextEncoderStream and TextDecoderStream (#282) (Tuesday, 8 January)
• Re: [w3ctag/design-reviews] IntersectionObserver V2 (#328) (Tuesday, 8 January)

Alexandre Gaudencio

• Re: [whatwg/fetch] SameSite cookies aren't sent on credentialed CORS requests (#769) (Thursday, 31 January)
• Re: [whatwg/fetch] SameSite cookies aren't sent on credentialed CORS requests (#769) (Thursday, 31 January)
• Re: [whatwg/fetch] SameSite cookies aren't sent on credentialed CORS requests (#769) (Thursday, 31 January)

aliams

• Re: [w3c/ServiceWorker] "no-cors" CSS SOP violation (#719) (Thursday, 3 January)

aliraj

• Re: [heycam/webidl] @shadulsikder90 can you please explain what this issue is about? (#629) (Wednesday, 23 January)
• [heycam/webidl] @shadulsikder90 can you please explain what this issue is about? (#629) (Wednesday, 23 January)
• [heycam/webidl] Intent to use Constants (#627) (Sunday, 20 January)

Amelia Bellamy-Royds

• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Tuesday, 8 January)

Andrea Giammarchi

• Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550) (Monday, 28 January)
• Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550) (Monday, 28 January)
• Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550) (Monday, 28 January)

Andrea Marchesini

• Re: [whatwg/xhr] FormData constructor should throw if "constructing the entry list" re… (#231) (Friday, 11 January)

Andreas

• Re: [w3c/webcomponents] appreciate your feedback for custom element diagram (#784) (Saturday, 26 January)
• Re: [w3c/webcomponents] appreciate your feedback for custom element diagram (#784) (Saturday, 26 January)
• [w3c/webcomponents] appreciate your feedback for custom element diagram (#784) (Wednesday, 23 January)

andreas-butler

• Re: [w3ctag/design-reviews] IndexedDB Transaction Explicit Commit API (#316) (Wednesday, 23 January)
• Re: [w3ctag/design-reviews] IndexedDB Transaction Explicit Commit API (#316) (Wednesday, 23 January)

Andrew Levine

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

Andrew Sutherland

• Re: [w3c/ServiceWorker] Add a script version property to the ServiceWorker object (#1387) (Thursday, 31 January)
• Re: [w3c/IndexedDB] Disallow starting readwrite transactions while readonly transactions are running? (#253) (Monday, 28 January)
• Re: [w3c/IndexedDB] Disallow starting readwrite transactions while readonly transactions are running? (#253) (Wednesday, 23 January)
• Re: [w3c/ServiceWorker] Update shouldn't fail due to MIME check or 404 for the incumbent's worker scripts (#1374) (Friday, 18 January)

Andrey Lushnikov

• Re: [GoogleChrome/puppeteer] Query nodes within shadow roots (#858) (Thursday, 10 January)
• Re: [GoogleChrome/puppeteer] Query nodes within shadow roots (#858) (Thursday, 10 January)

Andy Earnshaw

• Re: [w3c/webcomponents] [idea] making builtin elements more like custom elements (#785) (Monday, 28 January)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Monday, 28 January)
• Re: [whatwg/dom] addEventListener defer option to call that handler after all other handlers run (#730) (Tuesday, 22 January)
• Re: [whatwg/dom] addEventListener defer option to call that handler after all other handlers run (#730) (Monday, 21 January)
• [whatwg/dom] addEventListener defer option to call that handler after all other handlers run (#730) (Monday, 21 January)
• Re: [w3c/webcomponents] Lazy Custom Element Definitions (#782) (Monday, 21 January)
• Re: [w3c/webcomponents] Lazy Custom Element Definitions (#782) (Wednesday, 16 January)
• Re: [w3c/webcomponents] [Shadow]: return of multiple shadow roots? (#780) (Sunday, 13 January)
• [w3c/webcomponents] [Shadow]: return of multiple shadow roots? (#780) (Monday, 7 January)

Anirvann

• Re: [w3c/ServiceWorker] Allow Caching of POST requests (#977) (Wednesday, 23 January)

Anne van Kesteren

• Re: [heycam/webidl] Meta: point out commit instructions (#634) (Thursday, 31 January)
• Re: [w3c/webcomponents] HTML module should require a new top level element (#752) (Thursday, 31 January)
• Re: [w3c/webcomponents] HTML module should require a new MIME type (#742) (Thursday, 31 January)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Thursday, 31 January)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Thursday, 31 January)
• [heycam/webidl] Meta: point out commit instructions (#634) (Thursday, 31 January)
• Re: [heycam/webidl] Check ignoreNamedProps before the named property visibility algorithm. (#625) (Thursday, 31 January)
• Re: [heycam/webidl] Standardize around typography of IDL true/false/null (#457) (Thursday, 31 January)
• Re: [heycam/webidl] Check ignoreNamedProps before the named property visibility algorithm. (#625) (Thursday, 31 January)
• Re: [heycam/webidl] Check ignoreNamedProps before the named property visibility algorithm. (#625) (Thursday, 31 January)
• Re: [heycam/webidl] Editorial: Use some more abstract operations. (#601) (Thursday, 31 January)
• Re: [w3c/webcomponents] HTML module should require a new MIME type (#742) (Thursday, 31 January)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Wednesday, 30 January)
• Re: [whatwg/fetch] fetch (#864) (Wednesday, 30 January)
• Re: [heycam/webidl] Disallow underscore-and-hyphen only identifiers (#633) (Wednesday, 30 January)
• Re: [heycam/webidl] Disallow underscore-and-hyphen only identifiers (#633) (Wednesday, 30 January)
• Re: [whatwg/fetch] CORS: arbitrary blocking of accept header based on length (#862) (Tuesday, 29 January)
• Re: [whatwg/fetch] CORS: arbitrary blocking of accept header based on length (#862) (Tuesday, 29 January)
• Re: [heycam/webidl] Better regular expression for identifiers (#632) (Tuesday, 29 January)
• Re: [whatwg/fetch] CORS: arbitrary blocking of accept header based on length (#862) (Tuesday, 29 January)
• Re: [whatwg/fetch] CORS: arbitrary blocking of accept header based on length (#862) (Tuesday, 29 January)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Tuesday, 29 January)
• Re: [whatwg/fetch] IP address of response (#863) (Tuesday, 29 January)
• Re: [heycam/webidl] identifier needs to allow a leading hyphen (#564) (Tuesday, 29 January)
• Re: [heycam/webidl] Allow identifiers that start with a hyphen. (#612) (Tuesday, 29 January)
• Re: [heycam/webidl] Allow identifiers that start with a hyphen. (#612) (Tuesday, 29 January)
• [heycam/webidl] Better regular expression for identifiers (#632) (Tuesday, 29 January)
• Re: [heycam/webidl] Restrict the extended attributes for partial interfaces. (#620) (Tuesday, 29 January)
• Re: [w3c/DOM-Parsing] parseFromString() should be use case-insensitive MIME type matching (#40) (Tuesday, 29 January)
• Re: [w3c/DOM-Parsing] Spec out normative text when parseFromString() is passed an unsupported MIME type (#41) (Tuesday, 29 January)
• Re: [whatwg/url] searchParams.set("param", undefined) should not stringify as param=undefined (#427) (Tuesday, 29 January)
• Re: [whatwg/encoding] Big5 encoding mishandles some trailing bytes, with possible XSS (#171) (Tuesday, 29 January)
• Re: [w3c/DOM-Parsing] Spec out normative text when parseFromString() is passed an unsupported MIME type (#41) (Monday, 28 January)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Monday, 28 January)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Monday, 28 January)
• Re: [whatwg/fetch] CORS: arbitrary blocking of accept header based on length (#862) (Monday, 28 January)
• Re: [whatwg/fetch] Add Async Stale While Revalidate Handling (#853) (Monday, 28 January)
• Re: [whatwg/fetch] Add Async Stale While Revalidate Handling (#853) (Monday, 28 January)
• Re: [heycam/webidl] Rename the 'float' production to 'real'. (#616) (Monday, 28 January)
• Re: [heycam/webidl] "float" is the name of two distinct things in the grammar (#558) (Monday, 28 January)
• Re: [heycam/webidl] Rename the 'float' production to 'real'. (#616) (Monday, 28 January)
• Re: [whatwg/fetch] CORS: arbitrary blocking of accept header based on length (#862) (Monday, 28 January)
• Re: [heycam/webidl] Rename the 'float' production to 'real'. (#616) (Monday, 28 January)
• Re: [w3ctag/design-reviews] imagesrcset and imagesizes attributes on link rel=preload (#329) (Monday, 28 January)
• Re: [w3c/DOM-Parsing] Spec out normative text when parseFromString() is passed an unsupported MIME type (#41) (Monday, 28 January)
• Re: [w3c/DOM-Parsing] parseFromString() should be use case-insensitive MIME type matching (#40) (Monday, 28 January)
• Re: [whatwg/fetch] More CORB-protected MIME types - adding protected types one-by-one. (#860) (Friday, 25 January)
• Re: [whatwg/encoding] Big5 encoding mishandles some trailing bytes, with possible XSS (#171) (Friday, 25 January)
• Re: [whatwg/fetch] More CORB-protected MIME types - adding protected types one-by-one. (#860) (Thursday, 24 January)
• Re: [whatwg/encoding] Big5 encoding mishandles some trailing bytes, with possible XSS (#171) (Thursday, 24 January)
• Re: [whatwg/fullscreen] Review Draft Publication: January 2019 (#142) (Wednesday, 23 January)
• Re: [whatwg/fullscreen] Review Draft Publication: January 2019 (#142) (Wednesday, 23 January)
• [whatwg/fullscreen] Review Draft Publication: January 2019 (#143) (Wednesday, 23 January)
• Re: [whatwg/fetch] Change 3.2.6 Examples to reflect current state of implementations (#858) (Wednesday, 23 January)
• Re: [whatwg/fetch] Change 3.2.6 Examples to reflect current state of implementations (#858) (Wednesday, 23 January)
• Re: [whatwg/fetch] Change 3.2.6 Examples to reflect current state of implementations (#858) (Wednesday, 23 January)
• Re: [w3c/ServiceWorker] Correcting the use of types and simplifying the response body read. (#1384) (Tuesday, 22 January)
• Re: [w3c/ServiceWorker] Correcting the use of types and simplifying the response body read. (#1384) (Tuesday, 22 January)
• Re: [w3c/ServiceWorker] Correcting the use of types and simplifying the response body read. (#1384) (Tuesday, 22 January)
• Re: [w3c/ServiceWorker] Correcting the use of types and simplifying the response body read. (#1384) (Tuesday, 22 January)
• Re: [w3c/ServiceWorker] Correcting the use of types and simplifying the response body read. (#1384) (Tuesday, 22 January)
• Re: [w3c/ServiceWorker] Cache's put() says it clones the response (#1382) (Tuesday, 22 January)
• Re: [whatwg/fetch] EvalError refused to evaluate because CSP is defined to script-src set to 'self' 'unsafe-inline' (#861) (Tuesday, 22 January)
• Re: [whatwg/fetch] EvalError refused to evaluate because CSP is defined to script-src set to 'self' 'unsafe-inline' (#861) (Tuesday, 22 January)
• Re: [whatwg/xhr] Fix small grammer (#234) (Tuesday, 22 January)
• Re: [whatwg/dom] addEventListener defer option to call that handler after all other handlers run (#730) (Tuesday, 22 January)
• Re: [whatwg/xhr] Fix small grammer (#234) (Tuesday, 22 January)
• Re: [whatwg/fetch] Change 3.2.6 Examples to reflect current state of implementations (#858) (Tuesday, 22 January)
• Re: [whatwg/dom] addEventListener defer option to call that handler after all other handlers run (#730) (Monday, 21 January)
• Re: [w3c/ServiceWorker] Cache's put() says it clones the response (#1382) (Monday, 21 January)
• [w3c/ServiceWorker] Cache's put() says it clones the response (#1382) (Monday, 21 January)
• Re: [whatwg/fetch] More CORB-protected MIME types - adding protected types one-by-one. (#860) (Monday, 21 January)
• Re: [whatwg/xhr] Fix small grammer (#234) (Monday, 21 January)
• Re: [whatwg/xhr] Fix small grammer (#234) (Monday, 21 January)
• Re: [w3c/webcomponents] HTML modules spec draft editorial feedback (#783) (Monday, 21 January)
• Re: [whatwg/fetch] Add Async Stale While Revalidate Handling (#853) (Friday, 18 January)
• Re: [heycam/webidl] Check ignoreNamedProps before the named property visibility algorithm. (#625) (Friday, 18 January)
• [whatwg/fullscreen] Review Draft Publication: January 2019 (#142) (Friday, 18 January)
• Re: [heycam/webidl] Check ignoreNamedProps before the named property visibility algorithm. (#625) (Thursday, 17 January)
• Re: [heycam/webidl] Editorial: Remove section numbers from ES references. (#617) (Thursday, 17 January)
• Re: [heycam/webidl] Remove section numbers from ES references (#542) (Thursday, 17 January)
• Re: [heycam/webidl] Intent to use [TreatNonObjectAsNull] (#623) (Thursday, 17 January)
• Re: [whatwg/dom] Ground primitives in agents (#717) (Wednesday, 16 January)
• Re: [whatwg/dom] _Which_ unit of related similar-origin browsing contexts? (#88) (Wednesday, 16 January)
• Re: [heycam/webidl] Disallow a default value for required dictionary members in the grammar. (#622) (Wednesday, 16 January)
• Re: [whatwg/dom] Ground primitives in agents (#717) (Wednesday, 16 January)
• Re: [whatwg/dom] Ground primitives in agents (#717) (Wednesday, 16 January)
• Re: [whatwg/dom] Ground primitives in agents (#717) (Tuesday, 15 January)
• Re: [whatwg/dom] Ground primitives in agents (#717) (Tuesday, 15 January)
• Re: [whatwg/fetch] Cross-Origin-Resource-Policy (was: From-Origin) (#687) (Tuesday, 15 January)
• Re: [heycam/webidl] Editorial: Clarify the wording of an Exposed requirement. (#615) (Tuesday, 15 January)
• Re: [heycam/webidl] Editorial: Clarify the wording of an Exposed requirement. (#615) (Tuesday, 15 January)
• Re: [heycam/webidl] Poorly worded normative requirement could be improved (#548) (Tuesday, 15 January)
• Re: [heycam/webidl] Editorial: Clarify the wording of an Exposed requirement. (#615) (Tuesday, 15 January)
• Re: [heycam/webidl] Integer type conversions seem to return wrong type for unsigned types and long long (#579) (Tuesday, 15 January)
• Re: [heycam/webidl] Editorial: Refer to the correct types in integer conversion algorithms. (#613) (Tuesday, 15 January)
• Re: [heycam/webidl] Editorial: Refer to the correct types in integer conversion algorithms. (#613) (Tuesday, 15 January)
• Re: [whatwg/fetch] Change 3.2.6 Examples to reflect current state of implementations (#858) (Tuesday, 15 January)
• Re: [whatwg/dom] Bad "good first issue" labels (#729) (Tuesday, 15 January)
• Re: [whatwg/dom] Bad "good first issue" labels (#729) (Tuesday, 15 January)
• Re: [whatwg/fetch] Follow changes from whatwg/url#371. (#857) (Tuesday, 15 January)
• Re: [whatwg/fetch] Follow changes from whatwg/url#371. (#857) (Tuesday, 15 January)
• Re: [whatwg/fetch] Follow changes from whatwg/url#371. (#857) (Tuesday, 15 January)
• Re: [heycam/webidl] No mixin [NoInterfaceObject] usage (#430) (Tuesday, 15 January)
• Re: [whatwg/fetch] สวัสดี (#859) (Tuesday, 15 January)
• Re: [whatwg/fetch] Follow changes from whatwg/url#371. (#857) (Monday, 14 January)
• Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371) (Monday, 14 January)
• Re: [w3c/FileAPI] Fix Blob Origin (#20) (Monday, 14 January)
• Re: [w3c/FileAPI] "origin of a blob URL" is redundant/confusing (#63) (Monday, 14 January)
• Re: [whatwg/url] Origin of blob URLs doesn't match what implementations do (#127) (Monday, 14 January)
• Re: [whatwg/url] there can be more than one Blob URL Store (#290) (Monday, 14 January)
• Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371) (Monday, 14 January)
• Re: [w3c/FileAPI] Add readAsSharedArrayBuffer to FileReader (#73) (Monday, 14 January)
• Re: [whatwg/xhr] S (#233) (Monday, 14 January)
• Re: [heycam/webidl] Named properties object / named property visibility algorithm with property on Window.prototype (#607) (Friday, 11 January)
• Re: [whatwg/dom] Add a note about duplicate event listeners for removeEventListener (#722) (Friday, 11 January)
• Re: [whatwg/dom] Add a note about duplicate event listeners for removeEventListener (#722) (Friday, 11 January)
• Re: [whatwg/dom] Order of "contains" in removeEventListener (#664) (Friday, 11 January)
• Re: [whatwg/dom] Ground primitives in agents (#717) (Friday, 11 January)
• Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371) (Friday, 11 January)
• Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371) (Friday, 11 January)
• Re: [whatwg/fetch] Follow changes from whatwg/url#371. (#857) (Friday, 11 January)
• Re: [heycam/webidl] Allow overload resolution to "round down"? (#581) (Friday, 11 January)
• Re: [heycam/webidl] Allow overload resolution to "round down"? (#581) (Thursday, 10 January)
• Re: [heycam/webidl] Allow overload resolution to "round down"? (#581) (Thursday, 10 January)
• Re: [heycam/webidl] Give Location an immutable prototype object (#606) (Thursday, 10 January)
• Re: [heycam/webidl] Give Location an immutable prototype object (#606) (Thursday, 10 January)
• Re: [whatwg/xhr] Blob name (#232) (Thursday, 10 January)
• Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371) (Thursday, 10 January)
• Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371) (Thursday, 10 January)
• Re: [heycam/webidl] Give Location an immutable prototype object (#606) (Thursday, 10 January)
• [heycam/webidl] Give Location an immutable prototype object (#606) (Thursday, 10 January)
• Re: [w3c/webcomponents] [Shadow]: return of multiple shadow roots? (#780) (Thursday, 10 January)
• Re: [heycam/webidl] Detached ArrayBuffer objects should not throw (#605) (Thursday, 10 January)
• Re: [heycam/webidl] "get a copy of the bytes held by the buffer source" should not fail for detached buffers (#151) (Thursday, 10 January)
• Re: [heycam/webidl] Detached ArrayBuffer objects should not throw (#605) (Thursday, 10 January)
• Re: [heycam/webidl] Detached ArrayBuffer objects should not throw (#605) (Thursday, 10 January)
• Re: [heycam/webidl] [[ViewedArrayBuffer]] cannot be undefined during usage (#604) (Wednesday, 9 January)
• Re: [heycam/webidl] Detached ArrayBuffer objects should not throw (#605) (Wednesday, 9 January)
• Re: [whatwg/xhr] Blob name (#232) (Wednesday, 9 January)
• Re: [heycam/webidl] Detached ArrayBuffer objects should not throw (#605) (Wednesday, 9 January)
• [heycam/webidl] Detached ArrayBuffer objects should not throw (#605) (Wednesday, 9 January)
• Re: [heycam/webidl] [[ViewedArrayBuffer]] cannot be undefined during usage (#604) (Wednesday, 9 January)
• [heycam/webidl] [[ViewedArrayBuffer]] cannot be undefined during usage (#604) (Wednesday, 9 January)
• Re: [whatwg/dom] Composed tree infrastructure (#725) (Wednesday, 9 January)
• Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371) (Wednesday, 9 January)
• Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371) (Wednesday, 9 January)
• Re: [whatwg/encoding] Editorial: less than or equal to (#170) (Wednesday, 9 January)
• Re: [whatwg/encoding] Define encodeInto() API (#166) (Wednesday, 9 January)
• Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69) (Wednesday, 9 January)
• Re: [whatwg/encoding] Define encodeInto() API (#166) (Wednesday, 9 January)
• Re: [whatwg/encoding] Define encodeInto() API (#166) (Wednesday, 9 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Tuesday, 8 January)
• Re: [whatwg/url] Behaviour regarding percent-encoding of commas in URLSearchParams (#423) (Tuesday, 8 January)
• Re: [whatwg/xhr] FormData constructor should throw if "constructing the entry list" re… (#231) (Tuesday, 8 January)
• Re: [whatwg/encoding] Define encodeInto() API (#166) (Tuesday, 8 January)
• [whatwg/encoding] Editorial: less than or equal to (#170) (Tuesday, 8 January)
• Re: [whatwg/encoding] Define encodeInto() API (#166) (Tuesday, 8 January)
• Re: [whatwg/encoding] Define encodeInto() API (#166) (Tuesday, 8 January)
• Re: [whatwg/fetch] Doc: failed CORS fetch with credentials should ignore Set-Cookie response header (#855) (Tuesday, 8 January)
• Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371) (Tuesday, 8 January)
• Re: [whatwg/fetch] Consider "extract a MIME type and compare its essence" (#856) (Tuesday, 8 January)
• Re: [w3c/webcomponents] [Shadow]: return of multiple shadow roots? (#780) (Tuesday, 8 January)
• Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371) (Monday, 7 January)
• Re: [w3c/webcomponents] Element Behaviors, and the has="" attribute. A useful alternative to Custom Elements in many cases! (#727) (Monday, 7 January)
• Re: [heycam/webidl] A non-optional dictionary argument makes sense at times. (#130) (Monday, 7 January)
• [whatwg/fetch] Consider "extract a MIME type and compare its essence" (#856) (Monday, 7 January)
• Re: [whatwg/fetch] Doc: failed CORS fetch with credentials should ignore Set-Cookie response header (#855) (Monday, 7 January)
• Re: [whatwg/fetch] Doc: failed CORS fetch with credentials should ignore Set-Cookie response header (#855) (Friday, 4 January)
• Re: [whatwg/fetch] Doc: failed CORS fetch with credentials should ignore Set-Cookie response header (#855) (Friday, 4 January)
• Re: [whatwg/fetch] Doc: failed CORS fetch with credentials should ignore Set-Cookie response header (#855) (Friday, 4 January)
• Re: [w3c/webcomponents] Presence of disconnectedCallback can expedite an invocation of connectedCallback (#760) (Thursday, 3 January)
• Re: [whatwg/fetch] Consider removing trailers API (#772) (Thursday, 3 January)
• Re: [whatwg/fetch] CORB blocking JSON response after redirect (#854) (Thursday, 3 January)
• Re: [whatwg/fetch] Add option to reject the fetch promise automatically after a certain time elapsed (with no API for arbitrary aborts) (#179) (Wednesday, 2 January)
• Re: [whatwg/fetch] Add support for stale-while-revalidate handling (#852) (Wednesday, 2 January)
• Re: [whatwg/fetch] Add Async Stale While Revalidate Handling (#853) (Wednesday, 2 January)
• Re: [whatwg/dom] Events intro: Grammar/style tweaks (#723) (Wednesday, 2 January)
• Re: [whatwg/dom] This text needs to be proof-read for phrasing and grammar. (#718) (Wednesday, 2 January)
• Re: [whatwg/dom] Events intro: Grammar/style tweaks (#723) (Wednesday, 2 January)
• Re: [w3c/ServiceWorker] Can service workers mess with POST variables? (#1378) (Wednesday, 2 January)
• Re: [w3c/ServiceWorker] Can service workers mess with POST variables? (#1378) (Wednesday, 2 January)
• Re: [w3c/ServiceWorker] Can service workers mess with POST variables? (#1378) (Wednesday, 2 January)
• Re: [whatwg/dom] Fix a small but important error in composedPath() (#727) (Wednesday, 2 January)
• Re: [whatwg/dom] Fix a small but important error in composedPath() (#727) (Wednesday, 2 January)
• Re: [whatwg/xhr] FormData constructor should throw if "constructing the entry list" re… (#231) (Wednesday, 2 January)
• Re: [whatwg/xhr] FormData constructor should throw if "constructing the entry list" re… (#231) (Wednesday, 2 January)
• Re: [whatwg/fetch] Add option to reject the fetch promise automatically after a certain time elapsed (with no API for arbitrary aborts) (#179) (Wednesday, 2 January)
• Re: [whatwg/fetch] Consider removing trailers API (#772) (Wednesday, 2 January)
• Re: [whatwg/fetch] Consider removing trailers API (#772) (Wednesday, 2 January)
• Re: [whatwg/fetch] CORB blocking JSON response after redirect (#854) (Wednesday, 2 January)

Anton Platonov

• Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550) (Tuesday, 29 January)

arturjanc

• Re: [whatwg/fetch] SameSite cookies aren't sent on credentialed CORS requests (#769) (Thursday, 31 January)
• Re: [whatwg/fetch] SameSite cookies aren't sent on credentialed CORS requests (#769) (Thursday, 31 January)

Asa Kusuma

• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Tuesday, 29 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Monday, 28 January)

Ashley (Scirra)

• Re: [w3c/webcomponents] HTML Modules (#645) (Thursday, 17 January)

Atishay Jain

• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Wednesday, 9 January)
• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Monday, 7 January)

ayZagen

• Re: [w3c/ServiceWorker] Authenticated PWA ? (#909) (Wednesday, 9 January)

Ben Kelly

• Re: [w3c/ServiceWorker] Add a script version property to the ServiceWorker object (#1387) (Thursday, 31 January)
• Re: [w3c/ServiceWorker] Service worker not intercepting the call intiated for CSS from JS files “ css:”css/custom.css" (#1386) (Tuesday, 29 January)
• Re: [w3c/ServiceWorker] Service worker not intercepting the call intiated for CSS from JS files “ css:”css/custom.css" (#1386) (Tuesday, 29 January)
• Re: [w3c/ServiceWorker] clients.get() should not resolve before sandboxing determines the origin of the client (#1385) (Thursday, 24 January)
• Re: [w3c/ServiceWorker] Correcting the use of types and simplifying the response body read. (#1384) (Tuesday, 22 January)
• Re: [w3c/ServiceWorker] Update shouldn't fail due to MIME check or 404 for the incumbent's worker scripts (#1374) (Thursday, 17 January)
• Re: [w3c/ServiceWorker] Don't fail update upon error fetching the incumbent worker's import s… (#1377) (Wednesday, 16 January)
• Re: [w3ctag/design-reviews] FetchEvent Worker Timing (#317) (Monday, 14 January)
• Re: [w3c/ServiceWorker] "no-cors" CSS SOP violation (#719) (Thursday, 3 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Thursday, 3 January)

BigBlueHat

• Re: [w3c/webcomponents] HTML module should require a new MIME type (#742) (Thursday, 31 January)

Boris Zbarsky

• Re: [heycam/webidl] Disallow underscore-and-hyphen only identifiers (#633) (Wednesday, 30 January)
• Re: [heycam/webidl] Disallow underscore-and-hyphen only identifiers (#633) (Wednesday, 30 January)
• Re: [heycam/webidl] Consider removing call to named property setter in legacy platform object [[Set]] (#630) (Wednesday, 23 January)
• Re: [heycam/webidl] Consider removing call to named property setter in legacy platform object [[Set]] (#630) (Wednesday, 23 January)
• Re: [heycam/webidl] Check ignoreNamedProps before the named property visibility algorithm. (#625) (Tuesday, 22 January)
• Re: [heycam/webidl] Check ignoreNamedProps before the named property visibility algorithm. (#625) (Tuesday, 22 January)
• Re: [heycam/webidl] Editorial: fix language in nullable types section (#628) (Monday, 21 January)
• Re: [heycam/webidl] Editorial: fix language in nullable types section (#628) (Monday, 21 January)
• Re: [heycam/webidl] Intent to use Constants (#627) (Monday, 21 January)
• Re: [heycam/webidl] Intent to use Constants (#627) (Monday, 21 January)
• Re: [heycam/webidl] Various named property stuff seems confused in the face of symbols (#175) (Thursday, 17 January)
• Re: [heycam/webidl] IsDataDescriptor check for legacy setters is not implemented (#624) (Thursday, 17 January)
• Re: [heycam/webidl] Check ignoreNamedProps before the named property visibility algorithm. (#625) (Thursday, 17 January)
• Re: [heycam/webidl] Various named property stuff seems confused in the face of symbols (#175) (Thursday, 17 January)
• Re: [heycam/webidl] Editorial: Use some more abstract operations. (#601) (Tuesday, 15 January)
• Re: [heycam/webidl] No mixin [NoInterfaceObject] usage (#430) (Tuesday, 15 January)
• Re: [heycam/webidl] Use %PromiseProto_then% to 'perform some steps once a promise is settled'. (#611) (Tuesday, 15 January)
• Re: [heycam/webidl] Should "perform some steps once a promise is settled" use %PromiseProto_then%? (#583) (Tuesday, 15 January)
• Re: [heycam/webidl] Use %PromiseProto_then% to 'perform some steps once a promise is settled'. (#611) (Tuesday, 15 January)
• Re: [heycam/webidl] Use %PromiseProto_then% to 'perform some steps once a promise is settled'. (#611) (Tuesday, 15 January)
• Re: [heycam/webidl] Allow identifiers that start with a hyphen. (#612) (Tuesday, 15 January)
• Re: [heycam/webidl] Use map/exists to define dictionary/present. (#610) (Monday, 14 January)
• Re: [heycam/webidl] Use map/exists to define dictionary/present. (#610) (Monday, 14 January)
• Re: [heycam/webidl] Dictionary members' "present" definition seems circular (#381) (Monday, 14 January)
• Re: [heycam/webidl] Clarify [[Call]] + [[Construct]] for named (and possibly non-named) constructors (#278) (Monday, 14 January)
• Re: [heycam/webidl] Clarify [[Call]] + [[Construct]] for named (and possibly non-named) constructors (#278) (Monday, 14 January)
• Re: [heycam/webidl] Intent to use Constants (#608) (Sunday, 13 January)
• Re: [heycam/webidl] Named properties object / named property visibility algorithm with property on Window.prototype (#607) (Friday, 11 January)
• Re: [heycam/webidl] Named properties object / named property visibility algorithm with property on Window.prototype (#607) (Friday, 11 January)
• Re: [heycam/webidl] Allow overload resolution to "round down"? (#581) (Friday, 11 January)
• Re: [heycam/webidl] Allow overload resolution to "round down"? (#581) (Friday, 11 January)
• Re: [heycam/webidl] Give Location an immutable prototype object (#606) (Thursday, 10 January)
• Re: [heycam/webidl] Allow overload resolution to "round down"? (#581) (Thursday, 10 January)
• Re: [heycam/webidl] Allow overload resolution to "round down"? (#581) (Thursday, 10 January)

Brad Ziolko

• Re: [whatwg/fetch] CORB blocking JSON response after redirect (#854) (Friday, 4 January)
• Re: [whatwg/fetch] CORB blocking JSON response after redirect (#854) (Wednesday, 2 January)

Bradley Meck

• Re: [heycam/webidl] [[ViewedArrayBuffer]] cannot be undefined during usage (#604) (Wednesday, 9 January)
• Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97) (Monday, 7 January)

Brian Kardell

• Re: [w3ctag/design-reviews] Review MathML (#313) (Monday, 14 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Wednesday, 9 January)

Caridy Patiño

• Re: [w3c/webcomponents] Is there a way to detect if a custom element was constructed during parsing? (#789) (Thursday, 31 January)
• Re: [w3c/webcomponents] Serialize shadow DOM for use in javascript disabled user agents (#788) (Thursday, 31 January)
• Re: [whatwg/dom] MutationObserver needs an equivalent of disconnected & connected callbacks (#533) (Wednesday, 30 January)
• Re: [w3c/webcomponents] [idea] making builtin elements more like custom elements (#785) (Wednesday, 30 January)
• Re: [w3c/webcomponents] Lazy Custom Element Definitions (#782) (Friday, 18 January)
• Re: [w3c/webcomponents] Lazy Custom Element Definitions (#782) (Friday, 18 January)
• Re: [w3c/webcomponents] Lazy Custom Element Definitions (#782) (Thursday, 17 January)

Charles LaPierre

• Re: [w3ctag/design-reviews] Review MathML (#313) (Friday, 18 January)

Chris Needham

• Re: [w3ctag/design-reviews] Media Capabilities (#218) (Thursday, 10 January)

cybai

• Re: [whatwg/xhr] Fix small grammer (#234) (Tuesday, 22 January)
• Re: [whatwg/xhr] Fix small grammer (#234) (Tuesday, 22 January)
• Re: [whatwg/xhr] Fix small grammer (#234) (Monday, 21 January)
• [whatwg/xhr] Fix small grammer (#234) (Sunday, 20 January)
• Re: [whatwg/url] Remove "optional" for the init in URLSearchParams constructor? (#424) (Friday, 11 January)
• Re: [whatwg/url] Remove "optional" for the init in URLSearchParams constructor? (#424) (Friday, 11 January)
• [whatwg/url] Remove "optional" for the init in URLSearchParams constructor? (#424) (Friday, 11 January)

cynthia

• Re: [w3ctag/design-reviews] IndexedDB Transaction Explicit Commit API (#316) (Thursday, 24 January)
• Re: [w3ctag/design-reviews] HTML Modules (#334) (Tuesday, 22 January)
• Re: [w3ctag/design-reviews] Media Capabilities (#218) (Thursday, 10 January)

Dan Clark

• Re: [w3c/webcomponents] HTML module should require a new MIME type (#742) (Wednesday, 30 January)
• Re: [w3c/webcomponents] HTML modules spec draft editorial feedback (#783) (Thursday, 24 January)
• Re: [w3c/webcomponents] HTML modules spec draft editorial feedback (#783) (Friday, 18 January)
• [w3ctag/design-reviews] HTML Modules (#334) (Wednesday, 16 January)

Daniel Appelquist

• Re: [w3ctag/design-reviews] IndexedDB Transaction Explicit Commit API (#316) (Tuesday, 15 January)
• Re: [w3ctag/design-reviews] Privacy Mode (#101) (Tuesday, 15 January)
• Re: [w3ctag/design-reviews] Task Scheduling (#72) (Tuesday, 15 January)
• Re: [w3ctag/design-reviews] Serialization of natural language in data formats such as JSON [I18N] (#178) (Tuesday, 15 January)

Daniel Bates

• Re: [w3c/DOM-Parsing] Spec out normative text when parseFromString() is passed an unsupported MIME type (#41) (Monday, 28 January)
• Re: [w3c/DOM-Parsing] Spec out normative text when parseFromString() is passed an unsupported MIME type (#41) (Monday, 28 January)
• Re: [w3c/DOM-Parsing] Spec out normative text when parseFromString() is passed an unsupported MIME type (#41) (Monday, 28 January)
• Re: [w3c/DOM-Parsing] parseFromString() should be use case-insensitive MIME type matching (#40) (Monday, 28 January)
• Re: [w3c/DOM-Parsing] parseFromString() should be use case-insensitive MIME type matching (#40) (Monday, 28 January)
• Re: [w3c/DOM-Parsing] Spec out normative text when parseFromString() is passed an unsupported MIME type (#41) (Monday, 28 January)
• Re: [w3c/DOM-Parsing] Spec out normative text when parseFromString() is passed an unsupported MIME type (#41) (Saturday, 26 January)
• Re: [w3c/DOM-Parsing] parseFromString() should be use case-insensitive MIME type matching (#40) (Saturday, 26 January)
• Re: [w3c/DOM-Parsing] Spec out normative text when parseFromString() is passed an unsupported MIME type (#41) (Saturday, 26 January)
• [w3c/DOM-Parsing] Spec out normative text when parseFromString() is passed an unsupported MIME type (#41) (Saturday, 26 January)
• [w3c/DOM-Parsing] parseFromString() should be use case-insensitive MIME type matching (#40) (Saturday, 26 January)

Daniel Burnett

• [w3ctag/design-reviews] Heads up: Verifiable Credentials review request coming shortly (#335) (Saturday, 19 January)

Daniel Ehrenberg

• Re: [heycam/webidl] Consider adding support in WebIDL for defining template tags (#631) (Wednesday, 30 January)
• Re: [heycam/webidl] Consider adding support in WebIDL for defining template tags (#631) (Wednesday, 30 January)
• Re: [heycam/webidl] Consider adding support in WebIDL for defining template tags (#631) (Tuesday, 29 January)
• Re: [heycam/webidl] Consider adding support in WebIDL for defining template tags (#631) (Tuesday, 29 January)
• Re: [heycam/webidl] Intent to use Constants (#608) (Tuesday, 29 January)
• Re: [heycam/webidl] Consider adding support in WebIDL for defining template tags (#631) (Tuesday, 29 January)
• Re: [heycam/webidl] Editorial: Note that interface mixins' elements are included among interface elements (#594) (Monday, 28 January)
• Re: [heycam/webidl] Editorial: Note that interface mixins' elements are included among interface elements (#594) (Monday, 28 January)
• Re: [heycam/webidl] Rename the 'float' production to 'real'. (#616) (Monday, 28 January)
• Re: [heycam/webidl] Rename the 'float' production to 'real'. (#616) (Monday, 28 January)
• [heycam/webidl] Consider adding support in WebIDL for defining template tags (#631) (Monday, 28 January)
• Re: [heycam/webidl] Rename the 'float' production to 'real'. (#616) (Saturday, 26 January)
• Re: [heycam/webidl] Check ignoreNamedProps before the named property visibility algorithm. (#625) (Tuesday, 22 January)
• Re: [heycam/webidl] Use %PromiseProto_then% to 'perform some steps once a promise is settled'. (#611) (Friday, 18 January)
• Re: [heycam/webidl] Use %PromiseProto_then% to 'perform some steps once a promise is settled'. (#611) (Friday, 18 January)
• Re: [heycam/webidl] Give Location an immutable prototype object (#606) (Thursday, 10 January)
• Re: [heycam/webidl] Give Location an immutable prototype object (#606) (Thursday, 10 January)
• Re: [heycam/webidl] Give Location an immutable prototype object (#606) (Thursday, 10 January)
• Re: [heycam/webidl] Detached ArrayBuffer objects should not throw (#605) (Wednesday, 9 January)
• Re: [heycam/webidl] Detached ArrayBuffer objects should not throw (#605) (Wednesday, 9 January)

Daniel Marques

• Re: [w3ctag/design-reviews] Review MathML (#313) (Monday, 14 January)

Daniel Murphy

• Re: [w3c/IndexedDB] Disallow starting readwrite transactions while readonly transactions are running? (#253) (Friday, 25 January)

Dave Tapuska

• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Wednesday, 30 January)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Wednesday, 30 January)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Monday, 28 January)
• Re: [whatwg/fetch] Add Async Stale While Revalidate Handling (#853) (Monday, 28 January)
• Re: [whatwg/fetch] Add Async Stale While Revalidate Handling (#853) (Monday, 28 January)
• Re: [whatwg/fetch] Add Async Stale While Revalidate Handling (#853) (Tuesday, 22 January)
• Re: [whatwg/fetch] Add Async Stale While Revalidate Handling (#853) (Tuesday, 22 January)
• Re: [whatwg/fetch] Add Async Stale While Revalidate Handling (#853) (Monday, 21 January)
• Re: [whatwg/fetch] Add support for stale-while-revalidate handling (#852) (Tuesday, 15 January)

David Spector

• [whatwg/dom] Bad "good first issue" labels (#729) (Monday, 14 January)
• Re: [whatwg/dom] createElementNS() QName/Name confusion (#671) (Monday, 14 January)
• Re: [whatwg/dom] Use a single exception for name validation (follow up) (#675) (Monday, 14 January)

Dmitry Murzin

• [w3c/uievents] Fix link for `key attribute value` (#219) (Monday, 14 January)

Domenic Denicola

• Re: [whatwg/streams] Switching to Web IDL (#963) (Thursday, 31 January)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Wednesday, 30 January)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Wednesday, 30 January)
• Re: [heycam/webidl] Define "implements" checks using internal slots (#595) (Wednesday, 30 January)
• Re: [heycam/webidl] Disallow underscore-and-hyphen only identifiers (#633) (Wednesday, 30 January)
• Re: [heycam/webidl] Editorial: Use some more abstract operations. (#601) (Wednesday, 30 January)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Wednesday, 30 January)
• Re: [heycam/webidl] Defining a ByteString default value using a string literal gives no clear link to the explanation of how the string is converted to ByteString (#141) (Wednesday, 30 January)
• Re: [heycam/webidl] Clarify the interpretation of string literal tokens. (#621) (Wednesday, 30 January)
• Re: [heycam/webidl] Clarify the interpretation of string literal tokens. (#621) (Wednesday, 30 January)
• Re: [whatwg/url] searchParams.set("param", undefined) should not stringify as param=undefined (#427) (Tuesday, 29 January)
• Re: [heycam/webidl] Consider adding support in WebIDL for defining template tags (#631) (Tuesday, 29 January)
• Re: [heycam/webidl] Consider adding support in WebIDL for defining template tags (#631) (Tuesday, 29 January)
• Re: [heycam/webidl] Intent to use Constants (#608) (Tuesday, 29 January)
• Re: [heycam/webidl] Fix error handling when using Call() (#207) (Tuesday, 29 January)
• Re: [heycam/webidl] Fix error handling around Call(). (#618) (Tuesday, 29 January)
• Re: [heycam/webidl] Fix error handling around Call(). (#618) (Tuesday, 29 January)
• Re: [heycam/webidl] Clarify the interpretation of string literal tokens. (#621) (Tuesday, 29 January)
• Re: [heycam/webidl] Editorial: Note that interface mixins' elements are included among interface elements (#594) (Tuesday, 29 January)
• Re: [heycam/webidl] Editorial: Note that interface mixins' elements are included among interface elements (#594) (Tuesday, 29 January)
• Re: [whatwg/url] searchParams.set("param", undefined) should not stringify as param=undefined (#427) (Tuesday, 29 January)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Tuesday, 29 January)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Tuesday, 29 January)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Tuesday, 29 January)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Tuesday, 29 January)
• Re: [heycam/webidl] Improve the named property visibility algorithm for Window. (#626) (Monday, 28 January)
• Re: [heycam/webidl] Editorial: Note that interface mixins' elements are included among interface elements (#594) (Monday, 28 January)
• Re: [heycam/webidl] Editorial: Note that interface mixins' elements are included among interface elements (#594) (Monday, 28 January)
• Re: [heycam/webidl] Disallow a default value for required dictionary members in the grammar. (#622) (Monday, 28 January)
• Re: [heycam/webidl] We should disallow a default value for required dictionary members in the grammar (#569) (Monday, 28 January)
• Re: [heycam/webidl] Disallow a default value for required dictionary members in the grammar. (#622) (Monday, 28 January)
• Re: [heycam/webidl] Fix error handling when using Call() (#207) (Monday, 28 January)
• Re: [heycam/webidl] Fix error handling around Call(). (#618) (Monday, 28 January)
• Re: [heycam/webidl] Clarify the interpretation of string literal tokens. (#621) (Monday, 28 January)
• Re: [heycam/webidl] Restrict the extended attributes for partial interfaces. (#620) (Monday, 28 January)
• Re: [heycam/webidl] [Exposed] doesn't seem to work well with partial interfaces (#154) (Monday, 28 January)
• Re: [heycam/webidl] Restrict the extended attributes for partial interfaces. (#620) (Monday, 28 January)
• Re: [heycam/webidl] "call a user object’s operation" should not have an optional argument in the middle (#534) (Monday, 28 January)
• Re: [heycam/webidl] Editorial: Make the opName argument required. (#619) (Monday, 28 January)
• Re: [heycam/webidl] Editorial: Make the opName argument required. (#619) (Monday, 28 January)
• Re: [heycam/webidl] Editorial: Make the opName argument required. (#619) (Monday, 28 January)
• Re: [heycam/webidl] Allow identifiers that start with a hyphen. (#612) (Monday, 28 January)
• Re: [w3c/webcomponents] [idea] making builtin elements more like custom elements (#785) (Monday, 28 January)
• Re: [whatwg/streams] ReadableStream should be an async iterable (#778) (Sunday, 27 January)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Sunday, 27 January)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Sunday, 27 January)
• Re: [whatwg/fullscreen] Review Draft Publication: January 2019 (#143) (Wednesday, 23 January)
• Re: [whatwg/fullscreen] Review Draft Publication: January 2019 (#143) (Wednesday, 23 January)
• Re: [heycam/webidl] Import (and fix) the promises guide (#490) (Friday, 18 January)
• Re: [heycam/webidl] Use %PromiseProto_then% to 'perform some steps once a promise is settled'. (#611) (Friday, 18 January)
• [w3c/webcomponents] HTML modules spec draft editorial feedback (#783) (Thursday, 17 January)
• Re: [whatwg/dom] Ground primitives in agents (#717) (Wednesday, 16 January)
• Re: [heycam/webidl] Restrict the extended attributes for partial interfaces. (#620) (Wednesday, 16 January)
• Re: [heycam/webidl] Restrict the extended attributes for partial interfaces. (#620) (Wednesday, 16 January)
• Re: [heycam/webidl] Use %PromiseProto_then% to 'perform some steps once a promise is settled'. (#611) (Tuesday, 15 January)
• Re: [heycam/webidl] Can [Replaceable] be used on namespace members? (#572) (Tuesday, 15 January)
• Re: [heycam/webidl] Disallow Replaceable on namespaces, and fix the attribute setter creation. (#614) (Tuesday, 15 January)
• Re: [heycam/webidl] Disallow Replaceable on namespaces, and fix the attribute setter creation. (#614) (Tuesday, 15 January)
• Re: [heycam/webidl] No mixin [NoInterfaceObject] usage (#430) (Tuesday, 15 January)
• Re: [heycam/webidl] No mixin [NoInterfaceObject] usage (#430) (Tuesday, 15 January)
• Re: [whatwg/streams] Teeing dynamically (#979) (Monday, 14 January)
• Re: [whatwg/dom] Ground primitives in agents (#717) (Monday, 14 January)
• Re: [heycam/webidl] Remove [NoInterfaceObject]. (#609) (Monday, 14 January)
• Re: [heycam/webidl] Named properties object / named property visibility algorithm with property on Window.prototype (#607) (Friday, 11 January)
• Re: [heycam/webidl] Allow overload resolution to "round down"? (#581) (Friday, 11 January)
• Re: [whatwg/url] Remove "optional" for the init in URLSearchParams constructor? (#424) (Friday, 11 January)
• Re: [heycam/webidl] Detached ArrayBuffer objects should not throw (#605) (Wednesday, 9 January)
• Re: [w3c/webcomponents] Allow attribute changes/child creation on custom element creation (#781) (Wednesday, 9 January)
• Re: [w3c/webcomponents] Allow attribute changes/child creation on custom element creation (#781) (Wednesday, 9 January)
• Re: [heycam/webidl] Detached ArrayBuffer objects should not throw (#605) (Wednesday, 9 January)
• Re: [heycam/webidl] [[ViewedArrayBuffer]] cannot be undefined during usage (#604) (Wednesday, 9 January)
• Re: [w3c/webcomponents] Allow attribute changes/child creation on custom element creation (#781) (Tuesday, 8 January)
• Re: [w3c/webcomponents] Allow attribute changes/child creation on custom element creation (#781) (Tuesday, 8 January)
• Re: [w3ctag/design-reviews] TextEncoderStream and TextDecoderStream (#282) (Tuesday, 8 January)
• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Tuesday, 8 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Tuesday, 8 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Tuesday, 8 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Monday, 7 January)
• Re: [w3c/uievents] Add reference to the element (#217) (Thursday, 3 January)
• [whatwg/streams] Transferring errors for transferable streams (#978) (Wednesday, 2 January)

Dominic Farolino

• Re: [w3ctag/design-reviews] imagesrcset and imagesizes attributes on link rel=preload (#329) (Saturday, 26 January)

Dominick Ng

• Re: [w3c/screen-orientation] Promise for unlock()? (#104) (Wednesday, 30 January)

Emilio Cobos Álvarez

• Re: [w3c/webcomponents] Support for pseudo elements with ::slotted() selectors (#655) (Wednesday, 23 January)

Emircan Uysaler

• Re: [w3c/permissions] Rename 'display' permission to 'display-capture'. (#188) (Friday, 4 January)

Eric Portis

• Re: [whatwg/fetch] Copy client-hints list from env settings object. Align CH processing (#773) (Thursday, 24 January)
• Re: [whatwg/fetch] Copy client-hints list from env settings object. Align CH processing (#773) (Thursday, 24 January)
• Re: [whatwg/fetch] Copy client-hints list from env settings object. Align CH processing (#773) (Thursday, 24 January)
• Re: [whatwg/fetch] Copy client-hints list from env settings object. Align CH processing (#773) (Thursday, 24 January)
• Re: [w3ctag/design-reviews] imagesrcset and imagesizes attributes on link rel=preload (#329) (Thursday, 24 January)
• Re: [whatwg/fetch] Copy client-hints list from env settings object. Align CH processing (#773) (Thursday, 17 January)
• Re: [whatwg/fetch] Check Feature Policy before attaching Client Hints (#811) (Thursday, 17 January)
• Re: [whatwg/fetch] Check Feature Policy before attaching Client Hints (#811) (Thursday, 17 January)

ExE Boss

• Re: [w3c/webcomponents] HTML module should require a new MIME type (#742) (Thursday, 31 January)

Ezekiel Chentnik

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

Frank van Gemeren

• Re: [w3c/ServiceWorker] Add cookie accessor/setter methods? (#707) (Friday, 11 January)

Frederik Wessberg

• Re: [whatwg/dom] MutationObserver needs an equivalent of disconnected & connected callbacks (#533) (Thursday, 31 January)

Frédéric Wang

• Re: [w3ctag/design-reviews] Review MathML (#313) (Friday, 18 January)

Gary Kacmarcik

• Re: [w3c/uievents] MouseEvent.screenX/Y coordinate space id not clear (#150) (Thursday, 17 January)
• Re: [w3c/uievents] Fix link for `key attribute value` (#219) (Monday, 14 January)
• Re: [w3c/uievents] Fix link for `key attribute value` (#219) (Monday, 14 January)
• Re: [w3c/clipboard-apis] IDL doesn't link correctly (#83) (Wednesday, 9 January)
• Re: [w3c/uievents] Add reference to the element (#217) (Thursday, 3 January)
• Re: [w3c/clipboard-apis] Clarify promise rejection value (#76) (Thursday, 3 January)
• Re: [w3c/clipboard-apis] Specify NotAllowedError when permission is not granted (#82) (Thursday, 3 January)

Grisha Lyukshin

• Re: [w3c/editing] Should browsers support ContentEditable for <option> elements? (#180) (Friday, 4 January)
• Re: [w3c/clipboard-apis] Specify NotAllowedError when permission is not granted (#82) (Thursday, 3 January)
• Re: [w3c/clipboard-apis] Specify NotAllowedError when permission is not granted (#82) (Wednesday, 2 January)

Gus Caplan

• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Saturday, 26 January)
• Re: [whatwg/streams] add @@asyncIterator to ReadableStream (#954) (Saturday, 26 January)
• Re: [whatwg/streams] add @@asyncIterator to ReadableStream (#954) (Tuesday, 22 January)

Hadley Beeman

• Re: [w3ctag/design-reviews] hrefTranslate attribute (#301) (Tuesday, 8 January)
• Re: [w3ctag/design-reviews] Vehicle Information Service Specification (VISS) CR (#234) (Tuesday, 8 January)

Hayato Ito

• Re: [w3c/webcomponents] Support for pseudo elements with ::slotted() selectors (#655) (Wednesday, 23 January)
• Re: [whatwg/dom] Composed tree infrastructure (#725) (Wednesday, 9 January)
• Re: [w3c/webcomponents] [Shadow]: return of multiple shadow roots? (#780) (Tuesday, 8 January)

Henri Sivonen

• Re: [whatwg/encoding] Big5 encoding mishandles some trailing bytes, with possible XSS (#171) (Thursday, 31 January)
• Re: [whatwg/encoding] Big5 encoding mishandles some trailing bytes, with possible XSS (#171) (Wednesday, 30 January)
• Re: [whatwg/encoding] Big5 encoding mishandles some trailing bytes, with possible XSS (#171) (Wednesday, 30 January)
• Re: [whatwg/encoding] Big5 encoding mishandles some trailing bytes, with possible XSS (#171) (Tuesday, 29 January)
• Re: [whatwg/encoding] Big5 encoding mishandles some trailing bytes, with possible XSS (#171) (Tuesday, 29 January)

hober

• Re: [w3ctag/design-reviews] imagesrcset and imagesizes attributes on link rel=preload (#329) (Friday, 25 January)
• Re: [w3ctag/design-reviews] EME Extension: HDCP Policy Check (#323) (Tuesday, 22 January)

Hugo

• Re: [w3c/webcomponents] tabIndex -1 behaves differently on non-Custom Elements (#774) (Monday, 21 January)

Iain Shorter

• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Tuesday, 8 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Tuesday, 8 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Monday, 7 January)

Ian Clelland

• Re: [w3ctag/design-reviews] Feature Policy JS introspection API (#292) (Thursday, 31 January)
• [w3ctag/design-reviews] Feature policy control over sandbox features (#339) (Tuesday, 29 January)

Ilya Grigorik

• Re: [whatwg/fetch] Consider removing trailers API (#772) (Friday, 4 January)
• Re: [whatwg/fetch] Consider removing trailers API (#772) (Wednesday, 2 January)

Iona

• [w3c/ServiceWorker] The compatibility of service worker on ios devices (#1381) (Friday, 18 January)

Jake Archibald

• Re: [w3c/ServiceWorker] Correcting the use of types and simplifying the response body read. (#1384) (Wednesday, 30 January)
• Re: [w3c/ServiceWorker] Clarify dynamic-imported scripts are never installed (#1356) (Wednesday, 30 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Wednesday, 30 January)
• Re: [heycam/webidl] Async iterators (#580) (Wednesday, 23 January)
• Re: [w3c/ServiceWorker] Correcting the use of types and simplifying the response body read. (#1384) (Tuesday, 22 January)
• Re: [w3c/ServiceWorker] Correcting the use of types and simplifying the response body read. (#1384) (Tuesday, 22 January)
• Re: [w3c/ServiceWorker] Correcting the use of types and simplifying the response body read. (#1384) (Tuesday, 22 January)
• Re: [w3c/ServiceWorker] Correcting the use of types and simplifying the response body read. (#1384) (Tuesday, 22 January)
• Re: [w3c/ServiceWorker] Correcting the use of types and simplifying the response body read. (#1384) (Tuesday, 22 January)
• Re: [w3c/ServiceWorker] Correcting the use of types and simplifying the response body read. (#1384) (Tuesday, 22 January)
• Re: [w3c/ServiceWorker] Correcting the use of types and simplifying the response body read. (#1384) (Tuesday, 22 January)
• Re: [w3c/ServiceWorker] Correcting the use of types and simplifying the response body read. (#1384) (Tuesday, 22 January)
• Re: [w3c/ServiceWorker] Correcting the use of types and simplifying the response body read. (#1384) (Tuesday, 22 January)
• Re: [w3c/ServiceWorker] Correcting the use of types and simplifying the response body read. (#1384) (Tuesday, 22 January)
• Re: [w3c/ServiceWorker] Correcting the use of types and simplifying the response body read. (#1384) (Tuesday, 22 January)
• Re: [w3c/ServiceWorker] Correcting the use of types and simplifying the response body read. (#1384) (Tuesday, 22 January)
• Re: [w3c/ServiceWorker] Correcting the use of types and simplifying the response body read. (#1384) (Tuesday, 22 January)
• Re: [w3c/ServiceWorker] Correcting the use of types and simplifying the response body read. (#1384) (Tuesday, 22 January)
• [w3c/ServiceWorker] Correcting the use of types and simplifying the response body read. (#1384) (Tuesday, 22 January)
• Re: [w3c/ServiceWorker] The compatibility of service worker on ios devices (#1381) (Tuesday, 22 January)
• Re: [w3c/ServiceWorker] The compatibility of service worker on ios devices (#1381) (Tuesday, 22 January)
• Re: [w3c/ServiceWorker] Cache.put() does not read response's body (#1383) (Tuesday, 22 January)
• Re: [w3c/ServiceWorker] Cache's put() says it clones the response (#1382) (Tuesday, 22 January)
• Re: [w3c/ServiceWorker] Cache's put() says it clones the response (#1382) (Monday, 21 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Sunday, 20 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Wednesday, 16 January)
• Re: [w3c/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Tuesday, 15 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Tuesday, 15 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Wednesday, 9 January)
• Re: [w3c/ServiceWorker] Don't fail update upon error fetching the incumbent worker's import s… (#1377) (Wednesday, 9 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Wednesday, 9 January)
• Re: [w3ctag/design-reviews] Background fetch (#279) (Wednesday, 9 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Wednesday, 9 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Tuesday, 8 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Tuesday, 8 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Tuesday, 8 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Tuesday, 8 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Tuesday, 8 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Tuesday, 8 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Tuesday, 8 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Tuesday, 8 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Tuesday, 8 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Monday, 7 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Monday, 7 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Monday, 7 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Monday, 7 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Monday, 7 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Monday, 7 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Friday, 4 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Friday, 4 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Thursday, 3 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Thursday, 3 January)

James Browning

• Re: [w3c/webcomponents] HTML Modules (#645) (Thursday, 24 January)

Jan Miksovsky

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

Jason Miller

• Re: [w3c/webcomponents] CSS Modules (#759) (Thursday, 31 January)
• Re: [w3c/webcomponents] CSS Modules (#759) (Thursday, 31 January)
• Re: [w3c/ServiceWorker] Clarify dynamic-imported scripts are never installed (#1356) (Wednesday, 30 January)

Jay Harris

• Re: [w3c/manifest] Add a way to query whether there is a UA-provided back button (#693) (Thursday, 24 January)

Jeffrey Posnick

• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Tuesday, 8 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Friday, 4 January)

Jeffrey Yasskin

• Re: [whatwg/fetch] Consider "extract a MIME type and compare its essence" (#856) (Monday, 7 January)

Jeremy

• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Thursday, 17 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Wednesday, 16 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Tuesday, 15 January)

Jimmy Wärting

• Re: [w3c/FileAPI] Add readAsSharedArrayBuffer to FileReader (#73) (Sunday, 13 January)

Joe Pea

• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Thursday, 31 January)
• [w3c/webcomponents] Is there a way to detect is a custom element was constructed during parsing? (#789) (Thursday, 31 January)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Thursday, 31 January)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Thursday, 31 January)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Thursday, 31 January)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Thursday, 31 January)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Thursday, 31 January)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Thursday, 31 January)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Wednesday, 30 January)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Wednesday, 30 January)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Wednesday, 30 January)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Wednesday, 30 January)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Wednesday, 30 January)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Wednesday, 30 January)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Wednesday, 30 January)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Wednesday, 30 January)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Wednesday, 30 January)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Wednesday, 30 January)
• Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Tuesday, 29 January)
• Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Tuesday, 29 January)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Tuesday, 29 January)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Tuesday, 29 January)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Tuesday, 29 January)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Tuesday, 29 January)
• Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550) (Tuesday, 29 January)
• Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550) (Tuesday, 29 January)
• Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550) (Tuesday, 29 January)
• [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Tuesday, 29 January)
• Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550) (Monday, 28 January)
• Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550) (Monday, 28 January)
• Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550) (Monday, 28 January)
• [w3c/webcomponents] [idea] making builtin elements more like custom elements (#785) (Monday, 28 January)
• Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550) (Monday, 28 January)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Monday, 28 January)
• Re: [w3c/webcomponents] Should shadow host have `display: block` by default? (#426) (Monday, 28 January)
• Re: [w3c/webcomponents] Should shadow host have `display: block` by default? (#426) (Monday, 28 January)
• Re: [w3c/webcomponents] Should shadow host have `display: block` by default? (#426) (Sunday, 27 January)
• Re: [w3c/webcomponents] Lazy Custom Element Definitions (#782) (Wednesday, 23 January)
• Re: [w3c/webcomponents] Element Behaviors, and the has="" attribute. A useful alternative to Custom Elements in many cases! (#727) (Wednesday, 23 January)
• Re: [w3c/webcomponents] Element Behaviors, and the has="" attribute. A useful alternative to Custom Elements in many cases! (#727) (Wednesday, 23 January)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Wednesday, 23 January)
• Re: [w3c/webcomponents] Element Behaviors, and the has="" attribute. A useful alternative to Custom Elements in many cases! (#727) (Monday, 7 January)
• Re: [w3c/webcomponents] Element Behaviors, and the has="" attribute. A useful alternative to Custom Elements in many cases! (#727) (Monday, 7 January)
• Re: [w3c/webcomponents] Element Behaviors, and the has="" attribute. A useful alternative to Custom Elements in many cases! (#727) (Monday, 7 January)
• Re: [w3c/webcomponents] Element Behaviors, and the has="" attribute. A useful alternative to Custom Elements in many cases! (#727) (Monday, 7 January)
• Re: [w3c/webcomponents] Element Behaviors, and the has="" attribute. A useful alternative to Custom Elements in many cases! (#727) (Monday, 7 January)

Joel Einbinder

• Re: [w3c/webcomponents] tabIndex -1 behaves differently on non-Custom Elements (#774) (Friday, 18 January)

Johanna

• Re: [w3c/screen-orientation] Editorial: Internal slots (#144) (Thursday, 31 January)
• Re: [w3c/screen-orientation] Editorial: Internal slots (#144) (Thursday, 31 January)
• Re: [w3c/screen-orientation] Editorial: Internal slots (#144) (Thursday, 31 January)
• Re: [w3c/screen-orientation] Editorial: Internal slots (#144) (Thursday, 31 January)
• Re: [w3c/screen-orientation] Editorial: 2.1 Orientation attribute, 3. Screen Orientation and enums (#139) (Thursday, 31 January)
• Re: [w3c/screen-orientation] Editorial: 2.1 Orientation attribute, 3. Screen Orientation and enums (#139) (Thursday, 31 January)
• Re: [w3c/screen-orientation] Editorial: 2.1 Orientation attribute, 3. Screen Orientation and enums (#139) (Thursday, 31 January)
• Re: [w3c/screen-orientation] Editorial: 2.1 Orientation attribute, 3. Screen Orientation and enums (#139) (Thursday, 31 January)
• Re: [w3c/screen-orientation] Editorial: 2.1 Orientation attribute, 3. Screen Orientation and enums (#139) (Thursday, 31 January)
• Re: [w3c/screen-orientation] Editorial: 2.1 Orientation attribute, 3. Screen Orientation and enums (#139) (Thursday, 31 January)
• Re: [w3c/screen-orientation] Editorial: 2.1 Orientation attribute, 3. Screen Orientation and enums (#139) (Wednesday, 30 January)
• Re: [w3c/screen-orientation] Editorial: 2.1 Orientation attribute, 3. Screen Orientation and enums (#139) (Tuesday, 29 January)
• Re: [w3c/screen-orientation] Editorial: 2.1 Orientation attribute, 3. Screen Orientation and enums (#139) (Tuesday, 29 January)
• Re: [w3c/screen-orientation] Clarification on animation frame task (#136) (Tuesday, 29 January)
• Re: [w3c/screen-orientation] Clarification regarding locking the screen orientation (#143) (Tuesday, 29 January)
• Re: [w3c/screen-orientation] Editorial: Internal slots (#144) (Tuesday, 29 January)
• Re: [w3c/screen-orientation] Editorial: Internal slots (#144) (Tuesday, 29 January)
• Re: [w3c/screen-orientation] Editorial: Examples section edits (#137) (Tuesday, 29 January)
• Re: [w3c/screen-orientation] Editorial: Change pending promise to screen lock promise (#141) (Tuesday, 29 January)
• Re: [w3c/screen-orientation] Editorial: Change pending promise to screen lock promise (#141) (Tuesday, 29 January)
• Re: [w3c/screen-orientation] Editorial: Examples section edits (#137) (Tuesday, 29 January)
• Re: [w3c/screen-orientation] Editorial: Examples section edits (#137) (Tuesday, 29 January)
• Re: [w3c/screen-orientation] Editorial: Edits to sections 3.2-3.5 (#140) (Tuesday, 29 January)
• Re: [w3c/screen-orientation] Editorial: Edits to sections 3.2-3.5 (#140) (Tuesday, 29 January)
• [w3c/screen-orientation] Editorial: Internal slots (#144) (Monday, 28 January)
• [w3c/screen-orientation] Clarification regarding locking the screen orientation (#143) (Monday, 28 January)
• Re: [w3c/screen-orientation] Editorial: Section 7 edits (#142) (Monday, 28 January)
• Re: [w3c/screen-orientation] Editorial: Edits to sections 3.2-3.5 (#140) (Friday, 25 January)
• [w3c/screen-orientation] Editorial: Section 7 edits (#142) (Friday, 25 January)
• [w3c/screen-orientation] Editorial: Change pending promise to screen lock promise (#141) (Friday, 25 January)
• [w3c/screen-orientation] Editorial: Edits to sections 3.2-3.5 (#140) (Friday, 25 January)
• Re: [w3c/screen-orientation] Editorial: Introduction edits (#138) (Friday, 25 January)
• Re: [w3c/screen-orientation] Editorial: 2.1 Orientation attribute, 3. Screen Orientation and enums (#139) (Thursday, 24 January)
• Re: [w3c/screen-orientation] Editorial: 2.1 Orientation attribute, 3. Screen Orientation and enums (#139) (Thursday, 24 January)
• [w3c/screen-orientation] Editorial: 2.1 Orientation attribute, 3. Screen Orientation and enums (#139) (Thursday, 24 January)
• [w3c/screen-orientation] Editorial: Introduction edits (#138) (Thursday, 24 January)
• Re: [w3c/screen-orientation] Editorial: Examples section edits (#137) (Thursday, 24 January)
• Re: [w3c/screen-orientation] Editorial: Examples section edits (#137) (Thursday, 24 January)
• [w3c/screen-orientation] Editorial: Examples section edits (#137) (Wednesday, 23 January)
• Re: [w3c/screen-orientation] Editorial: Example 3 (#135) (Tuesday, 22 January)
• [w3c/screen-orientation] Clarification on animation frame task (#136) (Tuesday, 22 January)
• Re: [w3c/screen-orientation] Editorial: Example 3 (#135) (Tuesday, 22 January)
• Re: [w3c/screen-orientation] Editorial: Example 3 (#135) (Tuesday, 22 January)
• Re: [w3c/screen-orientation] Editorial: Introduction Section (#132) (Monday, 21 January)
• Re: [w3c/screen-orientation] Editorial: Example 3 (#135) (Monday, 21 January)
• Re: [w3c/screen-orientation] Editorial: Example 3 (#135) (Monday, 21 January)
• Re: [w3c/screen-orientation] Editorial: Introduction Section (#132) (Monday, 21 January)
• Re: [w3c/screen-orientation] Editorial: Introduction Section (#132) (Monday, 21 January)
• Re: [w3c/screen-orientation] Editorial: Introduction Section (#132) (Monday, 21 January)
• Re: [w3c/screen-orientation] Editorial: Introduction Section (#132) (Monday, 21 January)
• Re: [w3c/screen-orientation] Editorial: Example 3 (#135) (Monday, 21 January)
• Re: [w3c/screen-orientation] Editorial: Example 1 (#133) (Sunday, 20 January)
• Re: [w3c/screen-orientation] Editorial: Introduction Section (#132) (Thursday, 17 January)
• Re: [w3c/screen-orientation] Editorial: Introduction Section (#132) (Thursday, 17 January)
• Re: [w3c/screen-orientation] Editorial: Example 1 (#133) (Thursday, 17 January)
• Re: [w3c/screen-orientation] Editorial: Example 1 (#133) (Thursday, 17 January)
• Re: [w3c/screen-orientation] Editorial: Example 3 (#135) (Thursday, 17 January)
• Re: [w3c/screen-orientation] Editorial: Example 3 (#135) (Thursday, 17 January)
• Re: [w3c/screen-orientation] Editorial: Example 1 (#133) (Thursday, 17 January)
• Re: [w3c/screen-orientation] Editorial: Example 2 (#134) (Thursday, 17 January)
• Re: [w3c/screen-orientation] Editorial: Example 2 (#134) (Thursday, 17 January)
• Re: [w3c/screen-orientation] Editorial: Example 2 (#134) (Thursday, 17 January)
• Re: [w3c/screen-orientation] Editorial: Example 1 (#133) (Thursday, 17 January)
• Re: [w3c/screen-orientation] Editorial: Example 1 (#133) (Thursday, 17 January)
• Re: [w3c/screen-orientation] Editorial: Example 2 (#134) (Thursday, 17 January)
• [w3c/screen-orientation] Editorial: Example 3 (#135) (Wednesday, 16 January)
• Re: [w3c/screen-orientation] Editorial: Example 1 (#133) (Tuesday, 15 January)
• Re: [w3c/screen-orientation] Editorial: Example 1 (#133) (Tuesday, 15 January)
• Re: [w3c/screen-orientation] Editorial: Example 1 (#133) (Tuesday, 15 January)
• Re: [w3c/screen-orientation] Editorial: Example 1 (#133) (Tuesday, 15 January)
• Re: [w3c/screen-orientation] Editorial: Example 1 (#133) (Tuesday, 15 January)
• [w3c/screen-orientation] Editorial: Example 2 (#134) (Tuesday, 15 January)
• [w3c/screen-orientation] Editorial: Example 1 (#133) (Tuesday, 15 January)
• [w3c/screen-orientation] Editorial: Introduction Section (#132) (Thursday, 10 January)
• Re: [w3c/screen-orientation] Editorial: new algorithms section (#131) (Thursday, 10 January)
• Re: [w3c/screen-orientation] Editorial: new algorithms section (#131) (Thursday, 10 January)
• Re: [w3c/screen-orientation] Editorial: new algorithms section (#131) (Thursday, 10 January)
• [w3c/screen-orientation] Editorial: new algorithms section (#131) (Wednesday, 9 January)
• Re: [w3c/screen-orientation] Editorial: Move and edit Dependencies section (#129) (Wednesday, 9 January)
• Re: [w3c/screen-orientation] Editorial: Move and edit Dependencies section (#129) (Wednesday, 9 January)
• Re: [w3c/screen-orientation] Editorial: Move and edit Dependencies section (#129) (Wednesday, 9 January)
• Re: [w3c/screen-orientation] Where are terms 'primary' and 'secondary' defined within spec? (#113) (Wednesday, 9 January)
• Re: [w3c/screen-orientation] Edits Primary and Secondary orientation definitions (#126) (Wednesday, 9 January)
• Re: [w3c/screen-orientation] Editorial: Edits to Interface Definitions (#130) (Wednesday, 9 January)
• Re: [w3c/screen-orientation] Editorial: Edits to Interface Definitions (#130) (Wednesday, 9 January)
• Re: [w3c/screen-orientation] Editorial: Edits to Interface Definitions (#130) (Wednesday, 9 January)
• Re: [w3c/screen-orientation] Editorial: Edits to Interface Definitions (#130) (Wednesday, 9 January)
• Re: [w3c/screen-orientation] Editorial: Edits to Interface Definitions (#130) (Tuesday, 8 January)
• Re: [w3c/screen-orientation] Editorial: Edits to Interface Definitions (#130) (Tuesday, 8 January)
• Re: [w3c/screen-orientation] Editorial: Edits to Interface Definitions (#130) (Tuesday, 8 January)
• Re: [w3c/screen-orientation] Editorial: Move and edit Dependencies section (#129) (Tuesday, 8 January)
• Re: [w3c/screen-orientation] Edits Primary and Secondary orientation definitions (#126) (Tuesday, 8 January)
• Re: [w3c/screen-orientation] Editorial: Move and edit Dependencies section (#129) (Tuesday, 8 January)
• [w3c/screen-orientation] Editorial: Edits to Interface Definitions (#130) (Tuesday, 8 January)
• [w3c/screen-orientation] Editorial: Move and edit Dependencies section (#129) (Monday, 7 January)
• [w3c/screen-orientation] Editorial: Move and edit conformance section (#128) (Monday, 7 January)
• [w3c/screen-orientation] Editorial: Edit Abstract (#127) (Monday, 7 January)

Johannes Wilm

• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Tuesday, 29 January)
• [w3c/uievents] onbeforeinput (#218) (Monday, 14 January)

John Behan

• Re: [w3c/screen-orientation] Promise for unlock()? (#104) (Monday, 28 January)

John Saterfiel

• Re: [w3c/ServiceWorker] Consider exposing Page Lifecycle state to service-worker (#1345) (Thursday, 3 January)

Josh Bruce

• Re: [w3c/webcomponents] Element Behaviors, and the has="" attribute. A useful alternative to Custom Elements in many cases! (#727) (Monday, 7 January)

Joshua Bell

• Re: [w3c/IndexedDB] Disallow starting readwrite transactions while readonly transactions are running? (#253) (Tuesday, 29 January)
• Re: [w3c/IndexedDB] Disallow starting readwrite transactions while readonly transactions are running? (#253) (Tuesday, 29 January)
• [w3c/IndexedDB] Mark IDBTransaction's commit() method as [SecureContext] ? (#254) (Wednesday, 23 January)
• Re: [w3c/IndexedDB] Proposal: Add explicit IDBTransaction.commit() (was: add "writeonly" mode) (#234) (Wednesday, 23 January)
• Re: [w3c/IndexedDB] Proposal: Add explicit IDBTransaction.commit() (was: add "writeonly" mode) (#234) (Wednesday, 23 January)
• Re: [w3c/IndexedDB] Add IDBTransaction commit() method (#242) (Wednesday, 23 January)
• Re: [w3c/IndexedDB] Add IDBTransaction commit() method (#242) (Wednesday, 23 January)
• Re: [w3c/IndexedDB] Disallow starting readwrite transactions while readonly transactions are running? (#253) (Friday, 18 January)
• [w3c/IndexedDB] Disallow starting readwrite transactions while readonly transactions are running? (#253) (Friday, 18 January)

Jungshik Shin

• Re: [whatwg/encoding] Big5 encoding mishandles some trailing bytes, with possible XSS (#171) (Tuesday, 29 January)
• Re: [whatwg/encoding] Differences between tests and specification (#169) (Friday, 18 January)

Justin Fagnani

• Re: [heycam/webidl] Consider adding support in WebIDL for defining template tags (#631) (Wednesday, 30 January)
• Re: [w3c/webcomponents] Lazy Custom Element Definitions (#782) (Friday, 18 January)
• Re: [w3c/webcomponents] HTML Modules (#645) (Wednesday, 16 January)
• [w3c/webcomponents] Lazy Custom Element Definitions (#782) (Tuesday, 15 January)

Kagami Sascha Rosylight

• Re: [heycam/webidl] Better regular expression for identifiers (#632) (Tuesday, 29 January)
• Re: [heycam/webidl] Consider adding support in WebIDL for defining template tags (#631) (Tuesday, 29 January)
• Re: [heycam/webidl] Intent to use Constants (#608) (Tuesday, 29 January)
• Re: [heycam/webidl] Consider adding support in WebIDL for defining template tags (#631) (Tuesday, 29 January)
• Re: [heycam/webidl] Better regular expression for identifiers (#632) (Tuesday, 29 January)
• [w3c/touch-events] Respec fixes (#102) (Sunday, 6 January)

KANOKWAN Miss MANEEON

• [whatwg/fetch] fetch (#864) (Tuesday, 29 January)

Kenneth Rohde Christiansen

• Re: [w3ctag/design-reviews] HTML Modules (#334) (Wednesday, 30 January)
• Re: [w3ctag/design-reviews] HTML Modules (#334) (Wednesday, 30 January)
• Re: [w3ctag/design-reviews] HTML Modules (#334) (Wednesday, 30 January)
• Re: [w3c/screen-orientation] Promise for unlock()? (#104) (Tuesday, 29 January)
• Re: [w3ctag/design-reviews] IndexedDB Transaction Explicit Commit API (#316) (Tuesday, 22 January)
• Re: [w3ctag/design-reviews] HTML Modules (#334) (Tuesday, 22 January)
• Re: [w3ctag/design-reviews] IndexedDB Transaction Explicit Commit API (#316) (Wednesday, 16 January)

Kinuko Yasuda

• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Wednesday, 30 January)
• Re: [whatwg/fetch] Add Async Stale While Revalidate Handling (#853) (Tuesday, 22 January)
• Re: [whatwg/fetch] Add Async Stale While Revalidate Handling (#853) (Friday, 18 January)

Kornel

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

Krzysztof Maczyński

• Re: [heycam/webidl] A non-optional dictionary argument makes sense at times. (#130) (Monday, 7 January)

Kunihiko Sakamoto

• Re: [w3ctag/design-reviews] <link> rel="modulepreload" (#213) (Tuesday, 8 January)

L. David Baron

• Re: [w3ctag/design-reviews] imagesrcset and imagesizes attributes on link rel=preload (#329) (Tuesday, 22 January)

lambang11

• [whatwg/xhr] S (#233) (Saturday, 12 January)

Lea Verou

• Re: [whatwg/url] searchParams.set("param", undefined) should not stringify as param=undefined (#427) (Tuesday, 29 January)
• [whatwg/url] searchParams.set("param", undefined) should not stringify as param=undefined (#427) (Tuesday, 29 January)

Linus Unnebäck

• Re: [w3c/clipboard-apis] Specify NotAllowedError when permission is not granted (#82) (Friday, 4 January)

lopesdasilva

• [whatwg/fetch] EvalError refused to evaluate because CSP is defined to script-src set to 'self' 'unsafe-inline' (#861) (Tuesday, 22 January)

Lukasz Anforowicz

• Re: [whatwg/fetch] More CORB-protected MIME types - adding protected types one-by-one. (#860) (Thursday, 24 January)
• Re: [whatwg/fetch] More CORB-protected MIME types - adding protected types one-by-one. (#860) (Thursday, 24 January)
• Re: [whatwg/fetch] More CORB-protected MIME types - adding protected types one-by-one. (#860) (Wednesday, 23 January)
• Re: [whatwg/fetch] Extend Cross-Origin-Resource-Policy to take origin values (#760) (Tuesday, 22 January)
• Re: [whatwg/fetch] Extend Cross-Origin-Resource-Policy to take origin values (#760) (Tuesday, 22 January)
• Re: [whatwg/fetch] More CORB-protected MIME types - adding protected types one-by-one. (#860) (Saturday, 19 January)
• Re: [whatwg/fetch] More CORB-protected MIME types (#721) (Saturday, 19 January)
• [whatwg/fetch] More CORB-protected MIME types - adding protected types one-by-one. (#860) (Friday, 18 January)
• Re: [whatwg/fetch] Cross-Origin-Resource-Policy (was: From-Origin) (#687) (Tuesday, 15 January)
• Re: [whatwg/fetch] CORB blocking JSON response after redirect (#854) (Thursday, 3 January)

Lukasz Olejnik

• Re: [w3ctag/design-reviews] Privacy Mode (#101) (Tuesday, 15 January)
• Re: [w3ctag/design-reviews] FetchEvent Worker Timing (#317) (Monday, 14 January)

Madhukar Kedlaya

• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Tuesday, 8 January)

Makoto Shimazu

• Re: [w3c/ServiceWorker] Update shouldn't fail due to MIME check or 404 for the incumbent's worker scripts (#1374) (Thursday, 17 January)

Marc G.

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

Marcos Cáceres

• Re: [w3c/screen-orientation] Editorial: 2.1 Orientation attribute, 3. Screen Orientation and enums (#139) (Thursday, 31 January)
• Re: [w3c/screen-orientation] Editorial: Internal slots (#144) (Thursday, 31 January)
• Re: [w3c/screen-orientation] Editorial: 2.1 Orientation attribute, 3. Screen Orientation and enums (#139) (Thursday, 31 January)
• Re: [w3c/screen-orientation] Editorial: 2.1 Orientation attribute, 3. Screen Orientation and enums (#139) (Wednesday, 30 January)
• Re: [w3c/screen-orientation] Promise for unlock()? (#104) (Wednesday, 30 January)
• Re: [w3c/screen-orientation] Promise for unlock()? (#104) (Wednesday, 30 January)
• Re: [w3c/screen-orientation] Promise for unlock()? (#104) (Wednesday, 30 January)
• Re: [w3c/screen-orientation] Editorial: Examples section edits (#137) (Tuesday, 29 January)
• Re: [w3c/screen-orientation] "Security" condition should be something else (#82) (Tuesday, 29 January)
• Re: [w3c/screen-orientation] "Security" condition should be something else (#82) (Tuesday, 29 January)
• Re: [w3c/screen-orientation] Editorial: 2.1 Orientation attribute, 3. Screen Orientation and enums (#139) (Tuesday, 29 January)
• Re: [w3c/screen-orientation] Editorial: Edits to sections 3.2-3.5 (#140) (Tuesday, 29 January)
• Re: [w3c/screen-orientation] Editorial: Change pending promise to screen lock promise (#141) (Tuesday, 29 January)
• Re: [w3c/screen-orientation] Editorial: Change pending promise to screen lock promise (#141) (Tuesday, 29 January)
• Re: [w3c/screen-orientation] Editorial: Examples section edits (#137) (Tuesday, 29 January)
• Re: [w3c/screen-orientation] Promise for unlock()? (#104) (Tuesday, 29 January)
• Re: [w3c/screen-orientation] Editorial: Section 7 edits (#142) (Sunday, 27 January)
• Re: [w3c/screen-orientation] Send events before promise resolve (#120) (Sunday, 27 January)
• Re: [w3c/screen-orientation] Promise for unlock()? (#104) (Sunday, 27 January)
• Re: [w3c/screen-orientation] Editorial: 2.1 Orientation attribute, 3. Screen Orientation and enums (#139) (Thursday, 24 January)
• Re: [w3c/screen-orientation] Editorial: Introduction edits (#138) (Thursday, 24 January)
• Re: [w3c/screen-orientation] Editorial: Examples section edits (#137) (Thursday, 24 January)
• Re: [w3c/screen-orientation] Clarification on animation frame task (#136) (Wednesday, 23 January)
• Re: [w3c/screen-orientation] "Security" condition should be something else (#82) (Wednesday, 23 January)
• Re: [w3c/screen-orientation] "Security" condition should be something else (#82) (Wednesday, 23 January)
• Re: [w3c/screen-orientation] cordova-plugin-screen-orientation does not work (#123) (Wednesday, 23 January)
• Re: [w3c/screen-orientation] Editorial: Example 3 (#135) (Tuesday, 22 January)
• Re: [w3c/screen-orientation] Editorial: Example 3 (#135) (Tuesday, 22 January)
• Re: [w3c/screen-orientation] Editorial: Introduction Section (#132) (Monday, 21 January)
• Re: [w3c/screen-orientation] Editorial: Introduction Section (#132) (Monday, 21 January)
• Re: [w3c/screen-orientation] Editorial: Introduction Section (#132) (Monday, 21 January)
• Re: [w3c/screen-orientation] Editorial: Example 3 (#135) (Monday, 21 January)
• Re: [w3c/screen-orientation] Editorial: Introduction Section (#132) (Friday, 18 January)
• Re: [w3c/screen-orientation] Editorial: Example 1 (#133) (Thursday, 17 January)
• Re: [w3c/screen-orientation] Editorial: Example 1 (#133) (Thursday, 17 January)
• Re: [w3c/screen-orientation] Editorial: Example 1 (#133) (Thursday, 17 January)
• Re: [w3c/screen-orientation] Editorial: Example 1 (#133) (Thursday, 17 January)
• Re: [w3c/screen-orientation] Editorial: Example 1 (#133) (Thursday, 17 January)
• Re: [w3c/screen-orientation] Editorial: Example 2 (#134) (Thursday, 17 January)
• Re: [w3c/screen-orientation] Editorial: Example 2 (#134) (Thursday, 17 January)
• Re: [w3c/screen-orientation] Editorial: Example 2 (#134) (Thursday, 17 January)
• Re: [w3c/screen-orientation] Editorial: Example 3 (#135) (Thursday, 17 January)
• Re: [w3c/screen-orientation] Editorial: Example 1 (#133) (Wednesday, 16 January)
• Re: [w3c/screen-orientation] Editorial: Example 1 (#133) (Wednesday, 16 January)
• Re: [w3c/screen-orientation] Editorial: Example 2 (#134) (Wednesday, 16 January)
• Re: [w3c/screen-orientation] Editorial: Example 1 (#133) (Wednesday, 16 January)
• Re: [w3c/screen-orientation] Editorial: Example 1 (#133) (Wednesday, 16 January)
• Re: [w3c/screen-orientation] Editorial: Example 1 (#133) (Tuesday, 15 January)
• Re: [heycam/webidl] Allow identifiers that start with a hyphen. (#612) (Tuesday, 15 January)
• Re: [w3c/screen-orientation] Editorial: Introduction Section (#132) (Friday, 11 January)
• Re: [w3c/screen-orientation] Editorial: new algorithms section (#131) (Thursday, 10 January)
• Re: [w3c/screen-orientation] Editorial: new algorithms section (#131) (Thursday, 10 January)
• Re: [w3c/screen-orientation] Edits Primary and Secondary orientation definitions (#126) (Wednesday, 9 January)
• Re: [w3c/screen-orientation] Editorial: Move and edit Dependencies section (#129) (Wednesday, 9 January)
• Re: [w3c/screen-orientation] Editorial: Edits to Interface Definitions (#130) (Wednesday, 9 January)
• Re: [w3c/screen-orientation] Editorial: Edits to Interface Definitions (#130) (Wednesday, 9 January)
• Re: [w3c/screen-orientation] Editorial: Edits to Interface Definitions (#130) (Tuesday, 8 January)
• Re: [w3c/screen-orientation] Editorial: Move and edit Dependencies section (#129) (Tuesday, 8 January)
• Re: [w3c/screen-orientation] Editorial: Move and edit Dependencies section (#129) (Tuesday, 8 January)
• Re: [w3c/screen-orientation] Edits Primary and Secondary orientation definitions (#126) (Tuesday, 8 January)
• Re: [w3c/screen-orientation] Edits Primary and Secondary orientation definitions (#126) (Tuesday, 8 January)
• Re: [w3c/screen-orientation] Edits Primary and Secondary orientation definitions (#126) (Tuesday, 8 January)
• Re: [w3c/screen-orientation] Editorial: Move and edit conformance section (#128) (Tuesday, 8 January)
• Re: [w3c/screen-orientation] Editorial: Move and edit conformance section (#128) (Tuesday, 8 January)
• Re: [w3c/screen-orientation] Editorial: Move and edit Dependencies section (#129) (Tuesday, 8 January)
• Re: [w3c/screen-orientation] Editorial: Move and edit Dependencies section (#129) (Tuesday, 8 January)
• Re: [w3c/screen-orientation] Editorial: Edit Abstract (#127) (Tuesday, 8 January)
• Re: [w3c/screen-orientation] Editorial: Edit Abstract (#127) (Tuesday, 8 January)
• Re: [w3c/manifest] Application's expires (#738) (Monday, 7 January)
• Re: [w3c/manifest] Use WebIDL to describe the manifest data structure (#611) (Monday, 7 January)
• Re: [w3c/permissions] Rename 'display' permission to 'display-capture'. (#188) (Monday, 7 January)
• Re: [w3c/permissions] Rename 'display' permission to 'display-capture'. (#188) (Monday, 7 January)

Marijn Kruisselbrink

• Re: [whatwg/fetch] Follow changes from whatwg/url#371. (#857) (Monday, 14 January)
• Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371) (Friday, 11 January)
• Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371) (Thursday, 10 January)
• [whatwg/fetch] Follow changes from whatwg/url#371. (#857) (Thursday, 10 January)
• Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371) (Thursday, 10 January)
• Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371) (Wednesday, 9 January)
• Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371) (Wednesday, 9 January)
• Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371) (Wednesday, 9 January)
• Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371) (Tuesday, 8 January)
• Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371) (Tuesday, 8 January)
• Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371) (Tuesday, 8 January)
• Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371) (Monday, 7 January)
• Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371) (Monday, 7 January)
• Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371) (Monday, 7 January)
• Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371) (Friday, 4 January)

Mark Nottingham

• Re: [whatwg/fetch] Don't append controls for upstream caches. (#788) (Monday, 28 January)
• Re: [whatwg/fetch] Add support for stale-while-revalidate handling (#852) (Friday, 4 January)
• Re: [whatwg/fetch] Consider removing trailers API (#772) (Friday, 4 January)

Markus S.

• Re: [w3c/webcomponents] HTML Modules (#645) (Thursday, 17 January)
• Re: [w3c/webcomponents] HTML Modules (#645) (Wednesday, 16 January)

Masayuki Nakano

• Re: [w3c/uievents] InputEventInit data default value should be null (#139) (Monday, 21 January)

Matt Falkenhagen

• Re: [w3c/ServiceWorker] clients.get() should not resolve before sandboxing determines the origin of the client (#1385) (Thursday, 24 January)
• Re: [w3c/ServiceWorker] clients.get() should not resolve before sandboxing determines the origin of the client (#1385) (Thursday, 24 January)
• [w3c/ServiceWorker] clients.get() should not resolve before sandboxing determines the origin of the client (#1385) (Thursday, 24 January)
• Re: [w3c/ServiceWorker] Minor improvements around importScripts. (#1380) (Friday, 18 January)
• Re: [w3c/ServiceWorker] Minor improvements around importScripts. (#1380) (Friday, 18 January)
• Re: [w3c/ServiceWorker] Minor improvements around importScripts. (#1380) (Thursday, 17 January)
• Re: [w3c/ServiceWorker] Minor improvements around importScripts. (#1380) (Thursday, 17 January)
• [w3c/ServiceWorker] Minor improvements around importScripts. (#1380) (Thursday, 17 January)
• Re: [w3c/ServiceWorker] Update shouldn't fail due to MIME check or 404 for the incumbent's worker scripts (#1374) (Thursday, 17 January)
• Re: [w3c/ServiceWorker] Update shouldn't fail due to MIME check or 404 for the incumbent's worker scripts (#1374) (Thursday, 17 January)
• Re: [w3c/ServiceWorker] Don't fail update upon error fetching the incumbent worker's import s… (#1377) (Thursday, 17 January)
• Re: [w3c/ServiceWorker] Clarify dynamic-imported scripts are never installed (#1356) (Thursday, 17 January)
• Re: [w3c/ServiceWorker] Don't fail update upon error fetching the incumbent worker's import s… (#1377) (Wednesday, 16 January)
• Re: [w3c/ServiceWorker] Don't fail update upon error fetching the incumbent worker's import s… (#1377) (Wednesday, 16 January)
• Re: [w3c/ServiceWorker] Don't fail update upon error fetching the incumbent worker's import s… (#1377) (Wednesday, 16 January)

Matt Giuca

• Re: [w3c/manifest] Use WebIDL to describe the manifest data structure (#611) (Thursday, 3 January)
• Re: [w3c/manifest] When converting the JSON to IDL, catch type errors. (#753) (Thursday, 3 January)
• [w3c/manifest] When converting the JSON to IDL, catch type errors. (#753) (Thursday, 3 January)
• Re: [w3c/manifest] Application's expires (#738) (Thursday, 3 January)

Matt Polichette

• Re: [whatwg/streams] Teeing dynamically (#979) (Wednesday, 16 January)
• Re: [whatwg/streams] Teeing dynamically (#979) (Wednesday, 16 January)
• [whatwg/streams] Teeing dynamically (#979) (Friday, 11 January)

Matthew Phillips

• Re: [w3c/webcomponents] Lazy Custom Element Definitions (#782) (Thursday, 17 January)

Mattias Buelens

• Re: [whatwg/streams] ReadableStream should be an async iterable (#778) (Wednesday, 30 January)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Wednesday, 30 January)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Wednesday, 30 January)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Wednesday, 30 January)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Wednesday, 30 January)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Wednesday, 30 January)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Wednesday, 30 January)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Wednesday, 30 January)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Wednesday, 30 January)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Tuesday, 29 January)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Tuesday, 29 January)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Tuesday, 29 January)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Tuesday, 29 January)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Tuesday, 29 January)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Tuesday, 29 January)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Sunday, 27 January)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Saturday, 26 January)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Saturday, 26 January)
• [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Saturday, 26 January)
• Re: [whatwg/streams] add @@asyncIterator to ReadableStream (#954) (Thursday, 24 January)
• Re: [whatwg/streams] add @@asyncIterator to ReadableStream (#954) (Tuesday, 22 January)
• Re: [whatwg/streams] Editorial changes to transferable streams explainer (#977) (Wednesday, 16 January)

mcb0006

• [heycam/webidl] Intent to use [TreatNonObjectAsNull] (#623) (Thursday, 17 January)

mfluehr

• [whatwg/dom] Add `valid` event for form fields (#728) (Tuesday, 8 January)

Michael Stramel

• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Tuesday, 22 January)
• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Friday, 11 January)

Michael[tm] Smith

• Re: [whatwg/xhr] Fix small grammer (#234) (Monday, 21 January)

Mihai Nita

• Re: [whatwg/encoding] Big5 encoding mishandles some trailing bytes, with possible XSS (#171) (Wednesday, 30 January)
• Re: [whatwg/encoding] Big5 encoding mishandles some trailing bytes, with possible XSS (#171) (Tuesday, 29 January)
• Re: [whatwg/encoding] Big5 encoding mishandles some trailing bytes, with possible XSS (#171) (Tuesday, 29 January)
• Re: [whatwg/encoding] Big5 encoding mishandles some trailing bytes, with possible XSS (#171) (Monday, 28 January)
• Re: [whatwg/encoding] Big5 encoding mishandles some trailing bytes, with possible XSS (#171) (Thursday, 24 January)
• [whatwg/encoding] Big5 encoding mishandles some trailing bytes, with possible XSS (#171) (Wednesday, 23 January)

Mike West

• Re: [w3ctag/design-reviews] Migrating some high-entropy HTTP request headers to Client Hints. (#320) (Tuesday, 22 January)
• Re: [w3ctag/design-reviews] Migrating some high-entropy HTTP request headers to Client Hints. (#320) (Tuesday, 22 January)
• Re: [w3ctag/design-reviews] Trusted Types (#198) (Friday, 11 January)
• Re: [w3ctag/design-reviews] Migrating some high-entropy HTTP request headers to Client Hints. (#320) (Wednesday, 9 January)
• Re: [whatwg/fetch] Doc: failed CORS fetch with credentials should ignore Set-Cookie response header (#855) (Friday, 4 January)
• Re: [whatwg/fetch] Doc: failed CORS fetch with credentials should ignore Set-Cookie response header (#855) (Friday, 4 January)

mildred

• Re: [w3c/webcomponents] HTML module should require a new top level element (#752) (Thursday, 31 January)
• Re: [w3c/webcomponents] HTML module should require a new MIME type (#742) (Thursday, 31 January)
• Re: [whatwg/dom] Declarative Shadow DOM (#510) (Thursday, 31 January)
• Re: [w3c/webcomponents] [templates] Ensure that template instantiation actually improves the platform (#704) (Thursday, 31 January)
• Re: [w3c/webcomponents] Serialize shadow DOM for use in javascript disabled user agents (#788) (Wednesday, 30 January)
• [w3c/webcomponents] Serialize shadow DOM for use in javascript disabled user agents (#788) (Wednesday, 30 January)

Mounir Lamouri

• Re: [w3c/screen-orientation] Promise for unlock()? (#104) (Monday, 28 January)
• Re: [w3c/screen-orientation] Clarification regarding locking the screen orientation (#143) (Monday, 28 January)

Ms2ger

• Re: [heycam/webidl] Meta: point out commit instructions (#634) (Thursday, 31 January)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Thursday, 31 January)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Thursday, 31 January)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Thursday, 31 January)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Thursday, 31 January)
• [heycam/webidl] Add an algorithm to create a platform object. (#635) (Thursday, 31 January)
• Re: [heycam/webidl] Check ignoreNamedProps before the named property visibility algorithm. (#625) (Thursday, 31 January)
• Re: [heycam/webidl] Define "implements" checks using internal slots (#595) (Thursday, 31 January)
• Re: [heycam/webidl] Editorial: Use some more abstract operations. (#601) (Thursday, 31 January)
• Re: [heycam/webidl] Consider removing call to named property setter in legacy platform object [[Set]] (#630) (Wednesday, 30 January)
• Re: [heycam/webidl] Consider removing call to named property setter in legacy platform object [[Set]] (#630) (Wednesday, 30 January)
• Re: [heycam/webidl] Editorial: Use some more abstract operations. (#601) (Wednesday, 30 January)
• Re: [heycam/webidl] Clarify the interpretation of string literal tokens. (#621) (Wednesday, 30 January)
• Re: [heycam/webidl] Clarify the interpretation of string literal tokens. (#621) (Tuesday, 29 January)
• Re: [heycam/webidl] Fix error handling around Call(). (#618) (Tuesday, 29 January)
• Re: [heycam/webidl] Fix error handling around Call(). (#618) (Tuesday, 29 January)
• Re: [heycam/webidl] Editorial: Note that interface mixins' elements are included among interface elements (#594) (Tuesday, 29 January)
• Re: [heycam/webidl] Rename the 'float' production to 'real'. (#616) (Monday, 28 January)
• Re: [heycam/webidl] Rename the 'float' production to 'real'. (#616) (Monday, 28 January)
• Re: [heycam/webidl] Rename the 'float' production to 'real'. (#616) (Monday, 28 January)
• Re: [heycam/webidl] Consider removing call to named property setter in legacy platform object [[Set]] (#630) (Wednesday, 23 January)
• [heycam/webidl] Consider removing call to named property setter in legacy platform object [[Set]] (#630) (Wednesday, 23 January)
• Re: [heycam/webidl] Check ignoreNamedProps before the named property visibility algorithm. (#625) (Wednesday, 23 January)
• Re: [heycam/webidl] Check ignoreNamedProps before the named property visibility algorithm. (#625) (Tuesday, 22 January)
• Re: [heycam/webidl] Improve the named property visibility algorithm for Window. (#626) (Friday, 18 January)
• Re: [whatwg/fetch] Copy client-hints list from env settings object. Align CH processing (#773) (Friday, 18 January)
• [heycam/webidl] Improve the named property visibility algorithm for Window. (#626) (Friday, 18 January)
• Re: [heycam/webidl] Check ignoreNamedProps before the named property visibility algorithm. (#625) (Friday, 18 January)
• Re: [heycam/webidl] Check ignoreNamedProps before the named property visibility algorithm. (#625) (Thursday, 17 January)
• [heycam/webidl] Check ignoreNamedProps before the named property visibility algorithm. (#625) (Thursday, 17 January)
• [heycam/webidl] IsDataDescriptor check for legacy setters is not implemented (#624) (Thursday, 17 January)
• Re: [heycam/webidl] Restrict the extended attributes for partial interfaces. (#620) (Wednesday, 16 January)
• [heycam/webidl] Disallow a default value for required dictionary members in the grammar. (#622) (Wednesday, 16 January)
• Re: [heycam/webidl] Unexplained restrictions in operation bindings section (#511) (Wednesday, 16 January)
• [heycam/webidl] Clarify the interpretation of string literal tokens. (#621) (Wednesday, 16 January)
• [heycam/webidl] Restrict the extended attributes for partial interfaces. (#620) (Wednesday, 16 January)
• [heycam/webidl] Editorial: Make the opName argument required. (#619) (Wednesday, 16 January)
• Re: [heycam/webidl] "call a user object’s operation" should not have an optional argument in the middle (#534) (Wednesday, 16 January)
• Re: [heycam/webidl] Represent objects with both specified and unspecified members (#568) (Wednesday, 16 January)
• Re: [heycam/webidl] Editorial: Use some more abstract operations. (#601) (Wednesday, 16 January)
• Re: [heycam/webidl] Editorial: Remove section numbers from ES references. (#617) (Wednesday, 16 January)
• [heycam/webidl] Fix error handling around Call(). (#618) (Tuesday, 15 January)
• [heycam/webidl] Editorial: Remove section numbers from ES references. (#617) (Tuesday, 15 January)
• [heycam/webidl] Rename the 'float' production to 'real'. (#616) (Tuesday, 15 January)
• Re: [heycam/webidl] Rename the 'float' production to 'real'. (#616) (Tuesday, 15 January)
• Re: [heycam/webidl] Allow identifiers that start with a hyphen. (#612) (Tuesday, 15 January)
• [heycam/webidl] Editorial: Clarify the wording of an Exposed requirement. (#615) (Tuesday, 15 January)
• [heycam/webidl] Disallow Replaceable on namespaces, and fix the attribute setter creation. (#614) (Tuesday, 15 January)
• [heycam/webidl] Editorial: Refer to the correct types in integer conversion algorithms. (#613) (Tuesday, 15 January)
• [heycam/webidl] Allow identifiers that start with a hyphen. (#612) (Tuesday, 15 January)
• [heycam/webidl] Use %PromiseProto_then% to 'perform some steps once a promise is settled'. (#611) (Tuesday, 15 January)
• Re: [heycam/webidl] Track PR #425 (#429) (Tuesday, 15 January)
• Re: [heycam/webidl] Remove [NoInterfaceObject]. (#609) (Tuesday, 15 January)
• Re: [heycam/webidl] Specify that returned Promises are created in the relevant realm (#598) (Monday, 14 January)
• [heycam/webidl] Use map/exists to define dictionary/present. (#610) (Monday, 14 January)
• [heycam/webidl] Remove [NoInterfaceObject]. (#609) (Monday, 14 January)
• Re: [heycam/webidl] Clarify [[Call]] + [[Construct]] for named (and possibly non-named) constructors (#278) (Monday, 14 January)
• Re: [heycam/webidl] Investigate/file bugs on named constructor prototype chain (#276) (Monday, 14 January)
• Re: [heycam/webidl] Editorial: Use some more abstract operations. (#601) (Monday, 14 January)
• [heycam/webidl] Named properties object / named property visibility algorithm with property on Window.prototype (#607) (Friday, 11 January)
• Re: [heycam/webidl] Editorial: Use some more abstract operations. (#601) (Wednesday, 2 January)

Mustaq Ahmed

• Re: [w3c/uievents] MouseEvent.screenX/Y coordinate space id not clear (#150) (Thursday, 17 January)

Nashorn

• Re: [w3c/webcomponents] Element Behaviors, and the has="" attribute. A useful alternative to Custom Elements in many cases! (#727) (Thursday, 10 January)

Navid Zolghadr

• Re: [w3c/pointerlock] Treat DocumentOrShadowRoot as an interface mixin (#40) (Monday, 21 January)
• Re: [w3c/uievents] Add reference to the element (#217) (Thursday, 3 January)
• Re: [w3c/uievents] Add reference to the element (#217) (Thursday, 3 January)
• [w3c/uievents] Add reference to the element (#217) (Thursday, 3 January)

Nicholas Shanks

• [whatwg/url] Behaviour regarding percent-encoding of commas in URLSearchParams (#423) (Tuesday, 8 January)

Nick Fitzgerald

• Re: [heycam/webidl] Annotations for what may throw (#603) (Monday, 7 January)

Nicolas Hoizey

• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Tuesday, 8 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Monday, 7 January)

NSoiffer

• Re: [w3ctag/design-reviews] Review MathML (#313) (Tuesday, 22 January)

Osintopsec

• Re: [whatwg/fetch] Change 3.2.6 Examples to reflect current state of implementations (#858) (Wednesday, 23 January)
• Re: [whatwg/fetch] Change 3.2.6 Examples to reflect current state of implementations (#858) (Tuesday, 22 January)
• Re: [whatwg/fetch] Change 3.2.6 Examples to reflect current state of implementations (#858) (Tuesday, 22 January)
• [whatwg/fetch] Change 3.2.6 Examples to reflect current state of implementations (#858) (Monday, 14 January)
• Re: [whatwg/fetch] Doc: failed CORS fetch with credentials should ignore Set-Cookie response header (#855) (Tuesday, 8 January)
• Re: [whatwg/fetch] Doc: failed CORS fetch with credentials should ignore Set-Cookie response header (#855) (Saturday, 5 January)
• Re: [whatwg/fetch] Doc: failed CORS fetch with credentials should ignore Set-Cookie response header (#855) (Friday, 4 January)
• [whatwg/fetch] Doc: failed CORS fetch with credentials should ignore Set-Cookie response header (#855) (Friday, 4 January)

Patrick H. Lauke

• Re: [w3c/touch-events] Respec fixes (#102) (Sunday, 6 January)
• Re: [w3c/touch-events] Respec fixes (#102) (Sunday, 6 January)

peria

• Re: [heycam/webidl] Disallow underscore-and-hyphen only identifiers (#633) (Wednesday, 30 January)
• [heycam/webidl] Disallow underscore-and-hyphen only identifiers (#633) (Wednesday, 30 January)
• Re: [heycam/webidl] Better regular expression for identifiers (#632) (Tuesday, 29 January)
• Re: [heycam/webidl] Better regular expression for identifiers (#632) (Tuesday, 29 January)

Peter Beverloo

• [w3ctag/design-reviews] Contact API (#337) (Wednesday, 23 January)

Peter Linss

• Re: [w3ctag/design-reviews] Trusted Types (#198) (Friday, 11 January)

Philip Jägenstedt

• Re: [whatwg/encoding] Big5 encoding mishandles some trailing bytes, with possible XSS (#171) (Wednesday, 30 January)
• Re: [w3c/screen-orientation] Clarification on animation frame task (#136) (Thursday, 24 January)
• Re: [w3c/uievents] Change InputEventInit.data default value to null (#148) (Monday, 21 January)
• [w3c/pointerlock] Treat DocumentOrShadowRoot as an interface mixin (#40) (Monday, 21 January)
• Re: [whatwg/fullscreen] Review Draft Publication: January 2019 (#142) (Friday, 18 January)
• Re: [w3ctag/design-reviews] imagesrcset and imagesizes attributes on link rel=preload (#329) (Tuesday, 15 January)

Philip Walton

• Re: [w3c/ServiceWorker] Add a script version property to the ServiceWorker object (#1387) (Thursday, 31 January)
• [w3c/ServiceWorker] Add a script version property to the ServiceWorker object (#1387) (Thursday, 31 January)
• Re: [w3c/ServiceWorker] Clarify dynamic-imported scripts are never installed (#1356) (Friday, 18 January)
• Re: [w3c/ServiceWorker] Clarify dynamic-imported scripts are never installed (#1356) (Thursday, 17 January)
• [w3c/ServiceWorker] Add registeringClientId to the ServiceWorker object (#1379) (Wednesday, 2 January)

PhistucK

• Re: [whatwg/url] Make combining a URL (string) with a query easier (#413) (Friday, 18 January)

Pieter Colpaert

• Re: [whatwg/fetch] CORS: arbitrary blocking of accept header based on length (#862) (Tuesday, 29 January)
• Re: [whatwg/fetch] CORS: arbitrary blocking of accept header based on length (#862) (Tuesday, 29 January)
• Re: [whatwg/fetch] CORS: arbitrary blocking of accept header based on length (#862) (Tuesday, 29 January)
• Re: [whatwg/fetch] CORS: arbitrary blocking of accept header based on length (#862) (Tuesday, 29 January)
• Re: [whatwg/fetch] CORS: arbitrary blocking of accept header based on length (#862) (Tuesday, 29 January)
• Re: [whatwg/fetch] CORS: arbitrary blocking of accept header based on length (#862) (Monday, 28 January)
• [whatwg/fetch] CORS: arbitrary blocking of accept header based on length (#862) (Monday, 28 January)

Piotrek Koszuliński

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

Quinn Chaffee

• Re: [w3ctag/design-reviews] Migrating some high-entropy HTTP request headers to Client Hints. (#320) (Tuesday, 22 January)
• Re: [w3ctag/design-reviews] Migrating some high-entropy HTTP request headers to Client Hints. (#320) (Tuesday, 22 January)

Raphael Kubo da Costa

• Re: [heycam/webidl] Investigate/file bugs on named constructor prototype chain (#276) (Monday, 14 January)

Rasmus Eneman

• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Tuesday, 8 January)

Ricky Miller

• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Wednesday, 9 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Wednesday, 9 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Tuesday, 8 January)

riszinryan

• [whatwg/url] U got issues (#426) (Saturday, 26 January)

Robert Kelley

• Re: [w3c/webcomponents] Editor support for WebComponents (#776) (Wednesday, 23 January)

Ruben Verborgh

• [whatwg/fetch] Allow servers to completely opt out of current and future CORS protection (#865) (Thursday, 31 January)
• Re: [whatwg/fetch] CORS: arbitrary blocking of accept header based on length (#862) (Thursday, 31 January)
• Re: [whatwg/fetch] CORS: arbitrary blocking of accept header based on length (#862) (Tuesday, 29 January)
• Re: [whatwg/fetch] CORS: arbitrary blocking of accept header based on length (#862) (Tuesday, 29 January)

Rune Lillesveen

• Re: [w3c/webcomponents] Support for pseudo elements with ::slotted() selectors (#655) (Wednesday, 23 January)

Ryosuke Niwa

• Re: [whatwg/dom] MutationObserver needs an equivalent of disconnected & connected callbacks (#533) (Thursday, 31 January)
• Re: [whatwg/dom] MutationObserver needs an equivalent of disconnected & connected callbacks (#533) (Thursday, 31 January)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Thursday, 31 January)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Tuesday, 29 January)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Tuesday, 29 January)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Tuesday, 29 January)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Tuesday, 29 January)
• Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550) (Tuesday, 29 January)
• Re: [w3c/webcomponents] [idea] making builtin elements more like custom elements (#785) (Tuesday, 29 January)
• Re: [w3c/webcomponents] [idea] making builtin elements more like custom elements (#785) (Tuesday, 29 January)
• Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713) (Tuesday, 29 January)
• Re: [w3c/webcomponents] Web Components F2F topics for 2018 TPAC (#763) (Tuesday, 29 January)
• [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Tuesday, 29 January)
• Re: [w3c/DOM-Parsing] Spec out normative text when parseFromString() is passed an unsupported MIME type (#41) (Sunday, 27 January)
• Re: [w3c/webcomponents] [Shadow]: return of multiple shadow roots? (#780) (Wednesday, 9 January)
• Re: [whatwg/dom] Composed tree infrastructure (#725) (Wednesday, 9 January)

sam goto

• [w3ctag/design-reviews] User Idle Detection (#336) (Tuesday, 22 January)

Sam Richard

• Re: [w3c/webcomponents] Allow attribute changes/child creation on custom element creation (#781) (Wednesday, 9 January)
• Re: [w3c/webcomponents] Allow attribute changes/child creation on custom element creation (#781) (Wednesday, 9 January)
• [w3c/webcomponents] Allow attribute changes/child creation on custom element creation (#781) (Tuesday, 8 January)

Sam Vloeberghs

• Re: [w3c/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Thursday, 10 January)
• Re: [w3c/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Thursday, 10 January)

Samuel Williams

• Re: [whatwg/fetch] Consider removing trailers API (#772) (Wednesday, 2 January)

Sebastian Müller

• Re: [w3c/webcomponents] SVG use element can't reference an element within the same shadow tree (#772) (Tuesday, 15 January)

Selwyn

• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Thursday, 10 January)

Serhii Kulykov

• Re: [w3c/webcomponents] Support for pseudo elements with ::slotted() selectors (#655) (Friday, 18 January)

shadulsikder90

• [heycam/webidl] Intent to use Constants (#608) (Sunday, 13 January)

Shao, Ting

• Re: [w3c/ServiceWorker] Update shouldn't fail due to MIME check or 404 for the incumbent's worker scripts (#1374) (Thursday, 17 January)

Shrey Banga

• [w3c/editing] Disambiguate caret position at wrapped line boundaries (#189) (Wednesday, 30 January)

Simon Anciaux

• Re: [whatwg/encoding] Differences between tests and specification (#169) (Saturday, 26 January)

smaug----

• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Thursday, 31 January)
• Re: [whatwg/dom] Composed tree infrastructure (#725) (Monday, 14 January)
• Re: [whatwg/xhr] FormData constructor should throw if "constructing the entry list" re… (#231) (Thursday, 10 January)

spanicker

• [w3ctag/design-reviews] Scheduling APIs (#338) (Thursday, 24 January)

TAMURA, Kent

• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Wednesday, 9 January)
• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Tuesday, 8 January)

Terje Bråten

• Re: [whatwg/xhr] Blob name (#232) (Wednesday, 9 January)
• Re: [whatwg/xhr] Blob name (#232) (Wednesday, 9 January)
• Re: [whatwg/xhr] Blob name (#232) (Wednesday, 9 January)
• [whatwg/xhr] Blob name (#232) (Wednesday, 9 January)

tguild

• Re: [w3ctag/design-reviews] Vehicle Information Service Specification (VISS) CR (#234) (Wednesday, 9 January)

Thomas Allmer

• Re: [w3c/webcomponents] appreciate your feedback for custom element diagram (#784) (Saturday, 26 January)

Thomas Steiner

• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Monday, 7 January)

Till Schneidereit

• Re: [whatwg/streams] Switching to Web IDL (#963) (Thursday, 31 January)

Timothy Gu

• Re: [whatwg/url] U got issues (#426) (Saturday, 26 January)
• Re: [heycam/webidl] Editorial: Remove section numbers from ES references. (#617) (Wednesday, 16 January)
• Re: [heycam/webidl] Editorial: Remove section numbers from ES references. (#617) (Wednesday, 16 January)
• Re: [whatwg/url] Behaviour regarding percent-encoding of commas in URLSearchParams (#423) (Wednesday, 9 January)

Travis Leithead

• Re: [w3ctag/design-reviews] HTML Modules (#334) (Tuesday, 29 January)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Tuesday, 29 January)
• Re: [w3ctag/design-reviews] transferable streams (#332) (Tuesday, 15 January)
• Re: [whatwg/streams] Editorial changes to transferable streams explainer (#977) (Tuesday, 15 January)
• Re: [heycam/webidl] Poorly worded normative requirement could be improved (#548) (Tuesday, 15 January)
• Re: [w3ctag/design-reviews] HTML General Review: Web Sockets (#268) (Tuesday, 8 January)
• Re: [w3ctag/design-reviews] HTML General Review: Web Sockets (#268) (Tuesday, 8 January)
• Re: [w3ctag/design-reviews] Background fetch (#279) (Tuesday, 8 January)
• Re: [w3ctag/design-reviews] Background fetch (#279) (Tuesday, 8 January)
• Re: [w3ctag/design-reviews] Background fetch (#279) (Tuesday, 8 January)

Tsuyoshi Horo

• [whatwg/fetch] IP address of response (#863) (Tuesday, 29 January)

Victor Costan

• Re: [w3c/IndexedDB] Disallow starting readwrite transactions while readonly transactions are running? (#253) (Friday, 18 January)
• Re: [w3c/IndexedDB] Disallow starting readwrite transactions while readonly transactions are running? (#253) (Friday, 18 January)

victor felder

• [heycam/webidl] Editorial: fix language in nullable types section (#628) (Monday, 21 January)

Vincent Weevers

• Re: [w3c/IndexedDB] Disallow starting readwrite transactions while readonly transactions are running? (#253) (Friday, 18 January)
• Re: [w3c/IndexedDB] Disallow starting readwrite transactions while readonly transactions are running? (#253) (Friday, 18 January)
• Re: [w3c/IndexedDB] Disallow starting readwrite transactions while readonly transactions are running? (#253) (Friday, 18 January)

Wes Roberts

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

WORMSS

• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Wednesday, 9 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Monday, 7 January)

Xidorn Quan

• Re: [whatwg/fullscreen] Re-introduce the hierarchy restrictions (#140) (Friday, 4 January)
• Re: [whatwg/fullscreen] Investigate whether nested fullscreen element is necessary (#119) (Friday, 4 January)
• Re: [whatwg/fullscreen] Investigate whether nested fullscreen element is necessary (#119) (Friday, 4 January)

Yaron Tausky

• [w3c/ServiceWorker] Cache.put() does not read response's body (#1383) (Monday, 21 January)

Yoav Weiss

• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Thursday, 31 January)
• Re: [whatwg/fetch] IP address of response (#863) (Tuesday, 29 January)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Monday, 28 January)
• Re: [whatwg/fetch] Copy client-hints list from env settings object. Align CH processing (#773) (Wednesday, 23 January)
• Re: [whatwg/fetch] Copy client-hints list from env settings object. Align CH processing (#773) (Monday, 21 January)
• Re: [whatwg/fetch] Copy client-hints list from env settings object. Align CH processing (#773) (Friday, 18 January)
• Re: [whatwg/fetch] Copy client-hints list from env settings object. Align CH processing (#773) (Friday, 18 January)
• Re: [whatwg/fetch] Copy client-hints list from env settings object. Align CH processing (#773) (Thursday, 17 January)
• Re: [whatwg/fetch] Copy client-hints list from env settings object. Align CH processing (#773) (Thursday, 17 January)
• Re: [whatwg/fetch] Copy client-hints list from env settings object. Align CH processing (#773) (Thursday, 17 January)
• Re: [whatwg/fetch] Copy client-hints list from env settings object. Align CH processing (#773) (Thursday, 17 January)
• Re: [whatwg/fetch] Copy client-hints list from env settings object. Align CH processing (#773) (Thursday, 17 January)
• Re: [whatwg/fetch] Copy client-hints list from env settings object. Align CH processing (#773) (Wednesday, 16 January)
• Re: [w3c/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Thursday, 10 January)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Monday, 7 January)

youennf

• Re: [whatwg/fetch] Cross-Origin-Resource-Policy (was: From-Origin) (#687) (Wednesday, 16 January)
• Re: [whatwg/fetch] Cross-Origin-Resource-Policy (was: From-Origin) (#687) (Tuesday, 15 January)

Yutaka Hirano

• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Thursday, 31 January)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Wednesday, 30 January)

จตุรงค์ ประเสริฐ

• [whatwg/fetch] สวัสดี (#859) (Tuesday, 15 January)

Last message date: Thursday, 31 January 2019 23:29:42 UTC