[w3c/manifest] clarify the definition of "navigation scope", "applied", and off-scope theming (PR #1151)
Re: [w3c/manifest] Require document to be in scope to be styled by the manifest (#791)
- Re: [w3c/manifest] Require document to be in scope to be styled by the manifest (#791)
- Re: [w3c/manifest] Require document to be in scope to be styled by the manifest (#791)
Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880)
- Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880)
- Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880)
- Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880)
- Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880)
- Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880)
- Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880)
- Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880)
- Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880)
- Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880)
- Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880)
- Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880)
- Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880)
- Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880)
- Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880)
- Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880)
Re: [whatwg/storage] StorageEstimate.quota + Storage Pressure (#73)
Re: [w3c/manifest] Relationship between nestedly scoped web app manifests? (#539)
[whatwg/dom] Extension only API to query across shadow trees (Issue #1321)
- Re: [whatwg/dom] Extension only API to query across shadow trees (Issue #1321)
- Re: [whatwg/dom] Extension only API to query across shadow trees (Issue #1321)
- Re: [whatwg/dom] Extension only API to query across shadow trees (Issue #1321)
Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736)
- Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736)
- Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736)
Re: [whatwg/streams] define semantics of {source,sink}.finally() (#636)
[whatwg/dom] Allow custom activation behavior to be added to an event (Issue #1320)
Re: [whatwg/fetch] FetchObserver (for a single fetch) (#607)
Re: [w3ctag/design-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76)
[w3c/selection-api] Reference the move primitive in DOM mutations section (PR #341)
[w3c/selection-api] Tidied up document using tidy-html5 (PR #340)
[w3c/selection-api] Editorial: Correctly reference `{{Document/getSelection()}}` (PR #339)
- Re: [w3c/selection-api] Editorial: Correctly reference `{{Document/getSelection()}}` (PR #339)
- Re: [w3c/selection-api] Editorial: Correctly reference `{{Document/getSelection()}}` (PR #339)
- Re: [w3c/selection-api] Editorial: Correctly reference `{{Document/getSelection()}}` (PR #339)
[w3c/FileAPI] google chrome can’t be installed on iPhone (Issue #202)
Re: [WICG/webcomponents] Exploration: HTML Module Imports and Exports (Issue #1059)
[whatwg/encoding] In blink, we only do the lookup by frame name in the local process. So in all cases where we host the navigation in a different process, the lookup by name just never works. (Issue #337)
Re: [whatwg/fetch] Add request Content-Length to PerformanceResourceTiming entries (Issue #1777)
Re: [whatwg/fetch] Refactor quota based on new explainer (66d4fc1)
Re: [whatwg/streams] Cancelling and exception handling async iteration of ReadableStreams (Issue #1255)
[w3ctag/design-reviews] CSS :open pseudo-class (Issue #1010)
Re: [whatwg/dom] Proposal: DOM APIs in web workers? (Issue #1217)
[whatwg/streams] Editorial: replace uses of the Type macro with is-a tests (PR #1330)
- Re: [whatwg/streams] Editorial: replace uses of the Type macro with is-a tests (PR #1330)
- Re: [whatwg/streams] Editorial: replace uses of the Type macro with is-a tests (PR #1330)
Re: [w3ctag/design-reviews] View Transition Classes (Issue #938)
[whatwg/webidl] Editorial: replace uses of the Type macro with is-a tests (PR #1447)
- Re: [whatwg/webidl] Editorial: replace uses of the Type macro with is-a tests (PR #1447)
- Re: [whatwg/webidl] Editorial: replace uses of the Type macro with is-a tests (PR #1447)
- Re: [whatwg/webidl] Editorial: replace uses of the Type macro with is-a tests (PR #1447)
Re: [w3c/FileAPI] Blob URL store partitioning (#153)
[whatwg/streams] Unified way to clean up after ReadableStream finished/errored/was canceled (Issue #1329)
[whatwg/webidl] Fix Iterator prototype reference (PR #1446)
- Re: [whatwg/webidl] Fix Iterator prototype reference (PR #1446)
- Re: [whatwg/webidl] Fix Iterator prototype reference (PR #1446)
[whatwg/webidl] Promises: Return a PromiseCapability from react (PR #1445)
- Re: [whatwg/webidl] Promises: Return a PromiseCapability from react (PR #1445)
- Re: [whatwg/webidl] Promises: Return a PromiseCapability from react (PR #1445)
- Re: [whatwg/webidl] Promises: Return a PromiseCapability from react (PR #1445)
[whatwg/webidl] `make remote` fails due to missing ECMAScript references (Issue #1444)
- Re: [whatwg/webidl] `make` fails due to missing ECMAScript references (Issue #1444)
- Re: [whatwg/webidl] `make` fails due to missing ECMAScript references (Issue #1444)
[whatwg/fetch] Partition Blob URL fetches by Storage Key (PR #1783)
Re: [w3c/manifest] How to extend the scope to ensure that the PWA provides the same user experience when accessing pages in different domains? (#964)
[w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201)
Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)
[w3ctag/design-reviews] Review for Protected Audiences Bidding and Auction Services API (Issue #1009)
Re: [whatwg/dom] Document.defaultCharset (#58)
Re: [w3c/push-api] Add Declarative Web Push (PR #385)
[whatwg/fetch] Meta: reference new Structured Field Values RFC (PR #1782)
[w3c/FileAPI] Removed extra "be" in sentence. (PR #200)
- Re: [w3c/FileAPI] Removed extra "be" in sentence. (PR #200)
- Re: [w3c/FileAPI] Removed extra "be" in sentence. (PR #200)
- Re: [w3c/FileAPI] Removed extra "be" in sentence. (PR #200)
[whatwg/fetch] Skip localhost when evaluating HSTS upgrades (PR #1781)
- Re: [whatwg/fetch] Skip localhost when evaluating HSTS upgrades (PR #1781)
- Re: [whatwg/fetch] Skip localhost when evaluating HSTS upgrades (PR #1781)
- Re: [whatwg/fetch] Skip localhost when evaluating HSTS upgrades (PR #1781)
[whatwg/fetch] Exclude localhost from HTTPS upgrades (Issue #1780)
Re: [w3ctag/design-reviews] Early Design Review: Lightweight FedCM (Issue #986)
Re: [w3ctag/design-reviews] Updated review of WebNN API (Issue #933)
Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
- Re: [whatwg/fetch] Deferred fetching (PR #1647)
Re: [w3c/push-api] Declarative Web Push (Issue #360)
Re: [whatwg/fetch] Add a `timeout` option, to prevent hanging (#951)
[w3ctag/design-reviews] Vision for W3C: request horizontal architectural review and wide TAG review (Issue #1008)
[whatwg/webidl] Should react to a Promise steps return a PromiseCapability instead of a Promise? (Issue #1443)
- Re: [whatwg/webidl] Should react to a Promise steps return a PromiseCapability instead of a Promise? (Issue #1443)
- Re: [whatwg/webidl] Should react to a Promise steps return a PromiseCapability instead of a Promise? (Issue #1443)
Re: [w3c/ServiceWorker] Service Worker as secure storage and provider for access token and refresh token (Issue #1626)
[whatwg/fetch] Response body being null on 204/205/304 etc doesn't match any implementation (Issue #1779)
- Re: [whatwg/fetch] Response body being null on 204/205/304 etc doesn't match any implementation (Issue #1779)
- Re: [whatwg/fetch] Response body being null on 204/205/304 etc doesn't match any implementation (Issue #1779)
[w3c/clipboard-apis] SVG sanitization not defined (Issue #229)
Re: [w3ctag/design-reviews] FYI Private State Token API Permissions Policy Default Allowlist Wildcard (Issue #990)
- Re: [w3ctag/design-reviews] FYI Private State Token API Permissions Policy Default Allowlist Wildcard (Issue #990)
- Re: [w3ctag/design-reviews] FYI Private State Token API Permissions Policy Default Allowlist Wildcard (Issue #990)
Re: [w3c/push-api] Declarative Web Push: mutable field (Issue #391)
Re: [w3c/selection-api] Clarify association between a selection and its range (#2)
- Re: [w3c/selection-api] Clarify association between a selection and its range (#2)
- Re: [w3c/selection-api] Clarify association between a selection and its range (#2)
- Re: [w3c/selection-api] Clarify association between a selection and its range (#2)
- Re: [w3c/selection-api] Clarify association between a selection and its range (#2)
- Re: [w3c/selection-api] Clarify association between a selection and its range (#2)
[w3c/manifest] Add guidance for user agents about how to prevent malicious localization strings (Issue #1150)
- Re: [w3c/manifest] Add guidance for user agents about how to prevent malicious localization strings (Issue #1150)
- Re: [w3c/manifest] Add guidance for user agents about how to prevent malicious localization strings (Issue #1150)
Re: [w3ctag/design-reviews] [HTML] Canvas place element (Issue #997)
[w3c/ServiceWorker] after upgrading to 8.0.10, Blazor publishing with AOT:true freezes when trying to precompile System.Private.CoreLib.dll (Issue #1733)
Re: [w3c/manifest] Scope: Allow developer to have more fine-grained control of app scope. (#996)
- Re: [w3c/manifest] Scope: Allow developer to have more fine-grained control of app scope. (#996)
- Re: [w3c/manifest] Scope: Allow developer to have more fine-grained control of app scope. (#996)
- Re: [w3c/manifest] Scope: Allow developer to have more fine-grained control of app scope. (#996)
- Re: [w3c/manifest] Scope: Allow developer to have more fine-grained control of app scope. (#996)
- Re: [w3c/manifest] Scope: Allow developer to have more fine-grained control of app scope. (#996)
- Re: [w3c/manifest] Scope: Allow developer to have more fine-grained control of app scope. (#996)
Re: [w3c/charter-html] WebPlat charter: Deliverable state (#155)
Re: [w3c/uievents] Dead key symbols not included in KeyboardEvent (Issue #343)
[whatwg/dom] I'd expect consistency with () which has the connected check. (Issue #1319)
[w3c/ServiceWorker] Steps for Update have an empty condition for async modules (Issue #1732)
- Re: [w3c/ServiceWorker] Steps for Update have an empty condition for async modules (Issue #1732)
- Re: [w3c/ServiceWorker] Steps for Update have an empty condition for async modules (Issue #1732)
Re: [whatwg/fetch] Request with GET/HEAD method cannot have body. (#551)
Re: [w3c/screen-orientation] Add can-lock-orientation media feature to detect if locking is possible (Issue #206)
Re: [w3ctag/design-reviews] systemEntropy addition to PerformanceNavigationTiming (Issue #878)
[w3ctag/design-reviews] Customizable select element (Issue #1007)
Re: [w3ctag/design-reviews] A layer attribute for layering of linked CSS style sheets in HTML (Issue #970)
Re: [w3ctag/design-reviews] CSS Selectors 4; :local-link (Issue #998)
Re: [w3c/selection-api] Define to remove selection range automatically if a selection range is modified into different selection root (Issue #175)
Re: [w3c/selection-api] Specify the behavior when DOM mutation occurs across shadow-crossing selection (Issue #168)
Re: [whatwg/dom] Steps of removing a node definition about live range do not match with browsers if the range is in a shadow DOM and the shadow itself is removed (Issue #1274)
Re: [whatwg/fetch] Can the set of safelisted methods be extended? (Issue #1774)
[w3ctag/design-reviews] EPUB 3.3 2024-20-27 Recommendation with Candidate Corrections (Issue #1006)
[w3ctag/design-reviews] Dispatching Toggle Events for Dialog open/close (Issue #1005)
- Re: [w3ctag/design-reviews] Dispatching Toggle Events for Dialog open/close (Issue #1005)
- Re: [w3ctag/design-reviews] Dispatching Toggle Events for Dialog open/close (Issue #1005)
- Re: [w3ctag/design-reviews] Dispatching Toggle Events for Dialog open/close (Issue #1005)
- Re: [w3ctag/design-reviews] Dispatching Toggle Events for Dialog open/close (Issue #1005)
- Re: [w3ctag/design-reviews] Dispatching Toggle Events for Dialog open/close (Issue #1005)
- Re: [w3ctag/design-reviews] Dispatching Toggle Events for Dialog open/close (Issue #1005)
- Re: [w3ctag/design-reviews] Dispatching Toggle Events for Dialog open/close (Issue #1005)
[WICG/webcomponents] Preventing re-renders prior to first call to `connectedCallback()` (Issue #1081)
- Re: [WICG/webcomponents] Preventing re-renders prior to first call to `connectedCallback()` (Issue #1081)
- Re: [WICG/webcomponents] Preventing re-renders prior to first call to `connectedCallback()` (Issue #1081)
- Re: [WICG/webcomponents] Preventing re-renders prior to first call to `connectedCallback()` (Issue #1081)
- Re: [WICG/webcomponents] Preventing re-renders prior to first call to `connectedCallback()` (Issue #1081)
- Re: [WICG/webcomponents] Preventing re-renders prior to first call to `connectedCallback()` (Issue #1081)
- Re: [WICG/webcomponents] Preventing re-renders prior to first call to `connectedCallback()` (Issue #1081)
[WICG/webcomponents] add `node.isCustomElement` property (Issue #1080)
- Re: [WICG/webcomponents] add `node.isCustomElement` property (Issue #1080)
- Re: [WICG/webcomponents] add `node.isCustomElement` property (Issue #1080)
- Re: [WICG/webcomponents] add `node.isCustomElement` property (Issue #1080)
- Re: [WICG/webcomponents] add `node.isCustomElement` property (Issue #1080)
- Re: [WICG/webcomponents] add `node.isCustomElement` property (Issue #1080)
- Re: [WICG/webcomponents] add `node.isCustomElement` property (Issue #1080)
- Re: [WICG/webcomponents] add `node.isCustomElement` property (Issue #1080)
- Re: [WICG/webcomponents] add `node.isCustomElement` property (Issue #1080)
- Re: [WICG/webcomponents] add `node.isCustomElement` property (Issue #1080)
- Re: [WICG/webcomponents] add `node.isCustomElement` property (Issue #1080)
- Re: [WICG/webcomponents] add `node.isCustomElement` property (Issue #1080)
- Re: [WICG/webcomponents] add `node.isCustomElement` property (Issue #1080)
- Re: [WICG/webcomponents] add `node.isCustomElement` property (Issue #1080)
Re: [w3c/IndexedDB] Key Paths: Support iteration step operator (#35)
[w3ctag/design-reviews] Allowing SameSite=None Cookies in Sandboxed Contexts (Issue #1004)
Re: [w3ctag/design-reviews] Captured Surface Control (Issue #962)
- Re: [w3ctag/design-reviews] Captured Surface Control (Issue #962)
- Re: [w3ctag/design-reviews] Captured Surface Control (Issue #962)
- Re: [w3ctag/design-reviews] Captured Surface Control (Issue #962)
- Re: [w3ctag/design-reviews] Captured Surface Control (Issue #962)
Re: [w3c/manifest] related_applications is single engine feature (#956)
- Re: [w3c/manifest] related_applications is single engine feature (#956)
- Re: [w3c/manifest] related_applications is single engine feature (#956)
Re: [w3c/manifest] prefer_related_applications is single engine feature (#957)
- Re: [w3c/manifest] prefer_related_applications is single engine feature (#957)
- Re: [w3c/manifest] prefer_related_applications is single engine feature (#957)
Re: [w3ctag/design-reviews] Document-Isolation-Policy (Issue #995)
Re: [w3c/uievents-code] CFC to publish UI Events KeyboardEvent code Values as a Proposed Recommendation in the WebApps WG (Issue #43)
[WICG/webcomponents] getOutterHTML (Issue #1079)
- Re: [WICG/webcomponents] getOuterHTML (Issue #1079)
- Re: [WICG/webcomponents] getOuterHTML (Issue #1079)
- Re: [WICG/webcomponents] getOuterHTML (Issue #1079)
- Re: [WICG/webcomponents] . (Issue #1079)
Re: [w3ctag/design-reviews] Multiple import maps (Issue #980)
- Re: [w3ctag/design-reviews] Multiple import maps (Issue #980)
- Re: [w3ctag/design-reviews] Multiple import maps (Issue #980)
- Re: [w3ctag/design-reviews] Multiple import maps (Issue #980)
- Re: [w3ctag/design-reviews] Multiple import maps (Issue #980)
- Re: [w3ctag/design-reviews] Multiple import maps (Issue #980)
- Re: [w3ctag/design-reviews] Multiple import maps (Issue #980)
- Re: [w3ctag/design-reviews] Multiple import maps (Issue #980)
- Re: [w3ctag/design-reviews] Multiple import maps (Issue #980)
- Re: [w3ctag/design-reviews] Multiple import maps (Issue #980)
- Re: [w3ctag/design-reviews] Multiple import maps (Issue #980)
- Re: [w3ctag/design-reviews] Multiple import maps (Issue #980)
- Re: [w3ctag/design-reviews] Multiple import maps (Issue #980)
Re: [w3ctag/design-reviews] Realms Initialization Control (Issue #985)
- Re: [w3ctag/design-reviews] Realms Initialization Control (Issue #985)
- Re: [w3ctag/design-reviews] Realms Initialization Control (Issue #985)
Re: [w3c/selection-api] Add `selectionRoot` option to getComposedRanges parameter options (Issue #180)
Re: [w3c/manifest] "internationalization" section (Issue #1090)
[WICG/webcomponents] [Scoped Registries] Disconnected elements can retain their "origin" by utilising the dangling TreeScope ptr (Issue #1078)
- Re: [WICG/webcomponents] [Scoped Registries] Can disconnected elements can retain their shadowroot via dangling treeroot pointer? (Issue #1078)
- Re: [WICG/webcomponents] [Scoped Registries] Can disconnected elements can retain their shadowroot via dangling treeroot pointer? (Issue #1078)
Re: [w3c/manifest] Clarify case-insensitive parsing for enum values (Issue #1142)
[w3c/manifest] Make enums case-insensitive (PR #1149)
[w3c/IndexedDB] Delete entire site data on data corruption/loss? (Issue #431)
- Re: [w3c/IndexedDB] Delete entire site data on data corruption/loss? (Issue #431)
- Re: [w3c/IndexedDB] Delete entire site data on data corruption/loss? (Issue #431)
- Re: [w3c/IndexedDB] Delete entire site data on data corruption/loss? (Issue #431)
[whatwg/dom] Proposal: add `computed` attribute for great performance! (Issue #1318)
- Re: [whatwg/dom] Proposal: add `computed` attribute for great performance! (Issue #1318)
- Re: [whatwg/dom] Proposal: add `computed` attribute for great performance! (Issue #1318)
- Re: [whatwg/dom] Proposal: add `computed` attribute for great performance! (Issue #1318)
- Re: [whatwg/dom] Proposal: add `computed` attribute for great performance! (Issue #1318)
- Re: [whatwg/dom] Proposal: add `computed` attribute for great performance! (Issue #1318)
- Re: [whatwg/dom] Proposal: add `computed` attribute for great performance! (Issue #1318)
[whatwg/dom] Proposal: getImageData api for all element,not limited to canvas (Issue #1317)
Re: [w3c/IndexedDB] Specify the exception for read failures arising due to partial data loss on the file system (Issue #423)
[w3c/manifest] Unbind computed id from start_url (Issue #1148)
[WICG/webcomponents] A components framework based on <template> (Issue #1077)
Re: [w3c/IndexedDB] Add descending order for getAll() and getAllKeys() (#130)
Re: [w3ctag/design-reviews] CSS Scoping; :has-slotted (Issue #999)
Re: [w3ctag/design-reviews] Reference Target (Issue #961)
- Re: [w3ctag/design-reviews] Reference Target (Issue #961)
- Re: [w3ctag/design-reviews] Reference Target (Issue #961)
- Re: [w3ctag/design-reviews] Reference Target (Issue #961)
- Re: [w3ctag/design-reviews] Reference Target (Issue #961)
- Re: [w3ctag/design-reviews] Reference Target (Issue #961)
- Re: [w3ctag/design-reviews] Reference Target (Issue #961)
- Re: [w3ctag/design-reviews] Reference Target (Issue #961)
- Re: [w3ctag/design-reviews] Reference Target (Issue #961)
- Re: [w3ctag/design-reviews] Reference Target (Issue #961)
- Re: [w3ctag/design-reviews] Reference Target (Issue #961)
- Re: [w3ctag/design-reviews] Reference Target (Issue #961)
- Re: [w3ctag/design-reviews] Reference Target (Issue #961)
- Re: [w3ctag/design-reviews] Reference Target (Issue #961)
- Re: [w3ctag/design-reviews] Reference Target (Issue #961)
- Re: [w3ctag/design-reviews] Reference Target (Issue #961)
- Re: [w3ctag/design-reviews] Reference Target (Issue #961)
- Re: [w3ctag/design-reviews] Reference Target (Issue #961)
[w3ctag/design-reviews] CSS Masonry Layout (Issue #1003)
- Re: [w3ctag/design-reviews] CSS Masonry Layout (Issue #1003)
- Re: [w3ctag/design-reviews] CSS Masonry Layout (Issue #1003)
- Re: [w3ctag/design-reviews] CSS Masonry Layout (Issue #1003)
[WICG/webcomponents] case-sensitive attribute APIs would be useful. (Issue #1076)
- Re: [WICG/webcomponents] case-sensitive access to HTML attributes (as they were written) would be useful for framework authors (Issue #1076)
- Re: [WICG/webcomponents] case-sensitive access to HTML attributes (as they were written) would be useful for framework authors (Issue #1076)
- Re: [WICG/webcomponents] case-sensitive access to HTML attributes (as they were written) would be useful for framework authors (Issue #1076)
- Re: [WICG/webcomponents] case-sensitive access to HTML attributes (as they were written) would be useful for framework authors (Issue #1076)
- Re: [WICG/webcomponents] case-sensitive access to HTML attributes (as they were written) would be useful for framework authors (Issue #1076)
- Re: [WICG/webcomponents] case-sensitive access to HTML attributes (as they were written) would be useful for framework authors (Issue #1076)
- Re: [WICG/webcomponents] case-sensitive access to HTML attributes (as they were written) would be useful for framework authors (Issue #1076)
- Re: [WICG/webcomponents] case-sensitive access to HTML attributes (as they were written) would be useful for framework authors (Issue #1076)
Re: [w3ctag/design-reviews] Cryptographically secure random UUIDs (#623)
[whatwg/webidl] conda (Issue #1442)
Re: [w3c/selection-api] Determine whether addRange() and removeAllRanges() should reset direction (#3)
Re: [WICG/webcomponents] [scoped-registries] Consider future expansion to allow using a registry without new API (Issue #1043)
- Re: [WICG/webcomponents] [scoped-registries] Consider future expansion to allow using a registry without new API (Issue #1043)
- Re: [WICG/webcomponents] [scoped-registries] Consider future expansion to allow using a registry without new API (Issue #1043)
Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069)
Re: [w3c/gamepad] Add extended buttons to support trackpad (#191) (PR #196)
- Re: [w3c/gamepad] Add extended buttons to support trackpad (#191) (PR #196)
- Re: [w3c/gamepad] Add extended buttons to support trackpad (#191) (PR #196)
- Re: [w3c/gamepad] Add extended buttons to support trackpad (#191) (PR #196)
[w3c/gamepad] Make eventInitDict param optional in GamepadEvent constructor (PR #217)
- Re: [w3c/gamepad] Make eventInitDict param optional in GamepadEvent constructor (PR #217)
- Re: [w3c/gamepad] Make eventInitDict param optional in GamepadEvent constructor (PR #217)
- Re: [w3c/gamepad] Make eventInitDict param optional in GamepadEvent constructor (PR #217)
- Re: [w3c/gamepad] Make eventInitDict param optional in GamepadEvent constructor (PR #217)
[w3c/gamepad] eventInitDict parameter in GamepadEvent constructor should be optional (Issue #216)
Re: [whatwg/fetch] Allow request take AsyncIterable body? (#1291)
- Re: [whatwg/fetch] Allow request take AsyncIterable body? (#1291)
- Re: [whatwg/fetch] Allow request take AsyncIterable body? (#1291)
Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
- Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)
Re: [w3ctag/design-reviews] Shared Storage API (Issue #747)
[w3c/manifest] Clarification needed for document URL (Issue #1147)
Re: [w3ctag/design-reviews] Spec review for Animation.progress (Issue #994)
- Re: [w3ctag/design-reviews] Spec review for Animation.progress (Issue #994)
- Re: [w3ctag/design-reviews] Spec review for Animation.progress (Issue #994)
- Re: [w3ctag/design-reviews] Spec review for Animation.progress (Issue #994)
Re: [w3ctag/design-reviews] TAG Review for CSS Values & Units Level 5 (Issue #993)
Re: [whatwg/dom] Should there be a declarative version of adoptedStyleSheets? (#910)
[whatwg/dom] Update README.mdkoko (PR #1316)
[w3c/selection-api] Scheduling an selectionchange event does not set "has scheduled selectionchange event" to true (Issue #338)
Re: [w3ctag/design-reviews] Element Capture (Issue #954)
- Re: [w3ctag/design-reviews] Element Capture (Issue #954)
- Re: [w3ctag/design-reviews] Element Capture (Issue #954)
Re: [w3ctag/design-reviews] Early design review: Future browsing context group dependency hint (Issue #979)
- Re: [w3ctag/design-reviews] Early design review: Future browsing context group dependency hint (Issue #979)
- Re: [w3ctag/design-reviews] Early design review: Future browsing context group dependency hint (Issue #979)
- Re: [w3ctag/design-reviews] Early design review: Future browsing context group dependency hint (Issue #979)
- Re: [w3ctag/design-reviews] Early design review: Future browsing context group dependency hint (Issue #979)
Re: [w3c/uievents] Need virtual key codes (Issue #377)
Re: [w3c/manifest] "localizable members" should be defined separately? (Issue #1080)
Re: [w3c/manifest] `name` and `short_name` (and other localizable member's) relationship to localization and accessibility (Issue #1085)
Re: [w3c/manifest] Use of `CanonicalizeUnicodeLocaleId` (Issue #1084)
Re: [w3c/manifest] Application name section might need localization support (Issue #1088)
Re: [w3c/manifest] Add optional `translations` member (#676)
Re: [w3c/manifest] shortcuts and localizability (Issue #1087)
Re: [w3c/manifest] "security sensitive" items interaction with localization (Issue #1086)
Re: [w3c/manifest] Add members for localization (PR #1101)
- Re: [w3c/manifest] Add members for localization (PR #1101)
- Re: [w3c/manifest] Add members for localization (PR #1101)
- Re: [w3c/manifest] Add members for localization (PR #1101)
- Re: [w3c/manifest] Add members for localization (PR #1101)
Re: [w3c/manifest] No language/direction metadata for shortcuts? (Issue #1078)
Re: [w3c/manifest] No way to localize icons? (Issue #1077)
[w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430)
- Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430)
- Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430)
- Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430)
- Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430)
- Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430)
- Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430)
- Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430)
- Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430)
- Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430)
- Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430)
- Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430)
- Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430)
- Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430)
- Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430)
- Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430)
- Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430)
- Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430)
- Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430)
- Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430)
- Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430)
- Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430)
- Re: [w3c/IndexedDB] Specify the error code for failures when reading a value from disk (PR #430)
[whatwg/dom] DOM element with a name='currentScript' attribute can hijack document.currentScript.src (Issue #1315)
- Re: [whatwg/dom] DOM element with a name='currentScript' attribute can hijack document.currentScript.src (Issue #1315)
- Re: [whatwg/dom] DOM element with a name='currentScript' attribute can hijack document.currentScript.src (Issue #1315)
- Re: [whatwg/dom] DOM element with a name='currentScript' attribute can hijack document.currentScript.src (Issue #1315)
[w3ctag/design-reviews] Review for CR transition of WebAssembly specifications for version 2.0 features (Issue #1002)
- Re: [w3ctag/design-reviews] Review for CR transition of WebAssembly specifications for version 2.0 features (Issue #1002)
- Re: [w3ctag/design-reviews] Review for CR transition of WebAssembly specifications for version 2.0 features (Issue #1002)
- Re: [w3ctag/design-reviews] Review for CR transition of WebAssembly specifications for version 2.0 features (Issue #1002)
- Re: [w3ctag/design-reviews] Review for CR transition of WebAssembly specifications for version 2.0 features (Issue #1002)
- Re: [w3ctag/design-reviews] Review for CR transition of WebAssembly specifications for version 2.0 features (Issue #1002)
- Re: [w3ctag/design-reviews] Review for CR transition of WebAssembly specifications for version 2.0 features (Issue #1002)
- Re: [w3ctag/design-reviews] Review for CR transition of WebAssembly specifications for version 2.0 features (Issue #1002)
Re: [whatwg/fetch] redirects and etag/if-none-match (Issue #1770)
- Re: [whatwg/fetch] redirects and etag/if-none-match (Issue #1770)
- Re: [whatwg/fetch] redirects and etag/if-none-match (Issue #1770)
- Re: [whatwg/fetch] redirects and etag/if-none-match (Issue #1770)
Re: [w3c/selection-api] Need spec changes to Range and StaticRange to support nodes in different tree? (Issue #169)
Re: [w3c/clipboard-apis] ClipboardChange event spec: Callout transient user activation should be applied for focus requirement. (Issue #225)
Re: [w3c/clipboard-apis] Clipboard Change Event API (Issue #227)
Re: [w3c/editing] Clarify the nested case of `contenteditable=true` and `contenteditable=plaintext-only` (Issue #470)
[whatwg/webidl] Consider adding an `[InjectionMitigated]` extended attribute. (Issue #1440)
- Re: [whatwg/webidl] Consider adding an `[InjectionMitigated]` extended attribute. (Issue #1440)
- Re: [whatwg/webidl] Consider adding an `[InjectionMitigated]` extended attribute. (Issue #1440)
- Re: [whatwg/webidl] Consider adding an `[InjectionMitigated]` extended attribute. (Issue #1440)
- Re: [whatwg/webidl] Consider adding an `[InjectionMitigated]` extended attribute. (Issue #1440)
- Re: [whatwg/webidl] Consider adding an `[InjectionMitigated]` extended attribute. (Issue #1440)
- Re: [whatwg/webidl] Consider adding an `[InjectionMitigated]` extended attribute. (Issue #1440)
- Re: [whatwg/webidl] Consider adding an `[InjectionMitigated]` extended attribute. (Issue #1440)
[w3c/selection-api] Improve selection.isCollapsed (Issue #337)
- Re: [w3c/selection-api] Improve selection.isCollapsed (Issue #337)
- Re: [w3c/selection-api] Improve selection.isCollapsed (Issue #337)
- Re: [w3c/selection-api] Improve selection.isCollapsed (Issue #337)
- Re: [w3c/selection-api] Improve selection.isCollapsed (Issue #337)
[whatwg/dom] Fix Minor Writing Errors (PR #1314)
[WICG/webcomponents] Form associated custom elements: cross shadow root form participation (Issue #1075)
[w3c/uievents] Fix misspelling of nativeKey (PR #387)
[whatwg/streams] https://www.facebook.com/pages/Ptsunan-Rubbre-Pabrik-Getah-Karet-Palembang-Kertapati/499702870401821?mibextid=rS40aB7S9Ucbxw6v (Issue #1328)
- Re: [whatwg/streams] https://www.facebook.com/pages/Ptsunan-Rubbre-Pabrik-Getah-Karet-Palembang-Kertapati/499702870401821?mibextid=rS40aB7S9Ucbxw6v (Issue #1328)
- Re: [whatwg/streams] https://www.facebook.com/pages/Ptsunan-Rubbre-Pabrik-Getah-Karet-Palembang-Kertapati/499702870401821?mibextid=rS40aB7S9Ucbxw6v (Issue #1328)
Re: [w3c/uievents] Needs alternative WheelEvent.deltaMode, WheelEvent.delta(X|Y|Z) (#181)
Re: [whatwg/encoding] Editorial: use leading and trailing surrogate (PR #309)
- Re: [whatwg/encoding] Editorial: use leading and trailing surrogate (PR #309)
- Re: [whatwg/encoding] Editorial: use leading and trailing surrogate (PR #309)
Re: [whatwg/encoding] Editorial: use leading and pending surrogate (PR #309)
Re: [whatwg/encoding] If gb18030 is revised, consider aligning the Encoding Standard (#27)
Re: [whatwg/encoding] Reflect changes in GB 18030-2022 (Issue #312)
[whatwg/dom] Methods on ChildNode and ParentNode that take `(Node or DOMString)... nodes` should not use an intermediate DocumentFragment (Issue #1313)
- Re: [whatwg/dom] Methods on ChildNode and ParentNode that take `(Node or DOMString)... nodes` should not use an intermediate DocumentFragment (Issue #1313)
- Re: [whatwg/dom] Methods on ChildNode and ParentNode that take `(Node or DOMString)... nodes` should not use an intermediate DocumentFragment (Issue #1313)
- Re: [whatwg/dom] Methods on ChildNode and ParentNode that take `(Node or DOMString)... nodes` should not use an intermediate DocumentFragment (Issue #1313)
- Re: [whatwg/dom] Methods on ChildNode and ParentNode that take `(Node or DOMString)... nodes` should not use an intermediate DocumentFragment (Issue #1313)
[w3c/manifest] Up Dating a Galaxy A13a 5GHz Repository (Issue #1146)
[w3c/ServiceWorker] Job promise is an ECMAScript type, not WebIDL (Issue #1731)
- Re: [w3c/ServiceWorker] Job promise is an ECMAScript type, not WebIDL (Issue #1731)
- Re: [w3c/ServiceWorker] Job promise is an ECMAScript type, not WebIDL (Issue #1731)
Re: [whatwg/webidl] Intent use number / bigint union type (Issue #1426)
Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909)
Re: [WICG/webcomponents] Manage pseudo class matching state for custom elements (#813)
Re: [whatwg/dom] Proposal: rate limiting event listeners (debounce / throttle) (Issue #1298)
[w3ctag/design-reviews] CSS view transition auto name generation (Issue #1001)
- Re: [w3ctag/design-reviews] CSS view transition auto name generation (Issue #1001)
- Re: [w3ctag/design-reviews] CSS view transition auto name generation (Issue #1001)
- Re: [w3ctag/design-reviews] CSS view transition auto name generation (Issue #1001)
[whatwg/webidl] ConvertToInt should take an explicit argument for its conversion approach (Issue #1439)
Re: [WICG/webcomponents] Proposal: Allow custom elements to be in any namespace (#634)
Re: [whatwg/fetch] Make get, decode, and split handle edge cases correctly (3153e5e)
Re: [whatwg/dom] `mutationObserver.disconnect({ flush: true })` (Issue #1283)
- Re: [whatwg/dom] `mutationObserver.disconnect({ flush: true })` (Issue #1283)
- Re: [whatwg/dom] `mutationObserver.disconnect({ flush: true })` (Issue #1283)
- Re: [whatwg/dom] `mutationObserver.disconnect({ flush: true })` (Issue #1283)
- Re: [whatwg/dom] `mutationObserver.disconnect({ flush: true })` (Issue #1283)
- Re: [whatwg/dom] `mutationObserver.disconnect({ flush: true })` (Issue #1283)
- Re: [whatwg/dom] `mutationObserver.disconnect({ flush: true })` (Issue #1283)
- Re: [whatwg/dom] `mutationObserver.disconnect({ flush: true })` (Issue #1283)
- Re: [whatwg/dom] `mutationObserver.disconnect({ flush: true })` (Issue #1283)
[w3c/editing] CfC: Enable automated publication system for all Web Editing WG specs (Issue #471)
- Re: [w3c/editing] CfC: Enable automated publication system for all Web Editing WG specs (Issue #471)
- Re: [w3c/editing] CfC: Enable automated publication system for all Web Editing WG specs (Issue #471)
Re: [w3ctag/design-reviews] Vibration API (Issue #971)
- Re: [w3ctag/design-reviews] Vibration API (Issue #971)
- Re: [w3ctag/design-reviews] Vibration API (Issue #971)
- Re: [w3ctag/design-reviews] Vibration API (Issue #971)
- Re: [w3ctag/design-reviews] Vibration API (Issue #971)
- Re: [w3ctag/design-reviews] Vibration API (Issue #971)
Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577)
- Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577)
- Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577)
- Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577)
- Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577)
- Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577)
Re: [w3c/editing] Contenteditable re-creating deleted children when it shouldn't (Issue #468)
- Re: [w3c/editing] Contenteditable re-creating deleted children when it shouldn't (Issue #468)
- Re: [w3c/editing] Contenteditable re-creating deleted children when it shouldn't (Issue #468)
Re: [whatwg/encoding] Adopt GB18030-2022 (PR #336)
[w3ctag/design-reviews] Declarative CSS Modules and Declarative Shadow DOM `adoptedstylesheets` attribute (Issue #1000)
- Re: [w3ctag/design-reviews] Declarative CSS Modules and Declarative Shadow DOM `adoptedstylesheets` attribute (Issue #1000)
- Re: [w3ctag/design-reviews] Declarative CSS Modules and Declarative Shadow DOM `adoptedstylesheets` attribute (Issue #1000)
- Re: [w3ctag/design-reviews] Declarative CSS Modules and Declarative Shadow DOM `adoptedstylesheets` attribute (Issue #1000)
- Re: [w3ctag/design-reviews] Declarative CSS Modules and Declarative Shadow DOM `adoptedstylesheets` attribute (Issue #1000)
- Re: [w3ctag/design-reviews] Declarative CSS Modules and Declarative Shadow DOM `adoptedstylesheets` attribute (Issue #1000)
- Re: [w3ctag/design-reviews] Declarative CSS Modules and Declarative Shadow DOM `adoptedstylesheets` attribute (Issue #1000)
- Re: [w3ctag/design-reviews] Declarative CSS Modules and Declarative Shadow DOM `adoptedstylesheets` attribute (Issue #1000)
Re: [w3c/IndexedDB] Allow indexing on Request/Response properties (#305)
[w3c/ServiceWorker] Should IndexedDB allow indexing on Request/Response properties (Issue #1730)
Re: [w3c/IndexedDB] boolean should be a valid key (#76)
[w3c/IndexedDB] Support Temporal as key/value (Issue #429)
Re: [w3c/selection-api] Flat Tree or Composed Tree (Issue #336)
- Re: [w3c/selection-api] Flat Tree or Composed Tree (Issue #336)
- Re: [w3c/selection-api] Flat Tree or Composed Tree (Issue #336)
- Re: [w3c/selection-api] Flat Tree or Composed Tree (Issue #336)
- Re: [w3c/selection-api] Flat Tree or Composed Tree (Issue #336)
- Re: [w3c/selection-api] Flat Tree or Composed Tree (Issue #336)
Re: [w3c/IndexedDB] Why is delete() disallowed for key cursors? (#62)
Re: [w3c/IndexedDB] Add IDBCursor.close() (#185)
Re: [w3c/IndexedDB] Streaming data to/from IndexedDB (Issue #419)
Re: [w3c/IndexedDB] Prebuilt IndexedDB format (#224)
- Re: [w3c/IndexedDB] Prebuilt IndexedDB format (#224)
- Re: [w3c/IndexedDB] Prebuilt IndexedDB format (#224)
Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035)
Re: [w3c/IndexedDB] Projection Support (#366)
Re: [w3c/IndexedDB] Add a new event `onbeforecommit` on the interface IDBTransaction (#314)
- Re: [w3c/IndexedDB] Add a new event `onbeforecommit` on the interface IDBTransaction (#314)
- Re: [w3c/IndexedDB] Add a new event `onbeforecommit` on the interface IDBTransaction (#314)
- Re: [w3c/IndexedDB] Add a new event `onbeforecommit` on the interface IDBTransaction (#314)
Re: [w3c/IndexedDB] Batch get/getAll (Issue #376)
Re: [w3c/IndexedDB] `getAll()` with both key and value (or index key and primary key) (#206)
- Re: [w3c/IndexedDB] `getAll()` with both key and value (or index key and primary key) (#206)
- Re: [w3c/IndexedDB] `getAll()` with both key and value (or index key and primary key) (#206)
- Re: [w3c/IndexedDB] `getAll()` with both key and value (or index key and primary key) (#206)
- Re: [w3c/IndexedDB] `getAll()` with both key and value (or index key and primary key) (#206)
- Re: [w3c/IndexedDB] `getAll()` with both key and value (or index key and primary key) (#206)
- Re: [w3c/IndexedDB] `getAll()` with both key and value (or index key and primary key) (#206)
- Re: [w3c/IndexedDB] `getAll()` with both key and value (or index key and primary key) (#206)
[w3c/IndexedDB] Configurable task priority for IDBRequest and IDBTransaction? (Issue #428)
[w3c/IndexedDB] Add direction option to getAll() and getAllKeys() (Issue #427)
- Re: [w3c/IndexedDB] Add direction option to getAll() and getAllKeys() (Issue #427)
- Re: [w3c/IndexedDB] Add direction option to getAll() and getAllKeys() (Issue #427)
Re: [whatwg/fetch] Add ServiceWorker Static Routing API support (PR #1737)
- Re: [whatwg/fetch] Add ServiceWorker Static Routing API support (PR #1737)
- Re: [whatwg/fetch] Add ServiceWorker Static Routing API support (PR #1737)
Re: [whatwg/fetch] Unclear how to serialize request origin "client" (Issue #1773)
Re: [whatwg/fetch] Clarify that request.origin cannot be "client" at certain points (PR #1776)
- Re: [whatwg/fetch] Clarify that request.origin cannot be "client" at certain points (PR #1776)
- Re: [whatwg/fetch] Clarify that request.origin cannot be "client" at certain points (PR #1776)
Re: [WICG/webcomponents] Anonymous Custom Elements (Issue #1074)
- Re: [WICG/webcomponents] Anonymous Custom Elements (Issue #1074)
- Re: [WICG/webcomponents] Anonymous Custom Elements (Issue #1074)
- Re: [WICG/webcomponents] Anonymous Custom Elements (Issue #1074)
Re: [WICG/webcomponents] Web components authors are currently using ARIA in problematic ways that lead to duplicate announcements (Issue #1073)
- Re: [WICG/webcomponents] Web components authors are currently using ARIA in problematic ways that lead to duplicate announcements (Issue #1073)
- Re: [WICG/webcomponents] Web components authors are currently using ARIA in problematic ways that lead to duplicate announcements (Issue #1073)
- Re: [WICG/webcomponents] Web components authors are currently using ARIA in problematic ways that lead to duplicate announcements (Issue #1073)
Re: [WICG/webcomponents] Possibile way for cross shadowDom exclusive interactive elements (Issue #1054)
Re: [WICG/webcomponents] [exportparts] support exporting via wildcards `exportparts="*, primary-*"` (Issue #1051)
- Re: [WICG/webcomponents] [exportparts] support exporting via wildcards `exportparts="*, primary-*"` (Issue #1051)
- Re: [WICG/webcomponents] [exportparts] support exporting via wildcards `exportparts="*, primary-*"` (Issue #1051)