1337 H4X0|2
Aaron Gustafson
Adam Rice
alancutter
Alphabet
Amy Guy
Ana Sollano Kim
Andrea Giammarchi
Andreu Botella
Anne van Kesteren
- Re: [whatwg/fullscreen] ::backdrop and :fullscreen now defined in CSS specs (Issue #221) (Friday, 31 March)
- Re: [whatwg/dom] Documents never have their node document set? (Issue #1178) (Friday, 31 March)
- Re: [whatwg/dom] Fix #1178: Define a document's node document. (PR #1179) (Friday, 31 March)
- Re: [whatwg/dom] Fix #1178: Define a document's node document. (PR #1179) (Friday, 31 March)
- Re: [whatwg/dom] Disconnect single target instead of all (#126) (Friday, 31 March)
- Re: [whatwg/dom] Handle attribute changes after changing attribute (PR #1176) (Thursday, 30 March)
- Re: [whatwg/dom] Documents never have their node document set? (Issue #1178) (Thursday, 30 March)
- Re: [whatwg/dom] Handle attribute changes after changing attribute (PR #1176) (Wednesday, 29 March)
- Re: [whatwg/webidl] Clarify #named-properties-object (PR #1285) (Wednesday, 29 March)
- Re: [whatwg/webidl] Clarify #named-properties-object (PR #1285) (Wednesday, 29 March)
- Re: [whatwg/url] HISTORY & SECURITY: URL Parsing Differences Between Implementations Security Issues (Issue #766) (Tuesday, 28 March)
- Re: [whatwg/dom] [Range] Should the DOM range spec include an i18n warning? (Issue #1177) (Tuesday, 28 March)
- Re: [whatwg/fetch] Add `Set-Cookie` as a forbidden header name (PR #1453) (Friday, 24 March)
- Re: [whatwg/fetch] Response static methods use null this value to specify the realm (Issue #1603) (Friday, 24 March)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417) (Friday, 24 March)
- Re: [whatwg/fetch] Use a basic filtered response for redirect navigations (PR #1618) (Friday, 24 March)
- Re: [whatwg/fetch] Use a basic filtered response for redirect navigations (PR #1618) (Friday, 24 March)
- Re: [whatwg/fetch] Correct blob: URL range requests (PR #1621) (Thursday, 23 March)
- Re: [whatwg/fetch] Correct blob: URL range requests (PR #1621) (Thursday, 23 March)
- Re: [whatwg/fetch] Add `<div algorithm>` wrappers around algorithms (Issue #1526) (Thursday, 23 March)
- Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to data URLs (PR #1619) (Thursday, 23 March)
- Re: [whatwg/storage] Meta: update repository files (PR #161) (Thursday, 23 March)
- Re: [whatwg/storage] Meta: update repository files (PR #161) (Thursday, 23 March)
- [whatwg/storage] Meta: update repository files (PR #161) (Thursday, 23 March)
- Re: [whatwg/url] Let [=UTF-8 percent-encode=] take an extra optional boolean parameter spaceAsPlus (default false) (Issue #765) (Thursday, 23 March)
- Re: [whatwg/url] Let [=UTF-8 percent-encode=] take an extra optional boolean parameter spaceAsPlus (default false) (Issue #765) (Wednesday, 22 March)
- Re: [whatwg/dom] Export event listener callback (PR #1174) (Wednesday, 22 March)
- Re: [whatwg/dom] Export event listener callback (PR #1174) (Wednesday, 22 March)
- Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to data URLs (PR #1619) (Wednesday, 22 March)
- Re: [whatwg/url] Let [=UTF-8 percent-encode=] take an extra optional boolean parameter spaceAsPlus (default false) (Issue #765) (Wednesday, 22 March)
- Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to data URLs (PR #1619) (Wednesday, 22 March)
- Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to data URLs (PR #1619) (Wednesday, 22 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 22 March)
- Re: [whatwg/dom] Export terms needed for ServiceWorker/1674 (PR #1170) (Wednesday, 22 March)
- Re: [whatwg/dom] Export terms needed for ServiceWorker/1674 (PR #1170) (Wednesday, 22 March)
- Re: [whatwg/dom] Export terms needed for ServiceWorker/1674 (PR #1170) (Wednesday, 22 March)
- Re: [whatwg/dom] Editorial: an HTMLCollection (PR #1173) (Wednesday, 22 March)
- Re: [whatwg/dom] Editorial: an HTMLCollection (PR #1173) (Wednesday, 22 March)
- Re: [whatwg/dom] Editorial: an HTMLCollection (PR #1173) (Wednesday, 22 March)
- Re: [whatwg/dom] Editorial: an HTMLCollection (PR #1173) (Wednesday, 22 March)
- [whatwg/dom] Editorial: an HTMLCollection (PR #1173) (Wednesday, 22 March)
- Re: [whatwg/dom] Allow 'lower-boundary' scoping argument in querySelector() (Issue #1172) (Wednesday, 22 March)
- Re: [whatwg/url] Let [=UTF-8 percent-encode=] take an extra optional boolean parameter spaceAsPlus (default false) (Issue #765) (Wednesday, 22 March)
- Re: [whatwg/fetch] Correct blob: URL range requests (PR #1621) (Tuesday, 21 March)
- [whatwg/fetch] Correct blob: URL range requests (PR #1621) (Tuesday, 21 March)
- Re: [whatwg/dom] Export terms needed for ServiceWorker/1674 (PR #1170) (Monday, 20 March)
- Re: [whatwg/webidl] Purpose of call-a-user-object’s-operation’s opName parameter (Issue #1282) (Monday, 20 March)
- Re: [whatwg/fetch] CI test (PR #1605) (Monday, 20 March)
- Re: [whatwg/dom] Export terms needed for ServiceWorker/1674 (PR #1170) (Monday, 20 March)
- Re: [whatwg/dom] What exactly does reflect touch target list entity? (Issue #1171) (Monday, 20 March)
- Re: [whatwg/url] URL.canParse() (Issue #713) (Monday, 20 March)
- Re: [whatwg/url] Add URL.canParse() (PR #763) (Monday, 20 March)
- Re: [whatwg/webidl] Review Draft Publication: March 2023 (PR #1284) (Monday, 20 March)
- [whatwg/webidl] Review Draft Publication: March 2023 (PR #1284) (Monday, 20 March)
- Re: [whatwg/url] URLSearchParams append/set: variadic values argument? (Issue #762) (Saturday, 18 March)
- Re: [whatwg/xhr] Need Discussion of 'why' Behind Deprecation of sync xhr (Issue #371) (Friday, 17 March)
- Re: [whatwg/xhr] Need Discussion of 'why' Behind Deprecation of sync xhr (Issue #371) (Friday, 17 March)
- Re: [whatwg/fetch] Use a basic filtered response for redirect navigations (PR #1618) (Friday, 17 March)
- Re: [whatwg/dom] Rename Range's 'start' and 'end' to 'range start' and 'range end'. (PR #1168) (Friday, 17 March)
- Re: [whatwg/webidl] Should a read–write maplike/setlike interface be allowed having static operations with same name as set methods, e.g. clear, delete ... (Issue #1280) (Friday, 17 March)
- Re: [whatwg/webidl] Allow static operations with the same names as default operations in Maplike/Setlike/Iterable/AsyncIterable (PR #1281) (Friday, 17 March)
- Re: [whatwg/webidl] Allow static operations with the same names as default operations in Maplike/Setlike/Iterable/AsyncIterable (PR #1281) (Friday, 17 March)
- Re: [whatwg/webidl] Allow static operations with the same names as default operations in Maplike/Setlike/Iterable/AsyncIterable (PR #1281) (Friday, 17 March)
- Re: [whatwg/url] Add URL.canParse() (PR #763) (Thursday, 16 March)
- Re: [whatwg/url] URL.canParse() (Issue #713) (Thursday, 16 March)
- [whatwg/url] Add URL.canParse() (PR #763) (Thursday, 16 March)
- Re: [whatwg/dom] Prohibit ServiceWorker event handler update after the initialization. (PR #1161) (Thursday, 16 March)
- Re: [whatwg/webidl] Should a read–write maplike/setlike interface be allowed having static operations with same name as set methods, e.g. clear, delete ... (Issue #1280) (Thursday, 16 March)
- Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Wednesday, 15 March)
- Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354) (Wednesday, 15 March)
- Re: [whatwg/url] javascript: URL parsing (#307) (Wednesday, 15 March)
- Re: [whatwg/encoding] Static methods for TextEncoder and TextDecoder (PR #284) (Tuesday, 14 March)
- Re: [whatwg/dom] Prohibit ServiceWorker event handler update after the initialization. (PR #1161) (Tuesday, 14 March)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Tuesday, 14 March)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Monday, 13 March)
- Re: [whatwg/url] IPv4 parser "invents" a valid ip from doi prefix; is this / should this be correct behaviour? (Issue #761) (Monday, 13 March)
- Re: [whatwg/url] IPv4 parser "invents" a valid ip from doi prefix; is this / should this be correct behaviour? (Issue #761) (Monday, 13 March)
- Re: [whatwg/url] IPv4 parser "invents" a valid ip from doi prefix; is this / should this be correct behaviour? (Issue #761) (Monday, 13 March)
- Re: [whatwg/url] More IDNA roundtrippability issues (Issue #760) (Friday, 10 March)
- Re: [whatwg/url] javascript: URL parsing (#307) (Friday, 10 March)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Friday, 10 March)
- Re: [w3ctag/design-reviews] requestStorageAccessForOrigin (Issue #808) (Thursday, 9 March)
- Re: [w3ctag/design-reviews] requestStorageAccessForOrigin (Issue #808) (Thursday, 9 March)
- Re: [whatwg/url] Double-encoded IDNA labels don't roundtrip (#603) (Thursday, 9 March)
- Re: [whatwg/dom] Rename Range's 'start' and 'end' to 'range start' and 'range end'. (PR #1168) (Wednesday, 8 March)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Wednesday, 8 March)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Wednesday, 8 March)
- Re: [w3c/FileAPI] Proposal: Add a crossOrigin option to Blob (Issue #192) (Tuesday, 7 March)
- Re: [whatwg/dom] Rename Range's 'start' and 'end' to 'range start' and 'range end'. (PR #1168) (Monday, 6 March)
- Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to section 5. (PR #1616) (Monday, 6 March)
- Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to section 5. (PR #1616) (Monday, 6 March)
- Re: [whatwg/url] Allow queries in relative references when the baseURL has an opaque path (Issue #668) (Monday, 6 March)
- Re: [whatwg/url] Allow queries in relative references when the baseURL has an opaque path (Issue #668) (Monday, 6 March)
- Re: [whatwg/fetch] Allow pre-allocating array buffer for .arrayBuffer(), to allow zero-copy loads (Issue #1615) (Monday, 6 March)
- Re: [whatwg/url] [proposal] Enhanced the ability for multiple same-name-parameters to the URLSearchParams: .has() and .delete() (Issue #680) (Monday, 6 March)
- Re: [whatwg/url] [proposal] Enhanced the ability for multiple same-name-parameters to the URLSearchParams: .has() and .delete() (Issue #680) (Monday, 6 March)
- Re: [whatwg/url] [proposal] Enhanced the ability for multiple same-name-parameters to the URLSearchParams: .has() and .delete() (Issue #680) (Monday, 6 March)
- Re: [whatwg/url] Broken references in URL Standard (Issue #759) (Monday, 6 March)
- Re: [whatwg/url] Broken references in URL Standard (Issue #759) (Monday, 6 March)
- Re: [whatwg/url] URL.canParse() (Issue #713) (Monday, 6 March)
- Re: [whatwg/url] Expose a URLHost class to JavaScript (#288) (Monday, 6 March)
- Re: [whatwg/url] Allow queries in relative references when the baseURL has an opaque path (Issue #668) (Monday, 6 March)
- Re: [whatwg/url] Proposal: file: URL separator deduplication (#552) (Monday, 6 March)
- Re: [whatwg/url] URLSearchParams.appendAll(iterable) (#461) (Monday, 6 March)
- Re: [whatwg/url] javascript: URL parsing (#307) (Sunday, 5 March)
- Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to Request class (PR #1612) (Friday, 3 March)
- Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to Request class (PR #1612) (Friday, 3 March)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152) (Friday, 3 March)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152) (Friday, 3 March)
- Re: [WICG/webcomponents] Selection APIs for Shadow DOM (#79) (Thursday, 2 March)
- Re: [whatwg/fetch] Give guidance on when flags should be set, for other spec authors (#186) (Thursday, 2 March)
- Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Thursday, 2 March)
- Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Thursday, 2 March)
- Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585) (Thursday, 2 March)
- Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to Request class (PR #1612) (Thursday, 2 March)
- Re: [whatwg/url] Broken references in URL Standard (Issue #759) (Wednesday, 1 March)
ANTOGUTAR
Ari Chivukula
Arthur Hemery
Austin Sullivan
Ayu Ishii
Ben Delarre
bigopon
Botond Ballo
Bruce B. Anderson
btuhey42
Caleb Williams
Caridy Patiño
Carlos IL
Carlos Lopez
carmona8351516
Chris Rebert
Chris Thompson
CK_CatTeaHua
Dan Clark
Dan Robertson
- Re: [w3c/uievents] Wheel event groups are not defined (Issue #338) (Wednesday, 29 March)
- Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to data URLs (PR #1619) (Thursday, 23 March)
- Re: [whatwg/fetch] Correct blob: URL range requests (PR #1621) (Wednesday, 22 March)
- Re: [w3c/uievents] Specify wheel event groups (PR #344) (Friday, 17 March)
- Re: [w3c/uievents] Specify wheel event groups (PR #344) (Thursday, 16 March)
- [w3c/uievents] Specify wheel event groups (PR #344) (Thursday, 16 March)
- Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to data URLs (PR #1619) (Wednesday, 15 March)
- [whatwg/fetch] Editorial: add <div algorithm> wrappers to data URLs (PR #1619) (Wednesday, 15 March)
- [whatwg/fetch] Editorial: add <div algorithm> wrappers to section 5. (PR #1616) (Monday, 6 March)
- Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to Request class (PR #1612) (Friday, 3 March)
- Re: [whatwg/fetch] Editorial: add <div algorithm> wrappers to Request class (PR #1612) (Friday, 3 March)
Daniel Appelquist
- Re: [w3ctag/design-reviews] Background Blur API (Issue #826) (Wednesday, 29 March)
- Re: [w3ctag/design-reviews] Web Content Accessibility Guidelines (WCAG) 2.2 2023-01-30 > 2023-02-24 (Issue #811) (Wednesday, 29 March)
- Re: [w3ctag/design-reviews] Web Content Accessibility Guidelines (WCAG) 2.2 2023-01-30 > 2023-02-24 (Issue #811) (Wednesday, 29 March)
- Re: [w3ctag/design-reviews] Background Blur API (Issue #826) (Tuesday, 28 March)
- Re: [w3ctag/design-reviews] Multi-Screen Window Placement on the Web - Initiating Multi-Screen Experiences (Issue #767) (Thursday, 23 March)
- Re: [w3ctag/design-reviews] Multi-Screen Window Placement on the Web - Initiating Multi-Screen Experiences (Issue #767) (Thursday, 23 March)
- Re: [w3ctag/design-reviews] COOP: restrict-properties early review (Issue #760) (Thursday, 23 March)
- Re: [w3ctag/design-reviews] MiniApp Lifecycle (#523) (Tuesday, 21 March)
- Re: [w3ctag/design-reviews] The Popover API (previously Popup) (Issue #743) (Monday, 20 March)
- Re: [w3ctag/design-reviews] The Popover API (previously Popup) (Issue #743) (Monday, 20 March)
- Re: [w3ctag/design-reviews] The Popover API (previously Popup) (Issue #743) (Monday, 20 March)
- Re: [w3ctag/design-reviews] Moving local files with the File System Access API (Issue #805) (Tuesday, 14 March)
- Re: [w3ctag/design-reviews] Moving local files with the File System Access API (Issue #805) (Tuesday, 14 March)
- Re: [w3ctag/design-reviews] Moving local files with the File System Access API (Issue #805) (Tuesday, 14 March)
- Re: [w3ctag/design-reviews] Moving local files with the File System Access API (Issue #805) (Tuesday, 14 March)
- Re: [w3ctag/design-reviews] Gamepad Extensions API touch input (Issue #799) (Tuesday, 14 March)
- Re: [w3ctag/design-reviews] Gamepad Extensions API touch input (Issue #799) (Tuesday, 14 March)
- Re: [w3ctag/design-reviews] Web Content Accessibility Guidelines (WCAG) 2.2 2023-01-30 > 2023-02-24 (Issue #811) (Monday, 13 March)
- Re: [w3ctag/design-reviews] text-wrap: balance (Issue #822) (Monday, 13 March)
- Re: [w3ctag/design-reviews] Early Design Review: Pending Beacon API (Issue #776) (Monday, 13 March)
- Re: [w3ctag/design-reviews] requestStorageAccessForOrigin (Issue #808) (Thursday, 9 March)
- Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798) (Tuesday, 7 March)
- Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798) (Tuesday, 7 March)
Daniel Murphy
- Re: [w3c/manifest] Add scope conflict section about same-origin and nested scopes (PR #1034) (Thursday, 30 March)
- Re: [w3c/manifest] Add scope conflict section about same-origin and nested scopes (PR #1034) (Wednesday, 29 March)
- Re: [w3c/manifest] Allow manifest processing to be invoked without going through an HTML document (PR #1069) (Wednesday, 29 March)
- Re: [w3c/manifest] Rewrote Proprietary manifest members section to discourage vendor prefixing. (PR #1073) (Wednesday, 29 March)
- Re: [w3c/manifest] Rewrote Proprietary manifest members section to discourage vendor prefixing. (PR #1073) (Wednesday, 29 March)
- Re: [w3c/manifest] Add scope conflict section about same-origin and nested scopes (PR #1034) (Thursday, 2 March)
- Re: [w3c/manifest] Add scope conflict section about same-origin and nested scopes (PR #1034) (Thursday, 2 March)
- Re: [w3c/manifest] Add scope conflict section about same-origin and nested scopes (PR #1034) (Thursday, 2 March)
- Re: [w3c/manifest] Add scope conflict section about same-origin and nested scopes (PR #1034) (Thursday, 2 March)
- Re: [w3c/manifest] Add scope conflict section about same-origin and nested scopes (PR #1034) (Thursday, 2 March)
- Re: [w3c/manifest] Add scope conflict section about same-origin and nested scopes (PR #1034) (Thursday, 2 March)
- Re: [w3c/manifest] Add scope conflict section about same-origin and nested scopes (PR #1034) (Thursday, 2 March)
Danny Engelman
Darien Maillet Valentine
- Re: [whatwg/url] URLSearchParams append/set: variadic values argument? (Issue #762) (Monday, 20 March)
- Re: [whatwg/url] URLSearchParams append/set: variadic values argument? (Issue #762) (Saturday, 18 March)
- [whatwg/webidl] Purpose of call-a-user-object’s-operation’s opName parameter (Issue #1282) (Friday, 17 March)
- Re: [whatwg/dom] Do not dispatch a trusted event when target and reletedTarget are identical (#336) (Tuesday, 14 March)
- Re: [whatwg/url] URLSearchParams.appendAll(iterable) (#461) (Tuesday, 14 March)
- [whatwg/url] URLSearchParams append/set: variadic values argument? (Issue #762) (Tuesday, 14 March)
- Re: [whatwg/dom] Do not dispatch a trusted event when target and reletedTarget are identical (#336) (Tuesday, 14 March)
- Re: [whatwg/dom] Declarative Shadow DOM (#831) (Friday, 10 March)
- Re: [whatwg/dom] Declarative Shadow DOM (#831) (Friday, 10 March)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Friday, 10 March)
- Re: [whatwg/webidl] Seeking clarification on whether unioning promises and callbacks is allowed (Issue #1278) (Thursday, 9 March)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986) (Wednesday, 8 March)
- Re: [WICG/webcomponents] [scoped-registries] Interaction with HTML element's overridden constructor steps (Issue #969) (Tuesday, 7 March)
- Re: [WICG/webcomponents] [scoped-registries] Interaction with HTML element's overridden constructor steps (Issue #969) (Tuesday, 7 March)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152) (Friday, 3 March)
- Re: [whatwg/dom] Add AbortSignal.any() (PR #1152) (Friday, 3 March)
darkly2657
DarkWiiPlayer
Dave Batiste
Delan Azabani
Domenic Denicola
- Re: [whatwg/streams] Add an abstraction to pull from buffer into ReadableStream (PR #1263) (Friday, 31 March)
- Re: [whatwg/streams] Add an abstraction to pull from buffer into ReadableStream (PR #1263) (Friday, 31 March)
- Re: [whatwg/dom] Don't store is value when it won't be useful (#661) (Wednesday, 29 March)
- Re: [whatwg/dom] Don't store is value when it won't be useful (#661) (Wednesday, 29 March)
- Re: [whatwg/webidl] Clarify #named-properties-object (PR #1285) (Wednesday, 29 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 29 March)
- Re: [whatwg/webidl] Clarify #named-properties-object (PR #1285) (Wednesday, 29 March)
- Re: [whatwg/streams] Could a byte stream read directly into and out of a SAB (w/o transfer)? (#757) (Monday, 27 March)
- Re: [whatwg/fetch] Response static methods use null this value to specify the realm (Issue #1603) (Friday, 24 March)
- Re: [whatwg/fetch] Make response body streams readable byte streams (#1246) (Friday, 24 March)
- Re: [whatwg/fetch] Make response body streams readable byte streams (#1246) (Friday, 24 March)
- Re: [whatwg/fetch] Use a basic filtered response for redirect navigations (PR #1618) (Friday, 24 March)
- Re: [whatwg/fetch] Use a basic filtered response for redirect navigations (PR #1618) (Friday, 24 March)
- Re: [whatwg/fetch] Use a basic filtered response for redirect navigations (PR #1618) (Friday, 24 March)
- Re: [whatwg/streams] "If flushPromise was rejected with reason r, the..." (Issue #1262) (Friday, 24 March)
- Re: [whatwg/url] Let [=UTF-8 percent-encode=] take an extra optional boolean parameter spaceAsPlus (default false) (Issue #765) (Thursday, 23 March)
- Re: [whatwg/url] Let [=UTF-8 percent-encode=] take an extra optional boolean parameter spaceAsPlus (default false) (Issue #765) (Thursday, 23 March)
- Re: [whatwg/webidl] Purpose of call-a-user-object’s-operation’s opName parameter (Issue #1282) (Sunday, 19 March)
- Re: [whatwg/dom] Rename Range's 'start' and 'end' to 'range start' and 'range end'. (PR #1168) (Thursday, 9 March)
- [whatwg/fetch] Use a basic filtered response for redirect navigations (PR #1618) (Wednesday, 8 March)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Wednesday, 8 March)
- Re: [whatwg/dom] Rename Range's 'start' and 'end' to 'range start' and 'range end'. (PR #1168) (Wednesday, 8 March)
- Re: [whatwg/dom] Rename Range's 'start' and 'end' to 'range start' and 'range end'. (PR #1168) (Wednesday, 8 March)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986) (Wednesday, 1 March)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Wednesday, 1 March)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Wednesday, 1 March)
Dominic Farolino
donatocayurin
dontcallmedom-bot
Douglas Parker
dSalieri
Edgar Chen
- Re: [whatwg/webidl] Allow static operations with the same names as default operations in Maplike/Setlike/Iterable/AsyncIterable (PR #1281) (Thursday, 16 March)
- Re: [whatwg/webidl] Allow static operations with the same names as default operations in Maplike/Setlike/Iterable/AsyncIterable (PR #1281) (Thursday, 16 March)
- Re: [whatwg/webidl] Allow static operations with the same names as default operations in Maplike/Setlike/Iterable/AsyncIterable (PR #1281) (Thursday, 16 March)
- [whatwg/webidl] Allow static operations with the same names as default operations in Maplike/Setlike/Iterable/AsyncIterable (PR #1281) (Thursday, 16 March)
- Re: [whatwg/webidl] Should a read–write maplike/setlike interface be allowed having static operations with same name as set methods, e.g. clear, delete ... (Issue #1280) (Thursday, 16 March)
- [whatwg/webidl] Should a read–write maplike/setlike interface be allowed having static operations with same name as set methods, e.g. clear, delete ... (Issue #1280) (Thursday, 16 March)
Erik Taubeneck
ESTHERTERSEN
Evan Stade
FAIZUAN55
fantasai
fergald
flavi1
Frank Topel
François Beaufort
François Daoust
fredrikryden
Fuqiao Xue
Garrett Walker
Gary Kacmarcik
Guiccice
Gustav Corpas
Géry Ogam
Hadley Beeman
hober
Jacob Smith
Jake Archibald
- Re: [w3c/ServiceWorker] Skip service worker no-op fetch handler (Issue #1671) (Wednesday, 22 March)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1674) (Wednesday, 22 March)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1674) (Wednesday, 22 March)
- Re: [whatwg/dom] Export event listener callback (PR #1174) (Wednesday, 22 March)
- [whatwg/dom] Export event listener callback (PR #1174) (Wednesday, 22 March)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1674) (Wednesday, 22 March)
- Re: [whatwg/dom] Export terms needed for ServiceWorker/1674 (PR #1170) (Wednesday, 22 March)
- Re: [whatwg/dom] Export terms needed for ServiceWorker/1674 (PR #1170) (Wednesday, 22 March)
- Re: [whatwg/dom] Export terms needed for ServiceWorker/1674 (PR #1170) (Wednesday, 22 March)
- Re: [whatwg/dom] Export terms needed for ServiceWorker/1674 (PR #1170) (Tuesday, 21 March)
- Re: [whatwg/dom] Export terms needed for ServiceWorker/1674 (PR #1170) (Monday, 20 March)
- Re: [whatwg/dom] Export terms needed for ServiceWorker/1674 (PR #1170) (Monday, 20 March)
- Re: [whatwg/dom] Export terms needed for ServiceWorker/1674 (PR #1170) (Monday, 20 March)
- Re: [whatwg/dom] Export terms needed for ServiceWorker/1674 (PR #1170) (Monday, 20 March)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1674) (Monday, 20 March)
- [whatwg/dom] Export terms needed for ServiceWorker/1671 (PR #1170) (Monday, 20 March)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1674) (Monday, 20 March)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Monday, 20 March)
- [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1674) (Monday, 20 March)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Monday, 20 March)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Monday, 20 March)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Monday, 20 March)
- Re: [whatwg/dom] Export "event listener/type". (PR #1169) (Friday, 17 March)
- Re: [whatwg/dom] Export "event listener/type". (PR #1169) (Friday, 17 March)
- Re: [whatwg/dom] Prohibit ServiceWorker event handler update after the initialization. (PR #1161) (Thursday, 16 March)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Tuesday, 14 March)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Monday, 13 March)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Tuesday, 7 March)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Monday, 6 March)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Monday, 6 March)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Wednesday, 1 March)
James M Snell
Jeffrey Yasskin
Jen Simmons
Jeremy Roman
Jim (JR)
Jim Manico
jimmyfrasche
Joey Arhar
- Re: [w3ctag/design-reviews] Display and content-visibility animations (Issue #824) (Wednesday, 29 March)
- Re: [w3ctag/design-reviews] Transitions on specified discrete properties (Issue #825) (Wednesday, 29 March)
- Re: [w3ctag/design-reviews] Transitions on specified discrete properties (Issue #825) (Wednesday, 29 March)
- Re: [w3ctag/design-reviews] Display and content-visibility animations (Issue #824) (Wednesday, 29 March)
- [w3ctag/design-reviews] Entry and Exit Animations (Issue #829) (Wednesday, 29 March)
- Re: [w3ctag/design-reviews] Transitions on specified discrete properties (Issue #825) (Wednesday, 29 March)
- Re: [whatwg/fullscreen] Hide popovers when making an element fullscreen (PR #204) (Saturday, 25 March)
- Re: [whatwg/fullscreen] Hide popovers when making an element fullscreen (PR #204) (Saturday, 25 March)
- Re: [whatwg/fullscreen] Hide pop-ups when making an element fullscreen (PR #204) (Saturday, 25 March)
- Re: [whatwg/fullscreen] Hide pop-ups when making an element fullscreen (PR #204) (Saturday, 25 March)
- [whatwg/dom] Handle attribute changes after changing attribute (PR #1176) (Saturday, 25 March)
- [w3ctag/design-reviews] Display and content-visibility animations (Issue #824) (Wednesday, 15 March)
- [w3ctag/design-reviews] Transitions on specified discrete properties (Issue #825) (Wednesday, 15 March)
Johann Hofmann
Johannes Wilm
Jonathan Hao
Jonathan Leitschuh
Jose Vargas
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Wednesday, 15 March)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Wednesday, 8 March)
- Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) (Wednesday, 8 March)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Monday, 6 March)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Monday, 6 March)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Monday, 6 March)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Monday, 6 March)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Monday, 6 March)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Monday, 6 March)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Monday, 6 March)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Monday, 6 March)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Monday, 6 March)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Monday, 6 March)
Josh Karlin
Joshua Bell
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417) (Friday, 24 March)
- Re: [w3c/IndexedDB] Specifying "indexedDB" storage bottle deletion when data is evicted by quota (Issue #400) (Wednesday, 22 March)
- Re: [w3c/IndexedDB] Main (PR #399) (Wednesday, 22 March)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417) (Thursday, 9 March)
- Re: [w3c/IndexedDB] [WIP] Initial algorithms / methods for putAll (#343) (Friday, 3 March)
- Re: [w3c/IndexedDB] Normalize negative zero (PR #386) (Friday, 3 March)
- Re: [w3c/IndexedDB] Initial sketch of manual commit flag for transactions (#331) (Friday, 3 March)
- Re: [w3c/IndexedDB] Speculative getAllEntries() spec (#280) (Friday, 3 March)
- Re: [w3c/IndexedDB] Define Indexed DB as a storage endpoint, use hooks (#334) (Friday, 3 March)
- Re: [w3c/IndexedDB] Sketch out IDBCursor.close() (#302) (Friday, 3 March)
- Re: [w3c/IndexedDB] Rename 'array key' to 'composite key'. For #360 (PR #392) (Friday, 3 March)
- Re: [w3c/IndexedDB] Editorial: Remove redundant ticks from <dfn event> text (PR #398) (Friday, 3 March)
- [w3c/IndexedDB] Editorial: Remove redundant ticks from <dfn event> text (PR #398) (Friday, 3 March)
- Re: [w3c/IndexedDB] [WIP] Initial algorithms / methods for putAll (#343) (Friday, 3 March)
- Re: [w3c/IndexedDB] Normalize negative zero (PR #386) (Friday, 3 March)
- Re: [w3c/IndexedDB] Initial sketch of manual commit flag for transactions (#331) (Friday, 3 March)
- Re: [w3c/IndexedDB] Speculative getAllEntries() spec (#280) (Friday, 3 March)
- Re: [w3c/IndexedDB] Define Indexed DB as a storage endpoint, use hooks (#334) (Friday, 3 March)
- Re: [w3c/IndexedDB] Sketch out IDBCursor.close() (#302) (Friday, 3 March)
- Re: [w3c/IndexedDB] Rename 'array key' to 'composite key'. For #360 (PR #392) (Friday, 3 March)
- Re: [w3c/IndexedDB] Editorial: Replace markup <a type for> syntax with markdown {{...!!type}} (PR #397) (Friday, 3 March)
- Re: [w3c/IndexedDB] Editorial: Replace markup <a type for> syntax with markdown {{...!!type}} (PR #397) (Friday, 3 March)
- [w3c/IndexedDB] Editorial: Replace markup <a type for> syntax with markdown {{...!!type}} (PR #397) (Friday, 3 March)
- Re: [w3c/IndexedDB] [WIP] Initial algorithms / methods for putAll (#343) (Friday, 3 March)
- Re: [w3c/IndexedDB] Speculative getAllEntries() spec (#280) (Thursday, 2 March)
- Re: [w3c/IndexedDB] Rename 'array key' to 'composite key'. For #360 (PR #392) (Thursday, 2 March)
JR Conlin
Jun
Justin Fagnani
Kagami Sascha Rosylight
Karl
Karl Dubost
Keith Cirkel
Kevin McNee
Koji Ishii
Lea Verou
- Re: [w3ctag/design-reviews] Transitions on specified discrete properties (Issue #825) (Wednesday, 29 March)
- Re: [w3ctag/design-reviews] text-wrap: balance (Issue #822) (Monday, 20 March)
- Re: [w3ctag/design-reviews] text-wrap: balance (Issue #822) (Monday, 20 March)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986) (Thursday, 16 March)
- Re: [w3ctag/design-reviews] Native File System API (#390) (Wednesday, 15 March)
- Re: [w3ctag/design-reviews] Native File System API (#390) (Wednesday, 15 March)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986) (Wednesday, 8 March)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986) (Tuesday, 7 March)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986) (Friday, 3 March)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986) (Thursday, 2 March)
- Re: [w3ctag/design-reviews] Design Review: Speculation Rules (Prefetch) (Issue #721) (Wednesday, 1 March)
- Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986) (Wednesday, 1 March)
Leszek Swirski
Liam Murphy
Luca Casonato
Lukasz Olejnik
Luuk Lamers
Léonie Watson
mangelozzi
Marcos Cáceres
- Re: [w3c/manifest] Don't recommend extensions use vendor prefixing (Issue #1072) (Wednesday, 29 March)
- Re: [w3c/manifest] Rewrote Proprietary manifest members section to discourage vendor prefixing. (PR #1073) (Wednesday, 29 March)
- Re: [w3c/manifest] Rewrote Proprietary manifest members section to discourage vendor prefixing. (PR #1073) (Wednesday, 29 March)
- Re: [w3c/manifest] Rewrote Proprietary manifest members section to discourage vendor prefixing. (PR #1073) (Wednesday, 29 March)
- Re: [w3c/manifest] Rewrote Proprietary manifest members section to discourage vendor prefixing. (PR #1073) (Wednesday, 29 March)
- Re: [w3c/manifest] Rewrote Proprietary manifest members section to discourage vendor prefixing. (PR #1073) (Wednesday, 29 March)
- Re: [w3c/manifest] Rewrote Proprietary manifest members section to discourage vendor prefixing. (PR #1073) (Wednesday, 29 March)
- Re: [w3c/permissions] add accessibility considerations (PR #412) (Friday, 17 March)
- Re: [w3c/permissions] add accessibility considerations (PR #412) (Friday, 17 March)
- Re: [w3c/gamepad] Move James Hollyer to former editors (PR #185) (Friday, 10 March)
- Re: [w3c/gamepad] Restrict getGamepads() to [SecureContext] (#113) (Monday, 6 March)
- Re: [whatwg/fullscreen] Removing steps on fullscreen element leave a dangling fullscreen flag (Issue #217) (Wednesday, 1 March)
Marielle Volz
Marijn Kruisselbrink
Marius
Mark Nottingham
Markus Scherer
Martin Thomson
Mason Freed
- Re: [w3c/selection-api] getComposedRange() review (Issue #161) (Friday, 31 March)
- Re: [w3ctag/design-reviews] The Popover API (previously Popup) (Issue #743) (Monday, 20 March)
- Re: [w3ctag/design-reviews] The Popover API (previously Popup) (Issue #743) (Friday, 17 March)
- Re: [w3ctag/design-reviews] The Popover API (previously Popup) (Issue #743) (Friday, 17 March)
- Re: [w3c/selection-api] getComposedRange() review (Issue #161) (Wednesday, 15 March)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Wednesday, 15 March)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Wednesday, 15 March)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Tuesday, 14 March)
- Re: [whatwg/fullscreen] Consider removing the containing block adjustment for popovers (Issue #218) (Tuesday, 14 March)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Wednesday, 8 March)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Monday, 6 March)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Monday, 6 March)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Monday, 6 March)
- Re: [w3c/selection-api] getComposedRange() review (Issue #161) (Friday, 3 March)
- Re: [WICG/webcomponents] Selection APIs for Shadow DOM (#79) (Thursday, 2 March)
- Re: [w3c/selection-api] getComposedRange() review (Issue #161) (Thursday, 2 March)
Matt Giuca
Matt Menke
Matt Reynolds
Matthew Phillips
meacer
megangardner
Michael Turkeev
Michael Wasserman
Mike West
Mikhail Podgurskiy
Miniontoby
Miriam Suzanne
mreichhoff
MSFTKonnor
Murat Çorlu
Naiyer Asif
Nicholas Gulachek
Nicolas Gilbert
Noam Rosenthal
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 29 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 29 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 29 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 29 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 29 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 29 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 29 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 29 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 29 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 29 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 29 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 29 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Sunday, 26 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Sunday, 26 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Sunday, 26 March)
- Re: [whatwg/fetch] Define preconnect and dns-prefetch with CSP (PR #1620) (Monday, 20 March)
- [whatwg/fetch] Define preconnect and dns-prefetch with CSP (PR #1620) (Monday, 20 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Thursday, 16 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Thursday, 16 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 15 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 15 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 15 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 15 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 15 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 15 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Thursday, 9 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 8 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 8 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 8 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 8 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 8 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 8 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 8 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 8 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 8 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 8 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 8 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Wednesday, 8 March)
- [whatwg/fetch] WIP: Public subresource check (PR #1617) (Tuesday, 7 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Sunday, 5 March)
- Re: [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Sunday, 5 March)
- [whatwg/fetch] Editorial: Reword how-to section to explain how to use callbacks & controller (PR #1614) (Sunday, 5 March)
Nolan Lawson
omidiran52
Paul Jensen
Pedro Lopez
Peter Linss
Peter Van der Beken
Philip Jägenstedt
Pierre Ossman (Work account)
Pramualsup22
Qing An
qingxinwu
Rakina Zata Amni
Randall Leeds
Reachmanager
rektide
Rijubrata Bhaumik
Rik Cabanier
Rimas Misevičius
Robert Flack
Ronald Zielaznicki
Rossen Atanassov
RS
Ryosuke Niwa
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Thursday, 23 March)
- Re: [WICG/webcomponents] [dom-parts] Declarative API for defining DOM parts (Issue #990) (Tuesday, 21 March)
- Re: [WICG/webcomponents] [dom-parts] Declarative API for defining DOM parts (Issue #990) (Tuesday, 21 March)
- Re: [WICG/webcomponents] [dom-parts] Remove `.value` and `.commit()`, add `replaceChildren` (Issue #991) (Tuesday, 21 March)
- Re: [w3c/selection-api] getComposedRange() review (Issue #161) (Tuesday, 21 March)
- Re: [WICG/webcomponents] [dom-parts] Remove `.value` and `.commit()`, add `replaceChildren` (Issue #991) (Tuesday, 21 March)
- Re: [WICG/webcomponents] [dom-parts] Declarative API for defining DOM parts (Issue #990) (Tuesday, 21 March)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Tuesday, 21 March)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Thursday, 16 March)
- Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978) (Friday, 10 March)
- Re: [w3c/selection-api] getComposedRange() review (Issue #161) (Tuesday, 7 March)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Monday, 6 March)
- Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809) (Monday, 6 March)
- Re: [w3c/selection-api] getComposedRange() review (Issue #161) (Thursday, 2 March)
sam goto
Sanket Joshi
- Re: [whatwg/dom] [Range] Should the DOM range spec include an i18n warning? (Issue #1177) (Tuesday, 28 March)
- Re: [whatwg/dom] [Range] Should the DOM range spec include an i18n warning? (Issue #1177) (Tuesday, 28 March)
- [whatwg/dom] [Range] Should the DOM range spec include an i18n warning? (Issue #1177) (Monday, 27 March)
- Re: [w3c/editing] Add unsanitized html read/write doc. (PR #420) (Thursday, 23 March)
- Re: [w3c/editing] Add unsanitized html read/write doc. (PR #420) (Thursday, 23 March)
- Re: [w3c/editing] Add unsanitized html read/write doc. (PR #420) (Tuesday, 21 March)
- Re: [whatwg/webidl] Seeking clarification on whether unioning promises and callbacks is allowed (Issue #1278) (Thursday, 9 March)
- Re: [whatwg/webidl] Seeking clarification on whether unioning promises and callbacks is allowed (Issue #1278) (Thursday, 9 March)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417) (Thursday, 9 March)
- [whatwg/webidl] Seeking clarification on whether unioning promises and callbacks is allowed (Issue #1278) (Thursday, 9 March)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417) (Friday, 3 March)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417) (Friday, 3 March)
Sasha Firsov
Scott Haseley
Sean Feng
Sean4572435243
Shivan Kaul Sahib
Simon Pieters
smaug----
snek
snianu
- Re: [w3c/editing] Additional documents for unsanitized HTML read/write (PR #422) (Wednesday, 29 March)
- Re: [w3c/editing] Additional documents for unsanitized HTML read/write (PR #422) (Wednesday, 29 March)
- Re: [w3c/editing] Mark the old EditContext spec as archived (PR #421) (Friday, 24 March)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417) (Friday, 24 March)
- Re: [w3c/editing] Add unsanitized html read/write doc. (PR #420) (Tuesday, 21 March)
- Re: [w3c/editing] Add unsanitized html read/write doc. (PR #420) (Tuesday, 21 March)
- Re: [w3c/editing] Add unsanitized html read/write doc. (PR #420) (Tuesday, 21 March)
- Re: [w3c/editing] Add unsanitized html read/write doc. (PR #420) (Tuesday, 21 March)
- Re: [w3c/editing] Add unsanitized html read/write doc. (PR #420) (Tuesday, 21 March)
- [w3c/editing] Add unsanitized html read/write doc. (PR #420) (Tuesday, 21 March)
- Re: [w3c/clipboard-apis] Add clipboard IDL description. (#158) (Monday, 20 March)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417) (Friday, 10 March)
- Re: [w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417) (Thursday, 9 March)
steimelchrome
Tab Atkins Jr.
Takashi Toyoshima
Takeshi Kurosawa
TechAurelian
Tim Nguyen
Timothy Gu
Tom Wilkinson
- Re: [WICG/webcomponents] [dom-parts] Declarative API for defining DOM parts (Issue #990) (Tuesday, 21 March)
- Re: [WICG/webcomponents] [dom-parts] Declarative API for defining DOM parts (Issue #990) (Tuesday, 21 March)
- Re: [WICG/webcomponents] [dom-parts] Remove `.value` and `.commit()`, add `replaceChildren` (Issue #991) (Tuesday, 21 March)
- Re: [WICG/webcomponents] [dom-parts] Declarative API for defining DOM parts (Issue #990) (Tuesday, 21 March)
- Re: [WICG/webcomponents] [dom-parts] Remove `.value` and `.commit()`, add `replaceChildren` (Issue #991) (Tuesday, 21 March)
- [WICG/webcomponents] [dom-parts] Browser updating parts list from `getParts()` (Issue #993) (Tuesday, 21 March)
- [WICG/webcomponents] [dom-parts] Tree structure of parts in the DOM (Issue #992) (Tuesday, 21 March)
- [WICG/webcomponents] [dom-parts] Remove `.value` and `.commit()`, add `replaceChildren` (Issue #991) (Tuesday, 21 March)
- [WICG/webcomponents] [dom-parts] Declarative API for defining DOM parts (Issue #990) (Tuesday, 21 March)
trawn3333
Valentin Gosu
Varun Seth
Vincent Scheib
Wendy Reid
Wenson Hsieh
Wesley Luyten
Westbrook Johnson
Woodpile37
Xiaocheng Hu
Xiaoqian Wu
Yoshisato Yanagisawa
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Monday, 20 March)
- Re: [whatwg/dom] Export "event listener/type". (PR #1169) (Sunday, 19 March)
- Re: [whatwg/dom] Export "event listener/type". (PR #1169) (Sunday, 19 March)
- Re: [whatwg/dom] Export "event listener/type". (PR #1169) (Friday, 17 March)
- [whatwg/dom] Export "event listener/type". (PR #1169) (Friday, 17 March)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Friday, 17 March)
- Re: [whatwg/dom] Prohibit ServiceWorker event handler update after the initialization. (PR #1161) (Thursday, 16 March)
- Re: [whatwg/dom] Prohibit ServiceWorker event handler update after the initialization. (PR #1161) (Tuesday, 14 March)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Tuesday, 14 March)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Friday, 10 March)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Tuesday, 7 March)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Tuesday, 7 March)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Tuesday, 7 March)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Wednesday, 1 March)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Wednesday, 1 March)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Wednesday, 1 March)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Wednesday, 1 March)
- Re: [w3c/ServiceWorker] Skip executing fetch handlers if it is no-op. (PR #1672) (Wednesday, 1 March)
Yves Lafon
zeenza123
Last message date: Friday, 31 March 2023 22:57:10 UTC