Abin K Paul
abod1944
Adam Rice
Addison Phillips
alancutter
Alexey Rodionov
Amy Guy
- Re: [w3ctag/design-reviews] SameParty cookie attribute (#595) (Tuesday, 26 July)
- Re: [w3ctag/design-reviews] SameParty cookie attribute (#595) (Tuesday, 26 July)
- Re: [w3ctag/design-reviews] File Handling (#371) (Tuesday, 26 July)
- Re: [w3ctag/design-reviews] File Handling (#371) (Tuesday, 26 July)
- Re: [w3ctag/design-reviews] Web of Things (WoT) Architecture 1.1 (Issue #736) (Monday, 25 July)
- Re: [w3ctag/design-reviews] Web of Things (WoT) Architecture 1.1 (Issue #736) (Monday, 25 July)
- Re: [w3ctag/design-reviews] Web of Things (WoT) Discovery (Issue #733) (Monday, 25 July)
- Re: [w3ctag/design-reviews] Web of Things (WoT) Discovery (Issue #733) (Monday, 25 July)
- Re: [w3ctag/design-reviews] Web of Things (WoT) Architecture 1.1 (Issue #736) (Monday, 25 July)
- Re: [w3ctag/design-reviews] Web of Things (WoT) Architecture 1.1 (Issue #736) (Monday, 25 July)
- Re: [w3ctag/design-reviews] WebXR Raw Camera Access API (#652) (Tuesday, 12 July)
- Re: [w3ctag/design-reviews] FedCM (was WebID) (Issue #718) (Tuesday, 12 July)
- Re: [w3ctag/design-reviews] FedCM (was WebID) (Issue #718) (Monday, 11 July)
- Re: [w3ctag/design-reviews] FedCM (was WebID) (Issue #718) (Monday, 11 July)
Andrew Sutherland
Anne van Kesteren
- Re: [whatwg/fetch] blob: fetch of slice() without valid content type yields unexpected results (Issue #1464) (Thursday, 28 July)
- Re: [whatwg/fetch] Add response status to response body info (PR #1468) (Thursday, 28 July)
- Re: [whatwg/fetch] Add support for parsing a suffix byte range spec (PR #1454) (Thursday, 28 July)
- Re: [whatwg/fetch] Add special handling of `set-cookie` to Headers (PR #1346) (Thursday, 28 July)
- Re: [whatwg/fetch] Add render-blocking boolean to fetch timing info (PR #1449) (Thursday, 28 July)
- Re: [whatwg/fetch] Editorial: Add 103 to note about null body Response (PR #1465) (Thursday, 28 July)
- Re: [whatwg/fetch] HTTP 101 response NOT for websockets (Issue #1397) (Thursday, 28 July)
- Re: [w3ctag/design-reviews] Review request for HTTP Status Code in Resource Timing (Issue #757) (Thursday, 28 July)
- Re: [whatwg/fetch] Editorial: Add 103 to note about null body Response (PR #1465) (Thursday, 28 July)
- Re: [whatwg/fetch] HTTP 101 response NOT for websockets (Issue #1397) (Thursday, 28 July)
- Re: [whatwg/fetch] Always send Origin header for (non HEAD/GET) CORS requests (PR #1463) (Thursday, 28 July)
- Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Wednesday, 27 July)
- Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) (Wednesday, 27 July)
- Re: [whatwg/dom] Expose `signal.reason` as `error.cause` for `AbortError` (Issue #1090) (Wednesday, 27 July)
- Re: [whatwg/dom] Expose `signal.reason` as `error.cause` for `AbortError` (Issue #1090) (Wednesday, 27 July)
- Re: [whatwg/dom] Expose `signal.reason` as `error.cause` for `AbortError` (Issue #1090) (Tuesday, 26 July)
- Re: [whatwg/dom] Expose `signal.reason` as `error.cause` for `AbortError` (Issue #1090) (Tuesday, 26 July)
- Re: [whatwg/webidl] Fix incorrect wording in `2.9. Enumerations` (PR #1173) (Monday, 25 July)
- Re: [whatwg/webidl] 2.9. Enumerations - Incorrect wording (#972) (Monday, 25 July)
- Re: [whatwg/webidl] Fix incorrect wording in `2.9. Enumerations` (PR #1173) (Monday, 25 July)
- Re: [whatwg/webidl] Fix incorrect wording in `2.9. Enumerations` (PR #1173) (Monday, 25 July)
- Re: [whatwg/dom] Expose `signal.reason` as `error.cause` for `AbortError` (Issue #1090) (Sunday, 24 July)
- Re: [WICG/webcomponents] Template/part proposals - Naming for DOM Parts API (#902) (Friday, 22 July)
- Re: [whatwg/dom] Does `MutationObserver` `attributeFilter` accept itorators? (Issue #1092) (Friday, 22 July)
- Re: [whatwg/dom] Add a fully active check for EventTarget in event listener inner invoke (PR #1085) (Friday, 22 July)
- Re: [whatwg/dom] Add onabort definition and add onslotchange (#785) (Friday, 22 July)
- Re: [whatwg/dom] Expose `signal.reason` as `error.cause` for `AbortError` (Issue #1090) (Friday, 22 July)
- Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343) (Friday, 22 July)
- Re: [whatwg/fetch] Fetch body streams are not full duplex (#1254) (Friday, 1 July)
- Re: [whatwg/fetch] Streaming upload (Issue #1438) (Friday, 1 July)
- Re: [whatwg/fetch] Introduce RequestInit.duplex (PR #1457) (Friday, 1 July)
Arthur Hemery
Arthur Sonzogni
Austin Sullivan
Ayşenur BURAK
bashi
Ben Kelly
Bradley Needham
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168) (Monday, 25 July)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168) (Monday, 25 July)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168) (Monday, 25 July)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168) (Monday, 25 July)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168) (Monday, 25 July)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168) (Monday, 25 July)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168) (Monday, 25 July)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168) (Monday, 25 July)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168) (Monday, 25 July)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168) (Monday, 25 July)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168) (Monday, 25 July)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168) (Wednesday, 20 July)
- Re: [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168) (Wednesday, 20 July)
- [w3c/gamepad] Enhance Gamepad interface description for Touch (PR #168) (Tuesday, 19 July)
- [w3c/gamepad] Update subsections "Receiving inputs" and "Constructing a Gamepad" of Gamepad Interface for touch inputs. (Issue #167) (Friday, 15 July)
Brandon McConnell
Bruce B. Anderson
Caleb Williams
Caridy Patiño
Carlos Lopez
Cristal1214
Cristian12man
CSS Meeting Bot
cynthia
Dan Robertson
Daniel
Daniel Appelquist
- Re: [w3ctag/design-reviews] MiniApp Manifest (Issue #752) (Tuesday, 26 July)
- Re: [w3ctag/design-reviews] Fetch streaming upload (Issue #754) (Thursday, 21 July)
- Re: [w3ctag/design-reviews] early design review: Permissions-Policy: unload (Issue #738) (Thursday, 21 July)
- Re: [w3ctag/design-reviews] Fetch streaming upload (Issue #754) (Wednesday, 20 July)
- Re: [w3ctag/design-reviews] FYI review of Writable directory prompts for the File System Access API (Issue #749) (Wednesday, 20 July)
- Re: [w3ctag/design-reviews] Early design review: Back/forward cache NotRestoredReasons API (Issue #739) (Tuesday, 19 July)
- Re: [w3ctag/design-reviews] early design review: Permissions-Policy: unload (Issue #738) (Tuesday, 19 July)
- Re: [w3ctag/design-reviews] early design review: Permissions-Policy: unload (Issue #738) (Tuesday, 19 July)
- Re: [w3ctag/design-reviews] WebXR Raw Camera Access API (#652) (Tuesday, 19 July)
- Re: [w3ctag/design-reviews] WebXR Raw Camera Access API (#652) (Tuesday, 19 July)
- Re: [w3ctag/design-reviews] EditContext API (#416) (Tuesday, 19 July)
- Re: [w3ctag/design-reviews] FedCM (was WebID) (Issue #718) (Monday, 18 July)
- Re: [w3ctag/design-reviews] FedCM (was WebID) (Issue #718) (Monday, 18 July)
- Re: [w3ctag/design-reviews] EditContext API (#416) (Monday, 18 July)
Daniel Murphy
Dapeng(Max) Liu
Darien Maillet Valentine
Darin Adler
DarkTrick
devilblacknick
dmitriid
Domenic Denicola
- Re: [whatwg/fetch] Add render-blocking boolean to fetch timing info (PR #1449) (Friday, 29 July)
- Re: [whatwg/fetch] How to parse BigInt using Response.json() function ? (Issue #1473) (Friday, 29 July)
- Re: [whatwg/fetch] How to parse BigInt using Response.json() function ? (Issue #1473) (Friday, 29 July)
- Re: [whatwg/dom] Expose `signal.reason` as `error.cause` for `AbortError` (Issue #1090) (Tuesday, 26 July)
- Re: [w3ctag/design-reviews] import.meta.resolve() (Issue #746) (Thursday, 21 July)
- Re: [whatwg/xhr] Allow to send body within GET http requests (Issue #351) (Wednesday, 20 July)
- Re: [whatwg/xhr] Allow to send body within GET http requests (Issue #351) (Wednesday, 20 July)
- Re: [w3ctag/design-reviews] <search> HTML element (Issue #714) (Monday, 18 July)
- Re: [whatwg/webidl] New error name: OptOutError (Issue #1168) (Thursday, 14 July)
- Re: [whatwg/streams] Proposal: ReadableStream tee() backpressure (Issue #1235) (Thursday, 14 July)
- Re: [w3ctag/design-reviews] Review request for HTTP Status Code in Resource Timing (Issue #757) (Wednesday, 13 July)
- Re: [whatwg/webidl] Inconsistent enumerability on keys/values/entries and friends (#738) (Wednesday, 13 July)
- [whatwg/webidl] Make setlike/maplike generated properties enumerable (PR #1166) (Wednesday, 13 July)
- Re: [whatwg/webidl] Inconsistent enumerability on keys/values/entries and friends (#738) (Wednesday, 13 July)
- Re: [whatwg/fetch] Editorial: Use controller for navigation redirect (PR #1469) (Tuesday, 12 July)
- Re: [whatwg/fetch] Editorial: Move initiator type to other side of note (PR #1467) (Friday, 8 July)
- Re: [whatwg/fetch] Editorial: Move initiator type to other side of note (PR #1467) (Friday, 8 July)
- Re: [whatwg/webidl] Editorial: fix uses of `?` with `IfAbruptRejectPromise` (PR #1165) (Friday, 8 July)
- Re: [whatwg/webidl] Editorial: fix uses of `?` with `IfAbruptRejectPromise` (PR #1165) (Friday, 8 July)
- Re: [whatwg/streams] Proposal: ReadableStream tee() backpressure (Issue #1235) (Wednesday, 6 July)
Dominique Hazael-Massieux
- [w3c/selection-api] `selectstart` event handler needs to be exposed on `Text` (Issue #159) (Wednesday, 27 July)
- [w3c/clipboard-apis] Mark up definition of events following bikeshed conventions (PR #181) (Thursday, 7 July)
- Re: [w3c/clipboard-apis] Missing event handler IDL attributes (#74) (Thursday, 7 July)
- Re: [w3c/pointerlock] Use respec conventions for event definitions (PR #79) (Wednesday, 6 July)
- [w3c/pointerlock] Use respec conventions for event definitions (PR #79) (Wednesday, 6 July)
- Re: [w3c/gamepad] gamepad*connected handlers are only needed on Window (Issue #166) (Wednesday, 6 July)
- Re: [w3c/gamepad] gamepad*connected handlers are only needed on Window (Issue #166) (Wednesday, 6 July)
- Re: [w3c/gamepad] gamepad*connected handlers are only needed on Window (Issue #166) (Wednesday, 6 July)
- Re: [w3c/IndexedDB] Fix internal links to events (PR #388) (Tuesday, 5 July)
- [w3c/IndexedDB] Fix internal links to events (PR #388) (Tuesday, 5 July)
- [w3c/gamepad] gamepad*connected handlers are only needed on Window (Issue #166) (Tuesday, 5 July)
- [w3c/uievents] Use <thead> for table headers (PR #332) (Friday, 1 July)
Edvard
Elad Alon
Eli Grey
Elizabeth Marston
Enigma00713
Eric Covener
Erik Jensen
fergald
Frederik Creemers
Fuqiao Xue
Gary Kacmarcik
georgir
github-actions[bot]
Gérard jourdain
Hadley Beeman
Hamish Willee
Harsh Kanodiya
hober
Howard Edwards
hudsontrius
Isaac
Jake Archibald
Jakibaba
James
James Browning
James M Snell
Jeff Hykin
Jeremy Roman
Jesper Smith
Jesus Eduardo Peralta Martinez
Jiewei Qian
Jim Grisham
Joe Pea
- Re: [WICG/webcomponents] [element-internals] How to get internals in base class and subclass, without leaking it to public (Issue #962) (Sunday, 31 July)
- [WICG/webcomponents] [custom-elements] Why is `attributeChangedCallback` synchronous? (Issue #963) (Sunday, 31 July)
- Re: [WICG/webcomponents] [element-internals] How to get internals in base class and subclass, without leaking it to public (Issue #962) (Friday, 29 July)
- Re: [WICG/webcomponents] [element-internals] How to get internals in base class and subclass, without leaking it to public (Issue #962) (Friday, 29 July)
- Re: [WICG/webcomponents] Observable Properties (Issue #951) (Friday, 29 July)
- Re: [WICG/webcomponents] `customElements.upgrade` does not upgrade node subtrees cloned from `template` contents via `cloneNode` (Issue #946) (Friday, 29 July)
- Re: [WICG/webcomponents] `distributionchange` events, and `distributedNodes()` / `distributedElements()` APIs? (#940) (Friday, 29 July)
- Re: [WICG/webcomponents] CSS selector to style slots with slotted elements (#936) (Friday, 29 July)
- Re: [WICG/webcomponents] Allowing CSS combinators postfixed to the ::slotted() or :host selectors (#889) (Friday, 29 July)
- Re: [WICG/webcomponents] [scoped-registries] reduce pain by preventing logic from ever touching non-upgraded custom elements (Issue #960) (Friday, 29 July)
- Re: [WICG/webcomponents] [scoped-registries] reduce pain by preventing logic from ever touching non-upgraded custom elements (Issue #960) (Friday, 29 July)
- Re: [WICG/webcomponents] [element-internals] How to get internals in base class and subclass, without leaking it to public (Issue #962) (Friday, 29 July)
- Re: [WICG/webcomponents] [element-internals] How to get internals in base class and subclass, without leaking it to public (Issue #962) (Thursday, 28 July)
- Re: [WICG/webcomponents] [element-internals] How to get internals in base class and subclass, without leaking it to public (Issue #962) (Thursday, 28 July)
- Re: [WICG/webcomponents] [element-internals] (Issue #962) (Tuesday, 26 July)
- [WICG/webcomponents] [element-internals] (Issue #962) (Tuesday, 26 July)
- Re: [WICG/webcomponents] [templates] Ensure that template instantiation actually improves the platform (#704) (Monday, 25 July)
- Re: [WICG/webcomponents] [Template Instantiation] Layering and additional use cases (#747) (Monday, 25 July)
- [whatwg/dom] Does `attributeFilter` accept itorators? (Issue #1092) (Sunday, 10 July)
- [WICG/webcomponents] Please, PLEASE, do not allow custom elements to be upgraded in scoped `ShadowRoot` registries. (Issue #960) (Sunday, 3 July)
Johannes Wilm
Josh Karlin
JoshiPriyanka92
Joshua Bell
Julian Reschke
Justin Fagnani
Justin Levene
Kagami Sascha Rosylight
Karl
Keith Cirkel
Kellen Green
Kevin Gibbons
Klaus Frank
Kyle Simpson
Lea Verou
Leo Balter
Livia Medeiros
Lonnie Best
Louise Brett
Luca Casonato
Luca Colonnello
Lukasz Olejnik
Luke Wilde
Léonie Watson
Maliek2
mamumu123
Marcelo Ribeiro
Marcos Cáceres
- Re: [w3c/permissions] Editorial: add an introduction (PR #381) (Tuesday, 26 July)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381) (Tuesday, 26 July)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381) (Tuesday, 26 July)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381) (Tuesday, 26 July)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381) (Monday, 25 July)
- Re: [w3c/manifest] Web Manifest Overrides (Issue #1045) (Friday, 22 July)
- Re: [w3c/manifest] Web Manifest Overrides (Issue #1045) (Friday, 22 July)
- Re: [w3c/manifest] Use ordered map JSON in id processing (PR #1040) (Wednesday, 20 July)
- Re: [w3c/manifest] Use ordered map JSON in id processing (PR #1040) (Wednesday, 20 July)
- Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975) (Friday, 15 July)
- [w3c/manifest] Web Manifest Overrides (Issue #1045) (Friday, 15 July)
- Re: [w3c/manifest] Feature request: add option to disable built-in navigation gestures (Issue #1041) (Wednesday, 13 July)
- Re: [w3c/pointerlock] Tidied up document using tidy-html5 (PR #77) (Friday, 8 July)
- Re: [w3c/gamepad] gamepad*connected handlers are only needed on Window (Issue #166) (Wednesday, 6 July)
- Re: [w3c/gamepad] gamepad*connected handlers are only needed on Window (Issue #166) (Wednesday, 6 July)
- Re: [w3c/gamepad] gamepad*connected handlers are only needed on Window (Issue #166) (Wednesday, 6 July)
- Re: [w3c/gamepad] gamepad*connected handlers are only needed on Window (Issue #166) (Wednesday, 6 July)
- Re: [w3c/gamepad] gamepad*connected handlers are only needed on Window (Issue #166) (Wednesday, 6 July)
- Re: [w3c/gamepad] gamepad*connected handlers are only needed on Window (Issue #166) (Wednesday, 6 July)
- Re: [w3c/gamepad] gamepad*connected handlers are only needed on Window (Issue #166) (Wednesday, 6 July)
Marijn Kruisselbrink
Martin Middel
Martin Vejnár
Mason Freed
Matt Giuca
Matt Reynolds
Mattias Buelens
meshl555
Michael Lagally
Michael McCool
Michael Osipov
Mike Taylor
- Re: [w3c/permissions] Editorial: add an introduction (PR #381) (Saturday, 30 July)
- Re: [w3c/permissions] Chore: Tidied up document using tidy-html5 (PR #382) (Saturday, 30 July)
- Re: [w3c/permissions] Tidied up document using tidy-html5 (PR #382) (Saturday, 30 July)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381) (Saturday, 30 July)
- Re: [w3c/permissions] Add an introduction section? (#274) (Saturday, 30 July)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381) (Saturday, 30 July)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381) (Saturday, 30 July)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381) (Saturday, 30 July)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381) (Monday, 25 July)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381) (Monday, 25 July)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381) (Monday, 25 July)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381) (Monday, 25 July)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381) (Monday, 25 July)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381) (Friday, 22 July)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381) (Friday, 22 July)
- Re: [w3c/permissions] Editorial: add an introduction (PR #381) (Friday, 22 July)
- [w3c/permissions] Editorial: add an introduction (PR #381) (Friday, 22 July)
- Re: [w3c/permissions] Add an introduction section? (#274) (Friday, 1 July)
Mike West
Nathan Chase
Noam Rosenthal
- Re: [whatwg/fetch] Pass in response status to mark resource timing (PR #1468) (Friday, 29 July)
- Re: [whatwg/fetch] Editorial: Use controller for navigation redirect (PR #1469) (Friday, 29 July)
- Re: [whatwg/fetch] Add response status to response body info (PR #1468) (Thursday, 28 July)
- Re: [whatwg/fetch] HTTP 101 response NOT for websockets (Issue #1397) (Thursday, 28 July)
- Re: [whatwg/fetch] HTTP 101 response NOT for websockets (Issue #1397) (Thursday, 28 July)
- Re: [whatwg/fetch] HTTP 101 response NOT for websockets (Issue #1397) (Thursday, 28 July)
- Re: [whatwg/fetch] HTTP 101 response NOT for websockets (Issue #1397) (Thursday, 28 July)
- Re: [whatwg/fetch] Add response status to response body info (PR #1468) (Wednesday, 27 July)
- Re: [whatwg/fetch] Add response status to response body info (PR #1468) (Wednesday, 27 July)
- Re: [whatwg/fetch] Editorial: Use controller for navigation redirect (PR #1469) (Monday, 11 July)
- Re: [whatwg/fetch] Editorial: Use controller for navigation redirect (PR #1469) (Monday, 11 July)
- [whatwg/fetch] Editorial: Use controller for redirect navigation (PR #1469) (Monday, 11 July)
- Re: [whatwg/fetch] Proposal: CORS means TAO by default (Issue #1414) (Monday, 11 July)
- [whatwg/fetch] Editorial: Move initiator type to other side of note (PR #1467) (Friday, 8 July)
PacificGoal
Paul Jensen
Peter Linss
Philip Jägenstedt
Praveen Ponnusamy
priyansh sharma
pshaughn
Querulant
Quoc Duy Pham
Randall Leeds
Reilly Grant
Riccardo Albertoni
Rossen Atanassov
Rouslan Solomakhin
rubberyuzu
Ryosuke Niwa
- Re: [WICG/webcomponents] [custom-elements] Why is `attributeChangedCallback` synchronous? (Issue #963) (Sunday, 31 July)
- Re: [w3c/selection-api] `selectstart` event handler needs to be exposed on `Text` (Issue #159) (Friday, 29 July)
- Re: [w3c/selection-api] `selectstart` event handler needs to be exposed on `Text` (Issue #159) (Friday, 29 July)
- Re: [WICG/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 26 July)
- Re: [WICG/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Tuesday, 26 July)
- Re: [WICG/webcomponents] [element-internals] How to get internals in base class and subclass, without leaking it to public (Issue #962) (Tuesday, 26 July)
- Re: [WICG/webcomponents] [scoped-registries] reduce pain by preventing logic from ever touching non-upgraded custom elements (Issue #960) (Wednesday, 20 July)
- Re: [WICG/webcomponents] [scoped-registries] reduce pain by preventing logic from ever touching non-upgraded custom elements (Issue #960) (Tuesday, 19 July)
- Re: [w3c/selection-api] Editorial: fix the issues reported by HTML Tidy (PR #158) (Tuesday, 19 July)
- Re: [w3c/selection-api] Editorial: fix the issues reported by HTML Tidy (PR #158) (Tuesday, 19 July)
- Re: [WICG/webcomponents] Scoped Custom Element Registries (#716) (Tuesday, 19 July)
- Re: [WICG/webcomponents] Scoped Custom Element Registries (#716) (Monday, 18 July)
- Re: [WICG/webcomponents] Scoped Custom Element Registries (#716) (Monday, 18 July)
- Re: [w3c/selection-api] Specify Selection.modify()? (#37) (Wednesday, 13 July)
- Re: [w3c/selection-api] Define Selection.prototype.modify (PR #157) (Wednesday, 13 July)
- Re: [w3c/selection-api] Specify Selection.modify()? (#37) (Wednesday, 13 July)
- [w3c/selection-api] Define Selection.prototype.modify (PR #157) (Wednesday, 13 July)
- Re: [w3c/selection-api] Specify the selection behavior when selecting text in textarea or input (#78) (Wednesday, 13 July)
- Re: [w3c/selection-api] Specify the selection behavior when selecting text in textarea or input (#78) (Wednesday, 13 July)
- Re: [w3c/selection-api] Define "editing hosts cannot have a selection" (#1) (Wednesday, 13 July)
- Re: [w3c/selection-api] Define "editing hosts cannot have a selection" (#1) (Wednesday, 13 July)
- Re: [w3c/selection-api] Remove the stray sentence that editing hosts outside a document cannot have a selection (PR #156) (Wednesday, 13 July)
- [w3c/selection-api] Remove the stray sentence that editing hosts outside a document cannot have a selection (PR #156) (Wednesday, 13 July)
- Re: [w3c/selection-api] Define "editing hosts cannot have a selection" (#1) (Wednesday, 13 July)
- Re: [w3c/selection-api] Selection should detach associated Range when Range move to another root. (#79) (Wednesday, 13 July)
- Re: [w3c/selection-api] Add getComposedRange to Selection (#98) (Wednesday, 13 July)
- Re: [w3c/selection-api] What task source do we queue events on? (#117) (Wednesday, 13 July)
- Re: [w3c/selection-api] What task source do we queue events on? (#117) (Wednesday, 13 July)
- Re: [w3c/selection-api] Clarify that the user interaction task source is used for selectionchange event (PR #155) (Wednesday, 13 July)
- Re: [w3c/selection-api] Define getSelection on DocumentOrShadowRoot instead of Document (#114) (Wednesday, 13 July)
- Re: [w3c/selection-api] Define getSelection on DocumentOrShadowRoot instead of Document (#114) (Wednesday, 13 July)
- Re: [w3c/selection-api] Include information about where the selection is ending (#93) (Wednesday, 13 July)
- Re: [w3c/selection-api] Include information about where the selection is ending (#93) (Wednesday, 13 July)
- Re: [w3c/selection-api] Specification status report for TPAC 2019 (#111) (Wednesday, 13 July)
- [w3c/selection-api] Clarify that the user interaction task source is used for selectionchange event (PR #155) (Wednesday, 13 July)
- Re: [w3c/selection-api] add security considerations section (#132) (Wednesday, 13 July)
- Re: [w3c/selection-api] add privacy considerations section (#133) (Wednesday, 13 July)
- Re: [w3c/selection-api] Add security and privacy considerations. (PR #154) (Wednesday, 13 July)
- Re: [w3c/selection-api] What happens to direction when the range associated with the selection is modified? (#127) (Wednesday, 13 July)
- Re: [w3c/selection-api] What happens to direction when the range associated with the selection is modified? (#127) (Wednesday, 13 July)
- [w3c/selection-api] Add security and privacy considerations. (PR #154) (Wednesday, 13 July)
- Re: [w3c/selection-api] add privacy considerations section (#133) (Wednesday, 13 July)
- Re: [w3c/selection-api] add security considerations section (#132) (Wednesday, 13 July)
- Re: [w3c/selection-api] Clarify that the direction of selection is preserved when scripts mutates its range. (PR #153) (Wednesday, 13 July)
- [w3c/selection-api] Clarify that the direction of selection is preserved when scripts mutates its range. (PR #153) (Wednesday, 13 July)
- Re: [w3c/selection-api] What happens to direction when the range associated with the selection is modified? (#127) (Wednesday, 13 July)
- Re: [w3c/selection-api] Align description of events with DOM suggested phrasing (PR #148) (Wednesday, 13 July)
- Re: [w3c/selection-api] Align description of events with DOM suggested phrasing (PR #148) (Wednesday, 13 July)
- Re: [w3c/selection-api] Align description of events with DOM suggested phrasing (PR #148) (Wednesday, 13 July)
- Re: [w3c/selection-api] Why does getRangeAt must return a reference to (not a copy of) the range? (#40) (Tuesday, 12 July)
- Re: [w3c/selection-api] Why does getRangeAt must return a reference to (not a copy of) the range? (#40) (Tuesday, 12 July)
- Re: [w3c/selection-api] Bahavior without browsing context (#82) (Tuesday, 12 July)
- Re: [w3c/selection-api] Bahavior without browsing context (#82) (Tuesday, 12 July)
- Re: [w3c/selection-api] containsNode could return true for a node that doesn't intersect the selection at all (#116) (Tuesday, 12 July)
- Re: [w3c/selection-api] Fix the definition of containsNode() method when allowPartialContainment is true. (PR #152) (Tuesday, 12 July)
- [w3c/selection-api] Fix the definition of containsNode() method when allowPartialContainment is true. (PR #152) (Tuesday, 12 July)
- Re: [w3c/selection-api] containsNode could return true for a node that doesn't intersect the selection at all (#116) (Tuesday, 12 July)
- Re: [w3c/selection-api] Closes the issue 126. (PR #151) (Tuesday, 12 July)
- Re: [w3c/selection-api] Text says "below" when talking about text that is "above" (#126) (Tuesday, 12 July)
- [w3c/selection-api] Closes the issue 126. (PR #151) (Tuesday, 12 July)
- Re: [w3c/selection-api] Remove the outdated note to address the issue #128. (PR #150) (Tuesday, 12 July)
- Re: [w3c/selection-api] Remove outdated note about getSelection() (#128) (Tuesday, 12 July)
- [w3c/selection-api] Remove the outdated note to address the issue #128. (PR #150) (Tuesday, 12 July)
- Re: [w3c/selection-api] edge 中selection.focusOffset计算错误 (#97) (Tuesday, 12 July)
- Re: [w3c/selection-api] edge 中selection.focusOffset计算错误 (#97) (Tuesday, 12 July)
- Re: [w3c/selection-api] Changing the selection creates a Range object (#103) (Tuesday, 12 July)
- Re: [whatwg/dom] Adoption and DocumentFragment, part two (#819) (Saturday, 2 July)
Sasha Firsov
Scott Haseley
Shiino Yuki
Shivani Sharma
Shu-yu Guo
sis6326r
smaug----
snianu
Stefan
stefanKP50
Stephen McGruer
Steve Agoston
Steven Bingler
Takumi Fujimoto
The Contemporary Florals by Cesar Alvarez Pascual
Thomas Steiner
Tobias Buschor
Tom Schuster
Travis Leithead
Vadym Myrgorod
Victor Schedlyn GUTT
vmpstr
W3C Bot
Wenson Hsieh
Westbrook Johnson
Wiktor
Xiaoqian Wu
Yaseen Khan
Yoav Weiss
Yonathan Randolph
Yuri Sulyma
Yusuke Abe
Yutaka Hirano
Yves Lafon
醒
Last message date: Sunday, 31 July 2022 08:29:28 UTC