[whatwg/dom] dispatch algorithm doesn't seem to handle the case when target or relatedTarget is Window object (#580)
[whatwg/fetch] Using multipart/form-data with multer occasionally causes React app to crash and refresh (#677)
[whatwg/fetch] ReadableStreamDefaultReader.read() Errors Unavailable to Response Reader Rejection (#676)
[whatwg/fetch] Allow used body replacement in Request constructor (#675)
[whatwg/xhr] How is the about:blank case in send-non-same-origin supported by the spec? (#194)
Re: [w3c/ServiceWorker] windowClients state change events - loaded/unloaded (#1269)
Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587)
- Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587)
- Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587)
- Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587)
- Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587)
- Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587)
- Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587)
- Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587)
[heycam/webidl] ES bindings for constants on Globals (#528)
- Re: [heycam/webidl] ES bindings for constants on Globals (#528)
- Re: [heycam/webidl] ES bindings for constants on Globals (#528)
- Re: [heycam/webidl] ES bindings for constants on Globals (#528)
Re: [w3c/webcomponents] [templates] Is a global registry of template processors the right idea? (#681)
Re: [whatwg/streams] pipeTo() text appears to say all queued writable chunks must be written on readable error (#738)
[w3c/uievents] Move focus section to HTML (#185)
- Re: [w3c/uievents] Move focus section to HTML (#185)
- Re: [w3c/uievents] Move focus section to HTML (#185)
- Re: [w3c/uievents] Move focus section to HTML (#185)
- Re: [w3c/uievents] Move focus section to HTML (#185)
Re: [w3c/uievents] Figure out what to do with focusin/focusout (#88)
- Re: [w3c/uievents] Figure out what to do with focusin/focusout (#88)
- Re: [w3c/uievents] Figure out what to do with focusin/focusout (#88)
[w3ctag/design-reviews] CSS Selectors 4, :focus-visible. (#233)
[w3ctag/packaging-on-the-web] Ungutted (#36)
[whatwg/fetch] Inconsistency in Request constructor when rewriting a used body (#674)
- Re: [whatwg/fetch] Inconsistency in Request constructor when rewriting a used body (#674)
- Re: [whatwg/fetch] Inconsistency in Request constructor when rewriting a used body (#674)
- Re: [whatwg/fetch] Inconsistency in Request constructor when rewriting a used body (#674)
- Re: [whatwg/fetch] Inconsistency in Request constructor when rewriting a used body (#674)
- Re: [whatwg/fetch] Inconsistency in Request constructor when rewriting a used body (#674)
- Re: [whatwg/fetch] Inconsistency in Request constructor when rewriting a used body (#674)
- Re: [whatwg/fetch] Inconsistency in Request constructor when rewriting a used body (#674)
- Re: [whatwg/fetch] Inconsistency in Request constructor when rewriting a used body (#674)
- Re: [whatwg/fetch] Inconsistency in Request constructor when rewriting a used body (#674)
[w3c/WebPlatformWG] Update 18-03-Web-components.md (#116)
[w3c/WebPlatformWG] Add Salesforce attendees (#115)
[w3c/ServiceWorker] Service Worker handling of first page load subresources (#1282)
Re: [w3c/IndexedDB] Define storage operation of non-trivial StructuredSerializeForStorage records (e.g. Blob/File) (#203)
Re: [w3c/IndexedDB] Security and Web Worker access for IndexedDB (#141)
Re: [w3c/IndexedDB] Add support for URL as one of the basic types like Date (#108)
- Re: [w3c/IndexedDB] Add support for URL as one of the basic types like Date (#108)
- Re: [w3c/IndexedDB] Add support for URL as one of the basic types like Date (#108)
Re: [w3c/uievents-code] Need an implementation report (#20)
- Re: [w3c/uievents-code] Need an implementation report (#20)
- Re: [w3c/uievents-code] Need an implementation report (#20)
- Re: [w3c/uievents-code] Need an implementation report (#20)
- Re: [w3c/uievents-code] Need an implementation report (#20)
- Re: [w3c/uievents-code] Need an implementation report (#20)
- Re: [w3c/uievents-code] Need an implementation report (#20)
- Re: [w3c/uievents-code] Need an implementation report (#20)
[w3c/uievents-code] Move Keyboard Events Code Values to PR (#22)
Re: [w3c/uievents-code] Time to exit CR? (#21)
[w3c/uievents-key] Move Keyboard Events Key Values to PR (#47)
Re: [w3c/uievents-key] Implementation report (#45)
- Re: [w3c/uievents-key] Implementation report (#45)
- Re: [w3c/uievents-key] Implementation report (#45)
- Re: [w3c/uievents-key] Implementation report (#45)
- Re: [w3c/uievents-key] Implementation report (#45)
- Re: [w3c/uievents-key] Implementation report (#45)
Re: [w3c/uievents-key] Time to CR? (#46)
[w3c/WebPlatformWG] Update 18-03-Web-components.md (#114)
- Re: [w3c/WebPlatformWG] Update 18-03-Web-components.md (#114)
- Re: [w3c/WebPlatformWG] Update 18-03-Web-components.md (#114)
[w3c/webcomponents] [Template Instantiation] Review the cloning step (#740)
- Re: [w3c/webcomponents] [Template Instantiation] Review the cloning step (#740)
- Re: [w3c/webcomponents] [Template Instantiation] Review the cloning step (#740)
- Re: [w3c/webcomponents] [Template Instantiation] Review the cloning step (#740)
[whatwg/dom] chrome, doesn't accept preventDefault and stil cancelable is true (#579)
- Re: [whatwg/dom] chrome, doesn't accept preventDefault and still cancelable is true (#579)
- Re: [whatwg/dom] chrome, doesn't accept preventDefault and still cancelable is true (#579)
- Re: [whatwg/dom] chrome, doesn't accept preventDefault and still cancelable is true (#579)
- Re: [whatwg/dom] chrome, doesn't accept preventDefault and still cancelable is true (#579)
Re: [w3c/webcomponents] Having slots as element prevents styling empty containers (#701)
- Re: [w3c/webcomponents] Having slots as element prevents styling empty containers (#701)
- Re: [w3c/webcomponents] Having slots as element prevents styling empty containers (#701)
- Re: [w3c/webcomponents] Having slots as element prevents styling empty containers (#701)
- Re: [w3c/webcomponents] Having slots as element prevents styling empty containers (#701)
- Re: [w3c/webcomponents] Having slots as element prevents styling empty containers (#701)
- Re: [w3c/webcomponents] Having slots as element prevents styling empty containers (#701)
- Re: [w3c/webcomponents] Having slots as element prevents styling empty containers (#701)
[whatwg/dom] Need a method to fire :hover and :active states (#578)
Re: [whatwg/fetch] More informative error types (#526)
[whatwg/dom] Return value for DOMTokenList's replace() (#577)
Re: [heycam/webidl] [wip] First pass at adding internal slots (#495)
Re: [w3c/webcomponents] [templates] What is declareCallback? (#693)
[whatwg/fetch] Bob (#673)
[whatwg/fetch] :read-only and :read-write selectors: Consistency and cross-UA behavior (#672)
- Re: [whatwg/fetch] :read-only and :read-write selectors: Consistency and cross-UA behavior (#672)
- Re: [whatwg/fetch] :read-only and :read-write selectors: Consistency and cross-UA behavior (#672)
- Re: [whatwg/fetch] :read-only and :read-write selectors: Consistency and cross-UA behavior (#672)
Re: [whatwg/fetch] Handling Partial Content / 206 (#144)
- Re: [whatwg/fetch] Handling Partial Content / 206 (#144)
- Re: [whatwg/fetch] Handling Partial Content / 206 (#144)
- Re: [whatwg/fetch] Handling Partial Content / 206 (#144)
- Re: [whatwg/fetch] Handling Partial Content / 206 (#144)
Re: [w3c/manifest] feat: add support for adaptive icons (#563)
[w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657)
- Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657)
- Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657)
- Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657)
- Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657)
- Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657)
- Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657)
- Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657)
- Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657)
- Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657)
- Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657)
- Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657)
- Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657)
- Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657)
- Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657)
Re: [whatwg/fetch] Allow range header to be set by APIs (#560)
Re: [heycam/webidl] Exposing an interface "on all globals" (#468)
- Re: [heycam/webidl] Exposing an interface "on all globals" (#468)
- Re: [heycam/webidl] Exposing an interface "on all globals" (#468)
- Re: [heycam/webidl] Exposing an interface "on all globals" (#468)
- Re: [heycam/webidl] Exposing an interface "on all globals" (#468)
- Re: [heycam/webidl] Exposing an interface "on all globals" (#468)
Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447)
- Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447)
- Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447)
- Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447)
- Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447)
- Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447)
[w3c/gamepad] spec vibrationActuator gamepad extension (#68)
- Re: [w3c/gamepad] spec vibrationActuator gamepad extension (#68)
- Re: [w3c/gamepad] spec vibrationActuator gamepad extension (#68)
- Re: [w3c/gamepad] spec vibrationActuator gamepad extension (#68)
- Re: [w3c/gamepad] spec vibrationActuator gamepad extension (#68)
- Re: [w3c/gamepad] spec vibrationActuator gamepad extension (#68)
- Re: [w3c/gamepad] spec vibrationActuator gamepad extension (#68)
Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
Re: [w3c/manifest] Clarify rule of navigating away from the navigation scope (#646)
Re: [w3c/manifest] Add info push notifications to extensions registry (#529)
Re: [w3c/manifest] Allow app to load in parallel to splash screen (#559)
Re: [w3c/manifest] Status section has misleading info on filing bugs (#489)
Re: [w3c/manifest] Add shortcuts (#575)
Re: [w3c/manifest] FR: Context menus on app icons. (#582)
Re: [w3c/manifest] Don't use enums, because they throw (#633)
Re: [w3c/manifest] Add a means to associate a PWA with a file extension (#626)
- Re: [w3c/manifest] Add a means to associate a PWA with a file extension (#626)
- Re: [w3c/manifest] Add a means to associate a PWA with a file extension (#626)
- Re: [w3c/manifest] Add a means to associate a PWA with a file extension (#626)
- Re: [w3c/manifest] Add a means to associate a PWA with a file extension (#626)
- Re: [w3c/manifest] Add a means to associate a PWA with a file extension (#626)
- Re: [w3c/manifest] Add a means to associate a PWA with a file extension (#626)
- Re: [w3c/manifest] Add a means to associate a PWA with a file extension (#626)
- Re: [w3c/manifest] Add a means to associate a PWA with a file extension (#626)
- Re: [w3c/manifest] Add a means to associate a PWA with a file extension (#626)
Re: [w3c/manifest] Use data-cite for all references (#573)
- Re: [w3c/manifest] Use data-cite for all references (#573)
- Re: [w3c/manifest] Use data-cite for all references (#573)
Re: [w3c/manifest] Remove Trim() logic on string members (#620)
- Re: [w3c/manifest] Remove Trim() logic on string members (#620)
- Re: [w3c/manifest] Remove Trim() logic on string members (#620)
[heycam/webidl] Add [Exposed=*] to expose on all globals (#526)
- Re: [heycam/webidl] Add [Exposed=*] to expose on all globals (#526)
- Re: [heycam/webidl] Add [Exposed=*] to expose on all globals (#526)
- Re: [heycam/webidl] Add [Exposed=*] to expose on all globals (#526)
- Re: [heycam/webidl] Add [Exposed=*] to expose on all globals (#526)
- Re: [heycam/webidl] Add [Exposed=*] to expose on all globals (#526)
- Re: [heycam/webidl] Add [Exposed=*] to expose on all globals (#526)
- Re: [heycam/webidl] Add [Exposed=*] to expose on all globals (#526)
- Re: [heycam/webidl] Add [Exposed=*] to expose on all globals (#526)
- Re: [heycam/webidl] Add [Exposed=*] to expose on all globals (#526)
[heycam/webidl] Add bigint type (#525)
- Re: [heycam/webidl] Add bigint type (#525)
- Re: [heycam/webidl] Add bigint type (#525)
- Re: [heycam/webidl] Add bigint type (#525)
- Re: [heycam/webidl] Add bigint type (#525)
- Re: [heycam/webidl] Add bigint type (#525)
- Re: [heycam/webidl] Add bigint type (#525)
- Re: [heycam/webidl] Add bigint type (#525)
- Re: [heycam/webidl] Add bigint type (#525)
- Re: [heycam/webidl] Add bigint type (#525)
- Re: [heycam/webidl] Add bigint type (#525)
- Re: [heycam/webidl] Add bigint type (#525)
- Re: [heycam/webidl] Add bigint type (#525)
[w3c/editing] input setSelection() method workflow, when text overflows input container (#173)
[w3c/clipboard-apis] "context is editable" when firing events needs to be defined (#71)
[w3c/clipboard-apis] The "focused node" when determining event target needs to be defined (#70)
Re: [heycam/webidl] Figure-out what supporting Array-subclassing implies (#345)
[w3c/ServiceWorker] Update orphaned references in Query Cache algo (#1281)
- Re: [w3c/ServiceWorker] Update orphaned references in Query Cache algo (#1281)
- Re: [w3c/ServiceWorker] Update orphaned references in Query Cache algo (#1281)
- Re: [w3c/ServiceWorker] Update orphaned references in Query Cache algo (#1281)
- Re: [w3c/ServiceWorker] Update orphaned references in Query Cache algo (#1281)
[whatwg/streams] Interface for push based ReadableStream? (#889)
- Re: [whatwg/streams] Interface for push based ReadableStream? (#889)
- Re: [whatwg/streams] Interface for push based ReadableStream? (#889)
- Re: [whatwg/streams] Interface for push based ReadableStream? (#889)
- Re: [whatwg/streams] Interface for push based ReadableStream? (#889)
- Re: [whatwg/streams] Interface for push based ReadableStream? (#889)
- Re: [whatwg/streams] Interface for push based ReadableStream? (#889)
Re: [w3ctag/packaging-on-the-web] ECMAScript 2015 is not Draft anymore (#27)
[w3c/manifest] Improve references and minor fixups (#656)
- Re: [w3c/manifest] Improve references and minor fixups (#656)
- Re: [w3c/manifest] Improve references and minor fixups (#656)
- Re: [w3c/manifest] Improve references and minor fixups (#656)
- Re: [w3c/manifest] Improve references and minor fixups (#656)
- Re: [w3c/manifest] Improve references and minor fixups (#656)
- Re: [w3c/manifest] Improve references and minor fixups (#656)
- Re: [w3c/manifest] Improve references and minor fixups (#656)
- Re: [w3c/manifest] Improve references and minor fixups (#656)
- Re: [w3c/manifest] Improve references and minor fixups (#656)
- Re: [w3c/manifest] Improve references and minor fixups (#656)
- Re: [w3c/manifest] Improve references and minor fixups (#656)
- Re: [w3c/manifest] Improve references and minor fixups (#656)
- Re: [w3c/manifest] Improve references and minor fixups (#656)
- Re: [w3c/manifest] Improve references and minor fixups (#656)
- Re: [w3c/manifest] Improve references and minor fixups (#656)
- Re: [w3c/manifest] Improve references and minor fixups (#656)
- Re: [w3c/manifest] Improve references and minor fixups (#656)
- Re: [w3c/manifest] Improve references and minor fixups (#656)
- Re: [w3c/manifest] Improve references and minor fixups (#656)
- Re: [w3c/manifest] Improve references and minor fixups (#656)
[w3c/WebPlatformWG] Add declarative Shadow DOM to the Agenda (#113)
Re: [whatwg/fetch] CORS protocol and HTTP caches (#402)
[w3c/WebPlatformWG] Add Chris Joel to confirmed attendees (#112)
[whatwg/streams] Fix miscellaneous spelling mistakes (#888)
- Re: [whatwg/streams] Fix miscellaneous spelling mistakes (#888)
- Re: [whatwg/streams] Fix miscellaneous spelling mistakes (#888)
[w3c/WebPlatformWG] Add tkent-google (#111)
Re: [w3c/ServiceWorker] Consider providing `navigation` event (#1028)
[w3c/ServiceWorker] Query Cache algorithm contains orphaned 'f' references (#1280)
- Re: [w3c/ServiceWorker] Query Cache algorithm contains orphaned 'f' references (#1280)
- Re: [w3c/ServiceWorker] Query Cache algorithm contains orphaned 'f' references (#1280)
- Re: [w3c/ServiceWorker] Query Cache algorithm contains orphaned 'f' references (#1280)
Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550)
[whatwg/streams] Editorial: fix some double-word typos (#887)
- Re: [whatwg/streams] Editorial: fix some double-word typos (#887)
- Re: [whatwg/streams] Editorial: fix some double-word typos (#887)
Re: [whatwg/streams] Bikeshed warnings (#869)
[whatwg/xhr] XMLHttpRequest (#193)
- Re: [whatwg/xhr] XMLHttpRequest (#193)
- Re: [whatwg/xhr] XMLHttpRequest (#193)
- Re: [whatwg/xhr] XMLHttpRequest (#193)
- Re: [whatwg/xhr] XMLHttpRequest (#193)
[w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739)
- Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739)
- Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739)
- Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739)
- Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739)
- Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739)
- Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739)
- Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739)
- Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739)
- Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739)
- Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739)
- Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739)
- Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739)
- Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739)
- Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739)
- Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739)
- Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739)
- Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739)
- Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739)
- Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739)
- Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739)
- Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739)
[w3c/clipboard-apis] The "context is editable"-condition in the fire event-algorithm needs clarification (#69)
- Re: [w3c/clipboard-apis] The "context is editable"-condition in the fire event-algorithm needs clarification (#69)
- Re: [w3c/clipboard-apis] The "context is editable"-condition in the fire event-algorithm needs clarification (#69)
Re: [w3c/selection-api] No definition of hidden selections (#94)
Re: [w3c/selection-api] Background section is a mess (#84)
Re: [w3c/manifest] Fix references to lower case in spec (#602)
Re: [w3c/manifest] Use Infra spec for iterations (#621)
[whatwg/dom] Run insertion steps after DocumentFragment insertion completes (#576)
- Re: [whatwg/dom] Run insertion steps after DocumentFragment insertion completes (#576)
- Re: [whatwg/dom] Run insertion steps after DocumentFragment insertion completes (#576)
- Re: [whatwg/dom] Run insertion steps after DocumentFragment insertion completes (#576)
- Re: [whatwg/dom] Run insertion steps after DocumentFragment insertion completes (#576)
- Re: [whatwg/dom] Run insertion steps after DocumentFragment insertion completes (#576)
- Re: [whatwg/dom] Run insertion steps after DocumentFragment insertion completes (#576)
- Re: [whatwg/dom] Run insertion steps after DocumentFragment insertion completes (#576)
- Re: [whatwg/dom] Run insertion steps after DocumentFragment insertion completes (#576)
[w3c/manifest] Use infra spec and data-cite (#655)
- Re: [w3c/manifest] Use infra spec and data-cite (#655)
- Re: [w3c/manifest] Use infra spec and data-cite (#655)
- Re: [w3c/manifest] Use infra spec and data-cite (#655)
- Re: [w3c/manifest] Use infra spec and data-cite (#655)
- Re: [w3c/manifest] Use infra spec and data-cite (#655)
Re: [w3c/webcomponents] Which standard defines :defined (#665)
- Re: [w3c/webcomponents] Which standard defines :defined (#665)
- Re: [w3c/webcomponents] Which standard defines :defined (#665)
- Re: [w3c/webcomponents] Which standard defines :defined (#665)
- Re: [w3c/webcomponents] Which standard defines :defined (#665)
Re: [w3c/ServiceWorker] Should mixed content always be blocked? (#813)
Re: [whatwg/fetch] Should Content-Type header be stripped when redirecting from POST to GET? (#609)
- Re: [whatwg/fetch] Should Content-Type header be stripped when redirecting from POST to GET? (#609)
- Re: [whatwg/fetch] Should Content-Type header be stripped when redirecting from POST to GET? (#609)
- Re: [whatwg/fetch] Should Content-Type header be stripped when redirecting from POST to GET? (#609)
- Re: [whatwg/fetch] Should Content-Type header be stripped when redirecting from POST to GET? (#609)
[w3ctag/design-reviews] BCP56bis (#232)
[whatwg/xhr] Where in the spec is the content-type header filtered out on 301/302/303 redirects? (#192)
- Re: [whatwg/xhr] Where in the spec is the content-type header filtered out on 301/302/303 redirects? (#192)
- Re: [whatwg/xhr] Where in the spec is the content-type header filtered out on 301/302/303 redirects? (#192)
- Re: [whatwg/xhr] Where in the spec is the content-type header filtered out on 301/302/303 redirects? (#192)
- Re: [whatwg/xhr] Where in the spec is the content-type header filtered out on 301/302/303 redirects? (#192)
- Re: [whatwg/xhr] Where in the spec is the content-type header filtered out on 301/302/303 redirects? (#192)
Re: [w3c/webcomponents] Support `>>>` combinator in static profile (#78)
- Re: [w3c/webcomponents] Support `>>>` combinator in static profile (#78)
- Re: [w3c/webcomponents] Support `>>>` combinator in static profile (#78)
Re: [w3c/webcomponents] Need callback for form submit data (#187)
- Re: [w3c/webcomponents] Need callback for form submit data (#187)
- Re: [w3c/webcomponents] Need callback for form submit data (#187)
- Re: [w3c/webcomponents] Need callback for form submit data (#187)
- Re: [w3c/webcomponents] Need callback for form submit data (#187)
- Re: [w3c/webcomponents] Need callback for form submit data (#187)
- Re: [w3c/webcomponents] Need callback for form submit data (#187)
- Re: [w3c/webcomponents] Need callback for form submit data (#187)
- Re: [w3c/webcomponents] Need callback for form submit data (#187)
- Re: [w3c/webcomponents] Need callback for form submit data (#187)
- Re: [w3c/webcomponents] Need callback for form submit data (#187)
- Re: [w3c/webcomponents] Need callback for form submit data (#187)
- Re: [w3c/webcomponents] Need callback for form submit data (#187)
- Re: [w3c/webcomponents] Need callback for form submit data (#187)
- Re: [w3c/webcomponents] Need callback for form submit data (#187)
- Re: [w3c/webcomponents] Need callback for form submit data (#187)
- Re: [w3c/webcomponents] Need callback for form submit data (#187)
- Re: [w3c/webcomponents] Need callback for form submit data (#187)
[w3c/uievents] May the state of modifier keys influence MouseEvent.button? (#184)
[w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738)
- Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738)
- Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738)
- Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738)
- Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738)
- Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738)
- Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738)
- Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738)
- Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738)
- Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738)
- Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738)
- Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738)
- Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738)
- Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738)
- Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738)
- Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738)
- Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738)
- Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738)
- Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738)
- Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738)
- Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738)
- Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738)
- Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738)
- Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738)
Re: [w3c/webcomponents] Interface/class-based selector (#719)
- Re: [w3c/webcomponents] Interface/class-based selector (#719)
- Re: [w3c/webcomponents] Interface/class-based selector (#719)
- Re: [w3c/webcomponents] Interface/class-based selector (#719)
- Re: [w3c/webcomponents] Interface/class-based selector (#719)
- Re: [w3c/webcomponents] Interface/class-based selector (#719)
- Re: [w3c/webcomponents] Interface/class-based selector (#719)
- Re: [w3c/webcomponents] Interface/class-based selector (#719)
Re: [w3c/webcomponents] <iframe> and the History API (#184)
Re: [w3c/webcomponents] {DocumentOrShadowRoot or Slot}.activePath (#479)
Re: [w3ctag/design-reviews] Request to review First Paint Timing (#177)
Re: [whatwg/dom] Batched MutationObserver callbacks make it possibly difficult to reduce changes. (#484)
Re: [whatwg/encoding] Make TextEncoder and TextDecoder be transform streams (#127)
[whatwg/dom] Hook for SVG and HTML script element insertion (#575)
- Re: [whatwg/dom] Hook for SVG and HTML script element insertion (#575)
- Re: [whatwg/dom] Hook for SVG and HTML script element insertion (#575)
- Re: [whatwg/dom] Hook for SVG and HTML script element insertion (#575)
- Re: [whatwg/dom] Hook for SVG and HTML script element insertion (#575)
- Re: [whatwg/dom] Hook for SVG and HTML script element insertion (#575)
[heycam/webidl] Change dictionary section to encourage Infra wording (#524)
[w3c/manifest] Update the Service Worker object to not conflict with SW WebIDL (#654)
- Re: [w3c/manifest] Update the Service Worker object to not conflict with SW WebIDL (#654)
- Re: [w3c/manifest] Update the Service Worker object to not conflict with SW WebIDL (#654)
- Re: [w3c/manifest] Update the Service Worker object to not conflict with SW WebIDL (#654)
- Re: [w3c/manifest] Update the Service Worker object to not conflict with SW WebIDL (#654)
[whatwg/dom] Editorial: consider linking "present" consistently (#574)
- Re: [whatwg/dom] Editorial: consider linking "present" consistently (#574)
- Re: [whatwg/dom] Editorial: consider linking "present" consistently (#574)
- Re: [whatwg/dom] Editorial: consider linking "present" consistently (#574)
[whatwg/dom] Align with Selectors (#573)
[w3c/WebPlatformWG] Add references to Template instantiation & HTML modules (#110)
- Re: [w3c/WebPlatformWG] Add references to Template instantiation & HTML modules (#110)
- Re: [w3c/WebPlatformWG] Add references to Template instantiation & HTML modules (#110)
- Re: [w3c/WebPlatformWG] Add references to Template instantiation & HTML modules (#110)
[w3c/WebPlatformWG] Update Attending (#109)
Re: [w3c/webcomponents] Consider adding a childrenChangedCallback or something (#619)
- Re: [w3c/webcomponents] Consider adding a childrenChangedCallback or something (#619)
- Re: [w3c/webcomponents] Consider adding a childrenChangedCallback or something (#619)
- Re: [w3c/webcomponents] Consider adding a childrenChangedCallback or something (#619)
[whatwg/dom] Allow createElement/createElementNS()'s dictionary argument to be a s… (#572)
- Re: [whatwg/dom] Allow createElement/createElementNS()'s dictionary argument to be a s… (#572)
- Re: [whatwg/dom] Allow createElement/createElementNS()'s dictionary argument to be a s… (#572)
- Re: [whatwg/dom] Allow createElement/createElementNS()'s dictionary argument to be a s… (#572)
- Re: [whatwg/dom] Allow createElement/createElementNS()'s dictionary argument to be a s… (#572)
- Re: [whatwg/dom] Allow createElement/createElementNS()'s dictionary argument to be a s… (#572)
- Re: [whatwg/dom] Allow createElement/createElementNS()'s dictionary argument to be a s… (#572)
- Re: [whatwg/dom] Allow createElement/createElementNS()'s dictionary argument to be a s… (#572)
- Re: [whatwg/dom] Allow createElement/createElementNS()'s dictionary argument to be a s… (#572)
- Re: [whatwg/dom] Allow createElement/createElementNS()'s dictionary argument to be a s… (#572)
Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544)
- Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544)
- Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544)
- Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544)
- Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544)
Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300)
- Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300)
- Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300)
- Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300)
- Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300)
- Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300)
Re: [w3c/webcomponents] Close this repository in the future (#652)
- Re: [w3c/webcomponents] Close this repository in the future (#652)
- Re: [w3c/webcomponents] Close this repository in the future (#652)
- Re: [w3c/webcomponents] Close this repository in the future (#652)
- Re: [w3c/webcomponents] Close this repository in the future (#652)
- Re: [w3c/webcomponents] Close this repository in the future (#652)
- Re: [w3c/webcomponents] Close this repository in the future (#652)
- Re: [w3c/webcomponents] Close this repository in the future (#652)
[w3c/IndexedDB] Allow BigInts as IndexedDB keys (#231)
- Re: [w3c/IndexedDB] Allow BigInts as IndexedDB keys (#231)
- Re: [w3c/IndexedDB] Allow BigInts as IndexedDB keys (#231)
- Re: [w3c/IndexedDB] Allow BigInts as IndexedDB keys (#231)
- Re: [w3c/IndexedDB] Allow BigInts as IndexedDB keys (#231)
Re: [w3c/FileAPI] Remove definition of Blob.close() and all related terms. (#68)
- Re: [w3c/FileAPI] Remove definition of Blob.close() and all related terms. (#68)
- Re: [w3c/FileAPI] Remove definition of Blob.close() and all related terms. (#68)
- Re: [w3c/FileAPI] Remove definition of Blob.close() and all related terms. (#68)
- Re: [w3c/FileAPI] Remove definition of Blob.close() and all related terms. (#68)
- Re: [w3c/FileAPI] Remove definition of Blob.close() and all related terms. (#68)
- Re: [w3c/FileAPI] Remove definition of Blob.close() and all related terms. (#68)
- Re: [w3c/FileAPI] Remove definition of Blob.close() and all related terms. (#68)
[w3c/uievents] Declare keypress event should be fired when pressing Enter, Shift + Enter and Ctrl + Enter (#183)
Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640)
- Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640)
- Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640)
- Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640)
Re: [w3c/webcomponents] Add <a> to safelist of elements that can call attachShadowRoot (#511)
- Re: [w3c/webcomponents] Add <a> to safelist of elements that can call attachShadowRoot (#511)
- Re: [w3c/webcomponents] Add <a> to safelist of elements that can call attachShadowRoot (#511)
- Re: [w3c/webcomponents] Add <a> to safelist of elements that can call attachShadowRoot (#511)
[whatwg/dom] Extend `attachShadow()` safelist (#571)
- Re: [whatwg/dom] Extend `attachShadow()` safelist (#571)
- Re: [whatwg/dom] Extend `attachShadow()` safelist (#571)
- Re: [whatwg/dom] Extend `attachShadow()` safelist (#571)
Re: [w3c/webcomponents] aggravate => aggregate (#724)
Re: [w3c/webcomponents] Detecting finally-distributed nodes. (#675)
Re: [whatwg/dom] Proposal: DOMChangeList (#270)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270)
Re: [w3c/webcomponents] Custom Element - untrackable upgrade (#671)
- Re: [w3c/webcomponents] Custom Element - untrackable upgrade (#671)
- Re: [w3c/webcomponents] Custom Element - untrackable upgrade (#671)
- Re: [w3c/webcomponents] Custom Element - untrackable upgrade (#671)
Re: [w3c/webcomponents] Unexpected upgrade timing when appending an element and script together (#606)
- Re: [w3c/webcomponents] Unexpected upgrade timing when appending an element and script together (#606)
- Re: [w3c/webcomponents] Unexpected upgrade timing when appending an element and script together (#606)
- Re: [w3c/webcomponents] Unexpected upgrade timing when appending an element and script together (#606)
- Re: [w3c/webcomponents] Unexpected upgrade timing when appending an element and script together (#606)
- Re: [w3c/webcomponents] Unexpected upgrade timing when appending an element and script together (#606)
Re: [w3c/webcomponents] ARIA custom element API (#159)
Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567)
- Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567)
- Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567)
- Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567)
Re: [w3c/webcomponents] Should ARIA 2.0 have a role corresponding to every HTML element? (#552)
- Re: [w3c/webcomponents] Should ARIA 2.0 have a role corresponding to every HTML element? (#552)
- Re: [w3c/webcomponents] Should ARIA 2.0 have a role corresponding to every HTML element? (#552)
Re: [w3c/clipboard-apis] Fix algorithm for firing a clipboard event (11619a7)
Re: [w3c/webcomponents] The way to access current script or current root, from Shadow DOM (#717)
- Re: [w3c/webcomponents] The way to access current script or current root, from Shadow DOM (#717)
- Re: [w3c/webcomponents] The way to access current script or current root, from Shadow DOM (#717)
- Re: [w3c/webcomponents] The way to access current script or current root, from Shadow DOM (#717)
- Re: [w3c/webcomponents] The way to access current script or current root, from Shadow DOM (#717)
- Re: [w3c/webcomponents] The way to access current script or current root, from Shadow DOM (#717)
- Re: [w3c/webcomponents] The way to access current script or current root, from Shadow DOM (#717)
- Re: [w3c/webcomponents] The way to access current script or current root, from Shadow DOM (#717)
Re: [w3c/webcomponents] Add a CSS subtype selector. (#719)
[whatwg/xhr] The logic in the WPT send-authentication-competing-names-passwords.htm does not match the spec. (#191)
Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165)
[w3c/webcomponents] Some sort of guarantee on upgrade order? (#737)
- Re: [w3c/webcomponents] Some sort of guarantee on custom element lifecycle order of events (#737)
- Re: [w3c/webcomponents] Some sort of guarantee on custom element lifecycle order of events (#737)
- Re: [w3c/webcomponents] Some sort of guarantee on custom element lifecycle order of events (#737)
- Re: [w3c/webcomponents] Some sort of guarantee on custom element lifecycle order of events (#737)
- Re: [w3c/webcomponents] Some sort of guarantee on custom element lifecycle order of events (#737)
- Re: [w3c/webcomponents] Some sort of guarantee on custom element lifecycle order of events (#737)
Re: [whatwg/dom] MutationObserver needs an equivalent of disconnected & connected callbacks (#533)
- Re: [whatwg/dom] MutationObserver needs an equivalent of disconnected & connected callbacks (#533)
- Re: [whatwg/dom] MutationObserver needs an equivalent of disconnected & connected callbacks (#533)
- Re: [whatwg/dom] MutationObserver needs an equivalent of disconnected & connected callbacks (#533)
- Re: [whatwg/dom] MutationObserver needs an equivalent of disconnected & connected callbacks (#533)
- Re: [whatwg/dom] MutationObserver needs an equivalent of disconnected & connected callbacks (#533)
Re: [w3c/webcomponents] components v1 native implementation - inner components problem (#615)
Re: [w3c/webcomponents] Is there a way to retrieve the localName from a custom element constructor? (#566)
- Re: [w3c/webcomponents] Is there a way to retrieve the localName from a custom element constructor? (#566)
- Re: [w3c/webcomponents] Is there a way to retrieve the localName from a custom element constructor? (#566)
Re: [w3c/webcomponents] Bulk property updates (#718)
Re: [w3c/webcomponents] Undefined specification for @keyframe scope on slotted content (#715)
- Re: [w3c/webcomponents] Undefined specification for @keyframe scope on slotted content (#715)
- Re: [w3c/webcomponents] Undefined specification for @keyframe scope on slotted content (#715)
- Re: [w3c/webcomponents] Undefined specification for @keyframe scope on slotted content (#715)
- Re: [w3c/webcomponents] Undefined specification for @keyframe scope on slotted content (#715)
- Re: [w3c/webcomponents] Undefined specification for @keyframe scope on slotted content (#715)
Re: [w3c/webcomponents] Make custom elements w/ shadowRoot { display: contents } by default (#723)
- Re: [w3c/webcomponents] Make custom elements w/ shadowRoot { display: contents } by default (#723)
- Re: [w3c/webcomponents] Make custom elements w/ shadowRoot { display: contents } by default (#723)
- Re: [w3c/webcomponents] Make custom elements w/ shadowRoot { display: contents } by default (#723)
- Re: [w3c/webcomponents] Make custom elements w/ shadowRoot { display: contents } by default (#723)
Re: [w3c/webcomponents] Disconnected Events (#678)
Re: [w3c/webcomponents] fullscreenchange should be dispatched on each ancestor shadow root (#614)
Re: [w3c/webcomponents] [IDEA] deferred upgrade for Custom Elements. (#559)
- Re: [w3c/webcomponents] [IDEA] deferred upgrade for Custom Elements. (#559)
- Re: [w3c/webcomponents] [IDEA] deferred upgrade for Custom Elements. (#559)
[w3c/push-api] pushManager.subscribe should replace applicationServerKey if different (#291)
Re: [w3c/webcomponents] Extensibility: How should we best support accessible Custom widgets and interactivity with ARIA? (#553)
Re: [whatwg/encoding] Add LICENSE resource (990e16b)
Re: [heycam/webidl] Remove definition of class strings of default iterator objects (#501)
- Re: [heycam/webidl] Remove definition of class strings of default iterator objects (#501)
- Re: [heycam/webidl] Remove definition of class strings of default iterator objects (#501)
- Re: [heycam/webidl] Remove definition of class strings of default iterator objects (#501)
- Re: [heycam/webidl] Remove definition of class strings of default iterator objects (#501)
Re: [heycam/webidl] State that by default all objects are created in the relevant realm of `this` (#135)
[whatwg/xhr] UnioNas (#190)
Re: [w3c/clipboard-apis] Should clipboard actions consider whether selection has focus? (#57)
[whatwg/streams] Use sentence case, not title case, for headings (#886)
[whatwg/streams] Make the table of contents more useful/less dense (#885)
[w3c/clipboard-apis] Spec does not auto-deploy when changes are made (#68)
- Re: [w3c/clipboard-apis] Spec does not auto-deploy when changes are made (#68)
- Re: [w3c/clipboard-apis] Spec does not auto-deploy when changes are made (#68)
- Re: [w3c/clipboard-apis] Spec does not auto-deploy when changes are made (#68)
Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61)
Re: [w3c/ServiceWorker] Proposal: FetchEvent.navigationLoadType (#1167)
Re: [w3c/gamepad] Timeline to Recommendation? (#61)
[w3c/WebPlatformWG] Add Scoped Custom Element Registries to agenda (#108)
[w3c/IndexedDB] Track ES BigInt work (#230)
- Re: [w3c/IndexedDB] Track ES BigInt work (#230)
- Re: [w3c/IndexedDB] Track ES BigInt work (#230)
- Re: [w3c/IndexedDB] Track ES BigInt work (#230)
- Re: [w3c/IndexedDB] Track ES BigInt work (#230)
- Re: [w3c/IndexedDB] Track ES BigInt work (#230)
- Re: [w3c/IndexedDB] Track ES BigInt work (#230)
[whatwg/fetch] Proposal: Easier request/response rewrites (#671)
- Re: [whatwg/fetch] Proposal: Easier request/response rewrites (#671)
- Re: [whatwg/fetch] Proposal: Easier request/response rewrites (#671)
- Re: [whatwg/fetch] Proposal: Easier request/response rewrites (#671)
- Re: [whatwg/fetch] Proposal: Easier request/response rewrites (#671)
- Re: [whatwg/fetch] Proposal: Easier request/response rewrites (#671)
[whatwg/streams] Fix pipe not correctly waiting for writes to finish (#884)
- Re: [whatwg/streams] Fix pipe not correctly waiting for writes to finish (#884)
- Re: [whatwg/streams] Fix pipe not correctly waiting for writes to finish (#884)
- Re: [whatwg/streams] Fix pipe not correctly waiting for writes to finish (#884)
- Re: [whatwg/streams] Fix pipe not correctly waiting for writes to finish (#884)
- Re: [whatwg/streams] Fix pipe not correctly waiting for writes to finish (#884)
- Re: [whatwg/streams] Fix pipe not correctly waiting for writes to finish (#884)
- Re: [whatwg/streams] Fix pipe not correctly waiting for writes to finish (#884)
- Re: [whatwg/streams] Fix pipe not correctly waiting for writes to finish (#884)
- Re: [whatwg/streams] Fix pipe not correctly waiting for writes to finish (#884)
- Re: [whatwg/streams] Fix pipe not correctly waiting for writes to finish (#884)
- Re: [whatwg/streams] Fix pipe not correctly waiting for writes to finish (#884)
[w3c/clipboard-apis] Should we have an API to return the set of readable/writable data types? (#67)
[heycam/webidl] Return type on identifier-less named/indexed setter is pointless (#523)
- Re: [heycam/webidl] Return type on identifier-less named/indexed setter is pointless (#523)
- Re: [heycam/webidl] Return type on identifier-less named/indexed setter is pointless (#523)
Re: [w3c/clipboard-apis] Make all clipboard events composed by default. (#62)
- Re: [w3c/clipboard-apis] Make all clipboard events composed by default. (#62)
- Re: [w3c/clipboard-apis] Make all clipboard events composed by default. (#62)
- Re: [w3c/clipboard-apis] Make all clipboard events composed by default. (#62)
- Re: [w3c/clipboard-apis] Make all clipboard events composed by default. (#62)
- Re: [w3c/clipboard-apis] Make all clipboard events composed by default. (#62)
- Re: [w3c/clipboard-apis] Make all clipboard events composed by default. (#62)
- Re: [w3c/clipboard-apis] Make all clipboard events composed by default. (#62)
- Re: [w3c/clipboard-apis] Make all clipboard events composed by default. (#62)
Re: [w3c/clipboard-apis] Emphasize visability in the "pick target"-algorithm (#58)
- Re: [w3c/clipboard-apis] Emphasize visability in the "pick target"-algorithm (#58)
- Re: [w3c/clipboard-apis] Emphasize visability in the "pick target"-algorithm (#58)
- Re: [w3c/clipboard-apis] Emphasize visability in the "pick target"-algorithm (#58)
[heycam/webidl] `maplike<>` requires spec authors to interact with a real-deal ES Map object (and others), with unfortunate consequences/complexity (#522)
- Re: [heycam/webidl] `maplike<>` requires spec authors to interact with a real-deal ES Map object (and others), with unfortunate consequences/complexity (#522)
- Re: [heycam/webidl] `maplike<>` requires spec authors to interact with a real-deal ES Map object (and others), with unfortunate consequences/complexity (#522)
- Re: [heycam/webidl] `maplike<>` requires spec authors to interact with a real-deal ES Map object (and others), with unfortunate consequences/complexity (#522)
- Re: [heycam/webidl] `maplike<>` requires spec authors to interact with a real-deal ES Map object (and others), with unfortunate consequences/complexity (#522)
- Re: [heycam/webidl] `maplike<>` requires spec authors to interact with a real-deal ES Map object (and others), with unfortunate consequences/complexity (#522)
[heycam/webidl] [[MapData]] is not a thing (#521)
- Re: [heycam/webidl] [[MapData]] is not a thing (#521)
- Re: [heycam/webidl] [[MapData]] is not a thing (#521)
- Re: [heycam/webidl] [[MapData]] is not a thing (#521)
- Re: [heycam/webidl] [[MapData]] is not a thing (#521)
[w3c/webcomponents] It is unclear how elementFromPoint and elementsFromPoint should work (#736)
- Re: [w3c/webcomponents] It is unclear how elementFromPoint and elementsFromPoint should work (#736)
- Re: [w3c/webcomponents] It is unclear how elementFromPoint and elementsFromPoint should work (#736)
- Re: [w3c/webcomponents] It is unclear how elementFromPoint and elementsFromPoint should work (#736)
- Re: [w3c/webcomponents] It is unclear how elementFromPoint and elementsFromPoint should work (#736)
- Re: [w3c/webcomponents] It is unclear how elementFromPoint and elementsFromPoint should work (#736)
- Re: [w3c/webcomponents] It is unclear how elementFromPoint and elementsFromPoint should work (#736)
[w3c/webcomponents] elementsFromPoint behavior is unclear (#735)
- Re: [w3c/webcomponents] elementsFromPoint behavior is unclear (#735)
- Re: [w3c/webcomponents] elementsFromPoint behavior is unclear (#735)
- Re: [w3c/webcomponents] elementsFromPoint behavior is unclear (#735)
[whatwg/streams] Suppress Bikeshed warnings about <vars> used once (#883)
- Re: [whatwg/streams] Suppress Bikeshed warnings about <vars> used once (#883)
- Re: [whatwg/streams] Suppress Bikeshed warnings about <vars> used once (#883)
- Re: [whatwg/streams] Suppress Bikeshed warnings about <vars> used once (#883)
[w3c/WebPlatformWG] Add Github profile links to attendees (#107)
- Re: [w3c/WebPlatformWG] Add Github profile links to attendees (#107)
- Re: [w3c/WebPlatformWG] Add Github profile links to attendees (#107)
- Re: [w3c/WebPlatformWG] Add Github profile links to attendees (#107)
Re: [w3c/touch-events] Initialize touchList in Chrome (#78)
Re: [w3c/gamepad] Need to spec better support for control mapping (#7)
Re: [w3c/gamepad] Standard mapping image should be described in text (#57)
Re: [w3c/gamepad] Add [Exposed] to all interfaces (#63)
Re: [w3c/gamepad] Only 4 Gamepads? (#52)
Re: [w3c/gamepad] About the id (#65)
Re: [w3c/gamepad] Specify exact length of array returned by Navigator.getGamepads() (#13)
Re: [w3c/gamepad] Order in which index entries should be reused is unspecified (#11)
Re: [w3c/gamepad] Connected Attribute appears to serve no purpose if the Gamepad object is a snapshot (#10)
Re: [w3c/gamepad] It is not defined what the value of Gamepad.index should be after disconnecting the gamepad (#5)
- Re: [w3c/gamepad] It is not defined what the value of Gamepad.index should be after disconnecting the gamepad (#5)
- Re: [w3c/gamepad] It is not defined what the value of Gamepad.index should be after disconnecting the gamepad (#5)
[whatwg/streams] Pipe completes before all writes are finished with preventClose = true (#882)
- Re: [whatwg/streams] Pipe completes before all writes are finished with preventClose = true (#882)
- Re: [whatwg/streams] Pipe completes before all writes are finished with preventClose = true (#882)
- Re: [whatwg/streams] Pipe completes before all writes are finished with preventClose = true (#882)
- Re: [whatwg/streams] Pipe completes before all writes are finished with preventClose = true (#882)
- Re: [whatwg/streams] Pipe completes before all writes are finished with preventClose = true (#882)
- Re: [whatwg/streams] Pipe completes before all writes are finished with preventClose = true (#882)
[w3c/webstorage] Make session/localstorage iteratable (#8)
- Re: [w3c/webstorage] Make session/localstorage iteratable (#8)
- Re: [w3c/webstorage] Make session/localstorage iteratable (#8)
[whatwg/dom] Define a target concept that Event.target and Event.srcElement reflect (#570)
[w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734)
- Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734)
- Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734)
- Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734)
- Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734)
- Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734)
- Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734)
- Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734)
- Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734)
- Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734)
- Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734)
- Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734)
- Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734)
- Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734)
- Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734)
- Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734)
- Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734)
- Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734)
- Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734)
- Re: [w3c/webcomponents] Please add <map> to the list of elements that support attachShadow(init) (#734)
[w3c/clipboard-apis] When called without gesture, return an error describing rejection (#66)
- Re: [w3c/clipboard-apis] When called without gesture, return an error describing rejection (#66)
- Re: [w3c/clipboard-apis] When called without gesture, return an error describing rejection (#66)
Re: [whatwg/dom] Add window.event, event.srcElement, event.returnValue as a legacy compat requirements (#407)
- Re: [whatwg/dom] Add window.event, event.srcElement, event.returnValue as a legacy compat requirements (#407)
- Re: [whatwg/dom] Add window.event, event.srcElement, event.returnValue as a legacy compat requirements (#407)
- Re: [whatwg/dom] Add window.event, event.srcElement, event.returnValue as a legacy compat requirements (#407)
- Re: [whatwg/dom] Add window.event, event.srcElement, event.returnValue as a legacy compat requirements (#407)
- Re: [whatwg/dom] Add window.event, event.srcElement, event.returnValue as a legacy compat requirements (#407)
- Re: [whatwg/dom] Add window.event, event.srcElement, event.returnValue as a legacy compat requirements (#407)
- Re: [whatwg/dom] Add window.event, event.srcElement, event.returnValue as a legacy compat requirements (#407)
- Re: [whatwg/dom] Add window.event, event.srcElement, event.returnValue as a legacy compat requirements (#407)
[w3c/permissions] Preventing blackmail (#171)
- Re: [w3c/permissions] Preventing blackmail (#171)
- Re: [w3c/permissions] Preventing blackmail (#171)
- Re: [w3c/permissions] Preventing blackmail (#171)
- Re: [w3c/permissions] Preventing blackmail (#171)
- Re: [w3c/permissions] Preventing blackmail (#171)
- Re: [w3c/permissions] Preventing blackmail (#171)
- Re: [w3c/permissions] Preventing blackmail (#171)
- Re: [w3c/permissions] Preventing blackmail (#171)
- Re: [w3c/permissions] Preventing blackmail (#171)
Re: [heycam/webidl] Please prefix getter/setter/callback interface with legacy so it's clear they are (#100)
- Re: [heycam/webidl] Please prefix getter/setter/callback interface with legacy so it's clear they are (#100)
- Re: [heycam/webidl] Please prefix getter/setter/callback interface with legacy so it's clear they are (#100)
- Re: [heycam/webidl] Please prefix getter/setter/callback interface with legacy so it's clear they are (#100)
- Re: [heycam/webidl] Please prefix getter/setter/callback interface with legacy so it's clear they are (#100)
- Re: [heycam/webidl] Please prefix getter/setter/callback interface with legacy so it's clear they are (#100)
Re: [w3c/manifest] Richer splash screen backgrounds (#589)
Re: [w3c/manifest] feat: Add splashscreens member + purpose (closes #510) (#530)
[w3c/permissions] PermissionStatus's memory management is unclear (#170)
Re: [whatwg/dom] Define dataset as a mixin for HTMLElement and SVGElement (#280)
- Re: [whatwg/dom] Define dataset as a mixin for HTMLElement and SVGElement (#280)
- Re: [whatwg/dom] Define dataset as a mixin for HTMLElement and SVGElement (#280)
[whatwg/streams] Fix example for identity transform (#881)
- Re: [whatwg/streams] Fix example for identity transform (#881)
- Re: [whatwg/streams] Fix example for identity transform (#881)
- Re: [whatwg/streams] Fix example for identity transform (#881)
[w3c/uievents] single character typo fix (#182)
Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505)
- Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505)
- Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505)
- Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505)
- Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505)
- Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505)
- Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505)
- Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505)
- Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505)
- Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505)
- Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505)
Re: [w3c/ServiceWorker] passthrough service worker can break sites using redirected stylesheets (#757)
[w3c/WebPlatformWG] Add Diego Ferreiro to Web Components F2F 2018 attendees (#106)
Re: [w3c/webcomponents] Why do we really need hyphens? (#658)
- Re: [w3c/webcomponents] Why do we really need hyphens? (#658)
- Re: [w3c/webcomponents] Why do we really need hyphens? (#658)
- Re: [w3c/webcomponents] Why do we really need hyphens? (#658)
Re: [w3c/webcomponents] Add a strawman design for custom elements (d3f89c8)
[whatwg/streams] Meta: Fix CONTRIBUTING.md link (#880)
- Re: [whatwg/streams] Meta: Fix CONTRIBUTING.md link (#880)
- Re: [whatwg/streams] Meta: Fix CONTRIBUTING.md link (#880)
- Re: [whatwg/streams] Meta: Fix CONTRIBUTING.md link (#880)
- Re: [whatwg/streams] Meta: Fix CONTRIBUTING.md link (#880)
[whatwg/url] "Let pointer be a pointer to first code point in..." (#373)
- Re: [whatwg/url] "Let pointer be a pointer to first code point in..." (#373)
- Re: [whatwg/url] "Let pointer be a pointer to first code point in..." (#373)
- Re: [whatwg/url] "Let pointer be a pointer to first code point in..." (#373)
[w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
- Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
- Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
- Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
- Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
- Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
- Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
- Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
- Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
- Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
- Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
- Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
- Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
- Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
- Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
- Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
- Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
- Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
- Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
- Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
- Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
- Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
- Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
- Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
- Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
- Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
- Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
- Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
- Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
- Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
- Re: [w3c/FileAPI] Support `Response` in `URL.createObjectURL` (#97)
Re: [w3c/FileAPI] Async createObjectURL (#84)
Re: [heycam/webidl] Prototype of @@unscopable object (#496)
[whatwg/xhr] Please add followRedirects=true/false to XMLHttpRequest specification (#189)
- Re: [whatwg/xhr] Please add followRedirects=true/false to XMLHttpRequest specification (#189)
- Re: [whatwg/xhr] Please add followRedirects=true/false to XMLHttpRequest specification (#189)
[w3c/uievents] Needs alternative WheelEvent.deltaMode, WheelEvent.delat(X|Y|Z) (#181)
Re: [w3c/ServiceWorker] Expose GeoLocation to workers (#745)
- Re: [w3c/ServiceWorker] Expose GeoLocation to workers (#745)
- Re: [w3c/ServiceWorker] Expose GeoLocation to workers (#745)
- Re: [w3c/ServiceWorker] Expose GeoLocation to workers (#745)
- Re: [w3c/ServiceWorker] Expose GeoLocation to workers (#745)
- Re: [w3c/ServiceWorker] Expose GeoLocation to workers (#745)
- Re: [w3c/ServiceWorker] Expose GeoLocation to workers (#745)
- Re: [w3c/ServiceWorker] Expose GeoLocation to workers (#745)
Re: [w3c/webcomponents] Proposal: Allow custom elements to be in any namespace (#634)
Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)
- Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)
- Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)
- Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)
- Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)
- Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)
- Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)
- Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)
- Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)
- Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)
- Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)
- Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)
- Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)
- Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)
- Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)
- Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)
- Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)
Re: [w3c/webcomponents] Interfaces for web components (#725)
- Re: [w3c/webcomponents] Interfaces for web components (#725)
- Re: [w3c/webcomponents] Interfaces for web components (#725)
Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)
- Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)
- Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)
Re: [w3ctag/design-reviews] Request review of (text only) Async Clipboard API (#222)
- Re: [w3ctag/design-reviews] Request review of (text only) Async Clipboard API (#222)
- Re: [w3ctag/design-reviews] Request review of (text only) Async Clipboard API (#222)
- Re: [w3ctag/design-reviews] Request review of (text only) Async Clipboard API (#222)
[w3c/ServiceWorker] ready promise is kind of weird after you call unregister() (#1279)
[w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278)
- Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278)
- Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278)
- Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278)
- Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278)
- Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278)
- Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278)
- Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278)
- Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278)
- Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278)
- Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278)
- Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278)
- Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278)
- Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278)
- Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278)
- Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278)
- Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278)
- Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278)
- Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278)
- Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278)
- Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278)
- Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278)
- Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278)
- Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278)
[whatwg/streams] Write tests for the fixes in #870 (#879)
- Re: [whatwg/streams] Write tests for the fixes in #870 (#879)
- Re: [whatwg/streams] Write tests for the fixes in #870 (#879)
Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
[whatwg/streams] Disambiguate links to "resolve" (#878)
Re: [heycam/webidl] Require tests for PR/issues? (#268)
[whatwg/fetch] Following signals. Fixes #668. (#670)
- Re: [whatwg/fetch] Following signals. Fixes #668. (#670)
- Re: [whatwg/fetch] Following signals. Fixes #668. (#670)
- Re: [whatwg/fetch] Following signals. Fixes #668. (#670)
- Re: [whatwg/fetch] Following signals. Fixes #668. (#670)
[whatwg/dom] Following an abort signal (#569)
- Re: [whatwg/dom] Following an abort signal (#569)
- Re: [whatwg/dom] Following an abort signal (#569)
- Re: [whatwg/dom] Following an abort signal (#569)
- Re: [whatwg/dom] Following an abort signal (#569)
- Re: [whatwg/dom] Following an abort signal (#569)
- Re: [whatwg/dom] Following an abort signal (#569)
- Re: [whatwg/dom] Following an abort signal (#569)
- Re: [whatwg/dom] Following an abort signal (#569)
Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726)
- Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726)
- Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726)
- Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726)
- Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726)
- Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726)
- Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726)
- Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726)
- Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726)
- Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726)
- Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726)
- Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726)
- Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726)
- Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726)
- Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726)
- Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726)
- Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726)
- Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726)
- Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726)
- Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726)
[heycam/webidl] Testing (#520)
- Re: [heycam/webidl] Testing (#520)
- Re: [heycam/webidl] Testing (#520)
- Re: [heycam/webidl] Testing (#520)
- Re: [heycam/webidl] Testing (#520)
[w3c/ServiceWorker] Improve.ready and Activate (#1277)
- Re: [w3c/ServiceWorker] Improve.ready and Activate (#1277)
- Re: [w3c/ServiceWorker] Improve.ready and Activate (#1277)
- Re: [w3c/ServiceWorker] Improve.ready and Activate (#1277)
- Re: [w3c/ServiceWorker] Improve.ready and Activate (#1277)
- Re: [w3c/ServiceWorker] Improve.ready and Activate (#1277)
[whatwg/fetch] Location header is the empty string (#669)
- Re: [whatwg/fetch] Location header is the empty string (#669)
- Re: [whatwg/fetch] Location header is the empty string (#669)
- Re: [whatwg/fetch] Location header is the empty string (#669)
- Re: [whatwg/fetch] Location header is the empty string (#669)
- Re: [whatwg/fetch] Location header is the empty string (#669)
- Re: [whatwg/fetch] Location header is the empty string (#669)
- Re: [whatwg/fetch] Location header is the empty string (#669)
[w3c/WebPlatformWG] Add Web Share and Web Share Target APIs to charter (#105)
- Re: [w3c/WebPlatformWG] Add Web Share and Web Share Target APIs to charter (#105)
- Re: [w3c/WebPlatformWG] Add Web Share and Web Share Target APIs to charter (#105)
Re: [w3c/manifest] Make start_url relative to scope and not manifest location (#552)
- Re: [w3c/manifest] Make start_url relative to scope and not manifest location (#552)
- Re: [w3c/manifest] Make start_url relative to scope and not manifest location (#552)
Re: [w3c/manifest] Extension point should come after processing other members (#629)
[w3c/manifest] Move extension point to end of processing steps (#653)
- Re: [w3c/manifest] Move extension point to end of processing steps (#653)
- Re: [w3c/manifest] Move extension point to end of processing steps (#653)
- Re: [w3c/manifest] Move extension point to end of processing steps (#653)
Re: [heycam/webidl] Definition of "is an array index" makes "-0" an array index (#516)
Re: [whatwg/xhr] Allow developers to opt-out of sync XHR with feature policy (#178)
Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20)
[heycam/webidl] Four (not five) kind of special operations (#519)
[w3c/webcomponents] Consider adding user-defined attributes to slots (#733)
- Re: [w3c/webcomponents] Consider adding user-defined attributes to slots (#733)
- Re: [w3c/webcomponents] Consider adding user-defined attributes to slots (#733)
- Re: [w3c/webcomponents] Consider adding user-defined attributes to slots (#733)
[w3ctag/design-reviews] Payment Handler (#231)
- Re: [w3ctag/design-reviews] Payment Handler (#231)
- Re: [w3ctag/design-reviews] Payment Handler (#231)
- Re: [w3ctag/design-reviews] Payment Handler (#231)
- Re: [w3ctag/design-reviews] Payment Handler (#231)
- Re: [w3ctag/design-reviews] Payment Handler (#231)
- Re: [w3ctag/design-reviews] Payment Handler (#231)
Re: [whatwg/streams] "await writer.write(bytes);" in example seems wrong (#874)
- Re: [whatwg/streams] "await writer.write(bytes);" in example seems wrong (#874)
- Re: [whatwg/streams] "await writer.write(bytes);" in example seems wrong (#874)
Re: [w3c/pointerlock] Don't point to developers.whatwg.org (#26)
Re: [whatwg/url] Make property accessors into owned properties, or at least enumerable (#301)
Re: [whatwg/url] Need more changes for common deploy (#353)
Re: [whatwg/url] "For each code point in input, UTF-8 percent enc..." (#368)
Re: [whatwg/url] mailto hostnames (#331)
Re: [whatwg/streams] A variety of clarity and documentation improvements (#875)
- Re: [whatwg/streams] A variety of clarity and documentation improvements (#875)
- Re: [whatwg/streams] A variety of clarity and documentation improvements (#875)
- Re: [whatwg/streams] A variety of clarity and documentation improvements (#875)
- Re: [whatwg/streams] A variety of clarity and documentation improvements (#875)
- Re: [whatwg/streams] A variety of clarity and documentation improvements (#875)
- Re: [whatwg/streams] A variety of clarity and documentation improvements (#875)
- Re: [whatwg/streams] A variety of clarity and documentation improvements (#875)
- Re: [whatwg/streams] A variety of clarity and documentation improvements (#875)
- Re: [whatwg/streams] A variety of clarity and documentation improvements (#875)
- Re: [whatwg/streams] A variety of clarity and documentation improvements (#875)
- Re: [whatwg/streams] A variety of clarity and documentation improvements (#875)
- Re: [whatwg/streams] A variety of clarity and documentation improvements (#875)
- Re: [whatwg/streams] A variety of clarity and documentation improvements (#875)
- Re: [whatwg/streams] A variety of clarity and documentation improvements (#875)
- Re: [whatwg/streams] A variety of clarity and documentation improvements (#875)
- Re: [whatwg/streams] A variety of clarity and documentation improvements (#875)
- Re: [whatwg/streams] A variety of clarity and documentation improvements (#875)
- Re: [whatwg/streams] A variety of clarity and documentation improvements (#875)
- Re: [whatwg/streams] A variety of clarity and documentation improvements (#875)
- Re: [whatwg/streams] A variety of clarity and documentation improvements (#875)
- Re: [whatwg/streams] A variety of clarity and documentation improvements (#875)
- Re: [whatwg/streams] A variety of clarity and documentation improvements (#875)
Re: [whatwg/dom] No way to resolve a Promise with a cross domain WindowProxy (#536)
Re: [heycam/webidl] record with arbitrary value types as keys? (#509)
- Re: [heycam/webidl] record with arbitrary value types as keys? (#509)
- Re: [heycam/webidl] record with arbitrary value types as keys? (#509)
- Re: [heycam/webidl] record with arbitrary value types as keys? (#509)
- Re: [heycam/webidl] record with arbitrary value types as keys? (#509)
- Re: [heycam/webidl] record with arbitrary value types as keys? (#509)
- Re: [heycam/webidl] record with arbitrary value types as keys? (#509)
- Re: [heycam/webidl] record with arbitrary value types as keys? (#509)
- Re: [heycam/webidl] record with arbitrary value types as keys? (#509)
- Re: [heycam/webidl] record with arbitrary value types as keys? (#509)
- Re: [heycam/webidl] record with arbitrary value types as keys? (#509)
[w3c/webcomponents] typo (#732)
- Re: [w3c/webcomponents] typo (#732)
- Re: [w3c/webcomponents] typo (#732)
- Re: [w3c/webcomponents] typo (#732)
Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323)
- Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323)
- Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323)
- Re: [heycam/webidl] Replace serializers by toJSON and [Default] extended attribute (#323)
[w3c/pointerlock] fix references, see #26 (#31)
- Re: [w3c/pointerlock] fix references, see #26 (#31)
- Re: [w3c/pointerlock] fix references, see #26 (#31)
- Re: [w3c/pointerlock] fix references, see #26 (#31)
- Re: [w3c/pointerlock] fix references, see #26 (#31)
Re: [whatwg/dom] Declarative Shadow DOM (#510)
- Re: [whatwg/dom] Declarative Shadow DOM (#510)
- Re: [whatwg/dom] Declarative Shadow DOM (#510)
- Re: [whatwg/dom] Declarative Shadow DOM (#510)
- Re: [whatwg/dom] Declarative Shadow DOM (#510)
- Re: [whatwg/dom] Declarative Shadow DOM (#510)
- Re: [whatwg/dom] Declarative Shadow DOM (#510)
- Re: [whatwg/dom] Declarative Shadow DOM (#510)
- Re: [whatwg/dom] Declarative Shadow DOM (#510)
- Re: [whatwg/dom] Declarative Shadow DOM (#510)
- Re: [whatwg/dom] Declarative Shadow DOM (#510)
- Re: [whatwg/dom] Declarative Shadow DOM (#510)
- Re: [whatwg/dom] Declarative Shadow DOM (#510)
[w3c/manifest] Payment Handler spec defines IDL types very similar to manifest (#652)
- Re: [w3c/manifest] Payment Handler spec defines IDL types very similar to manifest (#652)
- Re: [w3c/manifest] Payment Handler spec defines IDL types very similar to manifest (#652)
- Re: [w3c/manifest] Payment Handler spec defines IDL types very similar to manifest (#652)
[whatwg/fetch] "If signal is not null, then add the following a..." (#668)
- Re: [whatwg/fetch] "If signal is not null, then add the following a..." (#668)
- Re: [whatwg/fetch] "If signal is not null, then add the following a..." (#668)
- Re: [whatwg/fetch] "If signal is not null, then add the following a..." (#668)
- Re: [whatwg/fetch] "If signal is not null, then add the following a..." (#668)
- Re: [whatwg/fetch] "If signal is not null, then add the following a..." (#668)
- Re: [whatwg/fetch] "If signal is not null, then add the following a..." (#668)
- Re: [whatwg/fetch] "If signal is not null, then add the following a..." (#668)
- Re: [whatwg/fetch] "If signal is not null, then add the following a..." (#668)
Re: [whatwg/dom] Removing event listeners through an identifier (#208)
[whatwg/dom] DOM ready is error prone, still requires libs, could be simpler: a document#ready Promise (#568)
- Re: [whatwg/dom] DOM ready is error prone, still requires libs, could be simpler: a document#ready Promise (#568)
- Re: [whatwg/dom] DOM ready is error prone, still requires libs, could be simpler: a document#ready Promise (#568)
- Re: [whatwg/dom] DOM ready is error prone, still requires libs, could be simpler: a document#ready Promise (#568)
- Re: [whatwg/dom] DOM ready is error prone, still requires libs, could be simpler: a document#ready Promise (#568)
[w3c/WebPlatformWG] Add Justin Fagnani to Web Components F2F attendees (#104)
Re: [whatwg/streams] Throw type error in ReadableStreamBYOBRequest ctor if view isn't a non-detached ArrayBuffer view object (#870)
- Re: [whatwg/streams] Throw type error in ReadableStreamBYOBRequest ctor if view isn't a non-detached ArrayBuffer view object (#870)
- Re: [whatwg/streams] Throw type error in ReadableStreamBYOBRequest ctor if view isn't a non-detached ArrayBuffer view object (#870)
- Re: [whatwg/streams] Throw type error in ReadableStreamBYOBRequest ctor if view isn't a non-detached ArrayBuffer view object (#870)
- Re: [whatwg/streams] Throw type error in ReadableStreamBYOBRequest ctor if view isn't a non-detached ArrayBuffer view object (#870)
- Re: [whatwg/streams] Throw type error in ReadableStreamBYOBRequest ctor if view isn't a non-detached ArrayBuffer view object (#870)
- Re: [whatwg/streams] Throw type error in ReadableStreamBYOBRequest ctor if view isn't a non-detached ArrayBuffer view object (#870)
- Re: [whatwg/streams] Throw type error in ReadableStreamBYOBRequest ctor if view isn't a non-detached ArrayBuffer view object (#870)
- Re: [whatwg/streams] Throw type error in ReadableStreamBYOBRequest ctor if view isn't a non-detached ArrayBuffer view object (#870)
- Re: [whatwg/streams] Throw type error in ReadableStreamBYOBRequest ctor if view isn't a non-detached ArrayBuffer view object (#870)
- Re: [whatwg/streams] Throw type error in ReadableStreamBYOBRequest ctor if view isn't a non-detached ArrayBuffer view object (#870)
[whatwg/streams] Readable byte stream must call pull after receiving new chunk (#877)
- Re: [whatwg/streams] Readable byte stream must call pull after receiving new chunk (#877)
- Re: [whatwg/streams] Readable byte stream must call pull after receiving new chunk (#877)
- Re: [whatwg/streams] Readable byte stream must call pull after receiving new chunk (#877)
- Re: [whatwg/streams] Readable byte stream must call pull after receiving new chunk (#877)
- Re: [whatwg/streams] Readable byte stream must call pull after receiving new chunk (#877)
- Re: [whatwg/streams] Readable byte stream must call pull after receiving new chunk (#877)
- Re: [whatwg/streams] Readable byte stream must call pull after receiving new chunk (#877)
- Re: [whatwg/streams] Readable byte stream must call pull after receiving new chunk (#877)
- Re: [whatwg/streams] Readable byte stream must call pull after receiving new chunk (#877)
- Re: [whatwg/streams] Readable byte stream must call pull after receiving new chunk (#877)
[w3c/webcomponents] Add Declarative Shadow DOM strawman proposal (#731)
- Re: [w3c/webcomponents] Add Declarative Shadow DOM strawman proposal (#731)
- Re: [w3c/webcomponents] Add Declarative Shadow DOM strawman proposal (#731)
- Re: [w3c/webcomponents] Add Declarative Shadow DOM strawman proposal (#731)
- Re: [w3c/webcomponents] Add Declarative Shadow DOM strawman proposal (#731)
- Re: [w3c/webcomponents] Add Declarative Shadow DOM strawman proposal (#731)
- Re: [w3c/webcomponents] Add Declarative Shadow DOM strawman proposal (#731)
- Re: [w3c/webcomponents] Add Declarative Shadow DOM strawman proposal (#731)
- Re: [w3c/webcomponents] Add Declarative Shadow DOM strawman proposal (#731)
[w3c/webcomponents] If a Custom Element is used as a placeholder for an HTML heading, would it be interpreted as a heading for SEO purposes? (#730)
- Re: [w3c/webcomponents] If a Custom Element is used as a placeholder for an HTML heading, would it be interpreted as a heading for SEO purposes? (#730)
- Re: [w3c/webcomponents] If a Custom Element is used as a placeholder for an HTML heading, would it be interpreted as a heading for SEO purposes? (#730)
- Re: [w3c/webcomponents] If a Custom Element is used as a placeholder for an HTML heading, would it be interpreted as a heading for SEO purposes? (#730)
- Re: [w3c/webcomponents] If a Custom Element is used as a placeholder for an HTML heading, would it be interpreted as a heading for SEO purposes? (#730)
- Re: [w3c/webcomponents] If a Custom Element is used as a placeholder for an HTML heading, would it be interpreted as a heading for SEO purposes? (#730)
- Re: [w3c/webcomponents] If a Custom Element is used as a placeholder for an HTML heading, would it be interpreted as a heading for SEO purposes? (#730)
Re: [w3c/ServiceWorker] Should we specify behavior for using objects from detached contexts? (#1221)
- Re: [w3c/ServiceWorker] Should we specify behavior for using objects from detached contexts? (#1221)
- Re: [w3c/ServiceWorker] Should we specify behavior for using objects from detached contexts? (#1221)
- Re: [w3c/ServiceWorker] Should we specify behavior for using objects from detached contexts? (#1221)
- Re: [w3c/ServiceWorker] Should we specify behavior for using objects from detached contexts? (#1221)
- Re: [w3c/ServiceWorker] Should we specify behavior for using objects from detached contexts? (#1221)
[w3c/webcomponents] Input requested on ARIA/HTML role parity (#729)
- Re: [w3c/webcomponents] Input requested on ARIA/HTML role parity (#729)
- Re: [w3c/webcomponents] Input requested on ARIA/HTML role parity (#729)
Re: [w3c/uievents-key] Implementation report (#44)
- Re: [w3c/uievents-key] Implementation report (#44)
- Re: [w3c/uievents-key] Implementation report (#44)
- Re: [w3c/uievents-key] Implementation report (#44)
[w3ctag/design-reviews] CSS ::part and ::theme pseudo elements (#230)
- Re: [w3ctag/design-reviews] CSS ::part and ::theme pseudo elements (#230)
- Re: [w3ctag/design-reviews] CSS ::part and ::theme pseudo elements (#230)
Re: [w3c/pointerlock] WD for PL2.0 (#25)
- Re: [w3c/pointerlock] WD for PL2.0 (#25)
- Re: [w3c/pointerlock] WD for PL2.0 (#25)
- Re: [w3c/pointerlock] WD for PL2.0 (#25)
[whatwg/fetch] No documentation of which ports are used by default (#667)
- Re: [whatwg/fetch] No documentation of which ports are used by default (#667)
- Re: [whatwg/fetch] No documentation of which ports are used by default (#667)
- Re: [whatwg/fetch] No documentation of which ports are used by default (#667)
Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517)
- Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517)
- Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517)
- Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517)
- Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517)
- Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517)
- Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517)
- Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517)
- Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517)
- Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517)
- Re: [heycam/webidl] Disallow -0 in algorithm for checking array index (#517)
Re: [w3c/manifest] PromptResponseObject definition is missing in "IDL Index" (#637)
- Re: [w3c/manifest] PromptResponseObject definition is missing in "IDL Index" (#637)
- Re: [w3c/manifest] PromptResponseObject definition is missing in "IDL Index" (#637)
Re: [w3c/manifest] ServiceWorkerRegistration dictionary conflicts with ServiceWorker WebIDL (#641)
- Re: [w3c/manifest] ServiceWorkerRegistration dictionary conflicts with ServiceWorker WebIDL (#641)
- Re: [w3c/manifest] ServiceWorkerRegistration dictionary conflicts with ServiceWorker WebIDL (#641)
- Re: [w3c/manifest] ServiceWorkerRegistration dictionary conflicts with ServiceWorker WebIDL (#641)
- Re: [w3c/manifest] ServiceWorkerRegistration dictionary conflicts with ServiceWorker WebIDL (#641)
[w3c/uievents] preventDefault() of keydown event should not kill composition start caused by the keydown (#180)
Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713)
- Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713)
- Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713)
- Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713)
- Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713)
- Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713)
- Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713)
- Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713)
- Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713)
- Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713)
- Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713)
Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662)
- Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662)
- Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662)
- Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662)
- Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662)
- Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662)
- Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662)
- Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662)
- Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662)
Re: [w3c/gamepad] Light Indicator (#67)
Re: [w3c/gamepad] Determine how Multi-touch surfaces should be handled. (#27)
Re: [w3c/ServiceWorker] How to handle redirected URL for login authentication offline. (#1226)
Re: [whatwg/streams] Add "was ever locked" flag for Encoding standard? (#873)
Re: [whatwg/encoding] Add Streams support (#72)
- Re: [whatwg/encoding] Add Streams support (#72)
- Re: [whatwg/encoding] Add Streams support (#72)
- Re: [whatwg/encoding] Add Streams support (#72)
- Re: [whatwg/encoding] Add Streams support (#72)
- Re: [whatwg/encoding] Add Streams support (#72)
- Re: [whatwg/encoding] Add Streams support (#72)
- Re: [whatwg/encoding] Add Streams support (#72)
- Re: [whatwg/encoding] Add Streams support (#72)
- Re: [whatwg/encoding] Add Streams support (#72)
- Re: [whatwg/encoding] Add Streams support (#72)
- Re: [whatwg/encoding] Add Streams support (#72)
- Re: [whatwg/encoding] Add Streams support (#72)
- Re: [whatwg/encoding] Add Streams support (#72)
Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176)
[whatwg/url] Consider adding non-throwing URL.parse(input, base) (#372)
Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
Re: [w3c/manifest] chore: Add Matt Giuca as co-editor (closes #650) (0528ad8)
- Re: [w3c/manifest] chore: Add Matt Giuca as co-editor (closes #650) (0528ad8)
- Re: [w3c/manifest] chore: Add Matt Giuca as co-editor (closes #650) (0528ad8)
- Re: [w3c/manifest] chore: Add Matt Giuca as co-editor (closes #650) (0528ad8)
- Re: [w3c/manifest] chore: Add Matt Giuca as co-editor (closes #650) (0528ad8)
Re: [w3c/ServiceWorker] Replaying POST requests (#693)
[w3c/manifest] chore: Add Matt Giuca as co-editor (closes #650) (#651)
- Re: [w3c/manifest] chore: Add Matt Giuca as co-editor (closes #650) (#651)
- Re: [w3c/manifest] chore: Add Matt Giuca as co-editor (closes #650) (#651)
- Re: [w3c/manifest] chore: Add Matt Giuca as co-editor (closes #650) (#651)
- Re: [w3c/manifest] chore: Add Matt Giuca as co-editor (closes #650) (#651)
- Re: [w3c/manifest] chore: Add Matt Giuca as co-editor (closes #650) (#651)
- Re: [w3c/manifest] chore: Add Matt Giuca as co-editor (closes #650) (#651)
- Re: [w3c/manifest] chore: Add Matt Giuca as co-editor (closes #650) (#651)
- Re: [w3c/manifest] chore: Add Matt Giuca as co-editor (closes #650) (#651)
[w3c/manifest] Add Matt Giuca as Co-Editor (#650)
- Re: [w3c/manifest] Add Matt Giuca as Co-Editor (#650)
- Re: [w3c/manifest] Add Matt Giuca as Co-Editor (#650)
- Re: [w3c/manifest] Add Matt Giuca as Co-Editor (#650)
[w3c/manifest] Fix or replace instances of "new URL" (#649)
- Re: [w3c/manifest] Fix or replace instances of "new URL" (#649)
- Re: [w3c/manifest] Fix or replace instances of "new URL" (#649)
[whatwg/xhr] Fix send() charset overriding to use new MIME type infrastructure (#188)
- Re: [whatwg/xhr] Fix send() charset overriding to use new MIME type infrastructure (#188)
- Re: [whatwg/xhr] Fix send() charset overriding to use new MIME type infrastructure (#188)
Re: [whatwg/xhr] Look at overrideMimeType() again (#157)
Re: [whatwg/fetch] data: URL generator (#665)
- Re: [whatwg/fetch] data: URL generator (#665)
- Re: [whatwg/fetch] data: URL generator (#665)
- Re: [whatwg/fetch] data: URL generator (#665)
- Re: [whatwg/fetch] data: URL generator (#665)
[heycam/webidl] Is an interface named I exposed in realm R (#518)
- Re: [heycam/webidl] Is an interface named I exposed in realm R (#518)
- Re: [heycam/webidl] Is an interface named I exposed in realm R (#518)
[w3c/webcomponents] Selectors in ::slotted don’t change specificity (#728)
- Re: [w3c/webcomponents] Selectors in ::slotted don’t change specificity (#728)
- Re: [w3c/webcomponents] Selectors in ::slotted don’t change specificity (#728)
- Re: [w3c/webcomponents] Selectors in ::slotted don’t change specificity (#728)
- Re: [w3c/webcomponents] Selectors in ::slotted don’t change specificity (#728)
- Re: [w3c/webcomponents] Selectors in ::slotted don’t change specificity (#728)
Re: [GoogleChrome/puppeteer] Query nodes within shadow roots (#858)
- Re: [GoogleChrome/puppeteer] Query nodes within shadow roots (#858)
- Re: [GoogleChrome/puppeteer] Query nodes within shadow roots (#858)
- Re: [GoogleChrome/puppeteer] Query nodes within shadow roots (#858)
- Re: [GoogleChrome/puppeteer] Query nodes within shadow roots (#858)
[w3c/WebPlatformWG] Add Patrick Kettner to attendees (#103)
[whatwg/dom] Export attribute change steps (#567)
- Re: [whatwg/dom] Export attribute change steps (#567)
- Re: [whatwg/dom] Export attribute change steps (#567)
[w3ctag/design-reviews] W3C DOM (#229)
Re: [w3c/uievents] Add specification for AltGraph key & modifier behaviour (#147)
[w3c/uievents] keydown event should have an attribute which is set to true when it's followed by a beforeinput or keypress event? (#179)
[w3c/ServiceWorker] The Cache objects do not expire unless authors *or users* delete the entries. (#1276)
- Re: [w3c/ServiceWorker] The Cache objects do not expire unless authors *or users* delete the entries. (#1276)
- Re: [w3c/ServiceWorker] The Cache objects do not expire unless authors *or users* delete the entries. (#1276)
[w3ctag/packaging-on-the-web] Please "un-gut" this specification (#35)
- Re: [w3ctag/packaging-on-the-web] Please "un-gut" this specification (#35)
- Re: [w3ctag/packaging-on-the-web] Please "un-gut" this specification (#35)
- Re: [w3ctag/packaging-on-the-web] Please "un-gut" this specification (#35)
[whatwg/dom] Change handling of is="" in element creation and cloning (#566)
- Re: [whatwg/dom] Change handling of is="" in element creation and cloning (#566)
- Re: [whatwg/dom] Change handling of is="" in element creation and cloning (#566)
- Re: [whatwg/dom] Change handling of is="" in element creation and cloning (#566)
- Re: [whatwg/dom] Change handling of is="" in element creation and cloning (#566)
- Re: [whatwg/dom] Change handling of is="" in element creation and cloning (#566)
Re: [w3ctag/design-reviews] Review request for ResizeObserver (#187)
Re: [w3ctag/design-reviews] CSS Selectors 4 (#219)
Re: [w3ctag/design-reviews] Privacy Mode (#101)
Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206)
- Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206)
- Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206)
- Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206)
- Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206)
Re: [w3ctag/design-reviews] Consider general storage observer that works for cookies (#210)
Re: [w3ctag/design-reviews] Web Share Target API (#221)
- Re: [w3ctag/design-reviews] Web Share Target API (#221)
- Re: [w3ctag/design-reviews] Web Share Target API (#221)
- Re: [w3ctag/design-reviews] Web Share Target API (#221)
Re: [w3ctag/design-reviews] TAG review of Web Audio API (round two) (#212)
- Re: [w3ctag/design-reviews] TAG review of Web Audio API (round two) (#212)
- Re: [w3ctag/design-reviews] TAG review of Web Audio API (round two) (#212)
- Re: [w3ctag/design-reviews] TAG review of Web Audio API (round two) (#212)
Re: [w3ctag/design-reviews] Streams General issue (#92)
- Re: [w3ctag/design-reviews] Streams General issue (#92)
- Re: [w3ctag/design-reviews] Streams General issue (#92)
- Re: [w3ctag/design-reviews] Streams General issue (#92)
Re: [w3ctag/design-reviews] Review Accessibility Object Model (#134)
Re: [w3ctag/design-reviews] CSS Layout API (#224)
Re: [w3ctag/design-reviews] saveData attribute in Network Information API (#204)
- Re: [w3ctag/design-reviews] saveData attribute in Network Information API (#204)
- Re: [w3ctag/design-reviews] saveData attribute in Network Information API (#204)
- Re: [w3ctag/design-reviews] saveData attribute in Network Information API (#204)
Re: [w3ctag/design-reviews] Review Request: Media Capabilities (#218)
- Re: [w3ctag/design-reviews] Review Request: Media Capabilities (#218)
- Re: [w3ctag/design-reviews] Review Request: Media Capabilities (#218)
- Re: [w3ctag/design-reviews] Review Request: Media Capabilities (#218)
- Re: [w3ctag/design-reviews] Review Request: Media Capabilities (#218)
- Re: [w3ctag/design-reviews] Review Request: Media Capabilities (#218)
Re: [w3ctag/design-reviews] Picture-in-Picture (PiP) (#226)
- Re: [w3ctag/design-reviews] Picture-in-Picture (PiP) (#226)
- Re: [w3ctag/design-reviews] Picture-in-Picture (PiP) (#226)
- Re: [w3ctag/design-reviews] Picture-in-Picture (PiP) (#226)
- Re: [w3ctag/design-reviews] Picture-in-Picture (PiP) (#226)
- Re: [w3ctag/design-reviews] Picture-in-Picture (PiP) (#226)
- Re: [w3ctag/design-reviews] Picture-in-Picture (PiP) (#226)
Re: [w3ctag/design-reviews] Permission Delegation (#225)
- Re: [w3ctag/design-reviews] Permission Delegation (#225)
- Re: [w3ctag/design-reviews] Permission Delegation (#225)
- Re: [w3ctag/design-reviews] Permission Delegation (#225)
- Re: [w3ctag/design-reviews] Permission Delegation (#225)
[w3c/ServiceWorker] What's the possible reason for navigator.serviceWorker.register error? (#1275)
- Re: [w3c/ServiceWorker] What's the possible reason for navigator.serviceWorker.register error? (#1275)
- Re: [w3c/ServiceWorker] What's the possible reason for navigator.serviceWorker.register error? (#1275)
- Re: [w3c/ServiceWorker] What's the possible reason for navigator.serviceWorker.register error? (#1275)
Re: [w3ctag/design-reviews] Review Decentralized identifiers (DIDs) (#216)
Re: [w3ctag/design-reviews] <link> rel="modulepreload" (#213)
- Re: [w3ctag/design-reviews] <link> rel="modulepreload" (#213)
- Re: [w3ctag/design-reviews] <link> rel="modulepreload" (#213)
Re: [w3ctag/design-reviews] Transform Streams (#211)
Re: [w3ctag/design-reviews] TAG review for CSS Typed OM (#223)
- Re: [w3ctag/design-reviews] TAG review for CSS Typed OM (#223)
- Re: [w3ctag/design-reviews] TAG review for CSS Typed OM (#223)
- Re: [w3ctag/design-reviews] TAG review for CSS Typed OM (#223)
- Re: [w3ctag/design-reviews] TAG review for CSS Typed OM (#223)
- Re: [w3ctag/design-reviews] TAG review for CSS Typed OM (#223)
- Re: [w3ctag/design-reviews] TAG review for CSS Typed OM (#223)
- Re: [w3ctag/design-reviews] TAG review for CSS Typed OM (#223)
- Re: [w3ctag/design-reviews] TAG review for CSS Typed OM (#223)
- Re: [w3ctag/design-reviews] TAG review for CSS Typed OM (#223)
[w3c/ServiceWorker] Clarify target object of Client.postMessage can be null (#1274)
- Re: [w3c/ServiceWorker] Clarify target object of Client.postMessage can be null (#1274)
- Re: [w3c/ServiceWorker] Clarify target object of Client.postMessage can be null (#1274)
- Re: [w3c/ServiceWorker] Clarify target object of Client.postMessage can be null (#1274)
- Re: [w3c/ServiceWorker] Clarify target object of Client.postMessage can be null (#1274)
- Re: [w3c/ServiceWorker] Clarify target object of Client.postMessage can be null (#1274)
[w3c/ServiceWorker] Should the worker be removed from the registration *before* its state is set to "redundant"? (#1273)
- Re: [w3c/ServiceWorker] Should the worker be removed from the registration *before* its state is set to "redundant"? (#1273)
- Re: [w3c/ServiceWorker] Should the worker be removed from the registration *before* its state is set to "redundant"? (#1273)
- Re: [w3c/ServiceWorker] Should the worker be removed from the registration *before* its state is set to "redundant"? (#1273)
- Re: [w3c/ServiceWorker] Should the worker be removed from the registration *before* its state is set to "redundant"? (#1273)
- Re: [w3c/ServiceWorker] Should the worker be removed from the registration *before* its state is set to "redundant"? (#1273)
- Re: [w3c/ServiceWorker] Should the worker be removed from the registration *before* its state is set to "redundant"? (#1273)
- Re: [w3c/ServiceWorker] Should the worker be removed from the registration *before* its state is set to "redundant"? (#1273)
[w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
- Re: [w3c/ServiceWorker] Scope matching algorithm breaks sites that don't end in a slash (#1272)
[whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371)
- Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371)
- Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371)
- Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371)
- Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371)
- Re: [whatwg/url] Use definitions in FileAPI spec to resolve blob URLs and their origins. (#371)
Re: [w3c/manifest] Should the scope terminate by "/"? (#554)
- Re: [w3c/manifest] Should the scope terminate by "/"? (#554)
- Re: [w3c/manifest] Should the scope terminate by "/"? (#554)
[w3c/webcomponents] [idea] Element Behaviors (#727)
- Re: [w3c/webcomponents] [idea] Element Behaviors, and the has="" attribute (#727)
- Re: [w3c/webcomponents] Element Behaviors, and the has="" attribute. A useful alternative to Custom Elements in many cases! (#727)
Re: [w3c/manifest] Allow for multiple scopes (#449)
[w3c/ServiceWorker] maybe explicitly set the `self.registration` DOM object on `ServiceWorkerGlobalScope` (#1271)
[w3c/ServiceWorker] `Clear Registration` should call `Update Registration State` before `Update Worker State` (#1270)
- Re: [w3c/ServiceWorker] `Clear Registration` should call `Update Registration State` before `Update Worker State` (#1270)
- Re: [w3c/ServiceWorker] `Clear Registration` should call `Update Registration State` before `Update Worker State` (#1270)
Re: [w3ctag/design-reviews] Request Review: Gesture Delegation (#199)
Re: [w3ctag/design-reviews] Trusted Types (#198)
- Re: [w3ctag/design-reviews] Trusted Types (#198)
- Re: [w3ctag/design-reviews] Trusted Types (#198)
- Re: [w3ctag/design-reviews] Trusted Types (#198)
Re: [whatwg/xhr] Integrate feature policy (#177)
- Re: [whatwg/xhr] Integrate feature policy (#177)
- Re: [whatwg/xhr] Integrate feature policy (#177)
- Re: [whatwg/xhr] Integrate feature policy (#177)
Re: [w3ctag/design-reviews] Intersection Observer review (#197)
Re: [w3ctag/design-reviews] ReportingObserver (#195)
Re: [w3ctag/design-reviews] Web Locks API (#217)
- Re: [w3ctag/design-reviews] Web Locks API (#217)
- Re: [w3ctag/design-reviews] Web Locks API (#217)
- Re: [w3ctag/design-reviews] Web Locks API (#217)
- Re: [w3ctag/design-reviews] Web Locks API (#217)
Re: [w3ctag/design-reviews] Request review of Keyboard Lock (#192)
Re: [w3ctag/design-reviews] ads.txt (#201)
Re: [w3c/ServiceWorker] should local URLs check origin before inheritting a controller? (#1262)
Re: [w3c/ServiceWorker] should blob URL clients have their controlled updated if their parent's controller is changed? (#1265)
Re: [w3ctag/design-reviews] Img decoding attribute (#220)
- Re: [w3ctag/design-reviews] Img decoding attribute (#220)
- Re: [w3ctag/design-reviews] Img decoding attribute (#220)
- Re: [w3ctag/design-reviews] Img decoding attribute (#220)
[w3c/permissions] Add optional consent due to GDPR (#169)
- Re: [w3c/permissions] Add optional consent due to GDPR (#169)
- Re: [w3c/permissions] Add optional consent due to GDPR (#169)
- Re: [w3c/permissions] Add optional consent due to GDPR (#169)
- Re: [w3c/permissions] Add optional consent due to GDPR (#169)
Re: [w3c/ServiceWorker] should `ServiceWorker` interface implement `AbstractWorker` mixin? (#1268)
Re: [w3ctag/design-reviews] HTML General Review (#174)
Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647)
- Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647)
- Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647)
- Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647)
- Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647)
- Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647)
[w3c/WebPlatformWG] Add Tomek Wytrębowicz to attendees (#102)
Re: [w3c/permissions] Media autoplay permission (#150)
Re: [whatwg/fullscreen] Meta: make Philip the editor (#121)
Re: [w3c/ServiceWorker] clarify when FetchEvent.clientId will or will not be set for navigations (#1267)
- Re: [w3c/ServiceWorker] clarify when FetchEvent.clientId will or will not be set for navigations (#1267)
- Re: [w3c/ServiceWorker] clarify when FetchEvent.clientId will or will not be set for navigations (#1267)
Re: [w3ctag/design-reviews] Review of signature-based resource loading restrictions. (#186)
- Re: [w3ctag/design-reviews] Review of signature-based resource loading restrictions. (#186)
- Re: [w3ctag/design-reviews] Review of signature-based resource loading restrictions. (#186)
Re: [w3c/webcomponents] A new attribute similar to is="", but would allow multiple behaviors to be attached to a given element. (#662)
- Re: [w3c/webcomponents] A new attribute similar to is="", but would allow multiple behaviors to be attached to a given element. (#662)
- Re: [w3c/webcomponents] A new attribute similar to is="", but would allow multiple behaviors to be attached to a given element. (#662)
- Re: [w3c/webcomponents] A new attribute similar to is="", but would allow multiple behaviors to be attached to a given element. (#662)
Re: [whatwg/fetch] Should fetches to blob URLs be more restricted? (#666)
Re: [whatwg/streams] Provide a way for the underlying sink to signal write progress? (#876)
- Re: [whatwg/streams] Provide a way for the underlying sink to signal write progress? (#876)
- Re: [whatwg/streams] Provide a way for the underlying sink to signal write progress? (#876)
Re: [w3c/ServiceWorker] Until resultingClientId is implemented, what should FetchEvent.clientId be for navigation requests? (#1266)
Re: [whatwg/fullscreen] Remove nodes from top layer as part of the removing steps (#102)
- Re: [whatwg/fullscreen] Remove nodes from top layer as part of the removing steps (#102)
- Re: [whatwg/fullscreen] Remove nodes from top layer as part of the removing steps (#102)
- Re: [whatwg/fullscreen] Remove nodes from top layer as part of the removing steps (#102)
- Re: [whatwg/fullscreen] Remove nodes from top layer as part of the removing steps (#102)
- Re: [whatwg/fullscreen] Remove nodes from top layer as part of the removing steps (#102)
- Re: [whatwg/fullscreen] Remove nodes from top layer as part of the removing steps (#102)
- Re: [whatwg/fullscreen] Remove nodes from top layer as part of the removing steps (#102)
- Re: [whatwg/fullscreen] Remove nodes from top layer as part of the removing steps (#102)
- Re: [whatwg/fullscreen] Remove nodes from top layer as part of the removing steps (#102)
[w3c/WebPlatformWG] Adds Karl Dubost as a lurker participant (#101)
- Re: [w3c/WebPlatformWG] Adds Karl Dubost as a lurker participant (#101)
- Re: [w3c/WebPlatformWG] Adds Karl Dubost as a lurker participant (#101)
Re: [heycam/webidl] [Exposed] section unnecessarily restrictive about partial interface + members (#515)
Re: [w3ctag/design-reviews] Files and Directory Entries API with webkit prefixes! (#215)
- Re: [w3ctag/design-reviews] Files and Directory Entries API with webkit prefixes! (#215)
- Re: [w3ctag/design-reviews] Files and Directory Entries API with webkit prefixes! (#215)
- Re: [w3ctag/design-reviews] Files and Directory Entries API with webkit prefixes! (#215)