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

Adam Rice

• Re: [whatwg/streams] ReadableStreamTee: do not read when already pulling (#997) (Monday, 25 February)
• Re: [whatwg/streams] ReadableStreamTee: do not read when already pulling (#997) (Monday, 25 February)
• Re: [whatwg/streams] ReadableStreamTee pulls too many chunks (#996) (Friday, 22 February)
• Re: [whatwg/streams] In ReadableStreamTee, replace _closedOrErrored_ with _closed_ (#994) (Thursday, 21 February)
• [whatwg/streams] In ReadableStreamTee, replace _closedOrErrored_ with _closed_ (#994) (Thursday, 21 February)
• Re: [whatwg/streams] Semantics of |closedOrErrored| variable in ReadableStreamTee are odd (#991) (Thursday, 21 February)
• Re: [whatwg/streams] Remove call to ClearPendingPullIntos from SetUpReadableByteSC (#993) (Wednesday, 20 February)
• Re: [whatwg/streams] SetUpReadableByteStreamController initializes [[pendingPullIntos]] twice (#975) (Wednesday, 20 February)
• Re: [whatwg/streams] ReadableStream reference implementation: remove unnecessary code (#992) (Wednesday, 20 February)
• Re: [whatwg/streams] ReadableStream reference implementation: remove unnecessary code (#992) (Wednesday, 20 February)
• [whatwg/streams] Remove call to ClearPendingPullIntos from SetUpReadableByteSC (#993) (Tuesday, 19 February)
• Re: [whatwg/streams] ReadableStream reference implementation: remove unnecessary code (#992) (Tuesday, 19 February)
• [whatwg/streams] ReadableStream reference implementation: remove unnecessary code (#992) (Tuesday, 19 February)
• Re: [whatwg/streams] Initialize ReadableByteStreamController.[[byobRequest]] to undefined (#990) (Tuesday, 19 February)
• [whatwg/streams] Semantics of |closedOrErrored| variable in ReadableStreamTee are odd (#991) (Tuesday, 19 February)
• Re: [whatwg/streams] Initialize ReadableByteStreamController.[[byobRequest]] to undefined (#990) (Tuesday, 19 February)
• Re: [whatwg/streams] Initialize ReadableByteStreamController.[[byobRequest]] to undefined (#990) (Tuesday, 19 February)
• [whatwg/streams] Give pipeTo more latitude about byob chunk sizes (#989) (Monday, 18 February)
• Re: [whatwg/streams] better-assert is broken (#985) (Monday, 18 February)
• Re: [whatwg/streams] Stop using better-assert (#988) (Monday, 18 February)
• Re: [whatwg/streams] Treat forAuthorCode as an internal slot of reader object. (#969) (Monday, 18 February)
• Re: [whatwg/streams] Treat forAuthorCode as an internal slot of reader object. (#969) (Monday, 18 February)
• Re: [whatwg/streams] Treat forAuthorCode as an internal slot of reader object (#984) (Monday, 18 February)
• Re: [whatwg/streams] forAuthorCode can be a bit per reader (#964) (Monday, 18 February)
• [whatwg/streams] Stop using better-assert (#988) (Monday, 18 February)
• [whatwg/streams] Replace impossible condition with assert (#987) (Monday, 18 February)
• Re: [whatwg/streams] better-assert is broken (#985) (Monday, 18 February)
• Re: [whatwg/streams] better-assert is broken (#985) (Friday, 15 February)
• [whatwg/streams] better-assert is broken (#985) (Friday, 15 February)
• Re: [whatwg/streams] Possible feature discussion: opaque streams (#983) (Thursday, 14 February)
• Re: [whatwg/streams] Treat forAuthorCode as an internal slot of reader object (#984) (Tuesday, 12 February)
• Re: [whatwg/streams] Treat forAuthorCode as an internal slot of reader object (#984) (Tuesday, 12 February)
• [whatwg/streams] Possible feature discussion: opaque streams (#983) (Thursday, 7 February)
• Re: [whatwg/streams] Switching to Web IDL (#963) (Thursday, 7 February)
• Re: [whatwg/streams] ReadableStream should be an async iterable (#778) (Thursday, 7 February)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Wednesday, 6 February)
• Re: [whatwg/streams] ReadableStream should be an async iterable (#778) (Wednesday, 6 February)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Wednesday, 6 February)
• Re: [whatwg/streams] Editorial changes to transferable streams explainer (#977) (Tuesday, 5 February)
• Re: [whatwg/streams] Editorial changes to transferable streams explainer (#977) (Tuesday, 5 February)
• Re: [whatwg/streams] Editorial changes to transferable streams explainer (#977) (Tuesday, 5 February)
• Re: [whatwg/streams] Editorial changes to transferable streams explainer (#977) (Tuesday, 5 February)
• Re: [whatwg/streams] Editorial changes to transferable streams explainer (#977) (Tuesday, 5 February)
• Re: [whatwg/streams] "Let returnValue be the result of performing con..." (#982) (Tuesday, 5 February)
• [whatwg/streams] "Let returnValue be the result of performing con..." (#982) (Monday, 4 February)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Monday, 4 February)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Monday, 4 February)
• Re: [whatwg/streams] "npm run coverage" is no longer working (#981) (Monday, 4 February)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Monday, 4 February)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Monday, 4 February)

Addison Phillips

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

Adrian

• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Wednesday, 6 February)
• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Wednesday, 6 February)

aleemb

• Re: [w3c/ServiceWorker] Service-Worker-Allowed can be cross-origin to the script URL. (#1307) (Thursday, 21 February)

Alex Inkin

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

Alex Patterson

• Re: [w3c/manifest] Icon shapes and masking (#555) (Monday, 18 February)
• Re: [w3c/manifest] Icon shapes and masking (#555) (Monday, 18 February)

Alex Russell

• Re: [w3ctag/design-reviews] FetchEvent Worker Timing (#317) (Wednesday, 6 February)
• Re: [w3ctag/design-reviews] FetchEvent Worker Timing (#317) (Wednesday, 6 February)
• Re: [w3ctag/design-reviews] JavaScript WeakRefs (#321) (Wednesday, 6 February)
• Re: [w3ctag/design-reviews] Feature policy control over sandbox features (#339) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] WebRTC DSCP Control API (#325) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] Scheduling APIs (#338) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] User Idle Detection (#336) (Tuesday, 5 February)

alexistderking

• Re: [whatwg/fetch] Fix typo in word "falure". (#868) (Monday, 11 February)
• Re: [whatwg/fetch] Fix typo in word "falure". (#868) (Monday, 11 February)
• [whatwg/fetch] Fix typo in word "falure". (#868) (Monday, 4 February)
• [whatwg/fetch] Typo "If mimeType is falure" (#866) (Friday, 1 February)

aliams

• Re: [w3c/WebPlatformWG] Promote File Handling to WICG (#127) (Friday, 8 February)

Alice

• Re: [w3ctag/design-reviews] JavaScript WeakRefs (#321) (Tuesday, 26 February)
• Re: [w3ctag/design-reviews] CSS Properties and Values API Level 1 (#318) (Tuesday, 5 February)

Allen Wirfs-Brock

• Re: [heycam/webidl] Can we use ObjectCreate in object creation? + other editorial tweaks (#655) (Tuesday, 26 February)

Amelia Bellamy-Royds

• Re: [w3c/webcomponents] Custom pseudo-classes for host elements via shadow roots (:state) (#738) (Saturday, 2 February)

Andrea Giammarchi

• Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550) (Sunday, 3 February)
• Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550) (Friday, 1 February)

Andrea Puddu

• Re: [w3c/uievents] Different mousedown behavior between Firefox and Chrome/Safari (#201) (Monday, 11 February)

Andreas

• Re: [w3c/webcomponents] appreciate your feedback for custom element diagram (#784) (Tuesday, 26 February)
• Re: [w3c/webcomponents] appreciate your feedback for custom element diagram (#784) (Tuesday, 26 February)
• Re: [w3c/webcomponents] appreciate your feedback for custom element diagram (#784) (Tuesday, 26 February)
• Re: [w3c/webcomponents] appreciate your feedback for custom element diagram (#784) (Wednesday, 20 February)
• Re: [w3c/webcomponents] appreciate your feedback for custom element diagram (#784) (Wednesday, 20 February)
• Re: [w3c/webcomponents] appreciate your feedback for custom element diagram (#784) (Wednesday, 20 February)
• Re: [w3c/webcomponents] appreciate your feedback for custom element diagram (#784) (Tuesday, 19 February)

Andrew Betts

• Re: [w3ctag/design-reviews] Feature policy evolution (#341) (Friday, 8 February)
• [w3ctag/design-reviews] Feature policy evolution (#341) (Thursday, 7 February)

andruud

• Re: [w3ctag/design-reviews] CSS Properties and Values API Level 1 (#318) (Monday, 11 February)
• Re: [w3ctag/design-reviews] CSS Properties and Values API Level 1 (#318) (Monday, 11 February)

Andy Allord

• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Wednesday, 6 February)
• Re: [w3c/manifest] Install button on another domain (#726) (Wednesday, 6 February)

Andy Earnshaw

• Re: [w3c/webcomponents] CSS encapsulation and common CSS rules (#800) (Thursday, 28 February)
• Re: [w3c/webcomponents] CSS encapsulation and common CSS rules (#800) (Thursday, 28 February)
• Re: [w3c/webcomponents] Proposal: a native solution for virtual scrolling (#791) (Thursday, 28 February)
• Re: [w3c/webcomponents] Proposal: a native solution for virtual scrolling (#791) (Wednesday, 27 February)
• Re: [w3c/webcomponents] Proposal: a native solution for virtual scrolling (#791) (Tuesday, 12 February)
• Re: [w3c/webcomponents] Proposal: a native solution for virtual scrolling (#791) (Sunday, 10 February)
• [w3c/webcomponents] Proposal: a native solution for virtual scrolling (#791) (Friday, 8 February)
• Re: [w3c/webcomponents] A way to detect if a custom element was constructed during customElements.define call? (#790) (Wednesday, 6 February)
• Re: [whatwg/dom] Declarative Shadow DOM (#510) (Monday, 4 February)
• Re: [w3c/webcomponents] Serialize shadow DOM for use in javascript disabled user agents (#788) (Saturday, 2 February)

Anne van Kesteren

• Re: [whatwg/fetch] More CORB-protected MIME types - safelist-based approach (#721) (Thursday, 28 February)
• Re: [heycam/webidl] Editorial: remove redundant requirement for existence of 'length' (#667) (Thursday, 28 February)
• Re: [heycam/webidl] Editorial: run platform algorithms on IDL objects (#666) (Thursday, 28 February)
• Re: [heycam/webidl] Editorial: run platform algorithms on IDL objects (#666) (Thursday, 28 February)
• Re: [heycam/webidl] Formalize the 'this' and 'given value' ambient values (#665) (Thursday, 28 February)
• Re: [heycam/webidl] Numeric type reform strawperson (#33) (Thursday, 28 February)
• Re: [w3c/webcomponents] Include updated info on HTML Modules (#799) (Wednesday, 27 February)
• Re: [heycam/webidl] Editorial: improve language around conversions to JS (#664) (Wednesday, 27 February)
• Re: [heycam/webidl] Formalize the 'this' and 'given value' ambient values (#665) (Wednesday, 27 February)
• Re: [heycam/webidl] Editorial: improve language around conversions to JS (#664) (Wednesday, 27 February)
• Re: [heycam/webidl] Is a subclass still a platform object? (#540) (Wednesday, 27 February)
• Re: [w3c/webcomponents] How to handle non-type=”module” scripts in HTML Modules? (#798) (Wednesday, 27 February)
• Re: [w3c/webcomponents] Quirks render mode in HTML Modules (#797) (Wednesday, 27 February)
• Re: [heycam/webidl] Remove the 'user object' concept. (#662) (Wednesday, 27 February)
• Re: [heycam/webidl] Review handling of WindowProxy (#656) (Wednesday, 27 February)
• Re: [heycam/webidl] Should callback interfaces with more than one operation be supported? (#661) (Tuesday, 26 February)
• [heycam/webidl] How to deal with Location (#660) (Tuesday, 26 February)
• Re: [heycam/webidl] Can we use ObjectCreate in object creation? + other editorial tweaks (#655) (Tuesday, 26 February)
• Re: [heycam/webidl] Referencing "implements" (#659) (Tuesday, 26 February)
• Re: [heycam/webidl] Review handling of WindowProxy (#656) (Tuesday, 26 February)
• Re: [whatwg/dom] Run insertion steps after DocumentFragment insertion completes (#576) (Tuesday, 26 February)
• Re: [whatwg/dom] Run insertion steps after DocumentFragment insertion completes (#576) (Tuesday, 26 February)
• Re: [whatwg/dom] Use a queue of deferred steps in the node insertion algorithm (#732) (Tuesday, 26 February)
• Re: [w3c/webcomponents] [Shadow] Slotting indirect children (#574) (Tuesday, 26 February)
• Re: [w3c/webcomponents] Update HTML Modules Proposed Spec changes and initial proposal document (#793) (Tuesday, 26 February)
• Re: [heycam/webidl] Can we use ObjectCreate in object creation? + other editorial tweaks (#655) (Tuesday, 26 February)
• Re: [heycam/webidl] Can we use ObjectCreate in object creation? + other editorial tweaks (#655) (Monday, 25 February)
• [heycam/webidl] Referencing "implements" (#659) (Monday, 25 February)
• Re: [heycam/webidl] Clarify object creation in named constructors (#652) (Monday, 25 February)
• Re: [heycam/webidl] Clarify object creation in named constructors (#652) (Monday, 25 February)
• Re: [heycam/webidl] Disallow combining LegacyWindowAlias and LegacyNamespace (#651) (Monday, 25 February)
• Re: [whatwg/fetch] Cannot get next URL for redirect="manual" (#763) (Saturday, 23 February)
• Re: [whatwg/fetch] Add domintro explanations for web developers (#543) (Friday, 22 February)
• Re: [whatwg/fetch] Remove "filesystem" URL scheme (#846) (Friday, 22 February)
• Re: [whatwg/fetch] Fixed Issue-846 : remove URL filesystem scheme (#873) (Friday, 22 February)
• Re: [whatwg/fetch] Fixed Issue-846 : remove URL filesystem scheme (#873) (Friday, 22 February)
• Re: [whatwg/fetch] Fixed Issue-846 : remove URL filesystem scheme (#873) (Friday, 22 February)
• Re: [whatwg/fetch] can body consuming be interrupted by response/body GC? (#874) (Friday, 22 February)
• Re: [whatwg/dom] window.event and IFRAMEs (#735) (Friday, 22 February)
• Re: [whatwg/dom] window.event and IFRAMEs (#735) (Friday, 22 February)
• Re: [whatwg/fetch] Remove "filesystem" URL scheme (#846) (Friday, 22 February)
• Re: [heycam/webidl] Add a Privacy and Security Considerations section (#647) (Friday, 22 February)
• Re: [whatwg/fullscreen] Fix logical error of filling fullscreenElements (3.12) (#145) (Friday, 22 February)
• Re: [whatwg/fetch] Fixed Issue-846 : remove URL filesystem scheme (#873) (Friday, 22 February)
• Re: [whatwg/fullscreen] Fix logical error of filling fullscreenElements (3.12) (#145) (Friday, 22 February)
• Re: [whatwg/dom] window.event and IFRAMEs (#735) (Friday, 22 February)
• Re: [whatwg/fetch] Remove "filesystem" URL scheme (#846) (Friday, 22 February)
• Re: [whatwg/fullscreen] Rephrase: 3.12 While the first element in fullscreenElements is ... (#144) (Thursday, 21 February)
• Re: [w3c/ServiceWorker] Service-Worker-Allowed can be cross-origin to the script URL. (#1307) (Thursday, 21 February)
• Re: [w3c/ServiceWorker] `<iframe sandbox />` + SW (#1390) (Wednesday, 20 February)
• Re: [w3c/ServiceWorker] `<iframe sandbox />` + SW (#1390) (Wednesday, 20 February)
• Re: [w3c/ServiceWorker] `<iframe sandbox />` + SW (#1390) (Wednesday, 20 February)
• Re: [w3c/ServiceWorker] `<iframe sandbox />` + SW (#1390) (Wednesday, 20 February)
• Re: [w3c/ServiceWorker] `<iframe sandbox />` + SW (#1390) (Wednesday, 20 February)
• Re: [heycam/webidl] Improve the named property visibility algorithm for Window. (#626) (Wednesday, 20 February)
• Re: [w3c/webcomponents] JSON "modules" (#770) (Wednesday, 20 February)
• Re: [heycam/webidl] Editorial: add a Privacy and Security Considerations section (#647) (Monday, 18 February)
• Re: [whatwg/url] Review Draft Publication: February 2019 (#431) (Monday, 18 February)
• [whatwg/url] Review Draft Publication: February 2019 (#432) (Monday, 18 February)
• Re: [whatwg/xhr] Review Draft Publication: February 2019 (#237) (Monday, 18 February)
• [whatwg/xhr] Review Draft Publication: February 2019 (#238) (Monday, 18 February)
• Re: [whatwg/xhr] Review Draft Publication: February 2019 (#237) (Monday, 18 February)
• Re: [whatwg/url] Review Draft Publication: February 2019 (#431) (Monday, 18 February)
• [whatwg/xhr] Review Draft Publication: February 2019 (#237) (Monday, 18 February)
• [whatwg/streams] Review Draft Publication: February 2019 (#986) (Monday, 18 February)
• [whatwg/url] Review Draft Publication: February 2019 (#431) (Monday, 18 February)
• [whatwg/storage] Review Draft Publication: February 2019 (#67) (Monday, 18 February)
• Re: [w3c/FileAPI] Fix Web IDL extended attribute usage: [Clamp] now applies to types (#116) (Monday, 18 February)
• Re: [w3c/FileAPI] Fix Web IDL extended attribute usage: [Clamp] now applies to types (#116) (Monday, 18 February)
• Re: [whatwg/fetch] Tests do not always require Origin header when mode is "cors" (#871) (Monday, 18 February)
• Re: [whatwg/fetch] Tests do not always require Origin header when mode is "cors" (#871) (Monday, 18 February)
• [whatwg/dom] Dispatching slotchange within a compound microtask (#734) (Sunday, 17 February)
• Re: [whatwg/fetch] Remove "filesystem" URL scheme (#846) (Sunday, 17 February)
• Re: [w3c/webcomponents] Question: where to incubate HTML modules? (#794) (Sunday, 17 February)
• Re: [w3c/webcomponents] Question: where to incubate HTML modules? (#794) (Sunday, 17 February)
• Re: [whatwg/fetch] Tests do not always require Origin header when mode is "cors" (#871) (Sunday, 17 February)
• Re: [whatwg/fetch] Tests do not always require Origin header when mode is "cors" (#871) (Sunday, 17 February)
• Re: [whatwg/fetch] Tests do not always require Origin header when mode is "cors" (#871) (Sunday, 17 February)
• Re: [w3c/webcomponents] Update HTML Modules Proposed Spec changes and initial proposal document (#793) (Friday, 15 February)
• Re: [w3c/webcomponents] Update HTML Modules Proposed Spec changes and initial proposal document (#793) (Friday, 15 February)
• Re: [whatwg/storage] Use [SameObject] for navigator.storage IDL (#66) (Thursday, 14 February)
• Re: [w3c/webcomponents] Update HTML Modules Proposed Spec changes and initial proposal document (#793) (Thursday, 14 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Thursday, 14 February)
• Re: [heycam/webidl] Editorial: correct 'callback interface' cross-reference (#646) (Wednesday, 13 February)
• Re: [heycam/webidl] Editorial: correct 'callback interface' cross-reference (#646) (Wednesday, 13 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Wednesday, 13 February)
• Re: [whatwg/url] Be clearer that URL serialization returns an ASCII string. (#428) (Tuesday, 12 February)
• Re: [whatwg/fetch] upload progress? (#21) (Tuesday, 12 February)
• Re: [whatwg/encoding] Editorial: gsnedders's name changed (#173) (Monday, 11 February)
• Re: [whatwg/dom] Editorial: gsnedders's name changed (#733) (Monday, 11 February)
• Re: [whatwg/xhr] Editorial: gsnedders's name changed (#236) (Monday, 11 February)
• [heycam/webidl] Editorial: gsnedders's name changed (#643) (Monday, 11 February)
• [whatwg/encoding] Editorial: gsnedders's name changed (#173) (Monday, 11 February)
• [whatwg/dom] Editorial: gsnedders's name changed (#733) (Monday, 11 February)
• [whatwg/xhr] Editorial: gsnedders's name changed (#236) (Monday, 11 February)
• Re: [w3c/DOM-Parsing] Add innerHTML to ShadowRoot (#42) (Monday, 11 February)
• Re: [w3c/DOM-Parsing] innerHTML should be defined on ShadowRoot interface in addition to Element interface (#21) (Monday, 11 February)
• Re: [w3c/DOM-Parsing] Add innerHTML to ShadowRoot (#42) (Monday, 11 February)
• Re: [w3c/DOM-Parsing] Add innerHTML to ShadowRoot (#42) (Monday, 11 February)
• Re: [whatwg/url] Suggest use of origin in warning text (Fixes #429) (#430) (Monday, 11 February)
• Re: [whatwg/url] Change warning about specs not depending on PSL (#429) (Monday, 11 February)
• Re: [whatwg/fetch] Fix typo in word "falure". (#868) (Monday, 11 February)
• Re: [whatwg/fetch] Typo "If mimeType is falure" (#866) (Monday, 11 February)
• Re: [heycam/webidl] Editorial: use the new signature of CreateBuiltinFunction (#642) (Monday, 11 February)
• Re: [whatwg/dom] Use a queue of deferred steps in the node insertion algorithm (#732) (Monday, 11 February)
• Re: [whatwg/dom] Use a queue of deferred steps in the node insertion algorithm (#732) (Monday, 11 February)
• Re: [whatwg/url] Be clearer that URL serialization returns an ASCII string. (#428) (Monday, 11 February)
• Re: [whatwg/url] Suggest use of origin in warning text (Fixes #429) (#430) (Monday, 11 February)
• Re: [whatwg/encoding] New TextDecoder.decode() API needed for Wasm multithreading (#172) (Monday, 11 February)
• Re: [w3c/webcomponents] CustomElementRegistry per shadow DOM (#792) (Sunday, 10 February)
• Re: [w3c/webcomponents] CustomElementRegistry per shadow DOM (#792) (Sunday, 10 February)
• Re: [w3c/ServiceWorker] WindowOrWorkerGlobalScope is a mixin (#1309) (Sunday, 10 February)
• Re: [w3c/ServiceWorker] WindowOrWorkerGlobalScope is a mixin (#1309) (Sunday, 10 February)
• Re: [whatwg/dom] Use a queue of deferred steps in the node insertion algorithm (#732) (Friday, 8 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Friday, 8 February)
• Re: [whatwg/url] Be clearer that URL serialization returns an ASCII string. (#428) (Friday, 8 February)
• Re: [whatwg/dom] Should adopting change an element's prototype? (#731) (Thursday, 7 February)
• Re: [whatwg/fetch] Fix typo in word "falure". (#868) (Thursday, 7 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Thursday, 7 February)
• Re: [whatwg/fetch] Allow servers to completely opt out of current and future CORS protection (#865) (Thursday, 7 February)
• Re: [whatwg/fetch] Allow servers to completely opt out of current and future CORS protection (#865) (Thursday, 7 February)
• Re: [w3c/FileAPI] Streams are hot, FileReader.readAs____ is not (#40) (Thursday, 7 February)
• Re: [heycam/webidl] Specify what typeof should return for exotic objects (#640) (Thursday, 7 February)
• Re: [heycam/webidl] typeof operator and platform objects (#512) (Thursday, 7 February)
• Re: [whatwg/encoding] New TextDecoder.decode() API needed for Wasm multithreading (#172) (Thursday, 7 February)
• Re: [heycam/webidl] Better regular expression for identifiers (#632) (Wednesday, 6 February)
• Re: [heycam/webidl] Better regular expression for identifiers (#632) (Wednesday, 6 February)
• Re: [heycam/webidl] Idea for [AllowShared] (handling SharedArrayBuffer safely) (#638) (Tuesday, 5 February)
• Re: [heycam/webidl] Idea for [AllowShared] (handling SharedArrayBuffer safely) (#638) (Tuesday, 5 February)
• Re: [heycam/webidl] Idea for [AllowShared] (handling SharedArrayBuffer safely) (#638) (Tuesday, 5 February)
• [heycam/webidl] Idea for [AllowShared] (handling SharedArrayBuffer safely) (#638) (Tuesday, 5 February)
• Re: [heycam/webidl] The [SecureContext] text is unclear on exposure for interfaces (#119) (Tuesday, 5 February)
• Re: [heycam/webidl] Add cross-reference to 'exposed' in the [SecureContext] definition (#637) (Tuesday, 5 February)
• Re: [heycam/webidl] Add cross-reference to 'exposed' in the [SecureContext] definition (#637) (Tuesday, 5 February)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Tuesday, 5 February)
• Re: [whatwg/xhr] The good (#235) (Tuesday, 5 February)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Monday, 4 February)
• Re: [whatwg/fetch] Does Client Hints have multi vendor support? (#867) (Monday, 4 February)
• Re: [heycam/webidl] Stop using extended attributes for constructors (#636) (Monday, 4 February)
• Re: [heycam/webidl] Stop using extended attributes for constructors (#636) (Monday, 4 February)
• Re: [whatwg/fetch] Typo "If mimeType is falure" (#866) (Friday, 1 February)
• Re: [w3c/FileAPI] Further integrate MediaSource documentation (#115) (Friday, 1 February)
• Re: [w3c/FileAPI] Further integrate MediaSource documentation (#115) (Friday, 1 February)
• Re: [w3c/FileAPI] Further integrate MediaSource documentation (#115) (Friday, 1 February)
• Re: [w3c/FileAPI] Further integrate MediaSource documentation (#115) (Friday, 1 February)
• Re: [w3c/FileAPI] Allow MediaSource, disallow any more extensions (#103) (Friday, 1 February)
• Re: [w3c/FileAPI] Allow MediaSource, disallow any more extensions (#103) (Friday, 1 February)
• Re: [w3c/FileAPI] Include MediaSource overload for createObjectURL (#100) (Friday, 1 February)
• Re: [w3c/FileAPI] Allow MediaSource, disallow any more extensions (#103) (Friday, 1 February)

Anthony Ramine

• Re: [whatwg/dom] Run insertion steps after DocumentFragment insertion completes (#576) (Tuesday, 12 February)
• Re: [whatwg/dom] Use a queue of deferred steps in the node insertion algorithm (#732) (Monday, 11 February)
• Re: [whatwg/dom] Use a queue of deferred steps in the node insertion algorithm (#732) (Friday, 8 February)
• [whatwg/dom] Use a queue of deferred steps in the node insertion algorithm (#732) (Friday, 8 February)
• Re: [whatwg/dom] Run insertion steps after DocumentFragment insertion completes (#576) (Monday, 4 February)
• Re: [whatwg/dom] Hook for SVG and HTML script element insertion (#575) (Monday, 4 February)
• Re: [whatwg/dom] Hook for SVG and HTML script element insertion (#575) (Monday, 4 February)
• Re: [whatwg/dom] Hook for SVG and HTML script element insertion (#575) (Friday, 1 February)

Arden de Raaij

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

Asa Kusuma

• Re: [w3c/ServiceWorker] Formalizing a timeout API (#1292) (Tuesday, 26 February)
• Re: [w3c/ServiceWorker] Immediate Service Worker (#1389) (Tuesday, 19 February)
• Re: [w3c/ServiceWorker] Allow active worker to immediately evict itself (#1296) (Thursday, 7 February)
• Re: [w3c/ServiceWorker] Add a script version property to the ServiceWorker object (#1387) (Tuesday, 5 February)
• Re: [w3c/ServiceWorker] Add a script version property to the ServiceWorker object (#1387) (Monday, 4 February)
• Re: [w3c/ServiceWorker] Add a script version property to the ServiceWorker object (#1387) (Friday, 1 February)

Axel D.

• [w3c/selection-api] Add Selection/Range methods based on anchestor element (#102) (Wednesday, 27 February)

Ben Kelly

• Re: [whatwg/fetch] can body consuming be interrupted by response/body GC? (#874) (Friday, 22 February)
• Re: [whatwg/fetch] can body consuming be interrupted by response/body GC? (#874) (Friday, 22 February)
• [whatwg/fetch] can body consuming be interrupted by response/body GC? (#874) (Friday, 22 February)
• Re: [w3c/ServiceWorker] `<iframe sandbox />` + SW (#1390) (Wednesday, 20 February)
• Re: [w3c/ServiceWorker] `<iframe sandbox />` + SW (#1390) (Wednesday, 20 February)
• Re: [w3c/ServiceWorker] `<iframe sandbox />` + SW (#1390) (Wednesday, 20 February)
• Re: [w3c/ServiceWorker] `<iframe sandbox />` + SW (#1390) (Tuesday, 19 February)
• Re: [w3c/ServiceWorker] `<iframe sandbox />` + SW (#1390) (Tuesday, 19 February)
• Re: [w3ctag/design-reviews] FetchEvent Worker Timing (#317) (Wednesday, 6 February)

Beni Cherniavsky-Paskin

• Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107) (Sunday, 10 February)

Benny Powers

• Re: [w3ctag/design-reviews] <link> rel="modulepreload" (#213) (Sunday, 24 February)

Bettelstab

• Re: [w3c/ServiceWorker] Add cookie accessor/setter methods? (#707) (Thursday, 14 February)

BigBlueHat

• Re: [w3ctag/design-reviews] Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312) (Friday, 15 February)
• Re: [w3ctag/design-reviews] Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312) (Wednesday, 13 February)
• Re: [w3ctag/design-reviews] Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312) (Friday, 8 February)

Binyamin Laukstein

• Re: [w3c/manifest] SVG icon sizes="any" (or without property "sizes") (#407) (Thursday, 7 February)
• Re: [w3c/manifest] SVG icon sizes="any" (or without property "sizes") (#407) (Monday, 4 February)

Boris Zbarsky

• [heycam/webidl] Is `long?` an integer type? (#670) (Thursday, 28 February)
• [heycam/webidl] [[DefineOwnProperty]] for legacy objects should not force configurability for a symbol name (#669) (Thursday, 28 February)
• Re: [heycam/webidl] Review handling of WindowProxy (#656) (Tuesday, 26 February)
• Re: [heycam/webidl] Is internal method setup in object creation correct? (#657) (Tuesday, 26 February)
• Re: [heycam/webidl] Is internal method setup in object creation correct? (#657) (Monday, 25 February)
• Re: [heycam/webidl] Interaction of extended attributes and typedefs is weird (#649) (Monday, 25 February)
• Re: [heycam/webidl] Interaction of extended attributes and typedefs is weird (#649) (Monday, 25 February)
• Re: [heycam/webidl] It looks like we started allowing [TreatNullAs] on dictionary members (#650) (Monday, 25 February)
• Re: [heycam/webidl] It looks like we started allowing [TreatNullAs] on dictionary members (#650) (Monday, 25 February)
• Re: [heycam/webidl] Define "implements" checks using internal slots (#654) (Monday, 25 February)
• [heycam/webidl] It looks like we started allowing [TreatNullAs] on dictionary members (#650) (Saturday, 23 February)
• Re: [heycam/webidl] Interaction of extended attributes and typedefs is weird (#649) (Saturday, 23 February)
• [heycam/webidl] Interaction of extended attributes and typedefs is weird (#649) (Saturday, 23 February)
• Re: [heycam/webidl] Imperatively define the interface objects (#648) (Friday, 22 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Thursday, 21 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Thursday, 21 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Thursday, 14 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Thursday, 14 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Tuesday, 12 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Friday, 8 February)
• Re: [heycam/webidl] Correct requirement to define Global properties on the object itself (#639) (Wednesday, 6 February)
• Re: [heycam/webidl] Correct requirement to define Global properties on the object itself (#639) (Wednesday, 6 February)
• Re: [heycam/webidl] Idea for [AllowShared] (handling SharedArrayBuffer safely) (#638) (Tuesday, 5 February)
• Re: [heycam/webidl] Idea for [AllowShared] (handling SharedArrayBuffer safely) (#638) (Tuesday, 5 February)
• Re: [heycam/webidl] Stop using extended attributes for constructors (#636) (Monday, 4 February)
• Re: [heycam/webidl] Stop using extended attributes for constructors (#636) (Monday, 4 February)

Brian Kardell

• Re: [w3c/webcomponents] Question: where to incubate HTML modules? (#794) (Friday, 15 February)

Caridy Patiño

• Re: [w3c/webcomponents] SVG use element can't reference an element within the same shadow tree (#772) (Saturday, 23 February)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Tuesday, 5 February)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Friday, 1 February)

chaals

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

Changwan Hong

• Re: [whatwg/fullscreen] Fix logical error of filling fullscreenElements (3.12) (#145) (Monday, 25 February)
• Re: [whatwg/fullscreen] Fix logical error of filling fullscreenElements (3.12) (#145) (Monday, 25 February)
• Re: [whatwg/fullscreen] Fix logical error of filling fullscreenElements (3.12) (#145) (Monday, 25 February)
• Re: [whatwg/fullscreen] Fix logical error of filling fullscreenElements (3.12) (#145) (Friday, 22 February)
• [whatwg/fullscreen] Fix logical error of filling fullscreenElements (3.12) (#145) (Friday, 22 February)
• Re: [whatwg/fullscreen] Rephrase: 3.12 While the first element in fullscreenElements is ... (#144) (Friday, 22 February)
• Re: [whatwg/fullscreen] Rephrase: 3.12 While the first element in fullscreenElements is ... (#144) (Thursday, 21 February)
• [whatwg/fullscreen] Rephrase: 3.12 While the first element in fullscreenElements is ... (#144) (Wednesday, 20 February)

Charles Vazac

• Re: [whatwg/dom] window.event and IFRAMEs (#735) (Friday, 22 February)
• Re: [whatwg/dom] window.event and IFRAMEs (#735) (Friday, 22 February)
• [whatwg/dom] window.event and IFRAMEs (#735) (Thursday, 21 February)

cynthia

• Re: [w3ctag/design-reviews] User Idle Detection (#336) (Tuesday, 26 February)
• Re: [w3ctag/design-reviews] User Idle Detection (#336) (Tuesday, 26 February)
• Re: [w3ctag/design-reviews] Portals (#331) (Saturday, 9 February)
• Re: [w3ctag/design-reviews] Element Timing API for img (#326) (Saturday, 9 February)
• Re: [w3ctag/design-reviews] Web Bluetooth Scanning (#333) (Friday, 8 February)
• Re: [w3ctag/design-reviews] Import maps (#340) (Thursday, 7 February)
• Re: [w3ctag/design-reviews] Trusted Types (#198) (Thursday, 7 February)
• Re: [w3ctag/design-reviews] Feature Policy JS introspection API (#292) (Wednesday, 6 February)
• Re: [w3ctag/design-reviews] Element Timing API for img (#326) (Wednesday, 6 February)
• Re: [w3ctag/design-reviews] Element Timing API for img (#326) (Wednesday, 6 February)
• Re: [w3ctag/design-reviews] Layered APIs (#276) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] Layered APIs (#276) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] WebRTC DSCP Control API (#325) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] Heads up: Verifiable Credentials review request coming shortly (#335) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] Heads up: Verifiable Credentials review request coming shortly (#335) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] Scheduling APIs (#338) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] Web Bluetooth Scanning (#333) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] JavaScript Decorators (#314) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] JavaScript Decorators (#314) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] Review MathML (#313) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] Review MathML (#313) (Tuesday, 5 February)

Damien Golding

• Re: [w3c/webcomponents] CSS encapsulation and common CSS rules (#800) (Thursday, 28 February)
• [w3c/webcomponents] CSS encapsulation and common CSS rules (#800) (Thursday, 28 February)

Dan Clark

• Re: [w3c/webcomponents] Move HTML Module Record definition from ES spec to HTML5 spec (#796) (Thursday, 28 February)
• Re: [w3c/webcomponents] Move HTML Module Record definition from ES spec to HTML5 spec (#796) (Thursday, 28 February)
• Re: [w3c/webcomponents] Move HTML Module Record definition from ES spec to HTML5 spec (#796) (Thursday, 28 February)
• Re: [w3c/webcomponents] Update HTML Modules Proposed Spec changes and initial proposal document (#793) (Wednesday, 27 February)
• Re: [w3c/webcomponents] Update HTML Modules Proposed Spec changes and initial proposal document (#793) (Monday, 25 February)
• Re: [w3c/webcomponents] HTML modules spec draft editorial feedback (#783) (Friday, 22 February)
• [w3c/webcomponents] Move HTML Module Record definition from ES spec to HTML5 spec (#796) (Friday, 22 February)
• Re: [w3c/webcomponents] HTML modules spec draft editorial feedback (#783) (Friday, 15 February)
• Re: [w3c/webcomponents] HTML modules spec draft editorial feedback (#783) (Friday, 15 February)
• Re: [w3c/webcomponents] Update HTML Modules Proposed Spec changes and initial proposal document (#793) (Thursday, 14 February)
• Re: [w3c/webcomponents] Update HTML Modules Proposed Spec changes and initial proposal document (#793) (Thursday, 14 February)
• Re: [w3c/webcomponents] Update HTML Modules Proposed Spec changes and initial proposal document (#793) (Thursday, 14 February)
• [w3c/webcomponents] Update HTML Modules Proposed Spec changes and initial proposal document (#793) (Wednesday, 13 February)
• Re: [w3c/webcomponents] HTML modules spec draft editorial feedback (#783) (Friday, 8 February)
• Re: [w3c/webcomponents] HTML modules spec draft editorial feedback (#783) (Friday, 8 February)
• Re: [w3c/webcomponents] HTML modules spec draft editorial feedback (#783) (Friday, 8 February)

Dana Keeler

• Re: [whatwg/fetch] Clarification on CORS preflight fetches for TLS client certificates (#869) (Monday, 11 February)

Daniel Appelquist

• Re: [w3ctag/design-reviews] Trusted Types (#198) (Thursday, 7 February)
• Re: [w3ctag/design-reviews] Review Request: Priority Hints API (#241) (Thursday, 7 February)
• Re: [w3ctag/design-reviews] User Activation API (#300) (Thursday, 7 February)
• Re: [w3ctag/design-reviews] User Activation API (#300) (Thursday, 7 February)
• Re: [w3ctag/design-reviews] User Activation API (#300) (Thursday, 7 February)
• Re: [w3ctag/design-reviews] FetchEvent Worker Timing (#317) (Wednesday, 6 February)
• Re: [w3ctag/design-reviews] JavaScript WeakRefs (#321) (Wednesday, 6 February)
• Re: [w3ctag/design-reviews] Event Timing API (#324) (Wednesday, 6 February)
• Re: [w3ctag/design-reviews] Web Bluetooth Scanning (#333) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] Web Bluetooth Scanning (#333) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] Feature policy control over sandbox features (#339) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] transferable streams (#332) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] Portals (#331) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] WebRTC DSCP Control API (#325) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] hrefTranslate attribute (#301) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] OffscreenCanvas new commit() and DedicatedWorker.requestAnimationFrame (#288) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] OffscreenCanvas new commit() and DedicatedWorker.requestAnimationFrame (#288) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] Carriage of Web Resource in ISOBMFF (#285) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] The web platform needs a service discovery mechanism (#240) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] Clear Site Data (#62) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312) (Tuesday, 5 February)

Daniel Burnett

• Re: [w3ctag/design-reviews] TAG review request: Verifiable Credentials Data Model 1.0 (#343) (Monday, 18 February)
• [w3ctag/design-reviews] TAG review request: Verifiable Credentials Data Model 1.0 (#343) (Monday, 11 February)

Daniel Ehrenberg

• Re: [heycam/webidl] Referencing "implements" (#659) (Thursday, 28 February)
• Re: [w3ctag/design-reviews] JavaScript WeakRefs (#321) (Wednesday, 27 February)
• Re: [heycam/webidl] Add a Privacy and Security Considerations section (#647) (Friday, 22 February)
• Re: [heycam/webidl] Define "implements" checks using internal slots (#595) (Thursday, 7 February)
• Re: [heycam/webidl] Define "implements" checks using internal slots (#595) (Thursday, 7 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Thursday, 7 February)
• Re: [heycam/webidl] Specify what typeof should return for exotic objects (#640) (Thursday, 7 February)
• Re: [w3ctag/design-reviews] Temporal proposal (#311) (Thursday, 7 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Thursday, 7 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Thursday, 7 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Thursday, 7 February)
• Re: [heycam/webidl] typeof operator and platform objects (#512) (Thursday, 7 February)
• Re: [w3ctag/design-reviews] Temporal proposal (#311) (Wednesday, 6 February)
• Re: [w3ctag/design-reviews] JavaScript WeakRefs (#321) (Wednesday, 6 February)
• Re: [heycam/webidl] Idea for [AllowShared] (handling SharedArrayBuffer safely) (#638) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] JavaScript Decorators (#314) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] JavaScript Decorators (#314) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] Temporal proposal (#311) (Tuesday, 5 February)
• Re: [heycam/webidl] Stop using extended attributes for constructors (#636) (Monday, 4 February)

Daniel Veditz

• Re: [whatwg/fetch] Restrict allowed JavaScript MIME types (#870) (Thursday, 7 February)

Dave Tapuska

• Re: [w3ctag/design-reviews] User Activation API (#300) (Monday, 25 February)
• Re: [w3ctag/design-reviews] User Activation API (#300) (Friday, 22 February)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Thursday, 21 February)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Thursday, 21 February)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Thursday, 21 February)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Thursday, 21 February)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Thursday, 21 February)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Thursday, 21 February)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Wednesday, 20 February)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Friday, 15 February)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Thursday, 7 February)
• Re: [w3ctag/design-reviews] User Activation API (#300) (Thursday, 7 February)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Wednesday, 6 February)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Wednesday, 6 February)
• Re: [w3ctag/design-reviews] hrefTranslate attribute (#301) (Tuesday, 5 February)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Friday, 1 February)

Dead J. Dona

• Re: [w3c/manifest] update (#754) (Monday, 25 February)
• [w3c/manifest] update (#754) (Monday, 25 February)

Dean Tribble

• Re: [w3ctag/design-reviews] JavaScript WeakRefs (#321) (Wednesday, 6 February)

dfabulich

• Re: [w3c/ServiceWorker] Provide a one-line way to listen for a waiting Service Worker (#1222) (Wednesday, 13 February)
• Re: [w3c/ServiceWorker] Provide an easier way to listen for waiting/activated/redundant Service Workers (#1247) (Wednesday, 13 February)
• Re: [w3c/ServiceWorker] Provide a one-line way to listen for a waiting Service Worker (#1222) (Wednesday, 13 February)
• Re: [w3c/ServiceWorker] Provide an easier way to listen for waiting/activated/redundant Service Workers (#1247) (Wednesday, 13 February)

Diego Ferreiro Val

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

Dima Voytenko

• Re: [w3c/webcomponents] [Shadow] Slotting indirect children (#574) (Monday, 25 February)

Domenic Denicola

• Re: [heycam/webidl] Editorial: run platform algorithms on IDL objects (#666) (Thursday, 28 February)
• Re: [heycam/webidl] Referencing "implements" (#659) (Thursday, 28 February)
• Re: [heycam/webidl] Numeric type reform strawperson (#33) (Wednesday, 27 February)
• Re: [heycam/webidl] Formalize the 'this' and 'given value' ambient values (#665) (Wednesday, 27 February)
• Re: [heycam/webidl] Editorial: improve language around conversions to JS (#664) (Wednesday, 27 February)
• Re: [heycam/webidl] State the associated realm when creating objects (#206) (Wednesday, 27 February)
• Re: [w3c/webcomponents] Proposal: a native solution for virtual scrolling (#791) (Wednesday, 27 February)
• Re: [w3c/webcomponents] Move HTML Module Record definition from ES spec to HTML5 spec (#796) (Tuesday, 26 February)
• Re: [heycam/webidl] Remove the 'user object' concept. (#662) (Tuesday, 26 February)
• Re: [heycam/webidl] Remove the 'user object' concept. (#662) (Tuesday, 26 February)
• Re: [heycam/webidl] Referencing "implements" (#659) (Tuesday, 26 February)
• Re: [whatwg/streams] better-assert is broken (#985) (Monday, 25 February)
• Re: [heycam/webidl] Formally define a [[Realm]] slot on platform objects (#658) (Monday, 25 February)
• [heycam/webidl] Is internal method setup in object creation correct? (#657) (Monday, 25 February)
• Re: [heycam/webidl] Can we use ObjectCreate in object creation? + other editorial tweaks (#655) (Monday, 25 February)
• Re: [heycam/webidl] Review handling of WindowProxy (#656) (Monday, 25 February)
• Re: [heycam/webidl] Interaction of extended attributes and typedefs is weird (#649) (Monday, 25 February)
• [heycam/webidl] Can we use ObjectCreate in object creation? + other editorial tweaks (#655) (Monday, 25 February)
• Re: [heycam/webidl] Define "implements" checks using internal slots (#654) (Monday, 25 February)
• Re: [heycam/webidl] It looks like we started allowing [TreatNullAs] on dictionary members (#650) (Monday, 25 February)
• Re: [heycam/webidl] It looks like we started allowing [TreatNullAs] on dictionary members (#650) (Monday, 25 February)
• Re: [heycam/webidl] typeof operator and platform objects (#512) (Monday, 25 February)
• Re: [heycam/webidl] Specify what typeof should return for exotic objects (#640) (Monday, 25 February)
• Re: [heycam/webidl] Specify what typeof should return for exotic objects (#640) (Monday, 25 February)
• Re: [heycam/webidl] Imperatively define the interface objects (#648) (Monday, 25 February)
• Re: [heycam/webidl] It looks like we started allowing [TreatNullAs] on dictionary members (#650) (Monday, 25 February)
• Re: [whatwg/streams] better-assert is broken (#985) (Monday, 25 February)
• Re: [heycam/webidl] Imperatively define the interface objects (#648) (Friday, 22 February)
• Re: [whatwg/fetch] Remove "filesystem" URL scheme (#846) (Friday, 22 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Friday, 22 February)
• Re: [whatwg/streams] ReadableStreamTee pulls too many chunks (#996) (Thursday, 21 February)
• Re: [whatwg/streams] Semantics of |closedOrErrored| variable in ReadableStreamTee are odd (#991) (Thursday, 21 February)
• Re: [whatwg/streams] In ReadableStreamTee, replace _closedOrErrored_ with _closed_ (#994) (Thursday, 21 February)
• Re: [whatwg/streams] In ReadableStreamTee, replace _closedOrErrored_ with _closed_ (#994) (Thursday, 21 February)
• Re: [whatwg/streams] Simplify [@@asyncIterator]().next() (#995) (Thursday, 21 February)
• Re: [whatwg/streams] Simplify [@@asyncIterator]().next() (#995) (Thursday, 21 February)
• Re: [whatwg/streams] Give pipeTo more latitude about byob chunk sizes (#989) (Thursday, 21 February)
• Re: [whatwg/streams] WritableStreamDefaultWriterGetDesiredSize(writer) cannot in general be used to determine size of chunks read by pipeTo (#938) (Thursday, 21 February)
• Re: [whatwg/streams] Give pipeTo more latitude about byob chunk sizes (#989) (Thursday, 21 February)
• Re: [whatwg/fetch] Remove "filesystem" URL scheme (#846) (Thursday, 21 February)
• Re: [whatwg/streams] Replace impossible condition with assert (#987) (Monday, 18 February)
• Re: [whatwg/streams] Replace impossible condition with assert (#987) (Monday, 18 February)
• Re: [whatwg/streams] Review Draft Publication: February 2019 (#986) (Monday, 18 February)
• Re: [whatwg/url] Review Draft Publication: February 2019 (#432) (Monday, 18 February)
• Re: [whatwg/xhr] Review Draft Publication: February 2019 (#238) (Monday, 18 February)
• Re: [whatwg/storage] Review Draft Publication: February 2019 (#67) (Monday, 18 February)
• Re: [whatwg/url] Review Draft Publication: February 2019 (#432) (Monday, 18 February)
• Re: [whatwg/xhr] Review Draft Publication: February 2019 (#238) (Monday, 18 February)
• Re: [whatwg/streams] Review Draft Publication: February 2019 (#986) (Monday, 18 February)
• Re: [whatwg/storage] Review Draft Publication: February 2019 (#67) (Monday, 18 February)
• Re: [whatwg/storage] Review Draft Publication: February 2019 (#67) (Monday, 18 February)
• Re: [w3c/webcomponents] HTML modules spec draft editorial feedback (#783) (Friday, 15 February)
• Re: [w3c/webcomponents] HTML modules spec draft editorial feedback (#783) (Friday, 15 February)
• Re: [heycam/webidl] Should LegacyWindowAlias and LegacyNamespace be allowed together? (#645) (Friday, 15 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Thursday, 14 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Wednesday, 13 February)
• Re: [w3c/webcomponents] Proposal: a native solution for virtual scrolling (#791) (Tuesday, 12 February)
• Re: [w3c/webcomponents] Proposal: a native solution for virtual scrolling (#791) (Tuesday, 12 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Tuesday, 12 February)
• Re: [heycam/webidl] Import (and fix) the promises guide (#490) (Tuesday, 12 February)
• Re: [heycam/webidl] Use PerformPromiseThen to perform some steps once a promise is settled (#644) (Tuesday, 12 February)
• Re: [heycam/webidl] Use PerformPromiseThen to perform some steps once a promise is settled (#644) (Tuesday, 12 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Monday, 11 February)
• Re: [whatwg/url] Be clearer that URL serialization returns an ASCII string. (#428) (Friday, 8 February)
• Re: [w3c/webcomponents] Proposal: a native solution for virtual scrolling (#791) (Friday, 8 February)
• Re: [w3c/webcomponents] HTML modules spec draft editorial feedback (#783) (Friday, 8 February)
• Re: [w3c/webcomponents] HTML modules spec draft editorial feedback (#783) (Friday, 8 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Friday, 8 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Friday, 8 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Friday, 8 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Friday, 8 February)
• Re: [w3c/FileAPI] Streams are hot, FileReader.readAs____ is not (#40) (Thursday, 7 February)
• Re: [heycam/webidl] Specify what typeof should return for exotic objects (#640) (Thursday, 7 February)
• Re: [heycam/webidl] Define the static operations on the interface object (#641) (Thursday, 7 February)
• Re: [heycam/webidl] Define the static operations on the interface object (#641) (Thursday, 7 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Thursday, 7 February)
• Re: [whatwg/streams] Switching to Web IDL (#963) (Thursday, 7 February)
• Re: [whatwg/encoding] New TextDecoder.decode() API needed for Wasm multithreading (#172) (Wednesday, 6 February)
• Re: [w3c/webcomponents] A way to detect if a custom element was constructed during customElements.define call? (#790) (Wednesday, 6 February)
• Re: [w3c/webcomponents] A way to detect if a custom element was constructed during customElements.define call? (#790) (Wednesday, 6 February)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Tuesday, 5 February)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Tuesday, 5 February)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Tuesday, 5 February)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Tuesday, 5 February)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] Layered APIs (#276) (Tuesday, 5 February)
• [w3ctag/design-reviews] Import maps (#340) (Tuesday, 5 February)
• Re: [whatwg/streams] "Let returnValue be the result of performing con..." (#982) (Monday, 4 February)
• Re: [heycam/webidl] Stop using extended attributes for constructors (#636) (Monday, 4 February)
• Re: [whatwg/streams] "npm run coverage" is no longer working (#981) (Friday, 1 February)

Dominic Farolino

• Re: [whatwg/fetch] Add domintro explanations for web developers (#543) (Friday, 22 February)

Doug Turner

• Re: [w3ctag/design-reviews] Web Bluetooth Scanning (#333) (Wednesday, 6 February)
• Re: [w3ctag/design-reviews] Web Bluetooth Scanning (#333) (Wednesday, 6 February)

Emilio Cobos Álvarez

• Re: [whatwg/dom] Inconsistency in execution of unclosed attribute selector for querySelector (#549) (Thursday, 28 February)

Eric Willigers

• Re: [w3c/WebPlatformWG] Promote File Handling to WICG (#127) (Tuesday, 12 February)

falsandtru

• Re: [w3c/webcomponents] CustomElementRegistry per shadow DOM (#792) (Sunday, 10 February)
• [w3c/webcomponents] CustomElementRegistry per shadow DOM (#792) (Saturday, 9 February)

fantasai

• [w3ctag/design-reviews] TAG review of whether element.pseudo(":unkown") should return null or throw (#348) (Monday, 25 February)

Felix Becker

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

Frederik

• Re: [whatwg/url] Suggest use of origin in warning text (Fixes #429) (#430) (Monday, 11 February)
• Re: [whatwg/url] Suggest use of origin in warning text (Fixes #429) (#430) (Monday, 11 February)
• Re: [whatwg/url] Suggest use of origin in warning text (Fixes #429) (#430) (Friday, 8 February)
• Re: [whatwg/url] Suggest use of origin in warning text (Fixes #429) (#430) (Friday, 8 February)
• [whatwg/url] Suggest use of origin in warning text (Fixes #429) (#430) (Friday, 8 February)
• [whatwg/url] Change warning about specs not depending on PSL (#429) (Friday, 8 February)

frlinw

• Re: [w3c/ServiceWorker] Add a script version property to the ServiceWorker object (#1387) (Tuesday, 5 February)

gerry sumaylo

• [whatwg/fullscreen] ruby3 (#147) (Tuesday, 26 February)
• [whatwg/fullscreen] I want to avoid fullscreen elements covering anything else in the top layer, e.g. dialog. (#146) (Tuesday, 26 February)

Hadley Beeman

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

Hayato Ito

• Re: [whatwg/dom] Capturing event listeners are called during bubbling phase for shadow hosts (#685) (Wednesday, 27 February)
• Re: [w3c/webcomponents] [Shadow] Slotting indirect children (#574) (Tuesday, 26 February)
• Re: [w3c/webcomponents] [Shadow] Slotting indirect children (#574) (Tuesday, 26 February)
• Re: [w3c/webcomponents] Can I style a slotted element by its slot name? (#795) (Saturday, 16 February)
• Re: [w3c/webcomponents] Question: where to incubate HTML modules? (#794) (Friday, 15 February)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Friday, 1 February)

Henri Sivonen

• Re: [whatwg/encoding] Make decode() and encodeInto() accept SharedArrayBuffer-backed views (#172) (Monday, 11 February)
• Re: [whatwg/encoding] Make decode() and encodeInto() accept SharedArrayBuffer-backed views (#172) (Monday, 11 February)
• Re: [whatwg/encoding] New TextDecoder.decode() API needed for Wasm multithreading (#172) (Monday, 11 February)
• Re: [whatwg/encoding] New TextDecoder.decode() API needed for Wasm multithreading (#172) (Monday, 11 February)
• Re: [whatwg/encoding] New TextDecoder.decode() API needed for Wasm multithreading (#172) (Monday, 11 February)
• Re: [whatwg/encoding] Big5 encoding mishandles some trailing bytes, with possible XSS (#171) (Saturday, 9 February)
• Re: [whatwg/encoding] Big5 encoding mishandles some trailing bytes, with possible XSS (#171) (Saturday, 9 February)
• Re: [whatwg/encoding] Big5 encoding mishandles some trailing bytes, with possible XSS (#171) (Friday, 8 February)
• Re: [whatwg/encoding] Big5 encoding mishandles some trailing bytes, with possible XSS (#171) (Friday, 8 February)
• Re: [whatwg/encoding] Big5 encoding mishandles some trailing bytes, with possible XSS (#171) (Thursday, 7 February)
• Re: [whatwg/encoding] Big5 encoding mishandles some trailing bytes, with possible XSS (#171) (Thursday, 7 February)
• Re: [whatwg/encoding] Big5 encoding mishandles some trailing bytes, with possible XSS (#171) (Thursday, 7 February)

hober

• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Sunday, 24 February)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Thursday, 21 February)
• Re: [w3ctag/design-reviews] Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312) (Wednesday, 13 February)
• Re: [w3ctag/design-reviews] User Activation API (#300) (Thursday, 7 February)
• Re: [w3ctag/design-reviews] Querying Encryption Scheme Support Through EME (#322) (Wednesday, 6 February)
• Re: [w3ctag/design-reviews] Querying Encryption Scheme Support Through EME (#322) (Wednesday, 6 February)
• Re: [w3ctag/design-reviews] EME Extension: HDCP Policy Check (#323) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] Temporal proposal (#311) (Tuesday, 5 February)

Ian Clelland

• Re: [w3ctag/design-reviews] Feature policy control over sandbox features (#339) (Wednesday, 6 February)
• Re: [w3ctag/design-reviews] Feature policy control over sandbox features (#339) (Monday, 4 February)

Irakli Gozalishvili

• Re: [w3c/ServiceWorker] `<iframe sandbox />` + SW (#1390) (Wednesday, 20 February)
• Re: [w3c/ServiceWorker] `<iframe sandbox />` + SW (#1390) (Tuesday, 19 February)
• Re: [w3c/ServiceWorker] `<iframe sandbox />` + SW (#1390) (Tuesday, 19 February)
• [w3c/ServiceWorker] `<iframe sandbox />` + SW (#1390) (Tuesday, 19 February)

Jacob Bearce

• Re: [w3c/manifest] Icon shapes and masking (#555) (Monday, 18 February)

Jake Archibald

• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Wednesday, 27 February)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Thursday, 21 February)
• Re: [whatwg/fetch] http (#872) (Monday, 18 February)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Monday, 18 February)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Friday, 15 February)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Thursday, 14 February)
• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Thursday, 14 February)
• Re: [w3c/ServiceWorker] Provide an easier way to listen for waiting/activated/redundant Service Workers (#1247) (Wednesday, 13 February)
• Re: [w3c/ServiceWorker] Cache.put() does not read response's body (#1383) (Monday, 11 February)
• Re: [w3c/ServiceWorker] Correcting the use of types and simplifying the response body read. (#1384) (Monday, 11 February)
• Re: [w3c/ServiceWorker] Minor improvements around importScripts. (#1380) (Friday, 8 February)
• Re: [whatwg/dom] Should adopting change an element's prototype? (#731) (Thursday, 7 February)
• Re: [whatwg/dom] Should adopting change an element's prototype? (#731) (Thursday, 7 February)
• Re: [whatwg/dom] Should adopting change an element's prototype? (#731) (Thursday, 7 February)
• [whatwg/dom] Should adopting change an element's prototype (#731) (Thursday, 7 February)

Jan Olaf Krems

• Re: [w3c/webcomponents] JSON "modules" (#770) (Tuesday, 19 February)

Jan Tošovský

• Re: [w3c/ServiceWorker] Immediate Service Worker (#1389) (Sunday, 24 February)
• Re: [w3c/ServiceWorker] Immediate Service Worker (#1389) (Tuesday, 19 February)
• [w3c/ServiceWorker] Immediate Service Worker (#1389) (Monday, 18 February)

Jan-Ivar Bruaroey

• Re: [heycam/webidl] Remove [NoInterfaceObject]. (#609) (Thursday, 14 February)
• Re: [heycam/webidl] Remove [NoInterfaceObject]. (#609) (Thursday, 14 February)

Jason Orendorff

• Re: [whatwg/streams] Treat forAuthorCode as an internal slot of reader object. (#969) (Friday, 8 February)

Javier Fernandez Garcia-Boente

• Re: [w3c/editing] indent elements in different lines created by forced breaks <br> (#190) (Thursday, 7 February)
• [w3c/editing] indent elements in different lines created by forced breaks <br> (#190) (Wednesday, 6 February)

Jay Harris

• Re: [w3c/WebPlatformWG] Promote File Handling to WICG (#127) (Wednesday, 13 February)
• Re: [w3c/WebPlatformWG] Promote File Handling to WICG (#127) (Monday, 11 February)
• [w3c/WebPlatformWG] Promote File Handling to WICG (#127) (Thursday, 7 February)

Jeffrey Yasskin

• Re: [whatwg/url] Be clearer that URL serialization returns an ASCII string. (#428) (Monday, 11 February)
• Re: [whatwg/url] Be clearer that URL serialization returns an ASCII string. (#428) (Monday, 11 February)
• Re: [whatwg/url] Be clearer that URL serialization returns an ASCII string. (#428) (Friday, 8 February)
• [whatwg/url] Be clearer that URL serialization returns an ASCII string. (#428) (Thursday, 7 February)

Jeremy Roman

• Re: [w3ctag/design-reviews] Portals (#331) (Wednesday, 13 February)
• Re: [w3ctag/design-reviews] Portals (#331) (Wednesday, 13 February)
• Re: [w3ctag/design-reviews] Portals (#331) (Monday, 11 February)

Jihye Hong

• Re: [w3ctag/design-reviews] Spatial Navigation (#287) (Friday, 1 February)

Jimmy Wärting

• Re: [w3c/editing] spellchecking - how to give JS devs more control (#166) (Thursday, 7 February)

jmdyck

• Re: [heycam/webidl] Can we use ObjectCreate in object creation? + other editorial tweaks (#655) (Tuesday, 26 February)

Joe Pea

• Re: [w3c/webcomponents] Expose "cloning steps" to custom elements (cloneCallback) (#176) (Monday, 25 February)
• Re: [w3c/webcomponents] A way to detect if a custom element was constructed during customElements.define call? (#790) (Sunday, 17 February)
• Re: [w3c/webcomponents] A way to detect if a custom element was constructed during customElements.define call? (#790) (Wednesday, 6 February)
• Re: [w3c/webcomponents] A way to detect if a custom element was constructed during customElements.define call? (#790) (Wednesday, 6 February)
• Re: [w3c/webcomponents] A way to detect if a custom element was constructed during customElements.define call? (#790) (Wednesday, 6 February)
• Re: [w3c/webcomponents] A way to detect if a custom element was constructed during customElements.define call? (#790) (Wednesday, 6 February)
• Re: [w3c/webcomponents] A way to detect if a custom element was constructed during customElements.define call? (#790) (Wednesday, 6 February)
• [w3c/webcomponents] A way to detect if a custom element was constructed during customElements.define call? (#790) (Wednesday, 6 February)
• Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Saturday, 2 February)
• Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550) (Saturday, 2 February)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Saturday, 2 February)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Saturday, 2 February)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Saturday, 2 February)
• Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550) (Saturday, 2 February)
• Re: [w3c/webcomponents] Is there a way to detect if a custom element was constructed during parsing? (#789) (Saturday, 2 February)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Saturday, 2 February)
• Re: [w3c/webcomponents] Is there a way to detect if a custom element was constructed during parsing? (#789) (Friday, 1 February)
• Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Friday, 1 February)
• Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) (Friday, 1 February)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Friday, 1 February)
• Re: [w3c/webcomponents] Is there a way to detect if a custom element was constructed during parsing? (#789) (Friday, 1 February)
• Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550) (Friday, 1 February)
• Re: [w3c/webcomponents] [feature request] change when upgrade/connected happens during parsing, so that it is the first event in the following microtask (#787) (Friday, 1 February)
• Re: [whatwg/dom] MutationObserver needs an equivalent of disconnected & connected callbacks (#533) (Friday, 1 February)
• Re: [w3c/webcomponents] [idea] making builtin elements more like custom elements (#785) (Friday, 1 February)

Johanna

• Re: [w3c/screen-orientation] Fix: move title inside best practice box (#163) (Thursday, 28 February)
• [w3c/screen-orientation] Fix: move title inside best practice box (#163) (Thursday, 28 February)
• Re: [w3c/screen-orientation] Reliability of angle (#162) (Thursday, 28 February)
• Re: [w3c/screen-orientation] Edit screen orientation type definitions (#161) (Tuesday, 26 February)
• Re: [w3c/screen-orientation] Edit screen orientation type definitions (#161) (Tuesday, 26 February)
• Re: [w3c/screen-orientation] Fix Web App Manifest link (#159) (Tuesday, 26 February)
• [w3c/screen-orientation] Edit screen orientation type definitions (#161) (Tuesday, 26 February)
• Re: [w3c/screen-orientation] Locking orientation algorithm edits (#160) (Tuesday, 26 February)
• Re: [w3c/screen-orientation] Fix Web App Manifest link (#159) (Tuesday, 26 February)
• [w3c/screen-orientation] Locking orientation algorithm edits (#160) (Monday, 25 February)
• [w3c/screen-orientation] Fix Web App Manifest link (#159) (Monday, 25 February)
• Re: [w3c/screen-orientation] Add test link for lock-basic.html (#153) (Monday, 18 February)
• Re: [w3c/screen-orientation] Definition of default orientation (#150) (Sunday, 17 February)
• [w3c/screen-orientation] Edit to updating orientation algorithm (#157) (Saturday, 16 February)
• Re: [w3c/screen-orientation] Add event-change.html test link to screen orientation change algorithm section (#154) (Friday, 15 February)
• Re: [w3c/screen-orientation] Add orientation-reading.html test (#155) (Friday, 15 February)
• Re: [w3c/screen-orientation] Add lock-sandboxed-iframe test (#156) (Friday, 15 February)
• [w3c/screen-orientation] Add lock-sandboxed-iframe test to locking algorithm section (#156) (Thursday, 14 February)
• [w3c/screen-orientation] Add orientation-reading.html test (#155) (Thursday, 14 February)
• [w3c/screen-orientation] Add event-change.html test link to screen orientation change algorithm section (#154) (Wednesday, 13 February)
• [w3c/screen-orientation] Add test link for lock-basic.html (#153) (Wednesday, 13 February)
• [w3c/screen-orientation] Add test link for lock-bad-argument (#152) (Wednesday, 13 February)
• Re: [w3c/screen-orientation] Resolving the promise after the change event is fired (#147) (Tuesday, 12 February)
• Re: [w3c/screen-orientation] Resolving the promise after the change event is fired (#147) (Thursday, 7 February)
• Re: [w3c/screen-orientation] Editorial: Internal slots (#144) (Thursday, 7 February)
• Re: [w3c/screen-orientation] Editorial: Internal slots (#144) (Thursday, 7 February)
• Re: [w3c/screen-orientation] Editorial: Internal slots (#144) (Thursday, 7 February)
• Re: [w3c/screen-orientation] Editorial: Internal slots (#144) (Thursday, 7 February)
• [w3c/screen-orientation] Definition of default orientation (#150) (Thursday, 7 February)
• Re: [w3c/screen-orientation] Editorial: Internal slots (#144) (Wednesday, 6 February)
• Re: [w3c/screen-orientation] Editorial: Internal slots (#144) (Wednesday, 6 February)
• Re: [w3c/screen-orientation] Editorial: Internal slots (#144) (Wednesday, 6 February)
• Re: [w3c/screen-orientation] Editorial: Internal slots (#144) (Wednesday, 6 February)
• Re: [w3c/screen-orientation] "Security" condition should be something else (#82) (Wednesday, 6 February)
• Re: [w3c/screen-orientation] Editorial: Change 'security conditions' to 'pre-lock conditions' (#149) (Wednesday, 6 February)
• Re: [w3c/screen-orientation] cordova-plugin-screen-orientation does not work (#123) (Tuesday, 5 February)
• Re: [w3c/screen-orientation] cordova-plugin-screen-orientation does not work (#123) (Tuesday, 5 February)
• [w3c/screen-orientation] Editorial: Change 'security conditions' to 'pre-lock conditions' (#149) (Tuesday, 5 February)
• Re: [w3c/screen-orientation] Editorial: Internal slots (#144) (Tuesday, 5 February)
• Re: [w3c/screen-orientation] Editorial: Internal slots (#144) (Tuesday, 5 February)
• [w3c/screen-orientation] Editorial: HTML Tidy gh-pages (#148) (Tuesday, 5 February)
• [w3c/screen-orientation] Resolving the promise after the change event is fired (#147) (Monday, 4 February)
• Re: [w3c/screen-orientation] Editorial: Internal slots (#144) (Monday, 4 February)

Johannes Wilm

• Re: [w3c/editing] indent elements in different lines created by forced breaks <br> (#190) (Thursday, 7 February)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Monday, 4 February)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Sunday, 3 February)

Jonathan Neal

• Re: [w3c/webcomponents] Can I style a slotted element by its slot name? (#795) (Friday, 22 February)
• Re: [w3c/webcomponents] Styling default slot content with ::slotted (#631) (Saturday, 16 February)
• [w3c/webcomponents] Can I style a slotted element by its slot name? (#795) (Friday, 15 February)

jonnycrunch

• Re: [w3ctag/design-reviews] Review Decentralized identifiers (DIDs) (#216) (Tuesday, 12 February)

Jordan Brennan

• Re: [w3c/webcomponents] JSON "modules" (#770) (Thursday, 21 February)
• Re: [w3c/webcomponents] JSON "modules" (#770) (Tuesday, 19 February)
• Re: [w3c/webcomponents] JSON "modules" (#770) (Tuesday, 19 February)

Joshua Bell

• Re: [w3ctag/design-reviews] User Idle Detection (#336) (Tuesday, 26 February)
• Re: [whatwg/encoding] New TextDecoder.decode() API needed for Wasm multithreading (#172) (Wednesday, 6 February)

juj

• [whatwg/encoding] New TextDecoder.decode() API needed for Wasm multithreading (#172) (Wednesday, 6 February)

Jungshik Shin

• Re: [whatwg/encoding] Big5 encoding mishandles some trailing bytes, with possible XSS (#171) (Saturday, 9 February)

Justin Fagnani

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

Kagami Sascha Rosylight

• Re: [w3c/DOM-Parsing] Add innerHTML to ShadowRoot (#42) (Monday, 11 February)
• [w3c/DOM-Parsing] Add innerHTML to ShadowRoot (#42) (Monday, 11 February)
• Re: [heycam/webidl] Better regular expression for identifiers (#632) (Tuesday, 5 February)
• Re: [w3c/FileAPI] Further integrate MediaSource documentation (#115) (Friday, 1 February)
• Re: [w3c/FileAPI] Further integrate MediaSource documentation (#115) (Friday, 1 February)
• Re: [w3c/FileAPI] Further integrate MediaSource documentation (#115) (Friday, 1 February)
• [w3c/FileAPI] Further integrate MediaSource documentation (#115) (Friday, 1 February)
• Re: [w3c/FileAPI] Allow MediaSource, disallow any more extensions (#103) (Friday, 1 February)
• Re: [w3c/FileAPI] Allow MediaSource, disallow any more extensions (#103) (Friday, 1 February)
• Re: [w3c/FileAPI] Allow MediaSource, disallow any more extensions (#103) (Friday, 1 February)

Kenneth Rohde Christiansen

• Re: [w3ctag/design-reviews] User Idle Detection (#336) (Tuesday, 26 February)
• Re: [w3ctag/design-reviews] Web Bluetooth Scanning (#333) (Wednesday, 6 February)
• Re: [w3ctag/design-reviews] Web Bluetooth Scanning (#333) (Wednesday, 6 February)
• Re: [w3ctag/design-reviews] Web Bluetooth Scanning (#333) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] Contact API (#337) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] Web Bluetooth Scanning (#333) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] JavaScript WeakRefs (#321) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] Layered APIs (#276) (Tuesday, 5 February)
• Re: [w3c/screen-orientation] Resolving the promise after the change event is fired (#147) (Tuesday, 5 February)
• Re: [w3c/screen-orientation] Resolving the promise after the change event is fired (#147) (Tuesday, 5 February)
• Re: [w3c/screen-orientation] Resolving the promise after the change event is fired (#147) (Tuesday, 5 February)

Kinuko Yasuda

• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Wednesday, 27 February)

Krzysztof Kotowicz

• Re: [w3ctag/design-reviews] Trusted Types (#198) (Thursday, 7 February)

L. David Baron

• Re: [w3ctag/design-reviews] User Activation API (#300) (Saturday, 23 February)
• Re: [w3ctag/design-reviews] CSS Properties and Values API Level 1 (#318) (Monday, 11 February)
• Re: [w3ctag/design-reviews] First-Party Sets (#342) (Friday, 8 February)
• Re: [w3ctag/design-reviews] User Activation API (#300) (Friday, 8 February)
• Re: [w3ctag/design-reviews] Trusted Types (#198) (Thursday, 7 February)
• Re: [w3ctag/design-reviews] User Activation API (#300) (Thursday, 7 February)
• Re: [w3ctag/design-reviews] Portals (#331) (Thursday, 7 February)
• Re: [w3ctag/design-reviews] Portals (#331) (Wednesday, 6 February)
• Re: [w3ctag/design-reviews] <link> rel="modulepreload" (#213) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] Task Scheduling (#72) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] Scheduling APIs (#338) (Monday, 4 February)
• Re: [w3ctag/design-reviews] Serialization of natural language in data formats such as JSON [I18N] (#178) (Monday, 4 February)
• Re: [w3ctag/design-reviews] Feature policy control over sandbox features (#339) (Monday, 4 February)

Lars T Hansen

• Re: [whatwg/encoding] Make decode() and encodeInto() accept SharedArrayBuffer-backed views (#172) (Monday, 11 February)
• Re: [whatwg/encoding] Make decode() and encodeInto() accept SharedArrayBuffer-backed views (#172) (Monday, 11 February)
• Re: [whatwg/encoding] New TextDecoder.decode() API needed for Wasm multithreading (#172) (Monday, 11 February)

Lucas Gadani

• Re: [w3ctag/design-reviews] Portals (#331) (Monday, 11 February)
• Re: [w3ctag/design-reviews] Portals (#331) (Friday, 8 February)

Luiz “Felds” Liscia

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

Lukasz Anforowicz

• Re: [whatwg/fetch] More CORB-protected MIME types - safelist-based approach (#721) (Thursday, 28 February)
• Re: [whatwg/fetch] More CORB-protected MIME types - safelist-based approach (#721) (Thursday, 28 February)

Lukasz Olejnik

• Re: [w3ctag/design-reviews] User Idle Detection (#336) (Tuesday, 26 February)
• Re: [w3ctag/design-reviews] Migrating some high-entropy HTTP request headers to Client Hints. (#320) (Thursday, 14 February)
• Re: [w3ctag/design-reviews] Web Bluetooth Scanning (#333) (Friday, 8 February)
• Re: [w3ctag/design-reviews] Review Request: Priority Hints API (#241) (Wednesday, 6 February)

Luke Wagner

• Re: [whatwg/encoding] New TextDecoder.decode() API needed for Wasm multithreading (#172) (Thursday, 7 February)
• Re: [heycam/webidl] Idea for [AllowShared] (handling SharedArrayBuffer safely) (#638) (Tuesday, 5 February)

Maciej Stachowiak

• Re: [w3ctag/design-reviews] Portals (#331) (Wednesday, 13 February)
• Re: [w3ctag/design-reviews] Portals (#331) (Tuesday, 12 February)
• Re: [w3ctag/design-reviews] Portals (#331) (Saturday, 9 February)
• Re: [w3ctag/design-reviews] Portals (#331) (Saturday, 9 February)
• Re: [whatwg/fetch] Does Client Hints have multi vendor support? (#867) (Monday, 4 February)
• [whatwg/fetch] Does Client Hints have multi vendor support? (#867) (Sunday, 3 February)

Manish Goregaokar

• Re: [heycam/webidl] Allow extended attributes to apply to types (#286) (Monday, 18 February)
• [w3c/FileAPI] [Clamp] now applies to types (#116) (Monday, 18 February)

Marc Gruetzmacher

• Re: [w3c/manifest] Allow for multiple scopes (#449) (Friday, 1 February)

Marcos Cáceres

• Re: [w3c/screen-orientation] Reliability of angle (#162) (Thursday, 28 February)
• Re: [w3c/screen-orientation] Fix: move title inside best practice box (#163) (Thursday, 28 February)
• [w3c/screen-orientation] Reliability of angle (#162) (Thursday, 28 February)
• Re: [w3c/screen-orientation] Locking orientation algorithm edits (#160) (Tuesday, 26 February)
• Re: [w3c/screen-orientation] Fix Web App Manifest link (#159) (Tuesday, 26 February)
• Re: [w3c/screen-orientation] Edit screen orientation type definitions (#161) (Tuesday, 26 February)
• Re: [w3c/screen-orientation] Fix Web App Manifest link (#159) (Monday, 25 February)
• Re: [w3c/gamepad] chore: add PULL_REQUEST_TEMPLATE (#86) (Sunday, 24 February)
• Re: [w3c/gamepad] Fix: Standard Gamepad dpad left / right button indices (#89) (Sunday, 24 February)
• Re: [w3c/gamepad] Fix: Standard Gamepad dpad left / right button indices (#89) (Sunday, 24 February)
• Re: [w3c/gamepad] Fix: Standard Gamepad dpad left / right button indices (#89) (Sunday, 24 February)
• Re: [w3c/screen-orientation] Resolving the promise after the change event is fired (#147) (Tuesday, 19 February)
• Re: [w3c/screen-orientation] Definition of default orientation (#150) (Tuesday, 19 February)
• Re: [w3c/screen-orientation] chore: enable respec-validator on TravisCI (#158) (Tuesday, 19 February)
• Re: [w3c/screen-orientation] chore: enable respec-validator on TravisCI (#158) (Tuesday, 19 February)
• Re: [w3c/screen-orientation] chore: enable respec-validator on TravisCI (#158) (Tuesday, 19 February)
• Re: [w3c/screen-orientation] chore: enable respec-validator on TravisCI (#158) (Tuesday, 19 February)
• Re: [w3c/screen-orientation] chore: enable respec-validator on TravisCI (#158) (Tuesday, 19 February)
• Re: [w3c/screen-orientation] chore: enable respec-validator on TravisCI (#158) (Tuesday, 19 February)
• Re: [w3c/screen-orientation] chore: enable respec-validator on TravisCI (#158) (Tuesday, 19 February)
• Re: [w3c/screen-orientation] chore: enable respec-validator on TravisCI (#158) (Tuesday, 19 February)
• Re: [w3c/screen-orientation] chore: enable respec-validator on TravisCI (#158) (Tuesday, 19 February)
• Re: [w3c/screen-orientation] chore: enable respec-validator on TravisCI (#158) (Tuesday, 19 February)
• Re: [w3c/screen-orientation] Add test link for lock-basic.html (#153) (Tuesday, 19 February)
• Re: [w3c/screen-orientation] chore: enable respect-validator on TravisCI (#158) (Tuesday, 19 February)
• [w3c/screen-orientation] chore: enable respect-validator on TravisCI (#158) (Tuesday, 19 February)
• Re: [w3c/screen-orientation] Add test link for lock-basic.html (#153) (Tuesday, 19 February)
• Re: [w3c/screen-orientation] Add test link for lock-basic.html (#153) (Monday, 18 February)
• Re: [heycam/webidl] Editorial: add a Privacy and Security Considerations section (#647) (Monday, 18 February)
• Re: [w3c/screen-orientation] Add test link for lock-basic.html (#153) (Monday, 18 February)
• Re: [w3c/screen-orientation] Add test link for lock-bad-argument (#152) (Monday, 18 February)
• Re: [w3c/screen-orientation] Add test link for lock-bad-argument (#152) (Monday, 18 February)
• Re: [w3c/screen-orientation] Edit to updating orientation algorithm (#157) (Monday, 18 February)
• Re: [w3c/screen-orientation] Edit to updating orientation algorithm (#157) (Monday, 18 February)
• Re: [w3c/screen-orientation] Add event-change.html test link to screen orientation change algorithm section (#154) (Friday, 15 February)
• Re: [w3c/screen-orientation] Add orientation-reading.html test (#155) (Friday, 15 February)
• Re: [w3c/screen-orientation] Add lock-sandboxed-iframe test (#156) (Friday, 15 February)
• Re: [w3c/permissions] chore(example): Escape special character (#149) (Thursday, 14 February)
• Re: [w3c/permissions] Use [SameObject] for navigator.permissions IDL (#190) (Thursday, 14 February)
• Re: [w3c/permissions] Use [SameObject] for navigator.permissions IDL (#190) (Thursday, 14 February)
• [w3c/screen-orientation] Double check lock(), event, re/unlock() behaviors (#151) (Wednesday, 13 February)
• Re: [w3c/screen-orientation] Send events before promise resolve (#120) (Tuesday, 12 February)
• Re: [w3c/screen-orientation] Resolving the promise after the change event is fired (#147) (Tuesday, 12 February)
• Re: [w3c/screen-orientation] Resolving the promise after the change event is fired (#147) (Tuesday, 12 February)
• Re: [w3c/screen-orientation] Resolving the promise after the change event is fired (#147) (Tuesday, 12 February)
• Re: [w3c/screen-orientation] Resolving the promise after the change event is fired (#147) (Monday, 11 February)
• Re: [w3c/WebPlatformWG] Promote File Handling to WICG (#127) (Monday, 11 February)
• Re: [w3c/screen-orientation] Resolving the promise after the change event is fired (#147) (Friday, 8 February)
• Re: [w3c/screen-orientation] Resolving the promise after the change event is fired (#147) (Friday, 8 February)
• Re: [w3c/screen-orientation] Resolving the promise after the change event is fired (#147) (Friday, 8 February)
• Re: [w3c/screen-orientation] Resolving the promise after the change event is fired (#147) (Thursday, 7 February)
• Re: [w3c/screen-orientation] Editorial: Internal slots (#144) (Thursday, 7 February)
• Re: [w3c/manifest] SVG icon sizes="any" (or without property "sizes") (#407) (Thursday, 7 February)
• Re: [w3c/screen-orientation] Editorial: Internal slots (#144) (Thursday, 7 February)
• Re: [w3c/screen-orientation] Editorial: Internal slots (#144) (Thursday, 7 February)
• Re: [w3c/screen-orientation] Editorial: Internal slots (#144) (Thursday, 7 February)
• Re: [w3c/screen-orientation] Editorial: Internal slots (#144) (Thursday, 7 February)
• Re: [w3c/screen-orientation] Editorial: Internal slots (#144) (Thursday, 7 February)
• Re: [w3c/screen-orientation] Editorial: Internal slots (#144) (Thursday, 7 February)
• Re: [w3c/screen-orientation] Editorial: Internal slots (#144) (Thursday, 7 February)
• Re: [w3c/screen-orientation] Resolving the promise after the change event is fired (#147) (Thursday, 7 February)
• Re: [w3c/screen-orientation] Editorial: Change 'security conditions' to 'pre-lock conditions' (#149) (Wednesday, 6 February)
• Re: [w3c/screen-orientation] Editorial: Change 'security conditions' to 'pre-lock conditions' (#149) (Wednesday, 6 February)
• Re: [w3c/screen-orientation] Editorial: Internal slots (#144) (Tuesday, 5 February)
• Re: [w3c/screen-orientation] Editorial: Internal slots (#144) (Tuesday, 5 February)
• Re: [w3c/screen-orientation] Editorial: HTML Tidy gh-pages (#148) (Tuesday, 5 February)
• Re: [w3c/screen-orientation] Editorial: HTML Tidy gh-pages (#148) (Tuesday, 5 February)
• Re: [w3c/screen-orientation] Resolving the promise after the change event is fired (#147) (Tuesday, 5 February)
• Re: [w3c/screen-orientation] Resolving the promise after the change event is fired (#147) (Tuesday, 5 February)
• Re: [w3c/screen-orientation] Resolving the promise after the change event is fired (#147) (Tuesday, 5 February)
• Re: [w3c/screen-orientation] Resolving the promise after the change event is fired (#147) (Monday, 4 February)
• Re: [w3c/screen-orientation] Resolving the promise after the change event is fired (#147) (Monday, 4 February)
• Re: [w3c/screen-orientation] Wide review tracker (#102) (Monday, 4 February)
• Re: [w3c/screen-orientation] Wide review tracker (#102) (Monday, 4 February)
• Re: [w3c/screen-orientation] Editorial: Internal slots (#144) (Monday, 4 February)
• [w3c/screen-orientation] The responsible document (#146) (Friday, 1 February)
• [w3c/screen-orientation] Clarify how to initialize the screen orientation (#145) (Friday, 1 February)

Marijn Kruisselbrink

• Re: [w3c/FileAPI] Fix Web IDL extended attribute usage: [Clamp] now applies to types (#116) (Tuesday, 19 February)
• Re: [w3c/FileAPI] Fix Web IDL extended attribute usage: [Clamp] now applies to types (#116) (Tuesday, 19 February)
• Re: [w3c/FileAPI] Streams are hot, FileReader.readAs____ is not (#40) (Friday, 8 February)
• Re: [w3c/FileAPI] Streams are hot, FileReader.readAs____ is not (#40) (Wednesday, 6 February)

Mark Kennedy

• Re: [w3ctag/design-reviews] Audiobooks (#345) (Friday, 15 February)

Mark Nottingham

• Re: [whatwg/fetch] Add Stale While Revalidate Handling (#853) (Tuesday, 19 February)
• Re: [whatwg/fetch] Allow servers to completely opt out of current and future CORS protection (#865) (Tuesday, 19 February)

Martin Thomson

• [w3c/permissions] Conditional permissions (#189) (Monday, 11 February)

Masayuki Nakano

• [w3c/uievents] "Process" key should be declared with more detail (#224) (Monday, 25 February)
• [w3c/uievents] Declare more detail of `InputEvent.data` value of `formatFontName` (#223) (Tuesday, 12 February)
• [w3c/uievents] Declare `InputEvent.data` value of `insertLink` should be relative URI if it's specified as relative URI (#222) (Tuesday, 12 February)
• Re: [w3c/editing] indent elements in different lines created by forced breaks <br> (#190) (Thursday, 7 February)
• [w3c/uievents] Event order between "keypress" and "beforeinput" (#220) (Friday, 1 February)

Matt Falkenhagen

• Re: [w3c/ServiceWorker] Don't fail update upon error fetching the incumbent worker's import s… (#1377) (Tuesday, 19 February)
• Re: [w3c/ServiceWorker] Don't fail update upon error fetching the incumbent worker's import s… (#1377) (Monday, 18 February)
• Re: [w3c/ServiceWorker] Minor improvements around importScripts. (#1380) (Monday, 18 February)
• Re: [w3c/ServiceWorker] Minor improvements around importScripts. (#1380) (Monday, 18 February)

Matteo Gioioso

• Re: [w3c/ServiceWorker] activate event not working with async function (#1388) (Thursday, 14 February)
• [w3c/ServiceWorker] activate event not working with async function (#1388) (Thursday, 14 February)

Matthew Phillips

• Re: [w3c/webcomponents] How to handle non-type=”module” scripts in HTML Modules? (#798) (Wednesday, 27 February)
• Re: [w3c/webcomponents] Move HTML Module Record definition from ES spec to HTML5 spec (#796) (Tuesday, 26 February)

Mattias Buelens

• Re: [whatwg/streams] better-assert is broken (#985) (Monday, 25 February)
• Re: [whatwg/streams] better-assert is broken (#985) (Monday, 25 February)
• Re: [whatwg/streams] ReadableStreamTee: do not read when already pulling (#997) (Monday, 25 February)
• Re: [whatwg/streams] ReadableStreamTee: do not read when already pulling (#997) (Monday, 25 February)
• Re: [whatwg/streams] ReadableStreamTee pulls too many chunks (#996) (Saturday, 23 February)
• Re: [whatwg/streams] ReadableStreamTee: do not read when already pulling (#997) (Saturday, 23 February)
• [whatwg/streams] ReadableStreamTee: do not read when already pulling (#997) (Saturday, 23 February)
• Re: [whatwg/streams] better-assert is broken (#985) (Saturday, 23 February)
• Re: [whatwg/streams] ReadableStreamTee pulls too many chunks (#996) (Friday, 22 February)
• Re: [whatwg/streams] ReadableStreamTee pulls too many chunks (#996) (Thursday, 21 February)
• [whatwg/streams] ReadableStreamTee pulls too many chunks (#996) (Thursday, 21 February)
• Re: [whatwg/streams] In ReadableStreamTee, replace _closedOrErrored_ with _closed_ (#994) (Thursday, 21 February)
• [whatwg/streams] Simplify [@@asyncIterator].next() (#995) (Thursday, 21 February)
• Re: [whatwg/streams] In ReadableStreamTee, replace _closedOrErrored_ with _closed_ (#994) (Thursday, 21 February)
• Re: [whatwg/streams] Semantics of |closedOrErrored| variable in ReadableStreamTee are odd (#991) (Thursday, 21 February)
• Re: [whatwg/streams] Semantics of |closedOrErrored| variable in ReadableStreamTee are odd (#991) (Thursday, 21 February)
• Re: [whatwg/streams] ReadableStream reference implementation: remove unnecessary code (#992) (Tuesday, 19 February)
• Re: [whatwg/streams] ReadableStream reference implementation: remove unnecessary code (#992) (Tuesday, 19 February)
• Re: [whatwg/streams] Remove call to ClearPendingPullIntos from SetUpReadableByteSC (#993) (Tuesday, 19 February)
• Re: [whatwg/streams] Initialize ReadableByteStreamController.[[byobRequest]] to undefined (#990) (Tuesday, 19 February)
• [whatwg/streams] Initialize ReadableByteStreamController.[[byobRequest]] to undefined (#990) (Monday, 18 February)
• Re: [whatwg/streams] Stop using better-assert (#988) (Monday, 18 February)
• Re: [whatwg/streams] better-assert is broken (#985) (Friday, 15 February)
• Re: [whatwg/streams] better-assert is broken (#985) (Friday, 15 February)
• Re: [whatwg/streams] Possible feature discussion: opaque streams (#983) (Thursday, 14 February)
• Re: [whatwg/streams] Possible feature discussion: opaque streams (#983) (Thursday, 14 February)
• Re: [whatwg/streams] Treat forAuthorCode as an internal slot of reader object (#984) (Saturday, 9 February)
• Re: [whatwg/streams] Treat forAuthorCode as an internal slot of reader object (#984) (Saturday, 9 February)
• Re: [whatwg/streams] Treat forAuthorCode as an internal slot of reader object (#984) (Saturday, 9 February)
• Re: [whatwg/streams] Treat forAuthorCode as an internal slot of reader object (#984) (Saturday, 9 February)
• [whatwg/streams] Treat forAuthorCode as an internal slot of reader object (#984) (Saturday, 9 February)
• Re: [whatwg/streams] Treat forAuthorCode as an internal slot of reader object. (#969) (Friday, 8 February)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Tuesday, 5 February)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Tuesday, 5 February)
• Re: [whatwg/streams] Editorial changes to transferable streams explainer (#977) (Tuesday, 5 February)
• Re: [whatwg/streams] Editorial changes to transferable streams explainer (#977) (Tuesday, 5 February)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Monday, 4 February)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Monday, 4 February)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Monday, 4 February)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Sunday, 3 February)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Sunday, 3 February)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Sunday, 3 February)
• Re: [whatwg/streams] Add @@asyncIterator to ReadableStream (#980) (Sunday, 3 February)

Md Zubair Ahmed

• Re: [whatwg/fetch] Add domintro explanations for web developers (#543) (Saturday, 23 February)
• Re: [whatwg/fetch] Add domintro explanations for web developers (#543) (Friday, 22 February)
• Re: [whatwg/fetch] Fixed Issue-846 : remove URL filesystem scheme (#873) (Friday, 22 February)
• Re: [whatwg/fetch] Fixed Issue-846 : remove URL filesystem scheme (#873) (Friday, 22 February)
• Re: [whatwg/fetch] Fixed Issue-846 : remove URL filesystem scheme (#873) (Friday, 22 February)
• Re: [whatwg/fetch] Fixed Issue-846 : remove URL filesystem scheme (#873) (Friday, 22 February)
• [whatwg/fetch] Fixed Issue-846 : remove URL filesystem scheme (#873) (Thursday, 21 February)
• Re: [whatwg/fetch] Remove "filesystem" URL scheme (#846) (Thursday, 21 February)
• Re: [whatwg/fetch] Remove "filesystem" URL scheme (#846) (Saturday, 16 February)

Michael Stramel

• Re: [w3c/webcomponents] Scoped Custom Element Registries (#716) (Monday, 18 February)

Michael[tm] Smith

• Re: [whatwg/fetch] Clarification on CORS preflight fetches for TLS client certificates (#869) (Thursday, 7 February)

Mike West

• Re: [w3ctag/design-reviews] Migrating some high-entropy HTTP request headers to Client Hints. (#320) (Thursday, 14 February)
• Re: [whatwg/fetch] Restrict allowed JavaScript MIME types (#870) (Monday, 11 February)
• Re: [w3ctag/design-reviews] First-Party Sets (#342) (Friday, 8 February)
• Re: [whatwg/fetch] Restrict allowed JavaScript MIME types (#870) (Friday, 8 February)
• [w3ctag/design-reviews] First-Party Sets (#342) (Friday, 8 February)
• Re: [w3ctag/design-reviews] Clear Site Data (#62) (Tuesday, 5 February)

Mo

• Re: [whatwg/fetch] Cannot get next URL for redirect="manual" (#763) (Saturday, 23 February)

Mounir Lamouri

• Re: [w3c/screen-orientation] Reliability of angle (#162) (Thursday, 28 February)
• Re: [w3c/screen-orientation] Resolving the promise after the change event is fired (#147) (Monday, 11 February)
• Re: [w3c/screen-orientation] Resolving the promise after the change event is fired (#147) (Friday, 8 February)
• Re: [w3c/screen-orientation] Resolving the promise after the change event is fired (#147) (Friday, 8 February)
• Re: [w3c/screen-orientation] Resolving the promise after the change event is fired (#147) (Thursday, 7 February)
• Re: [w3c/screen-orientation] Definition of default orientation (#150) (Thursday, 7 February)
• Re: [w3c/screen-orientation] Resolving the promise after the change event is fired (#147) (Monday, 4 February)

Ms2ger

• [heycam/webidl] Deduplicate unforgeable member functions (#668) (Thursday, 28 February)
• [heycam/webidl] Editorial: remove redundant requirement for existence of 'length' (#667) (Thursday, 28 February)
• Re: [heycam/webidl] Formalize the 'this' and 'given value' ambient values (#665) (Thursday, 28 February)
• Re: [heycam/webidl] Editorial: run platform algorithms on IDL objects (#666) (Thursday, 28 February)
• Re: [heycam/webidl] Formalize the 'this' and 'given value' ambient values (#665) (Wednesday, 27 February)
• [heycam/webidl] Editorial: run platform algorithms on IDL objects (#666) (Wednesday, 27 February)
• [heycam/webidl] Formalize the 'this' and 'given value' ambient values (#665) (Wednesday, 27 February)
• [heycam/webidl] Editorial: improve language around conversions to JS (#664) (Wednesday, 27 February)
• Re: [heycam/webidl] State the associated realm when creating objects (#206) (Wednesday, 27 February)
• Re: [heycam/webidl] Is a subclass still a platform object? (#540) (Wednesday, 27 February)
• [heycam/webidl] Remove the 'user object' concept. (#662) (Tuesday, 26 February)
• [heycam/webidl] Should callback interfaces with more than one operation be supported? (#661) (Tuesday, 26 February)
• Re: [heycam/webidl] Referencing "implements" (#659) (Tuesday, 26 February)
• Re: [heycam/webidl] Review handling of WindowProxy (#656) (Tuesday, 26 February)
• Re: [heycam/webidl] Improve the named property visibility algorithm for Window. (#626) (Tuesday, 26 February)
• Re: [heycam/webidl] Is internal method setup in object creation correct? (#657) (Tuesday, 26 February)
• Re: [heycam/webidl] Referencing "implements" (#659) (Tuesday, 26 February)
• Re: [heycam/webidl] Formally define a [[Realm]] slot on platform objects (#658) (Monday, 25 February)
• Re: [heycam/webidl] Is internal method setup in object creation correct? (#657) (Monday, 25 February)
• Re: [heycam/webidl] Imperatively define the global property references (#648) (Monday, 25 February)
• [heycam/webidl] Formally define a [[Realm]] slot on platform objects (#658) (Monday, 25 February)
• Re: [heycam/webidl] Define "implements" checks using internal slots (#654) (Monday, 25 February)
• Re: [heycam/webidl] Add [[PlatformBrand]] internal slot to all platform objects (#97) (Monday, 25 February)
• [heycam/webidl] Review handling of WindowProxy (#656) (Monday, 25 February)
• Re: [heycam/webidl] Can we use ObjectCreate in object creation? + other editorial tweaks (#655) (Monday, 25 February)
• Re: [heycam/webidl] Define "implements" checks using internal slots (#654) (Monday, 25 February)
• [heycam/webidl] Define "implements" checks using internal slots (#654) (Monday, 25 February)
• Re: [heycam/webidl] Clarify object creation in named constructors (#652) (Monday, 25 February)
• Re: [heycam/webidl] Disallow combining LegacyWindowAlias and LegacyNamespace (#651) (Monday, 25 February)
• Re: [heycam/webidl] Should LegacyWindowAlias and LegacyNamespace be allowed together? (#645) (Monday, 25 February)
• Re: [heycam/webidl] Clarify object creation in named constructors (#652) (Monday, 25 February)
• Re: [heycam/webidl] Clarify object creation in named constructors (#652) (Monday, 25 February)
• Re: [heycam/webidl] Clarify object creation in named constructors (#652) (Monday, 25 February)
• Re: [heycam/webidl] Imperatively define the interface objects (#648) (Monday, 25 February)
• [heycam/webidl] Consider allowing only one NamedConstructor per interface (#653) (Monday, 25 February)
• Re: [heycam/webidl] Imperatively define the interface objects (#648) (Monday, 25 February)
• Re: [w3c/DOM-Parsing] Improve definition of URL for Documents created by DOMParser (#46) (Monday, 25 February)
• [w3c/DOM-Parsing] Improve definition of URL for Documents created by DOMParser (#46) (Monday, 25 February)
• [heycam/webidl] Clarify object creation in named constructors (#652) (Monday, 25 February)
• [heycam/webidl] Disallow combining LegacyWindowAlias and LegacyNamespace (#651) (Monday, 25 February)
• Re: [heycam/webidl] Imperatively define the interface objects (#648) (Friday, 22 February)
• [heycam/webidl] Imperatively define the interface objects (#648) (Friday, 22 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Friday, 22 February)
• Re: [heycam/webidl] Improve the named property visibility algorithm for Window. (#626) (Wednesday, 20 February)
• Re: [heycam/webidl] Improve the named property visibility algorithm for Window. (#626) (Wednesday, 20 February)
• Re: [heycam/webidl] Improve the named property visibility algorithm for Window. (#626) (Wednesday, 20 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Tuesday, 19 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Tuesday, 19 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Tuesday, 19 February)
• [heycam/webidl] Editorial: add a Privacy and Security Considerations section (#647) (Friday, 15 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Thursday, 14 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Thursday, 14 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Thursday, 14 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Thursday, 14 February)
• [heycam/webidl] Editorial: correct 'callback interface' cross-reference (#646) (Wednesday, 13 February)
• [heycam/webidl] Should LegacyWindowAlias and LegacyNamespace be allowed together? (#645) (Wednesday, 13 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Wednesday, 13 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Wednesday, 13 February)
• Re: [heycam/webidl] Import (and fix) the promises guide (#490) (Tuesday, 12 February)
• [heycam/webidl] Use PerformPromiseThen to perform some steps once a promise is settled (#644) (Tuesday, 12 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Tuesday, 12 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Tuesday, 12 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Monday, 11 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Monday, 11 February)
• Re: [heycam/webidl] Editorial: gsnedders's name changed (#643) (Monday, 11 February)
• Re: [heycam/webidl] Editorial: gsnedders's name changed (#643) (Monday, 11 February)
• Re: [heycam/webidl] Editorial: use the new signature of CreateBuiltinFunction (#642) (Monday, 11 February)
• [heycam/webidl] Editorial: use the new signature of CreateBuiltinFunction (#642) (Monday, 11 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Friday, 8 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Friday, 8 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Friday, 8 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Friday, 8 February)
• [heycam/webidl] Define the static operations on the interface object (#641) (Thursday, 7 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Thursday, 7 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Thursday, 7 February)
• Re: [heycam/webidl] Specify what typeof should return for exotic objects (#640) (Thursday, 7 February)
• [heycam/webidl] Correct requirement to define Global properties on the object itself (#639) (Wednesday, 6 February)
• [heycam/webidl] Add cross-reference to 'exposed' in the [SecureContext] definition (#637) (Tuesday, 5 February)
• [heycam/webidl] Stop using extended attributes for constructors (#636) (Monday, 4 February)

Mustaq Ahmed

• [w3ctag/design-reviews] TAG review request: User Activation Delegation through postMessages (#347) (Friday, 22 February)

Myles Borins

• Re: [w3c/webcomponents] JSON "modules" (#770) (Tuesday, 26 February)

Narongrit Pilantasnarat

• Re: [w3c/ServiceWorker] Configure script's settings and realm for service workers (#1294) (Monday, 25 February)
• Re: [w3c/ServiceWorker] Configure script's settings and realm for service workers (#1294) (Monday, 25 February)

Nathan Schloss

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

Navid Zolghadr

• [w3ctag/design-reviews] Pointerevent getPredictedPoints (#346) (Tuesday, 19 February)

Neville Dabre

• Re: [w3c/ServiceWorker] Service Worker registration failed: DOMException: Failed to register a ServiceWorker: An SSL certificate error occurred when fetching the script. (#1159) (Thursday, 28 February)

npm1

• Re: [w3ctag/design-reviews] Element Timing API for img (#326) (Monday, 11 February)
• Re: [w3ctag/design-reviews] Element Timing API for img (#326) (Friday, 8 February)
• Re: [w3ctag/design-reviews] Element Timing API for img (#326) (Friday, 8 February)
• Re: [w3ctag/design-reviews] Event Timing API (#324) (Friday, 8 February)

Oliver Janik

• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Tuesday, 12 February)
• Re: [whatwg/fetch] upload progress? (#21) (Tuesday, 12 February)

ouksal

• Re: [w3c/ServiceWorker] Provide an easier way to listen for waiting/activated/redundant Service Workers (#1247) (Wednesday, 13 February)
• Re: [w3c/ServiceWorker] Provide an easier way to listen for waiting/activated/redundant Service Workers (#1247) (Wednesday, 13 February)

Patrick H. Lauke

• Re: [w3c/touch-events] Use GlobalEventHandlers as a mixin (#103) (Monday, 11 February)

Peter Linss

• Re: [w3ctag/design-reviews] User Activation API (#300) (Monday, 25 February)
• Re: [w3ctag/design-reviews] User Activation API (#300) (Monday, 25 February)

Philip Jägenstedt

• Re: [whatwg/fullscreen] Introduce document.exitFullscreen({ fully: true })? (#70) (Thursday, 28 February)
• Re: [whatwg/fullscreen] Introduce document.exitFullscreen({ fully: true })? (#70) (Wednesday, 27 February)
• Re: [whatwg/fullscreen] Introduce document.exitFullscreen({ fully: true })? (#70) (Tuesday, 26 February)
• Re: [whatwg/fullscreen] I want to avoid fullscreen elements covering anything else in the top layer, e.g. dialog. (#146) (Tuesday, 26 February)
• Re: [whatwg/fullscreen] ruby3 (#147) (Tuesday, 26 February)
• Re: [whatwg/fullscreen] Fix logical error of filling fullscreenElements (3.12) (#145) (Monday, 25 February)
• Re: [whatwg/fullscreen] Rephrase: 3.12 While the first element in fullscreenElements is ... (#144) (Monday, 25 February)
• Re: [whatwg/fullscreen] Fix logical error of filling fullscreenElements (3.12) (#145) (Monday, 25 February)
• Re: [whatwg/fullscreen] Fix logical error of filling fullscreenElements (3.12) (#145) (Monday, 25 February)
• Re: [whatwg/fullscreen] Fix logical error of filling fullscreenElements (3.12) (#145) (Friday, 22 February)
• Re: [heycam/webidl] Remove [NoInterfaceObject]. (#609) (Thursday, 14 February)
• Re: [heycam/webidl] Remove [NoInterfaceObject]. (#609) (Thursday, 14 February)
• Re: [heycam/webidl] Remove [NoInterfaceObject]. (#609) (Thursday, 14 February)
• [whatwg/storage] Use [SameObject] for navigator.storage IDL (#66) (Thursday, 14 February)
• [w3c/permissions] Use [SameObject] for navigator.permissions IDL (#190) (Thursday, 14 February)
• Re: [w3c/touch-events] Use GlobalEventHandlers as a mixin (#103) (Monday, 11 February)
• [w3c/touch-events] Use GlobalEventHandlers as a mixin (#103) (Saturday, 9 February)
• Re: [w3c/ServiceWorker] WindowOrWorkerGlobalScope is a mixin (#1309) (Saturday, 9 February)

Philip Walton

• Re: [w3c/ServiceWorker] Provide a one-line way to listen for a waiting Service Worker (#1222) (Wednesday, 13 February)
• Re: [w3c/ServiceWorker] Provide a one-line way to listen for a waiting Service Worker (#1222) (Wednesday, 13 February)
• Re: [w3c/ServiceWorker] Add a script version property to the ServiceWorker object (#1387) (Monday, 4 February)
• Re: [w3c/ServiceWorker] Add a script version property to the ServiceWorker object (#1387) (Friday, 1 February)
• Re: [w3c/ServiceWorker] Add a script version property to the ServiceWorker object (#1387) (Friday, 1 February)

Photopea

• Re: [w3c/manifest] Allowing only site-triggered install prompt (#627) (Wednesday, 6 February)

Pieter Colpaert

• Re: [whatwg/fetch] Allow servers to completely opt out of current and future CORS protection (#865) (Thursday, 7 February)

Pine

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

Piotrek Koszuliński

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

poeske887@users.noreply.github.com

• [whatwg/fetch] http (#872) (Monday, 18 February)

Randall Leeds

• Re: [w3c/selection-api] Add Selection/Range methods based on anchestor element (#102) (Thursday, 28 February)

Richard Bushell

• Re: [whatwg/fullscreen] Introduce document.exitFullscreen({ fully: true })? (#70) (Thursday, 28 February)
• Re: [whatwg/fullscreen] Introduce document.exitFullscreen({ fully: true })? (#70) (Wednesday, 27 February)
• Re: [whatwg/fullscreen] Introduce document.exitFullscreen({ fully: true })? (#70) (Tuesday, 26 February)

Robert Linder

• Re: [w3c/ServiceWorker] Hiding add to homescreen minibar for certain urls. (#1375) (Tuesday, 19 February)
• Re: [w3c/ServiceWorker] Immediate Service Worker (#1389) (Tuesday, 19 February)

Ruben Verborgh

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

Ryosuke Niwa

• Re: [whatwg/dom] Capturing event listeners are called during bubbling phase for shadow hosts (#685) (Wednesday, 27 February)
• Re: [w3c/webcomponents] SVG use element can't reference an element within the same shadow tree (#772) (Monday, 25 February)
• Re: [w3c/webcomponents] Can I style a slotted element by its slot name? (#795) (Friday, 22 February)
• Re: [w3c/webcomponents] Can I style a slotted element by its slot name? (#795) (Friday, 22 February)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Friday, 22 February)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Wednesday, 20 February)
• Re: [w3c/webcomponents] JSON "modules" (#770) (Tuesday, 19 February)
• Re: [w3c/webcomponents] Question: where to incubate HTML modules? (#794) (Saturday, 16 February)
• Re: [w3c/webcomponents] Can I style a slotted element by its slot name? (#795) (Saturday, 16 February)
• Re: [w3c/webcomponents] Question: where to incubate HTML modules? (#794) (Friday, 15 February)
• Re: [w3c/selection-api] Selection events for text controls (#53) (Thursday, 7 February)
• Re: [w3c/webcomponents] A way to detect if a custom element was constructed during customElements.define call? (#790) (Thursday, 7 February)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Monday, 4 February)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Sunday, 3 February)
• Re: [w3c/webcomponents] Serialize shadow DOM for use in javascript disabled user agents (#788) (Sunday, 3 February)
• Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550) (Sunday, 3 February)
• Re: [w3c/webcomponents] Is there a way to detect if a custom element was constructed during parsing? (#789) (Friday, 1 February)
• Re: [w3c/webcomponents] Is there a way to detect if a custom element was constructed during parsing? (#789) (Friday, 1 February)
• Re: [w3c/webcomponents] Is there a way to detect if a custom element was constructed during parsing? (#789) (Friday, 1 February)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Friday, 1 February)
• Re: [w3c/webcomponents] Serialize shadow DOM for use in javascript disabled user agents (#788) (Friday, 1 February)
• Re: [w3c/webcomponents] Is there a way to detect if a custom element was constructed during parsing? (#789) (Friday, 1 February)
• Re: [w3c/webcomponents] Web Components F2F Spring 2019 (#786) (Friday, 1 February)

Sahel Sharify

• Re: [whatwg/dom] Add the ability for an EventTarget to provide an algorithm to override (#366) (Friday, 1 February)

sam goto

• Re: [w3ctag/design-reviews] User Idle Detection (#336) (Thursday, 28 February)
• Re: [w3ctag/design-reviews] User Idle Detection (#336) (Tuesday, 26 February)
• Re: [w3ctag/design-reviews] User Idle Detection (#336) (Tuesday, 26 February)
• Re: [w3ctag/design-reviews] User Idle Detection (#336) (Tuesday, 26 February)

Sebastian Müller

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

sengsoulivanh

• [whatwg/xhr] madness (#239) (Thursday, 28 February)

Serhii Kulykov

• Re: [w3c/webcomponents] appreciate your feedback for custom element diagram (#784) (Wednesday, 20 February)

Shiino Yuki

• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Friday, 8 February)
• Re: [heycam/webidl] Stop using extended attributes for constructors (#636) (Tuesday, 5 February)

singsong

• [w3c/ServiceWorker] A description mistake in spec document (#1391) (Wednesday, 20 February)

sleevi

• Re: [whatwg/fetch] Clarification on CORS preflight fetches for TLS client certificates (#869) (Monday, 11 February)
• Re: [whatwg/fetch] Clarification on CORS preflight fetches for TLS client certificates (#869) (Wednesday, 6 February)
• [whatwg/fetch] Clarification on CORS preflight fetches for TLS client certificates (#869) (Wednesday, 6 February)

spanicker

• Re: [w3ctag/design-reviews] Scheduling APIs (#338) (Tuesday, 12 February)
• Re: [w3ctag/design-reviews] Scheduling APIs (#338) (Tuesday, 12 February)

Stephen McGruer

• Re: [w3ctag/design-reviews] Scroll-linked Animations (#330) (Tuesday, 5 February)

Stephen Niedzielski

• [w3c/gamepad] Fix: Standard Gamepad dpad left / right button indices (#89) (Sunday, 24 February)

Steven Hatzakis

• [w3c/ServiceWorker] Fully inline (.js + json manifest) service worker (#1392) (Tuesday, 26 February)
• Re: [w3c/ServiceWorker] Remove foreign fetch (#1188) (Monday, 25 February)

Steven Penny

• Re: [whatwg/fetch] Should we send an Origin header for no-cors fetches? (#225) (Sunday, 17 February)
• Re: [whatwg/fetch] Tests do not always require Origin header when mode is "cors" (#871) (Sunday, 17 February)
• [whatwg/fetch] vague spec result in Firefox security hole (#871) (Saturday, 16 February)

Tab Atkins Jr.

• Re: [heycam/webidl] Stop using extended attributes for constructors (#636) (Wednesday, 6 February)

TAMURA, Kent

• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Tuesday, 26 February)
• Re: [w3c/webcomponents] Need callback for form submit data (#187) (Tuesday, 26 February)
• [w3c/DOM-Parsing] It's possible that 'retrieve a preferred prefix string' returns a wrong prefix for the specified namespace (#45) (Friday, 15 February)
• [w3c/DOM-Parsing] It's possible for 'generate a prefix' algorithm to generate a prefix conflicting with an existing one (#44) (Friday, 15 February)
• [w3c/DOM-Parsing] Editorial error in 'XML serializing an Element node' (#43) (Friday, 15 February)
• Re: [w3ctag/design-reviews] Form Participation API (#305) (Thursday, 7 February)

Thomas Allmer

• Re: [w3c/webcomponents] appreciate your feedback for custom element diagram (#784) (Wednesday, 20 February)
• Re: [w3c/webcomponents] appreciate your feedback for custom element diagram (#784) (Wednesday, 20 February)

Thomas Steiner

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

Timothy Gu

• Re: [heycam/webidl] Editorial: run platform algorithms on IDL objects (#666) (Wednesday, 27 February)
• Re: [heycam/webidl] How to deal with Location (#660) (Tuesday, 26 February)
• [heycam/webidl] Clean up some parts of object creation (#663) (Tuesday, 26 February)
• Re: [heycam/webidl] Review handling of WindowProxy (#656) (Monday, 25 February)
• Re: [heycam/webidl] Can we use ObjectCreate in object creation? + other editorial tweaks (#655) (Monday, 25 February)
• Re: [heycam/webidl] Is internal method setup in object creation correct? (#657) (Monday, 25 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Thursday, 14 February)
• Re: [heycam/webidl] Add an algorithm to create a platform object. (#635) (Wednesday, 13 February)
• Re: [heycam/webidl] Specify what typeof should return for exotic objects (#640) (Saturday, 9 February)
• Re: [heycam/webidl] Specify what typeof should return for exotic objects (#640) (Saturday, 9 February)
• [heycam/webidl] Specify what typeof should return for exotic objects (#640) (Wednesday, 6 February)
• Re: [heycam/webidl] Stop using extended attributes for constructors (#636) (Monday, 4 February)

Tom Schuster

• Re: [whatwg/fetch] Restrict allowed JavaScript MIME types (#870) (Friday, 8 February)
• [whatwg/fetch] Restrict allowed JavaScript MIME types (#870) (Thursday, 7 February)

Travis Leithead

• Re: [w3c/webcomponents] Include updated info on HTML Modules (#799) (Wednesday, 27 February)
• [w3c/webcomponents] Include updated info on HTML Modules (#799) (Wednesday, 27 February)
• [w3c/webcomponents] How to handle non-type=”module” scripts in HTML Modules? (#798) (Wednesday, 27 February)
• Re: [w3c/webcomponents] Quirks render mode in HTML Modules (#797) (Wednesday, 27 February)
• [w3c/webcomponents] Quirks render mode in HTML Modules (#797) (Wednesday, 27 February)
• Re: [w3c/webcomponents] Question: where to incubate HTML modules? (#794) (Wednesday, 27 February)
• Re: [w3c/webcomponents] Question: where to incubate HTML modules? (#794) (Wednesday, 27 February)
• Re: [w3c/webcomponents] Move HTML Module Record definition from ES spec to HTML5 spec (#796) (Wednesday, 27 February)
• Re: [w3c/webcomponents] Question: where to incubate HTML modules? (#794) (Saturday, 16 February)
• Re: [w3c/webcomponents] Update HTML Modules Proposed Spec changes and initial proposal document (#793) (Friday, 15 February)
• Re: [w3c/webcomponents] Update HTML Modules Proposed Spec changes and initial proposal document (#793) (Friday, 15 February)
• [w3c/webcomponents] Question: where to incubate HTML modules? (#794) (Thursday, 14 February)
• Re: [w3ctag/design-reviews] Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312) (Wednesday, 13 February)
• Re: [w3ctag/design-reviews] Trusted Types (#198) (Thursday, 7 February)
• Re: [w3ctag/design-reviews] Temporal proposal (#311) (Thursday, 7 February)
• Re: [w3ctag/design-reviews] Wide gamut support for Canvas/OffscreenCanvas/ImageBitmap (#315) (Thursday, 7 February)
• Re: [w3ctag/design-reviews] Scroll-linked Animations (#330) (Thursday, 7 February)
• Re: [w3ctag/design-reviews] Migrating some high-entropy HTTP request headers to Client Hints. (#320) (Wednesday, 6 February)
• Re: [w3ctag/design-reviews] Migrating some high-entropy HTTP request headers to Client Hints. (#320) (Wednesday, 6 February)
• Re: [w3ctag/design-reviews] Event Timing API (#324) (Wednesday, 6 February)
• Re: [w3ctag/design-reviews] Element Timing API for img (#326) (Wednesday, 6 February)
• Re: [w3ctag/design-reviews] Element Timing API for img (#326) (Wednesday, 6 February)
• Re: [w3ctag/design-reviews] imagesrcset and imagesizes attributes on link rel=preload (#329) (Wednesday, 6 February)
• Re: [w3ctag/design-reviews] imagesrcset and imagesizes attributes on link rel=preload (#329) (Wednesday, 6 February)
• Re: [w3ctag/design-reviews] Scroll-linked Animations (#330) (Tuesday, 5 February)
• Re: [w3ctag/design-reviews] Contact API (#337) (Tuesday, 5 February)

Tzviya

• Re: [w3ctag/design-reviews] Audiobooks (#345) (Friday, 15 February)
• Re: [w3ctag/design-reviews] Audiobooks (#345) (Friday, 15 February)
• [w3ctag/design-reviews] Audiobooks (#345) (Friday, 15 February)
• [w3ctag/design-reviews] Web Publications review (#344) (Friday, 15 February)

Wendy Seltzer

• Re: [w3ctag/design-reviews] ads.txt (#201) (Tuesday, 5 February)

Wenson Hsieh

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

Xidorn Quan

• Re: [whatwg/fullscreen] Rephrase: 3.12 While the first element in fullscreenElements is ... (#144) (Wednesday, 20 February)

Yoav Weiss

• Re: [whatwg/fetch] Copy client-hints list from env settings object. Align CH processing (#773) (Tuesday, 12 February)
• Re: [whatwg/fetch] Copy client-hints list from env settings object. Align CH processing (#773) (Tuesday, 12 February)
• Re: [whatwg/fetch] Copy client-hints list from env settings object. Align CH processing (#773) (Tuesday, 12 February)
• Re: [whatwg/fetch] Copy client-hints list from env settings object. Align CH processing (#773) (Tuesday, 12 February)
• Re: [whatwg/fetch] Allow servers to completely opt out of current and future CORS protection (#865) (Thursday, 7 February)
• Re: [w3ctag/design-reviews] Review Request: Priority Hints API (#241) (Monday, 4 February)
• Re: [whatwg/fetch] Does Client Hints have multi vendor support? (#867) (Monday, 4 February)

Yutaka Hirano

• Re: [whatwg/fetch] Tests do not always require Origin header when mode is "cors" (#871) (Tuesday, 19 February)
• Re: [whatwg/fetch] Tests do not always require Origin header when mode is "cors" (#871) (Monday, 18 February)
• Re: [whatwg/fetch] Tests do not always require Origin header when mode is "cors" (#871) (Monday, 18 February)
• Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425) (Tuesday, 12 February)

Yves Lafon

• Re: [w3ctag/design-reviews] Migrating some high-entropy HTTP request headers to Client Hints. (#320) (Wednesday, 6 February)
• Re: [w3c/ServiceWorker] Declarative routing (#1373) (Tuesday, 5 February)

Zaquan59

• [whatwg/xhr] The good (#235) (Monday, 4 February)

Þórhallur Helgason

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

積丹尼 Dan Jacobson

• [w3c/uievents] mouseover/mouseout events can repeatedly causing infinite re-layout in some buggy content (#221) (Monday, 4 February)

Last message date: Thursday, 28 February 2019 23:48:12 UTC