Re: [IndexedDB] Support queries retrieving disjoint sets of keys (#19)
[webidl] support [Exposed=Worklet] (#87)
Re: [dom] High resolution timing for events (#23)
Re: [webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354)
- Re: [webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354)
- Re: [webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354)
- Re: [webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354)
Re: [FileAPI] Persistent blob urls (#27)
[manifest] Icon schema considerations (#422)
- Re: [manifest] Icon schema considerations (#422)
- Re: [manifest] Icon schema considerations (#422)
- Re: [manifest] Icon schema considerations (#422)
[push-api] Push API - Authenticating to Push Service (#185)
- Re: [push-api] Push API - Authenticating to Push Service (#185)
- Re: [push-api] Push API - Authenticating to Push Service (#185)
- Re: [push-api] Push API - Authenticating to Push Service (#185)
- Re: [push-api] Push API - Authenticating to Push Service (#185)
- Re: [push-api] Push API - Authenticating to Push Service (#185)
- Re: [push-api] Push API - Authenticating to Push Service (#185)
- Re: [push-api] Push API - Authenticating to Push Service (#185)
Re: [fetch] Add "must-revalidate" to RequestCache enumeration (#165)
Re: [fetch] Fix #197: explain cache modes (a47e1e4)
[ServiceWorker] clarify Request.isReload for sub-resources (#827)
[manifest] Support for deep integrations, e.g. OpenSearch (#421)
- Re: [manifest] Support for deep integrations, e.g. OpenSearch (#421)
- Re: [manifest] Support for deep integrations, e.g. OpenSearch (#421)
- Re: [manifest] Support for deep integrations, e.g. OpenSearch (#421)
- Re: [manifest] Support for deep integrations, e.g. OpenSearch (#421)
- Re: [manifest] Support for deep integrations, e.g. OpenSearch (#421)
- Re: [manifest] Support for deep integrations, e.g. OpenSearch (#421)
- Re: [manifest] Support for deep integrations, e.g. OpenSearch (#421)
Re: [dom] Merge DOMSettableTokenList into DOMTokenList (#119)
Re: [webcomponents] Need "slotting changed" event (#288)
- Re: [webcomponents] Need "slotting changed" event (#288)
- Re: [webcomponents] Need "slotting changed" event (#288)
- Re: [webcomponents] Need "slotting changed" event (#288)
- Re: [webcomponents] Need "slotting changed" event (#288)
- Re: [webcomponents] Need "slotting changed" event (#288)
- Re: [webcomponents] Need "slotting changed" event (#288)
- Re: [webcomponents] Need "slotting changed" event (#288)
- Re: [webcomponents] Need "slotting changed" event (#288)
- Re: [webcomponents] Need "slotting changed" event (#288)
- Re: [webcomponents] Need "slotting changed" event (#288)
- Re: [webcomponents] Need "slotting changed" event (#288)
- Re: [webcomponents] Need "slotting changed" event (#288)
[push-api] Expose PushSubscriptionOptions value on PushSubscription (#184)
[push-api] Can you change the value of PushSubscriptionOptions (#183)
[webcomponents] Update Section 6.2 Focus Navigation to reflect TPAC discussion (#375)
- Re: [webcomponents] Update Section 6.2 Focus Navigation to reflect TPAC discussion (#375)
- Re: [webcomponents] Update Section 6.2 Focus Navigation to reflect TPAC discussion (#375)
- Re: [webcomponents] Update Section 6.2 Focus Navigation to reflect TPAC discussion (#375)
- Re: [webcomponents] Update Section 6.2 Focus Navigation to reflect TPAC discussion (#375)
[webcomponents] Treatment of retargeting focus events is ambiguous (#374)
[webcomponents] deepPath should return an empty array if it's no longer being dispatched (#373)
- Re: [webcomponents] deepPath should return an empty array if it's no longer being dispatched (#373)
- Re: [webcomponents] deepPath should return an empty array if it's no longer being dispatched (#373)
- Re: [webcomponents] deepPath should return an empty array if it's no longer being dispatched (#373)
[webcomponents] Event path trimming should use `scoped` flag and not rely on trustedness (#372)
[fetch] RFC: a mechanism to bypass CORS preflight (#210)
- Re: [fetch] RFC: a mechanism to bypass CORS preflight (#210)
- Re: [fetch] RFC: a mechanism to bypass CORS preflight (#210)
- Re: [fetch] RFC: a mechanism to bypass CORS preflight (#210)
- Re: [fetch] RFC: a mechanism to bypass CORS preflight (#210)
- Re: [fetch] RFC: a mechanism to bypass CORS preflight (#210)
- Re: [fetch] RFC: a mechanism to bypass CORS preflight (#210)
- Re: [fetch] RFC: a mechanism to bypass CORS preflight (#210)
- Re: [fetch] RFC: a mechanism to bypass CORS preflight (#210)
- Re: [fetch] RFC: a mechanism to bypass CORS preflight (#210)
- Re: [fetch] RFC: a mechanism to bypass CORS preflight (#210)
[fetch] Should user be prompted in case Request credentials is set to "omit" (#209)
- Re: [fetch] Should user be prompted in case Request credentials is set to "omit" (#209)
- Re: [fetch] Should user be prompted in case Request credentials is set to "omit" (#209)
[fetch] Should request constructor throw in case of invalid enumeration parameter (#208)
- Re: [fetch] Should request constructor throw in case of invalid enumeration parameter (#208)
- Re: [fetch] Should request constructor throw in case of invalid enumeration parameter (#208)
- Re: [fetch] Should request constructor throw in case of invalid enumeration parameter (#208)
[xhr] Sort headers lexicographically in getAllResponseHeaders and combine values too (#50)
[fetch] Use `,` rather than ` ,` for combine operation (#207)
[dom] Fix typo. (#154)
Re: [fetch] Add option to reject the fetch promise automatically after a certain time elapsed (with no API for arbitrary aborts) (#179)
Re: [selection-api] Add a "Selection interface" section (#29)
[xhr] Fix global variable leaks (#49)
- Re: [xhr] Fix global variable leaks (#49)
- Re: [xhr] Fix global variable leaks (#49)
- Re: [xhr] Fix global variable leaks (#49)
[webcomponents] HTML Imports bug link is wrong (#371)
[webcomponents] HTML Imports typo: s/altorighm/algorithm (#370)
[manifest] Enable RDFa (#420)
[ServiceWorker] Should foreign fetch work same-origin? (#826)
- Re: [ServiceWorker] Should foreign fetch work same-origin? (#826)
- Re: [ServiceWorker] Should foreign fetch work same-origin? (#826)
- Re: [ServiceWorker] Should foreign fetch work same-origin? (#826)
[ServiceWorker] Installing a foreign SW as part of a subresource request (#825)
- Re: [ServiceWorker] Installing a foreign SW as part of a subresource request (#825)
- Re: [ServiceWorker] Installing a foreign SW as part of a subresource request (#825)
- Re: [ServiceWorker] Installing a foreign SW as part of a subresource request (#825)
[manifest] Accessible Platform Architectures WG review (#419)
- Re: [manifest] Accessible Platform Architectures WG review (#419)
- Re: [manifest] Accessible Platform Architectures WG review (#419)
- Re: [manifest] Accessible Platform Architectures WG review (#419)
- Re: [manifest] Accessible Platform Architectures WG review (#419)
- Re: [manifest] Accessible Platform Architectures WG review (#419)
- Re: [manifest] Accessible Platform Architectures WG review (#419)
- Re: [manifest] Accessible Platform Architectures WG review (#419)
- Re: [manifest] Accessible Platform Architectures WG review (#419)
- Re: [manifest] Accessible Platform Architectures WG review (#419)
- Re: [manifest] Accessible Platform Architectures WG review (#419)
- Re: [manifest] Accessible Platform Architectures WG review (#419)
Re: [directory-upload] path 'relative to its root directory' (#6)
[fetch] Explain some of the design decisions behind CORS (#206)
Re: [ServiceWorker] How to deal with cookie bombing (#704)
Re: [ServiceWorker] When does the openWindow promise resolve? (#728)
Re: [fetch] Add a bit to Opaque Responses to distinguish redirects (#79)
- Re: [fetch] Add a bit to Opaque Responses to distinguish redirects (#79)
- Re: [fetch] Add a bit to Opaque Responses to distinguish redirects (#79)
Re: [ServiceWorker] Make the Cache API deal with request's redirect mode not being "follow" (#737)
- Re: [ServiceWorker] Make the Cache API deal with request's redirect mode not being "follow" (#737)
- Re: [ServiceWorker] Make the Cache API deal with request's redirect mode not being "follow" (#737)
- Re: [ServiceWorker] Make the Cache API deal with request's redirect mode not being "follow" (#737)
[gamepad] Vibrate feature for Gamepad (#19)
Re: [ServiceWorker] Allow waitUntil to be called multiple times, async (#771)
Re: [ServiceWorker] what should the document base URI for an intercepted navigation (#787)
- Re: [ServiceWorker] what should the document base URI for an intercepted navigation (#787)
- Re: [ServiceWorker] what should the document base URI for an intercepted navigation (#787)
[editing] execCommand('inserttext',...) behavior (#112)
Re: [ServiceWorker] A header-based SW installation (#685)
- Re: [ServiceWorker] A header-based SW installation (#685)
- Re: [ServiceWorker] A header-based SW installation (#685)
- Re: [ServiceWorker] A header-based SW installation (#685)
- Re: [ServiceWorker] A header-based SW installation (#685)
- Re: [ServiceWorker] A header-based SW installation (#685)
- Re: [ServiceWorker] A header-based SW installation (#685)
- Re: [ServiceWorker] A header-based SW installation (#685)
- Re: [ServiceWorker] A header-based SW installation (#685)
[editing] Revert "Remove ContentEditableTrue" (#111)
[webcomponents] Change registries to be per document and never shared between documents (#369)
[webcomponents] Things to definitely document in non-normative notes (#368)
[webcomponents] Add attributeFilter (#367)
- Re: [webcomponents] Add attributeFilter (#367)
- Re: [webcomponents] Add attributeFilter (#367)
- Re: [webcomponents] Add attributeFilter (#367)
- Re: [webcomponents] Add attributeFilter (#367)
- Re: [webcomponents] Add attributeFilter (#367)
[dom] Exclude style="" by default from mutation observers (#153)
[encoding] Replacement encoding should handle empty input better (#33)
[webcomponents] Changes to element creation during parsing per F2F (#366)
[webcomponents] Rename registerElement and change API slightly (#365)
Re: [webcomponents] [Shadow]: Need mechanism to tell if an element in a ShadowRoot has been inserted into the Document (bugzilla: 22141) (#81)
Re: [push-api] Fire pushsubscriptionchange when user revokes permission (#116)
[fetch] error types too vague for TLS certificate error (#205)
Re: [webidl] Rename Date to LegacyDateDoNotUse, or at least add a big warning (#66)
Re: [encoding] iso-2022-jp encoder XSS risks (#15)
- Re: [encoding] iso-2022-jp encoder XSS risks (#15)
- Re: [encoding] iso-2022-jp encoder XSS risks (#15)
- Re: [encoding] iso-2022-jp encoder XSS risks (#15)
- Re: [encoding] iso-2022-jp encoder XSS risks (#15)
- Re: [encoding] iso-2022-jp encoder XSS risks (#15)
- Re: [encoding] iso-2022-jp encoder XSS risks (#15)
- Re: [encoding] iso-2022-jp encoder XSS risks (#15)
- Re: [encoding] iso-2022-jp encoder XSS risks (#15)
- Re: [encoding] iso-2022-jp encoder XSS risks (#15)
- Re: [encoding] iso-2022-jp encoder XSS risks (#15)
- Re: [encoding] iso-2022-jp encoder XSS risks (#15)
[ServiceWorker] Browser Cache and ServiceWorker (#824)
- Re: [ServiceWorker] Browser Cache and ServiceWorker (#824)
- Re: [ServiceWorker] Browser Cache and ServiceWorker (#824)
Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
Re: [fetch] Add option to automatically abort response stream if the data stopped arriving for longer than a specified time (#180)
- Re: [fetch] Add option to automatically abort response stream if the data stopped arriving for longer than a specified time (#180)
- Re: [fetch] Add option to automatically abort response stream if the data stopped arriving for longer than a specified time (#180)
[ServiceWorker] Cache transactions & fixing `addAll` (#823)
- Re: [ServiceWorker] Cache transactions & fixing `addAll` (#823)
- Re: [ServiceWorker] Cache transactions & fixing `addAll` (#823)
- Re: [ServiceWorker] Cache transactions & fixing `addAll` (#823)
- Re: [ServiceWorker] Cache transactions & fixing `addAll` (#823)
- Re: [ServiceWorker] Cache transactions & fixing `addAll` (#823)
- Re: [ServiceWorker] Cache transactions & fixing `addAll` (#823)
- Re: [ServiceWorker] Cache transactions & fixing `addAll` (#823)
- Re: [ServiceWorker] Cache transactions & fixing `addAll` (#823)
- Re: [ServiceWorker] Cache transactions & fixing `addAll` (#823)
- Re: [ServiceWorker] Cache transactions & fixing `addAll` (#823)
- Re: [ServiceWorker] Cache transactions & fixing `addAll` (#823)
- Re: [ServiceWorker] Cache transactions & fixing `addAll` (#823)
- Re: [ServiceWorker] Cache transactions & fixing `addAll` (#823)
- Re: [ServiceWorker] Cache transactions & fixing `addAll` (#823)
- Re: [ServiceWorker] Cache transactions & fixing `addAll` (#823)
- Re: [ServiceWorker] Cache transactions & fixing `addAll` (#823)
- Re: [ServiceWorker] Cache transactions & fixing `addAll` (#823)
- Re: [ServiceWorker] Cache transactions & fixing `addAll` (#823)
- Re: [ServiceWorker] Cache transactions & fixing `addAll` (#823)
- Re: [ServiceWorker] Cache transactions & fixing `addAll` (#823)
- Re: [ServiceWorker] Cache transactions & fixing `addAll` (#823)
- Re: [ServiceWorker] Cache transactions & fixing `addAll` (#823)
- Re: [ServiceWorker] Cache transactions & fixing `addAll` (#823)
- Re: [ServiceWorker] Cache transactions & fixing `addAll` (#823)
- Re: [ServiceWorker] Cache transactions & fixing `addAll` (#823)
- Re: [ServiceWorker] Cache transactions & fixing `addAll` (#823)
- Re: [ServiceWorker] Cache transactions & fixing `addAll` (#823)
- Re: [ServiceWorker] Cache transactions & fixing `addAll` (#823)
- Re: [ServiceWorker] Cache transactions & fixing `addAll` (#823)
[encoding] Consider making the DOM name the canonical name (#32)
- Re: [encoding] Consider making the DOM name the canonical name (#32)
- Re: [encoding] Consider making the DOM name the canonical name (#32)
- Re: [encoding] Consider making the DOM name the canonical name (#32)
- Re: [encoding] Consider making the DOM name the canonical name (#32)
[webcomponents] attributeChanged callback should be invoked on every attribute upon creation (#364)
[webcomponents] Disallow extension of subclasses of HTMLElement and SVGElement/MathMLElement (#363)
[webcomponents] Replace attached/detached callbacks with insertedIntoDocument/removedFromDocument (#362)
- Re: [webcomponents] Replace attached/detached callbacks with insertedIntoDocument/removedFromDocument (#362)
- Re: [webcomponents] Replace attached/detached callbacks with insertedIntoDocument/removedFromDocument (#362)
- Re: [webcomponents] Replace attached/detached callbacks with insertedIntoDocument/removedFromDocument (#362)
- Re: [webcomponents] Replace attached/detached callbacks with insertedIntoDocument/removedFromDocument (#362)
- Re: [webcomponents] Replace attached/detached callbacks with insertedIntoDocument/removedFromDocument (#362)
- Re: [webcomponents] Replace attached/detached callbacks with insertedIntoDocument/removedFromDocument (#362)
[webidl] Fix a typo in a link: "environemnt" (#86)
[encoding] SHIFT_JISX0213 are not supported. (#31)
- Re: [encoding] SHIFT_JISX0213 are not supported. (#31)
- Re: [encoding] SHIFT_JISX0213 are not supported. (#31)
- Re: [encoding] SHIFT_JISX0213 are not supported. (#31)
- Re: [encoding] SHIFT_JISX0213 are not supported. (#31)
- Re: [encoding] SHIFT_JISX0213 are not supported. (#31)
- Re: [encoding] SHIFT_JISX0213 are not supported. (#31)
[encoding] Creating test suites for each encoding. (#30)
- Re: [encoding] Creating test suites for each encoding. (#30)
- Re: [encoding] Creating test suites for each encoding. (#30)
- Re: [encoding] Creating test suites for each encoding. (#30)
- Re: [encoding] Creating test suites for each encoding. (#30)
- Re: [encoding] Creating test suites for each encoding. (#30)
- Re: [encoding] Creating test suites for each encoding. (#30)
[dom] Lock a few IDs into place, so a recent Bikeshed update wont' change them. (#152)
- Re: [dom] Lock a few IDs into place, so a recent Bikeshed update wont' change them. (#152)
- Re: [dom] Lock a few IDs into place, so a recent Bikeshed update wont' change them. (#152)
[fetch] Redirect on preflighted CORS requests generally impossible (#204)
- Re: [fetch] Redirect on preflighted CORS requests generally impossible (#204)
- Re: [fetch] Redirect on preflighted CORS requests generally impossible (#204)
- Re: [fetch] Redirect on preflighted CORS requests generally impossible (#204)
- Re: [fetch] Redirect on preflighted CORS requests generally impossible (#204)
- Re: [fetch] Redirect on preflighted CORS requests generally impossible (#204)
[url] Confused about the constructor argument types (#80)
- Re: [url] Confused about the constructor argument types (#80)
- Re: [url] Confused about the constructor argument types (#80)
- Re: [url] Confused about the constructor argument types (#80)
- Re: [url] Confused about the constructor argument types (#80)
[encoding] Introduce "output encoding" (#29)
Re: [ServiceWorker] Proposal: Optimized No-Fetch Service Workers (#718)
- Re: [ServiceWorker] Proposal: Optimized No-Fetch Service Workers (#718)
- Re: [ServiceWorker] Proposal: Optimized No-Fetch Service Workers (#718)
- Re: [ServiceWorker] Proposal: Optimized No-Fetch Service Workers (#718)
- Re: [ServiceWorker] Proposal: Optimized No-Fetch Service Workers (#718)
Re: [ServiceWorker] Receivers of ranged responses must ensure all ranges come from the same underlying resource (#703)
- Re: [ServiceWorker] Receivers of ranged responses must ensure all ranges come from the same underlying resource (#703)
- Re: [ServiceWorker] Receivers of ranged responses must ensure all ranges come from the same underlying resource (#703)
Re: [webcomponents] [Shadow]: Style element should specify when to create and add style sheet in shadow DOM (bugzilla: 26850) (#56)
- Re: [webcomponents] [Shadow]: Style element should specify when to create and add style sheet in shadow DOM (bugzilla: 26850) (#56)
- Re: [webcomponents] [Shadow]: Style element should specify when to create and add style sheet in shadow DOM (bugzilla: 26850) (#56)
- Re: [webcomponents] [Shadow]: Style element should specify when to create and add style sheet in shadow DOM (bugzilla: 26850) (#56)
- Re: [webcomponents] [Shadow]: Style element should specify when to create and add style sheet in shadow DOM (bugzilla: 26850) (#56)
[WebPlatformWG] Add Justin Fagnani and Monica Dinculescu to attendee list (#12)
[ServiceWorker] Preventing server-forced updates (#822)
- Re: [ServiceWorker] Preventing server-forced updates (#822)
- Re: [ServiceWorker] Preventing server-forced updates (#822)
- Re: [ServiceWorker] Preventing server-forced updates (#822)
[fetch] Headers.get/getAll/has do not byte-lowercase the name (#203)
[WebPlatformWG] Update 25janWC.md (#11)
[fetch] Algorithm for exluded headers in CORS filtered responses is hard to parse (#202)
- Re: [fetch] Algorithm for excluded headers in CORS filtered responses is hard to parse (#202)
- Re: [fetch] Algorithm for excluded headers in CORS filtered responses is hard to parse (#202)
- Re: [fetch] Algorithm for excluded headers in CORS filtered responses is hard to parse (#202)
- Re: [fetch] Algorithm for excluded headers in CORS filtered responses is hard to parse (#202)
[fetch] RequestCache "reload" type must also set no-cache headers (#201)
- Re: [fetch] RequestCache "reload" type must also set no-cache headers (#201)
- Re: [fetch] RequestCache "reload" type must also set no-cache headers (#201)
- Re: [fetch] RequestCache "reload" type must also set no-cache headers (#201)
- Re: [fetch] RequestCache "reload" type must also set no-cache headers (#201)
[IndexedDB] Why is delete() restricted to IDBCursorWithValue? (#62)
- Re: [IndexedDB] Why is delete() disallowed for key cursors? (#62)
- Re: [IndexedDB] Why is delete() disallowed for key cursors? (#62)
- Re: [IndexedDB] Why is delete() disallowed for key cursors? (#62)
[url] Parsing an empty host (#79)
- Re: [url] Parsing an empty host (#79)
- Re: [url] Parsing an empty host (#79)
- Re: [url] Parsing an empty host (#79)
- Re: [url] Parsing an empty host (#79)
- Re: [url] Parsing an empty host (#79)
- Re: [url] Parsing an empty host (#79)
- Re: [url] Parsing an empty host (#79)
- Re: [url] Parsing an empty host (#79)
[ServiceWorker] skip waiting flag purges active worker early (#821)
- Re: [ServiceWorker] skip waiting flag purges active worker early (#821)
- Re: [ServiceWorker] skip waiting flag purges active worker early (#821)
- Re: [ServiceWorker] skip waiting flag purges active worker early (#821)
Re: [ServiceWorker] should update on navigation or the subsequent updatefound event be delayed until document DOM is loaded? (#788)
- Re: [ServiceWorker] should update on navigation or the subsequent updatefound event be delayed until document DOM is loaded? (#788)
- Re: [ServiceWorker] should update on navigation or the subsequent updatefound event be delayed until document DOM is loaded? (#788)
- Re: [ServiceWorker] should update on navigation or the subsequent updatefound event be delayed until document DOM is loaded? (#788)
Re: [xhr] Creating an ArrayBuffer can fail (#26)
Re: [ServiceWorker] matchAll() runs Request constructor off the main thread (#672)
- Re: [ServiceWorker] matchAll() runs Request constructor off the main thread (#672)
- Re: [ServiceWorker] matchAll() runs Request constructor off the main thread (#672)
Re: [webcomponents] [Shadow]: Have a common interface between Document and ShadowRoot (bugzilla: 28493) (#91)
[fetch] Replace byte stream with ReadableStream. (#200)
- Re: [fetch] Replace byte stream with ReadableStream. (#200)
- Re: [fetch] Replace byte stream with ReadableStream. (#200)
- Re: [fetch] Replace byte stream with ReadableStream. (#200)
- Re: [fetch] Replace byte stream with ReadableStream. (#200)
- Re: [fetch] Replace byte stream with ReadableStream. (#200)
- Re: [fetch] Replace byte stream with ReadableStream. (#200)
- Re: [fetch] Replace byte stream with ReadableStream. (#200)
- Re: [fetch] Replace byte stream with ReadableStream. (#200)
- Re: [fetch] Replace byte stream with ReadableStream. (#200)
- Re: [fetch] Replace byte stream with ReadableStream. (#200)
- Re: [fetch] Replace byte stream with ReadableStream. (#200)
- Re: [fetch] Replace byte stream with ReadableStream. (#200)
- Re: [fetch] Replace byte stream with ReadableStream. (#200)
- Re: [fetch] Replace byte stream with ReadableStream. (#200)
- Re: [fetch] Replace byte stream with ReadableStream. (#200)
- Re: [fetch] Replace byte stream with ReadableStream. (#200)
- Re: [fetch] Replace byte stream with ReadableStream. (#200)
Re: [webcomponents] [Shadow]: Node should expose their scope so that shared state can be scoped to components. (bugzilla: 22080) (#80)
Re: [webcomponents] How the current model and the v1 model should interact? (#130)
Re: [directory-upload] easier way to determine if something is a directory? (#24)
Re: [directory-upload] It isn't clear whether Directory.path should include the name of the directory itself (#10)
Re: [directory-upload] Easier way to get files without complicated asynchronous traversal code (#26)
Re: [ServiceWorker] Is fetchEvent.client a performance concern? (#723)
- Re: [ServiceWorker] Is fetchEvent.client a performance concern? (#723)
- Re: [ServiceWorker] Is fetchEvent.client a performance concern? (#723)
- Re: [ServiceWorker] Is fetchEvent.client a performance concern? (#723)
Re: [directory-upload] Bikeshed: getFilesAndDirectories() (#25)
- Re: [directory-upload] Bikeshed: getFilesAndDirectories() (#25)
- Re: [directory-upload] Bikeshed: getFilesAndDirectories() (#25)
[xhr] "For the purposes of interaction with other algo..." (#48)
- Re: [xhr] "For the purposes of interaction with other algo..." (#48)
- Re: [xhr] "For the purposes of interaction with other algo..." (#48)
[xhr] first step of open() method does not work in workers anymore (#47)
[xhr] Remove references to the storage mutex (#46)
- Re: [xhr] Remove references to the storage mutex (#46)
- Re: [xhr] Remove references to the storage mutex (#46)
- Re: [xhr] Remove references to the storage mutex (#46)
[push-api] A lower level version of #180 (#182)
- Re: [push-api] A lower level version of #180 (#182)
- Re: [push-api] A lower level version of #180 (#182)
- Re: [push-api] Provide support for subscription association (#182)
- Re: [push-api] Provide support for subscription association (#182)
- Re: [push-api] Provide support for subscription association (#182)
- Re: [push-api] Provide support for subscription association (#182)
[push-api] It's PushEvent, not PushMessageEvent (#181)
- Re: [push-api] It's PushEvent, not PushMessageEvent (#181)
- Re: [push-api] It's PushEvent, not PushMessageEvent (#181)
- Re: [push-api] It's PushEvent, not PushMessageEvent (#181)
[push-api] Voluntary server identification, WebCrypto version (#180)
- Re: [push-api] Voluntary server identification, WebCrypto version (#180)
- Re: [push-api] Voluntary server identification, WebCrypto version (#180)
[ServiceWorker] Save initial files into cache storage instead of browser's cache (#820)
[ServiceWorker] Update service worker with a response object (#819)
- Re: [ServiceWorker] Update service worker with a response object (#819)
- Re: [ServiceWorker] Update service worker with a response object (#819)
[fetch] Fix a typo on "constructing a ReadableStream" algorithm. (#199)
- Re: [fetch] Fix a typo on "constructing a ReadableStream" algorithm (#199)
- Re: [fetch] Fix a typo on "constructing a ReadableStream" algorithm (#199)
[xhr] "Release the storage mutex. " (#45)
- Re: [xhr] "Release the storage mutex. " (#45)
- Re: [xhr] "Release the storage mutex. " (#45)
- Re: [xhr] "Release the storage mutex. " (#45)
Re: [uievents] CustomEvent.initCustomEvent() is in DOM (#45)
- Re: [uievents] CustomEvent.initCustomEvent() is in DOM (#45)
- Re: [uievents] CustomEvent.initCustomEvent() is in DOM (#45)
Re: [uievents] FocusEvent.initFocusEvent is not needed for web compat (#44)
Re: [uievents] Reference to createEvent("FocusEvent") (#41)
Re: [uievents] Should not recommend DocumentEvent.createEvent (#51)
Re: [uievents-key] AudioVolume(Down|Up|Mute) shouldn't be changed from Volume(Down|Up|Mute)? (#14)
Re: [uievents-code] Mismatch between code value, Volume(Down|Up|Mute) and key value AudioVolume(Down|Up|Mut) (#8)
Re: [uievents] scroll should be a simple Event not a UIEvent (#47)
Re: [uievents] Broken links make documentation useless (#53)
[url] Add a note in the URL parser. (#78)
[dom] Fix #146: Only run adopting steps when changing documents (#151)
- Re: [dom] Fix #146: Only run adopting steps when changing documents (#151)
- Re: [dom] Fix #146: Only run adopting steps when changing documents (#151)
- Re: [dom] Fix #146: Only run adopting steps when changing documents (#151)
- Re: [dom] Fix #146: Only run adopting steps when changing documents (#151)
- Re: [dom] Fix #146: Only run adopting steps when changing documents (#151)
- Re: [dom] Fix #146: Only run adopting steps when changing documents (#151)
[fetch] Only append Authorization if none is set (#198)
- Re: [fetch] Only append Authorization if none is set (#198)
- Re: [fetch] Only append Authorization if none is set (#198)
- Re: [fetch] Only append Authorization if none is set (#198)
- Re: [fetch] Only append Authorization if none is set (#198)
- Re: [fetch] Only append Authorization if none is set (#198)
- Re: [fetch] Only append Authorization if none is set (#198)
[permissions] Update contributing.md (#58)
[permissions] Mediacapture permissions (#57)
- Re: [permissions] Mediacapture permissions (#57)
- Re: [permissions] Mediacapture permissions (#57)
- Re: [permissions] Mediacapture permissions (#57)
- Re: [permissions] Mediacapture permissions (#57)
- Re: [permissions] Mediacapture permissions (#57)
- Re: [permissions] Mediacapture permissions (#57)
- Re: [permissions] Mediacapture permissions (#57)
- Re: [permissions] Mediacapture permissions (#57)
- Re: [permissions] Mediacapture permissions (#57)
- Re: [permissions] Mediacapture permissions (#57)
- Re: [permissions] Mediacapture permissions (#57)
- Re: [permissions] Mediacapture permissions (#57)
- Re: [permissions] Mediacapture permissions (#57)
- Re: [permissions] Mediacapture permissions (#57)
- Re: [permissions] Mediacapture permissions (#57)
- Re: [permissions] Mediacapture permissions (#57)
- Re: [permissions] Mediacapture permissions (#57)
- Re: [permissions] Mediacapture permissions (#57)
- Re: [permissions] Mediacapture permissions (#57)
- Re: [permissions] Mediacapture permissions (#57)
[permissions] contributing.md file says webapps is the WG to call, while document says webappsec (#56)
- Re: [permissions] contributing.md file says webapps is the WG to call, while document says webappsec (#56)
- Re: [permissions] contributing.md file says webapps is the WG to call, while document says webappsec (#56)
[xhr] "relative flag" outdated terminology? (#44)
- Re: [xhr] "relative flag" outdated terminology? (#44)
- Re: [xhr] "relative flag" outdated terminology? (#44)
[manifest] Add ack to Dave and myself for HTML5Apps contribution (#418)
- Re: [manifest] Add ack to Dave and myself for HTML5Apps contribution (#418)
- Re: [manifest] Add ack to Dave and myself for HTML5Apps contribution (#418)
Re: [webidl] Add a [SecureContext] operator attribute (#65)
- Re: [webidl] Add a [SecureContext] operator attribute (#65)
- Re: [webidl] Add a [SecureContext] operator attribute (#65)
- Re: [webidl] Add a [SecureContext] operator attribute (#65)
Re: [webcomponents] [Shadow]: The return type of Event.path should leverage WebIDL sequences (bugzilla: 25458) (#101)
[FileAPI] Bikeshed the spec (#29)
[streams] Fix typos (#426)
Re: [WebPlatformWG] Need PAG for "Web Components vs Extract Widget patent"? (#4)
[encoding] What's the correct choice for BIG5 F9FE? (#28)
- Re: [encoding] What's the correct choice for BIG5 F9FE? (#28)
- Re: [encoding] What's the correct choice for BIG5 F9FE? (#28)
- Re: [encoding] What's the correct choice for BIG5 F9FE? (#28)
- Re: [encoding] What's the correct choice for BIG5 F9FE? (#28)
- Re: [encoding] What's the correct choice for BIG5 F9FE? (#28)
Re: [directory-upload] The spec should define integration with FormData (#14)
[encoding] Remove the last 14 characters PUA of GB18030-2005 (#27)
- Re: [encoding] Remove the last 14 characters PUA of GB18030-2005 (#27)
- Re: [encoding] Remove the last 14 characters PUA of GB18030-2005 (#27)
- Re: [encoding] Remove the last 14 characters PUA of GB18030-2005 (#27)
- Re: [encoding] Remove the last 14 characters PUA of GB18030-2005 (#27)
- Re: [encoding] Remove the last 14 characters PUA of GB18030-2005 (#27)
- Re: [encoding] Remove the last 14 characters PUA of GB18030-2005 (#27)
- Re: [encoding] Remove the last 14 characters PUA of GB18030-2005 (#27)
- Re: [encoding] Remove the last 14 characters PUA of GB18030-2005 (#27)
- Re: [encoding] Remove the last 14 characters PUA of GB18030-2005 (#27)
[webidl] Add NotAllowedError exception (#85)
- Re: [webidl] Add NotAllowedError exception (#85)
- Re: [webidl] Add NotAllowedError exception (#85)
- Re: [webidl] Add NotAllowedError exception (#85)
- Re: [webidl] Add NotAllowedError exception (#85)
- Re: [webidl] Add NotAllowedError exception (#85)
[fetch] Explain cache modes (#197)
[streams] Description of "pull" is misleading (#425)
- Re: [streams] Description of "pull" is misleading (#425)
- Re: [streams] Description of "pull" is misleading (#425)
- Re: [streams] Description of "pull" is misleading (#425)
[streams] Revisiting what's reasonable return value for each method of the controller (#424)
- Re: [streams] Revisiting what's reasonable return value for each method of the controller (#424)
- Re: [streams] Revisiting what's reasonable return value for each method of the controller (#424)
- Re: [streams] Revisiting what's reasonable return value for each method of the controller (#424)
Re: [streams] ReadableByteStream needs reference implementation/tests (#355)
Re: [streams] Consider moving stuff into ReadableStreamController (#364)
Re: [webcomponents] [Shadow]: Add "closed" flag to createShadowRoot (bugzilla: 20144) (#100)
- Re: [webcomponents] [Shadow]: Add "closed" flag to createShadowRoot (bugzilla: 20144) (#100)
- Re: [webcomponents] [Shadow]: Add "closed" flag to createShadowRoot (bugzilla: 20144) (#100)
- Re: [webcomponents] [Shadow]: Add "closed" flag to createShadowRoot (bugzilla: 20144) (#100)
- Re: [webcomponents] [Shadow]: Add "closed" flag to createShadowRoot (bugzilla: 20144) (#100)
- Re: [webcomponents] [Shadow]: Add "closed" flag to createShadowRoot (bugzilla: 20144) (#100)
Re: [ServiceWorker] What's proper SW name? :) (#705)
[streams] Finalize pull/pullInto behavior (#423)
- Re: [streams] Finalize pull/pullInto behavior (#423)
- Re: [streams] Finalize pull/pullInto behavior (#423)
- Re: [streams] Finalize pull/pullInto behavior (#423)
- Re: [streams] Finalize pull/pullInto behavior (#423)
- Re: [streams] Finalize pull/pullInto behavior (#423)
- Re: [streams] Finalize pull/pullInto behavior (#423)
- Re: [streams] Finalize pull/pullInto behavior (#423)
- Re: [streams] Finalize pull/pullInto behavior (#423)
- Re: [streams] Finalize pull/pullInto behavior (#423)
- Re: [streams] Finalize pull/pullInto behavior (#423)
[ServiceWorker] Use “service worker” consistently (#818)
[fetch] Question — Why can I not read the stream again ? (#196)
- Re: [fetch] Question — Why can I not read the stream again ? (#196)
- Re: [fetch] Question — Why can I not read the stream again ? (#196)
- Re: [fetch] Question — Why can I not read the stream again ? (#196)
- Re: [fetch] Question — Why can I not read the stream again ? (#196)
- Re: [fetch] Question — Why can I not read the stream again ? (#196)
- Re: [fetch] Question — Why can I not read the stream again ? (#196)
- Re: [fetch] Question — Why can I not read the stream again ? (#196)
Re: [push-api] Make `PushEvent.data` nullable (#161)
Re: [streams] Readable byte streams should support an internal queue (#353)
Re: [streams] ReadableByteStream: pull + pullInto or just pullInto (#363)
Re: [spec-reviews] W3C Push API - data payloads (#98)
[webidl] provide clearer advice about USVString vs. DOMString (#84)
Re: [spec-reviews] Review Web Annotations specs (#93)
Re: [FileAPI] Bikeshedding the spec (#5)
- Re: [FileAPI] Bikeshedding the spec (#5)
- Re: [FileAPI] Bikeshedding the spec (#5)
- Re: [FileAPI] Bikeshedding the spec (#5)
[xhr] Ajax call to server in synchronous mode <> disrupt user experience! (#43)
- Re: [xhr] Ajax call to server in synchronous mode <> disrupt user experience! (#43)
- Re: [xhr] Ajax call to server in synchronous mode <> disrupt user experience! (#43)
Re: [push-api] Rewriting push event handling; allowing data to be optional. (#166)
- Re: [push-api] Rewriting push event handling; allowing data to be optional. (#166)
- Re: [push-api] Rewriting push event handling; allowing data to be optional. (#166)
- Re: [push-api] Rewriting push event handling; allowing data to be optional. (#166)
Re: [url] IPv4 serializer should use floor(n / 256), not n/256 (#39)
Re: [streams] Investigate merging RS and RBS (#379)
- Re: [streams] Investigate merging RS and RBS (#379)
- Re: [streams] Investigate merging RS and RBS (#379)
- Re: [streams] Investigate merging RS and RBS (#379)
- Re: [streams] Investigate merging RS and RBS (#379)
[ServiceWorker] Is a new property to get the navigation's target client needed? (#817)
[dom] Proposal to improve the DOM creation api (#150)
- Re: [dom] Proposal to improve the DOM creation api (#150)
- Re: [dom] Proposal to improve the DOM creation api (#150)
- Re: [dom] Proposal to improve the DOM creation api (#150)
- Re: [dom] Proposal to improve the DOM creation api (#150)
- Re: [dom] Proposal to improve the DOM creation api (#150)
- Re: [dom] Proposal to improve the DOM creation api (#150)
- Re: [dom] Proposal to improve the DOM creation api (#150)
Re: [spec-reviews] Indexed DB getAll(), openKeyCursor() and objectStoreNames (#84)
Re: [spec-reviews] Streams General issue (#92)
[webcomponents] Use FrozenArray<T> in WebIDL (#361)
- Re: [webcomponents] Use FrozenArray<T> in WebIDL (#361)
- Re: [webcomponents] Use FrozenArray<T> in WebIDL (#361)
- Re: [webcomponents] Use FrozenArray<T> in WebIDL (#361)
- Re: [webcomponents] Use FrozenArray<T> in WebIDL (#361)
- Re: [webcomponents] Use FrozenArray<T> in WebIDL (#361)
- Re: [webcomponents] Use FrozenArray<T> in WebIDL (#361)
- Re: [webcomponents] Use FrozenArray<T> in WebIDL (#361)
- Re: [webcomponents] Use FrozenArray<T> in WebIDL (#361)
- Re: [webcomponents] Use FrozenArray<T> in WebIDL (#361)
- Re: [webcomponents] Use FrozenArray<T> in WebIDL (#361)
- Re: [webcomponents] Use FrozenArray<T> in WebIDL (#361)
- Re: [webcomponents] Use FrozenArray<T> in WebIDL (#361)
- Re: [webcomponents] Use FrozenArray<T> in WebIDL (#361)
Re: [ServiceWorker] Define the lifetime of a blob URL created inside a service worker (#688)
- Re: [ServiceWorker] Define the lifetime of a blob URL created inside a service worker (#688)
- Re: [ServiceWorker] Define the lifetime of a blob URL created inside a service worker (#688)
- Re: [ServiceWorker] Define the lifetime of a blob URL created inside a service worker (#688)
- Re: [ServiceWorker] Define the lifetime of a blob URL created inside a service worker (#688)
Re: [spec-reviews] Geofencing FPWD (#89)
Re: [spec-reviews] Write up the Secure Stop issue for ddorwin (#73)
Re: [spec-reviews] Review FormData additions in XHR (#87)
- Re: [spec-reviews] Review FormData additions in XHR (#87)
- Re: [spec-reviews] Review FormData additions in XHR (#87)
- Re: [spec-reviews] Review FormData additions in XHR (#87)
- Re: [spec-reviews] Review FormData additions in XHR (#87)
- Re: [spec-reviews] Review FormData additions in XHR (#87)
Re: [streams] Rename ReadableByteStream (#405)
Re: [ServiceWorker] Editorial: Reword normative uses of "can" (#795)
Re: [spec-reviews] Network Information API (#86)
Re: [streams] Byte streams tracking bug (#300)
Re: [spec-reviews] Review FIDO spec (#97)
- Re: [spec-reviews] Review FIDO spec (#97)
- Re: [spec-reviews] Review FIDO spec (#97)
- Re: [spec-reviews] Review FIDO spec (#97)
- Re: [spec-reviews] Review FIDO spec (#97)
- Re: [spec-reviews] Review FIDO spec (#97)
- Re: [spec-reviews] Review FIDO spec (#97)
- Re: [spec-reviews] Review FIDO spec (#97)
- Re: [spec-reviews] Review FIDO spec (#97)
- Re: [spec-reviews] Review FIDO spec (#97)
- Re: [spec-reviews] Review FIDO spec (#97)
- Re: [spec-reviews] Review FIDO spec (#97)
- Re: [spec-reviews] Review FIDO spec (#97)
Re: [spec-reviews] Storage persistence (#85)
Re: [spec-reviews] Performance API review (#83)
Re: [spec-reviews] Automotive Working Group - API Refactor or Not? (#81)
- Re: [spec-reviews] Automotive Working Group - API Refactor or Not? (#81)
- Re: [spec-reviews] Automotive Working Group - API Refactor or Not? (#81)
- Re: [spec-reviews] Automotive Working Group - API Refactor or Not? (#81)
Re: [spec-reviews] HTTP Opportunistic Security (#80)
Re: [uievents] Expose 'direction-inversion' in wheel events (#57)
- Re: [uievents] Expose 'direction-inversion' in wheel events (#57)
- Re: [uievents] Expose 'direction-inversion' in wheel events (#57)
- Re: [uievents] Expose 'direction-inversion' in wheel events (#57)
- Re: [uievents] Expose 'direction-inversion' in wheel events (#57)
- Re: [uievents] Expose 'direction-inversion' in wheel events (#57)
- Re: [uievents] Expose 'direction-inversion' in wheel events (#57)
- Re: [uievents] Expose 'direction-inversion' in wheel events (#57)
- Re: [uievents] Expose 'direction-inversion' in wheel events (#57)
Re: [spec-reviews] Secure / Powerful / Features / Contexts (#75)
- Re: [spec-reviews] Secure / Powerful / Features / Contexts (#75)
- Re: [spec-reviews] Secure / Powerful / Features / Contexts (#75)
[url] All instances of %2e in the path should be decoded into `.` (#77)
- Re: [url] All instances of %2e in the path should be decoded into `.` (#77)
- Re: [url] All instances of %2e in the path should be decoded into `.` (#77)
- Re: [url] All instances of %2e in the path should be decoded into `.` (#77)
Re: [ServiceWorker] Foreign fetch (#751)
[DOM-Parsing] Test suite link doesn't link to all the relevant tests (#3)
[streams] Added message to check in bad strategies (#422)
- Re: [streams] Added message to check in bad strategies (#422)
- Re: [streams] Added message to check in bad strategies (#422)
[push-api] Add applicability statement (#179)
Re: [webcomponents] [Shadow]: Need to define what .styleSheets actually does on a shadow root (bugzilla: 27418) (#70)
Re: [webcomponents] Interaction between CSS and composed tree needs to be better defined (#305)
[dom] Resize events needed? (#149)
Re: [webcomponents] It is unclear how tree of tress whose root tree is not a document tree should behave. (#356)
- Re: [webcomponents] It is unclear how tree of tress whose root tree is not a document tree should behave. (#356)
- Re: [webcomponents] It is unclear how tree of tress whose root tree is not a document tree should behave. (#356)
- Re: [webcomponents] It is unclear how tree of tress whose root tree is not a document tree should behave. (#356)
- Re: [webcomponents] It is unclear how tree of tress whose root tree is not a document tree should behave. (#356)
- Re: [webcomponents] It is unclear how tree of tress whose root tree is not a document tree should behave. (#356)
Re: [webcomponents] Resize events needed? (#352)
- Re: [webcomponents] Resize events needed? (#352)
- Re: [webcomponents] Resize events needed? (#352)
- Re: [webcomponents] Resize events needed? (#352)
- Re: [webcomponents] Resize events needed? (#352)
- Re: [webcomponents] Resize events needed? (#352)
- Re: [webcomponents] Resize events needed? (#352)
- Re: [webcomponents] Resize events needed? (#352)
- Re: [webcomponents] Resize events needed? (#352)
Re: [spec-reviews] Potential for coordination about task scheduling (#72)
Re: [webcomponents] Rename Distributed Nodes Algorithm to Slot Assignment Algorithm (#323)
- Re: [webcomponents] Rename Distributed Nodes Algorithm to Slot Assignment Algorithm (#323)
- Re: [webcomponents] Rename Distributed Nodes Algorithm to Slot Assignment Algorithm (#323)
- Re: [webcomponents] Rename Distributed Nodes Algorithm to Slot Assignment Algorithm (#323)
- Re: [webcomponents] Rename Distributed Nodes Algorithm to Slot Assignment Algorithm (#323)
- Re: [webcomponents] Rename Distributed Nodes Algorithm to Slot Assignment Algorithm (#323)
- Re: [webcomponents] Rename Distributed Nodes Algorithm to Slot Assignment Algorithm (#323)
Re: [webcomponents] Event path trimming should only happen for mouseover and mouseout (#330)
- Re: [webcomponents] Event path trimming should only happen for mouseover and mouseout (#330)
- Re: [webcomponents] Event path trimming should only happen for mouseover and mouseout (#330)
Re: [webcomponents] [Shadow]: url fragment identifiers should be followed into ShadowDOM (bugzilla: 23161) (#66)
- Re: [webcomponents] [Shadow]: url fragment identifiers should be followed into ShadowDOM (bugzilla: 23161) (#66)
- Re: [webcomponents] [Shadow]: url fragment identifiers should be followed into ShadowDOM (bugzilla: 23161) (#66)
- Re: [webcomponents] [Shadow]: url fragment identifiers should be followed into ShadowDOM (bugzilla: 23161) (#66)
- Re: [webcomponents] [Shadow]: url fragment identifiers should be followed into ShadowDOM (bugzilla: 23161) (#66)
- Re: [webcomponents] [Shadow]: url fragment identifiers should be followed into ShadowDOM (bugzilla: 23161) (#66)
- Re: [webcomponents] [Shadow]: url fragment identifiers should be followed into ShadowDOM (bugzilla: 23161) (#66)
- Re: [webcomponents] [Shadow]: url fragment identifiers should be followed into ShadowDOM (bugzilla: 23161) (#66)
- Re: [webcomponents] [Shadow]: url fragment identifiers should be followed into ShadowDOM (bugzilla: 23161) (#66)
Re: [webcomponents] ownerDocument of a node in a shadow tree isn't well defined (#303)
Re: [webcomponents] caretPositionFromPoint, elementFromPoint, and elementsFromPoint should respect shadow boundary (#313)
Re: [webcomponents] Combining :host-context and :host (#359)
- Re: [webcomponents] Combining :host-context and :host (#359)
- Re: [webcomponents] Combining :host-context and :host (#359)
- Re: [webcomponents] Combining :host-context and :host (#359)
Re: [spec-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76)
- Re: [spec-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76)
- Re: [spec-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76)
- Re: [spec-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76)
- Re: [spec-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76)
- Re: [spec-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76)
Re: [webcomponents] Restrict the types of nodes that could be assigned to a slot (#351)
- Re: [webcomponents] Restrict the types of nodes that could be assigned to a slot (#351)
- Re: [webcomponents] Restrict the types of nodes that could be assigned to a slot (#351)
- Re: [webcomponents] Restrict the types of nodes that could be assigned to a slot (#351)
- Re: [webcomponents] Restrict the types of nodes that could be assigned to a slot (#351)
- Re: [webcomponents] Restrict the types of nodes that could be assigned to a slot (#351)
Re: [spec-reviews] Unblocking the HTTPS Transitions (#74)
- Re: [spec-reviews] Unblocking the HTTPS Transitions (#74)
- Re: [spec-reviews] Unblocking the HTTPS Transitions (#74)
Re: [spec-reviews] CSS font-display (#71)
Re: [spec-reviews] requestIdleCallback (#70)
Re: [spec-reviews] Cross-spec device identification & association (#64)
Re: [spec-reviews] Sketch out proposals for event synthesis/flow and reusable a11y behavior (#63)
Re: [spec-reviews] Presentation API Request for Feedback (#61)
Re: [spec-reviews] CSSOM View document.scrollingElement (#51)
[spec-reviews] Privacy Mode (#101)
[uievents] We should fire beforeInput event before compositioinupdate. (#67)
[uievents] Should DOM be modified before or after compositionupdate? edge/IE do one thing, chrome/saf/firefox do another? (#66)
[editing] inputType should be tied to the command names and having that tied to a way of declaring what you support (#110)
[editing] Should DOM be modified before or after compositionupdate? edge/IE do one thing, chrome/saf/firefox do another? (#109)
- Re: [editing] Should DOM be modified before or after compositionupdate? edge/IE do one thing, chrome/saf/firefox do another? (#109)
- Re: [editing] Should DOM be modified before or after compositionupdate? edge/IE do one thing, chrome/saf/firefox do another? (#109)
[editing] • Currently, there are multiple documents that pertain to editing. We should merge all the editing related specs into one (#108)
[editing] We should ensure drag/drop also fires beforeInput (#107)
[editing] We should keep data in UI events for beforeInput that does the text/plain serialization. We should add dataTransfer to the editing spec for other mime types(html, text with line breaks, etc) (#106)
[editing] We could have "data" property that returns the text/plain version and a dataTransfer field for richer things. (#105)
[editing] We should update the spec with an ImmutableStaticRange that is a subset of the Range interface and return them via the getTargetRanges method. s/ImmutableStaticRange/StaticRange/ in the actual spec (#104)
[editing] isComposing field should be consistent with the composition events, no need to redefine it. So just provide a reference to spec. (#103)
- Re: [editing] isComposing field should be consistent with the composition events, no need to redefine it. So just provide a reference to spec. (#103)
- Re: [editing] isComposing field should be consistent with the composition events, no need to redefine it. So just provide a reference to spec. (#103)
- Re: [editing] isComposing field should be consistent with the composition events, no need to redefine it. So just provide a reference to spec. (#103)
[editing] Chrome/Safari need to fix a bug. Compositioinupdate is not firing before the compositionend. (#102)
- Re: [editing] Chrome/Safari need to fix a bug. Compositioinupdate is not firing before the compositionend. (#102)
- Re: [editing] Chrome/Safari need to fix a bug. Compositioinupdate is not firing before the compositionend. (#102)
- Re: [editing] Chrome/Safari need to fix a bug. Compositioinupdate is not firing before the compositionend. (#102)
[editing] We should fire beforeInput event before compositioinupdate. (#101)
- Re: [editing] We should fire beforeInput event before compositioinupdate. (#101)
- Re: [editing] We should fire beforeInput event before compositioinupdate. (#101)
[editing] Cancelable attribute should be removed from the spec because it already referenced in Event.idl (#100)
[editing] Base definition and ordering of beforeInput/input events should be in UI events, but the editing specific stuff should be in a separate editing spec. (#99)
- Re: [editing] Base definition and ordering of beforeInput/input events should be in UI events, but the editing specific stuff should be in a separate editing spec. (#99)
- Re: [editing] Base definition and ordering of beforeInput/input events should be in UI events, but the editing specific stuff should be in a separate editing spec. (#99)
[editing] We should remove EditTypes/InputTypes it from the UI events spec. It should be specced in editing Spec. (#98)
- Re: [editing] We should remove EditTypes/InputTypes it from the UI events spec. It should be specced in editing Spec. (#98)
- Re: [editing] We should remove EditTypes/InputTypes it from the UI events spec. It should be specced in editing Spec. (#98)
- Re: [editing] We should remove EditTypes/InputTypes it from the UI events spec. It should be specced in editing Spec. (#98)
[editing] rename EditTypes to InputTypes for beforeInput events (#97)
- Re: [editing] rename EditTypes to InputTypes for beforeInput events (#97)
- Re: [editing] rename EditTypes to InputTypes for beforeInput events (#97)
[editing] beforeInput/input events should be fired for any element with contentEditable enabled, input and textArea elements where input element and textArea will have targetRanges set to null. (#96)
[spec-reviews] Create a document to explain web platform async timing entry-points (#100)
- Re: [spec-reviews] Create a document to explain web platform async timing entry-points (#100)
- Re: [spec-reviews] Create a document to explain web platform async timing entry-points (#100)
- Re: [spec-reviews] Create a document to explain web platform async timing entry-points (#100)
- Re: [spec-reviews] Create a document to explain web platform async timing entry-points (#100)
- Re: [spec-reviews] Create a document to explain web platform async timing entry-points (#100)
- Re: [spec-reviews] Create a document to explain web platform async timing entry-points (#100)
Re: [spec-reviews] Security Questionnaire (#77)
Re: [spec-reviews] Credential Management API (#49)
Re: [spec-reviews] CSP (#42)
Re: [spec-reviews] Performance Observer Review (formerly Navigation Timing 2 concepts) (#18)
Re: [spec-reviews] Browser Fingerprinting Document (#38)
- Re: [spec-reviews] Browser Fingerprinting Document (#38)
- Re: [spec-reviews] Browser Fingerprinting Document (#38)
- Re: [spec-reviews] Browser Fingerprinting Document (#38)
- Re: [spec-reviews] Browser Fingerprinting Document (#38)
- Re: [spec-reviews] Browser Fingerprinting Document (#38)
- Re: [spec-reviews] Browser Fingerprinting Document (#38)
Re: [spec-reviews] WebRTC (#14)
- Re: [spec-reviews] WebRTC (#14)
- Re: [spec-reviews] WebRTC (#14)
- Re: [spec-reviews] WebRTC (#14)
- Re: [spec-reviews] WebRTC (#14)
Re: [webidl] Move the overload resolution algorithm into a separate section. (#77)
[dom] Drop "keyevents" as an alias of "keyboardevent" for createEvent (#148)
- Re: [dom] Drop "keyevents" as an alias of "keyboardevent" for createEvent (#148)
- Re: [dom] Drop "keyevents" as an alias of "keyboardevent" for createEvent (#148)
- Re: [dom] Drop "keyevents" as an alias of "keyboardevent" for createEvent (#148)
- Re: [dom] Drop "keyevents" as an alias of "keyboardevent" for createEvent (#148)
[dom] Consider support for ES2015 iterator protocol for NodeIterator (#147)
[fetch] "компания IMG-ФОК " (#195)
[dom] Only run "adopting steps" if oldDocument !== document (#146)
- Re: [dom] Only run "adopting steps" if oldDocument !== document (#146)
- Re: [dom] Only run "adopting steps" if oldDocument !== document (#146)
- Re: [dom] Only run "adopting steps" if oldDocument !== document (#146)
[xhr] Fix typo in FormData idl (#42)
- Re: [xhr] Fix typo in FormData idl (#42)
- Re: [xhr] Fix typo in FormData idl (#42)
- Re: [xhr] Fix typo in FormData idl (#42)
- Re: [xhr] Fix typo in FormData idl (#42)
- Re: [xhr] Fix typo in FormData idl (#42)
- Re: [xhr] Fix typo in FormData idl (#42)
Re: [manifest] Add integrity to image objects (#411)
Re: [webcomponents] Style attributes in Shadow DOM Cascade Order Proposal (#316)
- Re: [webcomponents] Style attributes in Shadow DOM Cascade Order Proposal (#316)
- Re: [webcomponents] Style attributes in Shadow DOM Cascade Order Proposal (#316)
- Re: [webcomponents] Style attributes in Shadow DOM Cascade Order Proposal (#316)
- Re: [webcomponents] Style attributes in Shadow DOM Cascade Order Proposal (#316)
Re: [streams] Improved tests abour erroring a RS when enqueing (#420)
- Re: [streams] Improved tests abour erroring a RS when enqueing (#420)
- Re: [streams] Improved tests abour erroring a RS when enqueing (#420)
[fetch] Introduce HTTP-redirect fetch (#194)
[fetch] Fix #169: ban combination of "no-cors" and "same-origin" (#193)
- Re: [fetch] Fix #169: ban combination of "no-cors" and "same-origin" (#193)
- Re: [fetch] Fix #169: ban combination of "no-cors" and "same-origin" (#193)
Re: [selection-api] Make some arguments optional (#30)
- Re: [selection-api] Make some arguments optional (#30)
- Re: [selection-api] Make some arguments optional (#30)
- Re: [selection-api] Make some arguments optional (#30)
- Re: [selection-api] Make some arguments optional (#30)
Re: [selection-api] The spec doesn't define event handlers onselectstart and onselectionchange (#55)
- Re: [selection-api] The spec doesn't define event handlers onselectstart and onselectionchange (#55)
Re: [selection-api] The node argument of collapse and setPosition should be nullable (#64)
- Re: [selection-api] The node argument of collapse and setPosition should be nullable (#64)
- Re: [selection-api] The node argument of collapse and setPosition should be nullable (#64)
[ServiceWorker] ExtendableMessageEvent.source cannot be SameObject (#816)
- Re: [ServiceWorker] ExtendableMessageEvent.source cannot be SameObject (#816)
- Re: [ServiceWorker] ExtendableMessageEvent.source cannot be SameObject (#816)
- Re: [ServiceWorker] ExtendableMessageEvent.source cannot be SameObject (#816)
[ServiceWorker] FetchEvent's constructor's second argument must be optional (#815)
- Re: [ServiceWorker] FetchEvent's constructor's second argument must be optional (#815)
- Re: [ServiceWorker] FetchEvent's constructor's second argument must be optional (#815)
- Re: [ServiceWorker] FetchEvent's constructor's second argument must be optional (#815)
- Re: [ServiceWorker] FetchEvent's constructor's second argument must be optional (#815)
- Re: [ServiceWorker] FetchEvent's constructor's second argument must be optional (#815)
- Re: [ServiceWorker] FetchEvent's constructor's second argument must be optional (#815)
- Re: [ServiceWorker] FetchEvent's constructor's second argument must be optional (#815)
- Re: [ServiceWorker] FetchEvent's constructor's second argument must be optional (#815)
[editing] Remove ContentEditableTrue (#95)
- Re: [editing] Remove ContentEditableTrue (#95)
- Re: [editing] Remove ContentEditableTrue (#95)
- Re: [editing] Remove ContentEditableTrue (#95)
- Re: [editing] Remove ContentEditableTrue (#95)
- Re: [editing] Remove ContentEditableTrue (#95)
- Re: [editing] Remove ContentEditableTrue (#95)
- Re: [editing] Remove ContentEditableTrue (#95)
- Re: [editing] Remove ContentEditableTrue (#95)
[fetch] add a missing space (#192)
- Re: [fetch] add a missing space (#192)
- Re: [fetch] add a missing space (#192)
- Re: [fetch] add a missing space (#192)
- Re: [fetch] add a missing space (#192)
[xhr] FormData.set has 3 params variant in implementations but not in the spec (#41)
- Re: [xhr] FormData.set has 3 params variant in implementations but not in the spec (#41)
- Re: [xhr] FormData.set has 3 params variant in implementations but not in the spec (#41)
- Re: [xhr] FormData.set has 3 params variant in implementations but not in the spec (#41)
Re: [touch-events] rotationAngle range of 0-90 seems counterintuitive - add a diagram? (#53)
[ServiceWorker] should subresource FetchEvents trigger an update if 24-hours since last check? (#814)
- Re: [ServiceWorker] should subresource FetchEvents trigger an update if 24-hours since last check? (#814)
- Re: [ServiceWorker] should subresource FetchEvents trigger an update if 24-hours since last check? (#814)
- Re: [ServiceWorker] should subresource FetchEvents trigger an update if 24-hours since last check? (#814)
- Re: [ServiceWorker] should subresource FetchEvents trigger an update if 24-hours since last check? (#814)
- Re: [ServiceWorker] should subresource FetchEvents trigger an update if 24-hours since last check? (#814)
- Re: [ServiceWorker] should subresource FetchEvents trigger an update if 24-hours since last check? (#814)
Re: [fetch] Replace "flags" with "booleans" (#175)
Re: [fetch] "Let internalResponse be response's internal res..." (#171)
[fetch] Add a way to copy Requests with a different URL (#191)
Re: [streams] Target for web-platform-tests streams API tests (#411)
- Re: [streams] Target for web-platform-tests streams API tests (#411)
- Re: [streams] Target for web-platform-tests streams API tests (#411)
- Re: [streams] Target for web-platform-tests streams API tests (#411)
- Re: [streams] Target for web-platform-tests streams API tests (#411)
Re: [fetch] "no-cors" and credentials mode (#169)
- Re: [fetch] "no-cors" and credentials mode (#169)
- Re: [fetch] "no-cors" and credentials mode (#169)
- Re: [fetch] "no-cors" and credentials mode (#169)
- Re: [fetch] "no-cors" and credentials mode (#169)
- Re: [fetch] "no-cors" and credentials mode (#169)
- Re: [fetch] "no-cors" and credentials mode (#169)
- Re: [fetch] "no-cors" and credentials mode (#169)
- Re: [fetch] "no-cors" and credentials mode (#169)
- Re: [fetch] "no-cors" and credentials mode (#169)
- Re: [fetch] "no-cors" and credentials mode (#169)
- Re: [fetch] "no-cors" and credentials mode (#169)
- Re: [fetch] "no-cors" and credentials mode (#169)
- Re: [fetch] "no-cors" and credentials mode (#169)
- Re: [fetch] "no-cors" and credentials mode (#169)
- Re: [fetch] "no-cors" and credentials mode (#169)
- Re: [fetch] "no-cors" and credentials mode (#169)
- Re: [fetch] "no-cors" and credentials mode (#169)
- Re: [fetch] "no-cors" and credentials mode (#169)
- Re: [fetch] "no-cors" and credentials mode (#169)
Re: [fetch] Question about credentials mode of no-cors mode requests. (#168)
- Re: [fetch] Question about credentials mode of no-cors mode requests. (#168)
- Re: [fetch] Question about credentials mode of no-cors mode requests. (#168)
Re: [fetch] Tests (#62)
Re: [fetch] Response.prototype.clone() should take into account the internal response. (#148)
[ServiceWorker] Should mixed content always be blocked? (#813)
- Re: [ServiceWorker] Should mixed content always be blocked? (#813)
- Re: [ServiceWorker] Should mixed content always be blocked? (#813)
- Re: [ServiceWorker] Should mixed content always be blocked? (#813)
- Re: [ServiceWorker] Should mixed content always be blocked? (#813)
- Re: [ServiceWorker] Should mixed content always be blocked? (#813)
- Re: [ServiceWorker] Should mixed content always be blocked? (#813)
- Re: [ServiceWorker] Should mixed content always be blocked? (#813)
- Re: [ServiceWorker] Should mixed content always be blocked? (#813)
- Re: [ServiceWorker] Should mixed content always be blocked? (#813)
- Re: [ServiceWorker] Should mixed content always be blocked? (#813)
- Re: [ServiceWorker] Should mixed content always be blocked? (#813)
- Re: [ServiceWorker] Should mixed content always be blocked? (#813)
- Re: [ServiceWorker] Should mixed content always be blocked? (#813)
Re: [streams] Move stuff into controller to make RS and RBS closer (#418)
- Re: [streams] Move stuff into controller to make RS and RBS closer (#418)
- Re: [streams] Move stuff into controller to make RS and RBS closer (#418)
- Re: [streams] Move stuff into controller to make RS and RBS closer (#418)
- Re: [streams] Move stuff into controller to make RS and RBS closer (#418)
- Re: [streams] Move stuff into controller to make RS and RBS closer (#418)
- Re: [streams] Move stuff into controller to make RS and RBS closer (#418)
- Re: [streams] Move stuff into controller to make RS and RBS closer (#418)
- Re: [streams] Move stuff into controller to make RS and RBS closer (#418)
- Re: [streams] Move stuff into controller to make RS and RBS closer (#418)
- Re: [streams] Move stuff into controller to make RS and RBS closer (#418)
- Re: [streams] Move stuff into controller to make RS and RBS closer (#418)
- Re: [streams] Move stuff into controller to make RS and RBS closer (#418)
- Re: [streams] Move stuff into controller to make RS and RBS closer (#418)
- Re: [streams] Move stuff into controller to make RS and RBS closer (#418)
- Re: [streams] Move stuff into controller to make RS and RBS closer (#418)
- Re: [streams] Move stuff into controller to make RS and RBS closer (#418)
- Re: [streams] Move stuff into controller to make RS and RBS closer (#418)
- Re: [streams] Move stuff into controller to make RS and RBS closer (#418)
- Re: [streams] Move stuff into controller to make RS and RBS closer (#418)
- Re: [streams] Move stuff into controller to make RS and RBS closer (#418)
- Re: [streams] Move stuff into controller to make RS and RBS closer (#418)
- Re: [streams] Move stuff into controller to make RS and RBS closer (#418)
- Re: [streams] Move stuff into controller to make RS and RBS closer (#418)
- Re: [streams] Move stuff into controller to make RS and RBS closer (#418)
- Re: [streams] Move stuff into controller to make RS and RBS closer (#418)
[ServiceWorker] Service worker state on system restart (#812)
- Re: [ServiceWorker] Service worker state on system restart (#812)
- Re: [ServiceWorker] Service worker state on system restart (#812)
Re: [streams] Fix the spec for the last commit (4ba861e)
[uievents] Add a note to document of default action of KeyboardEvent for allowing UA not to fire key events for some shortcut keys (#65)
- Re: [uievents] Add a note to document of default action of KeyboardEvent for allowing UA not to fire key events for some shortcut keys (#65)
- Re: [uievents] Add a note to document of default action of KeyboardEvent for allowing UA not to fire key events for some shortcut keys (#65)
[dom] Consider adding more utils to Elements (#145)
- Re: [dom] Consider adding more utils to Elements (#145)
- Re: [dom] Consider adding more utils to Elements (#145)
Re: [ServiceWorker] Remove frameType, maybe add ancestorOrigins (#732)
[fetch] Behavior unspecified with multiple headers with same name (#190)
- Re: [fetch] Behavior unspecified with multiple headers with same name (#190)
- Re: [fetch] Behavior unspecified with multiple headers with same name (#190)
- Re: [fetch] Behavior unspecified with multiple headers with same name (#190)
- Re: [fetch] Behavior unspecified with multiple headers with same name (#190)
- Re: [fetch] Behavior unspecified with multiple headers with same name (#190)
- Re: [fetch] Behavior unspecified with multiple headers with same name (#190)
- Re: [fetch] Behavior unspecified with multiple headers with same name (#190)
[ServiceWorker] Should the active worker move to environment settings object? (#811)
- Re: [ServiceWorker] Should the active worker move to environment settings object? (#811)
- Re: [ServiceWorker] Should the active worker move to environment settings object? (#811)
- Re: [ServiceWorker] Should the active worker move to environment settings object? (#811)
Re: [spec-reviews] Web Background Sync API (#95)
- Re: [spec-reviews] Web Background Sync API (#95)
- Re: [spec-reviews] Web Background Sync API (#95)
- Re: [spec-reviews] Web Background Sync API (#95)
Re: [ServiceWorker] should update() during top level script evaluation be ignored? (#800)
- Re: [ServiceWorker] should update() during top level script evaluation be ignored? (#800)
- Re: [ServiceWorker] should update() during top level script evaluation be ignored? (#800)
- Re: [ServiceWorker] should update() during top level script evaluation be ignored? (#800)
- Re: [ServiceWorker] should update() during top level script evaluation be ignored? (#800)
- Re: [ServiceWorker] should update() during top level script evaluation be ignored? (#800)
- Re: [ServiceWorker] should update() during top level script evaluation be ignored? (#800)
- Re: [ServiceWorker] should update() during top level script evaluation be ignored? (#800)
- Re: [ServiceWorker] should update() during top level script evaluation be ignored? (#800)
- Re: [ServiceWorker] should update() during top level script evaluation be ignored? (#800)
- Re: [ServiceWorker] should update() during top level script evaluation be ignored? (#800)
- Re: [ServiceWorker] should update() during top level script evaluation be ignored? (#800)
Re: [ServiceWorker] navigations that are not intercepted should still allow interception on further redirects (#793)
Re: [ServiceWorker] Implement API to reject PUSH_PROMISEs sent by the server over HTTP/2 (#796)
Re: [ServiceWorker] Can we add some options to ClientQueryOptions? (#801)
Re: [spec-reviews] HTTP 451 Status (#99)
Re: [spec-reviews] Feedback on DOMError -> DOMException in Indexed DB (#88)
- Re: [spec-reviews] Feedback on DOMError -> DOMException in Indexed DB (#88)
- Re: [spec-reviews] Feedback on DOMError -> DOMException in Indexed DB (#88)
Re: [fetch] `user-agent` header control (#37)
[encoding] Fix #22: align with GB18030-2005 (#26)
- Re: [encoding] Fix #22: align with GB18030-2005 (#26)
- Re: [encoding] Fix #22: align with GB18030-2005 (#26)
[encoding] Fix #17: gb18030 cannot encode U+E5E5 (#25)
- Re: [encoding] Fix #17: gb18030 cannot encode U+E5E5 (#25)
- Re: [encoding] Fix #17: gb18030 cannot encode U+E5E5 (#25)
[dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
- Re: [dom] Added an example showing feature detection with supports() (#144)
Re: [webidl] Promise type on an attribute should be allowed (#71)
[ServiceWorker] MessagePort[] no longer valid in WebIDL (#810)
[ServiceWorker] It notes that this is very tightened to the use of promises (#809)
Re: [encoding] GB 18030 2000 vs 2005 (#22)
- Re: [encoding] GB 18030 2000 vs 2005 (#22)
- Re: [encoding] GB 18030 2000 vs 2005 (#22)
- Re: [encoding] GB 18030 2000 vs 2005 (#22)
- Re: [encoding] GB 18030 2000 vs 2005 (#22)
Re: [ServiceWorker] Can create caches in the persistent storage? (#803)
Re: [ServiceWorker] unregister() in service worker navigation fetch event (#804)
- Re: [ServiceWorker] unregister() in service worker navigation fetch event (#804)
- Re: [ServiceWorker] unregister() in service worker navigation fetch event (#804)
- Re: [ServiceWorker] unregister() in service worker navigation fetch event (#804)
- Re: [ServiceWorker] unregister() in service worker navigation fetch event (#804)
- Re: [ServiceWorker] unregister() in service worker navigation fetch event (#804)
- Re: [ServiceWorker] unregister() in service worker navigation fetch event (#804)
- Re: [ServiceWorker] unregister() in service worker navigation fetch event (#804)
- Re: [ServiceWorker] unregister() in service worker navigation fetch event (#804)
Re: [webcomponents] Define the behavior of '::slotted' (the former name is '::content'). (#331)
- Re: [webcomponents] Define the behavior of '::slotted' (the former name is '::content'). (#331)
- Re: [webcomponents] Define the behavior of '::slotted' (the former name is '::content'). (#331)
- Re: [webcomponents] Define the behavior of '::slotted' (the former name is '::content'). (#331)
- Re: [webcomponents] Define the behavior of '::slotted' (the former name is '::content'). (#331)
Re: [xhr] Abandon hope of removing sync XHR from the web platform? (#20)
- Re: [xhr] Abandon hope of removing sync XHR from the web platform? (#20)
- Re: [xhr] Abandon hope of removing sync XHR from the web platform? (#20)
- Re: [xhr] Abandon hope of removing sync XHR from the web platform? (#20)
- Re: [xhr] Abandon hope of removing sync XHR from the web platform? (#20)
[xhr] XHR using sync warning (#40)
[fullscreen] onway lRmt (#32)
[dom] Having getElementsByTagName match on localName is not "web"-compatible for IE and Firefox (#143)
- Re: [dom] Having getElementsByTagName match on localName is not "web"-compatible for IE and Firefox (#143)
- Re: [dom] Having getElementsByTagName match on localName is not "web"-compatible for IE and Firefox (#143)
- Re: [dom] Having getElementsByTagName match on localName is not "web"-compatible for IE and Firefox (#143)
- Re: [dom] Having getElementsByTagName match on localName is not "web"-compatible for IE and Firefox (#143)
- Re: [dom] Having getElementsByTagName match on localName is not "web"-compatible for IE and Firefox (#143)
- Re: [dom] Having getElementsByTagName match on localName is not "web"-compatible for IE and Firefox (#143)
- Re: [dom] Having getElementsByTagName match on localName is not "web"-compatible for IE and Firefox (#143)
- Re: [dom] Having getElementsByTagName match on localName is not "web"-compatible for IE and Firefox (#143)
- Re: [dom] Having getElementsByTagName match on localName is not "web"-compatible for IE and Firefox (#143)
- Re: [dom] Having getElementsByTagName match on localName is not "web"-compatible for IE and Firefox (#143)
- Re: [dom] Having getElementsByTagName match on localName is not "web"-compatible for IE and Firefox (#143)
- Re: [dom] Having getElementsByTagName match on localName is not "web"-compatible for IE and Firefox (#143)
- Re: [dom] Having getElementsByTagName match on localName is not "web"-compatible for IE and Firefox (#143)
- Re: [dom] Having getElementsByTagName match on localName is not "web"-compatible for IE and Firefox (#143)
[webidl] Check if NodeFilter.length is defined correctly. (#83)
- Re: [webidl] Check if NodeFilter.length is defined correctly. (#83)
- Re: [webidl] Check if NodeFilter.length is defined correctly. (#83)
- Re: [webidl] Check if NodeFilter.length is defined correctly. (#83)
- Re: [webidl] Check if NodeFilter.length is defined correctly. (#83)
- Re: [webidl] Check if NodeFilter.length is defined correctly. (#83)
- Re: [webidl] Check if NodeFilter.length is defined correctly. (#83)
- Re: [webidl] Check if NodeFilter.length is defined correctly. (#83)
- Re: [webidl] Check if NodeFilter.length is defined correctly. (#83)
Re: [encoding] "gb18030 ranges" have problematic definitions (#17)
- Re: [encoding] "gb18030 ranges" have problematic definitions (#17)
- Re: [encoding] "gb18030 ranges" have problematic definitions (#17)
- Re: [encoding] "gb18030 ranges" have problematic definitions (#17)
- Re: [encoding] "gb18030 ranges" have problematic definitions (#17)
- Re: [encoding] "gb18030 ranges" have problematic definitions (#17)
- Re: [encoding] "gb18030 ranges" have problematic definitions (#17)
Re: [encoding] Use floor() more (#23)
[FileAPI] Use the W3C logo over https. (#28)
[dom] Why remove CDataSection? (#142)
- Re: [dom] Why remove CDataSection? (#142)
- Re: [dom] Why remove CDataSection? (#142)
- Re: [dom] Why remove CDataSection? (#142)
- Re: [dom] Why remove CDataSection? (#142)
- Re: [dom] Why remove CDataSection? (#142)
- Re: [dom] Why remove CDataSection? (#142)
- Re: [dom] Why remove CDataSection? (#142)
- Re: [dom] Why remove CDataSection? (#142)
- Re: [dom] Why remove CDataSection? (#142)
- Re: [dom] Why remove CDataSection? (#142)
- Re: [dom] Why remove CDataSection? (#142)
- Re: [dom] Why remove CDataSection? (#142)
- Re: [dom] Why remove CDataSection? (#142)
- Re: [dom] Why remove CDataSection? (#142)
Re: [ServiceWorker] Race when registering multiple service workers for the same scope (#783)
- Re: [ServiceWorker] Race when registering multiple service workers for the same scope (#783)
- Re: [ServiceWorker] Race when registering multiple service workers for the same scope (#783)
- Re: [ServiceWorker] Race when registering multiple service workers for the same scope (#783)
- Re: [ServiceWorker] Race when registering multiple service workers for the same scope (#783)
- Re: [ServiceWorker] Race when registering multiple service workers for the same scope (#783)
- Re: [ServiceWorker] Race when registering multiple service workers for the same scope (#783)
Re: [webcomponents] Clarify which registry is used for the result of create*Document() (#353)
[url] "A URL’s port is either null or a 16-bit integer" (#76)
- Re: [url] "A URL’s port is either null or a 16-bit integer" (#76)
- Re: [url] "A URL’s port is either null or a 16-bit integer" (#76)
[fetch] Can headers ordering be lessened? (#189)
- Re: [fetch] Can headers ordering be lessened? (#189)
- Re: [fetch] Can headers ordering be lessened? (#189)
- Re: [fetch] Can headers ordering be lessened? (#189)
- Re: [fetch] Can headers ordering be lessened? (#189)
- Re: [fetch] Can headers ordering be lessened? (#189)
- Re: [fetch] Can headers ordering be lessened? (#189)
- Re: [fetch] Can headers ordering be lessened? (#189)
- Re: [fetch] Can headers ordering be lessened? (#189)
- Re: [fetch] Can headers ordering be lessened? (#189)
- Re: [fetch] Can headers ordering be lessened? (#189)
- Re: [fetch] Can headers ordering be lessened? (#189)
- Re: [fetch] Can headers ordering be lessened? (#189)
- Re: [fetch] Can headers ordering be lessened? (#189)
- Re: [fetch] Can headers ordering be lessened? (#189)
- Re: [fetch] Can headers ordering be lessened? (#189)
- Re: [fetch] Can headers ordering be lessened? (#189)
- Re: [fetch] Can headers ordering be lessened? (#189)
- Re: [fetch] Can headers ordering be lessened? (#189)
- Re: [fetch] Can headers ordering be lessened? (#189)
- Re: [fetch] Can headers ordering be lessened? (#189)
- Re: [fetch] Can headers ordering be lessened? (#189)
- Re: [fetch] Can headers ordering be lessened? (#189)
- Re: [fetch] Can headers ordering be lessened? (#189)
Re: [webcomponents] [Shadow] activeElement behavior seems to break encapsulation (#358)
Re: [fetch] Why are headers a special data-structure? (#154)
- Re: [fetch] Why are headers a special data-structure? (#154)
- Re: [fetch] Why are headers a special data-structure? (#154)
- Re: [fetch] Why are headers a special data-structure? (#154)
- Re: [fetch] Why are headers a special data-structure? (#154)
[fetch] Update the "determine request's referrer" algorithm link (#188)
- Re: [fetch] Update the "determine request's referrer" algorithm link (#188)
- Re: [fetch] Update the "determine request's referrer" algorithm link (#188)
[ServiceWorker] What is FetchEvent.clientId for navigation requests (#808)
- Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808)
- Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808)
- Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808)
- Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808)
- Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808)
- Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808)
- Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808)
- Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808)
- Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808)
- Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808)
- Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808)
- Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808)
- Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808)
- Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808)
- Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808)
- Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808)
- Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808)
- Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808)
- Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808)
- Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808)
- Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808)
- Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808)
- Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808)
- Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808)
- Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808)
- Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808)
[streams] Style guide (#421)
Re: [streams] Fill the internal slots section of ReadableByteStreamController (#417)
Re: [touch-events] createTouch has all the params as required, should probably have them optional (#58)
- Re: [touch-events] createTouch has all the params as required, should probably have them optional (#58)
- Re: [touch-events] createTouch has all the params as required, should probably have them optional (#58)
- Re: [touch-events] createTouch has all the params as required, should probably have them optional (#58)
- Re: [touch-events] createTouch has all the params as required, should probably have them optional (#58)
- Re: [touch-events] createTouch has all the params as required, should probably have them optional (#58)
[ServiceWorker] The "uninstalling flag" check in ServiceWorkerRegistration.update() should be moved to the Update algorithm (#807)
- Re: [ServiceWorker] The "uninstalling flag" check in ServiceWorkerRegistration.update() should be moved to the Update algorithm (#807)
- Re: [ServiceWorker] The "uninstalling flag" check in ServiceWorkerRegistration.update() should be moved to the Update algorithm (#807)
- Re: [ServiceWorker] The "uninstalling flag" check in ServiceWorkerRegistration.update() should be moved to the Update algorithm (#807)
- Re: [ServiceWorker] The "uninstalling flag" check in ServiceWorkerRegistration.update() should be moved to the Update algorithm (#807)
- Re: [ServiceWorker] The "uninstalling flag" check in ServiceWorkerRegistration.update() should be moved to the Update algorithm (#807)
[webcomponents] HTML Modules proposal. (#360)
Re: [dom] Close #123: remove feature detection from add() and add supports() (ff4f0e8)
Re: [dom] Fix some references around Document interface. (#108)
- Re: [dom] Fix some references around Document interface. (#108)
- Re: [dom] Fix some references around Document interface. (#108)
Re: [dom] More bikeshed problems (#62)
Re: [push-api] "the URL-safe base64 encoding" is not defined (#177)
Re: [push-api] Adding base64 reference (#178)
[ServiceWorker] Create F2F agenda (#806)
- Re: [ServiceWorker] Create F2F agenda (#806)
- Re: [ServiceWorker] Create F2F agenda (#806)
- Re: [ServiceWorker] Create F2F agenda (#806)
- Re: [ServiceWorker] Create F2F agenda (#806)
- Re: [ServiceWorker] Create F2F agenda (#806)
- Re: [ServiceWorker] Create F2F agenda (#806)
- Re: [ServiceWorker] Create F2F agenda (#806)
- Re: [ServiceWorker] Create F2F agenda (#806)
- Re: [ServiceWorker] Create F2F agenda (#806)
- Re: [ServiceWorker] Create F2F agenda (#806)
[fetch] Request body should be removed when method changed to GET (#187)
- Re: [fetch] Request body should be removed when method changed to GET (#187)
- Re: [fetch] Request body should be removed when method changed to GET (#187)
- Re: [fetch] Request body should be removed when method changed to GET (#187)
- Re: [fetch] Request body should be removed when method changed to GET (#187)
- Re: [fetch] Request body should be removed when method changed to GET (#187)
[dom] Supported property names for NamedNodeMap (#141)
- Re: [dom] Supported property names for NamedNodeMap (#141)
- Re: [dom] Supported property names for NamedNodeMap (#141)
- Re: [dom] Supported property names for NamedNodeMap (#141)
- Re: [dom] Supported property names for NamedNodeMap (#141)
- Re: [dom] Supported property names for NamedNodeMap (#141)
- Re: [dom] Supported property names for NamedNodeMap (#141)
- Re: [dom] Supported property names for NamedNodeMap (#141)
- Re: [dom] Supported property names for NamedNodeMap (#141)
- Re: [dom] Supported property names for NamedNodeMap (#141)
- Re: [dom] Supported property names for NamedNodeMap (#141)
- Re: [dom] Supported property names for NamedNodeMap (#141)
- Re: [dom] Supported property names for NamedNodeMap (#141)
- Re: [dom] Supported property names for NamedNodeMap (#141)
- Re: [dom] Supported property names for NamedNodeMap (#141)
- Re: [dom] Supported property names for NamedNodeMap (#141)
- Re: [dom] Supported property names for NamedNodeMap (#141)
- Re: [dom] Supported property names for NamedNodeMap (#141)
- Re: [dom] Supported property names for NamedNodeMap (#141)
- Re: [dom] Supported property names for NamedNodeMap (#141)
- Re: [dom] Supported property names for NamedNodeMap (#141)
Re: [manifest] Allow developers to detect when the user has added the site to their home screen (or equivalent) (#417)
- Re: [manifest] Allow developers to detect when the user has added the site to their home screen (or equivalent) (#417)
- Re: [manifest] Allow developers to detect when the user has added the site to their home screen (or equivalent) (#417)
- Re: [manifest] Allow developers to detect when the user has added the site to their home screen (or equivalent) (#417)
[dom] Allow usage of IDL attributes for Element::setAttribute? (#140)
- Re: [dom] Allow usage of IDL attributes for Element::setAttribute? (#140)
- Re: [dom] Allow usage of IDL attributes for Element::setAttribute? (#140)
- Re: [dom] Allow usage of IDL attributes for Element::setAttribute? (#140)
[fetch] Give guidance on when flags should be set, for other spec authors (#186)
Re: [dom] Add EventListenerOptions and passive event listeners (#82)
- Re: [dom] Add EventListenerOptions and passive event listeners (#82)
- Re: [dom] Add EventListenerOptions and passive event listeners (#82)
- Re: [dom] Add EventListenerOptions and passive event listeners (#82)
- Re: [dom] Add EventListenerOptions and passive event listeners (#82)
- Re: [dom] Add EventListenerOptions and passive event listeners (#82)
- Re: [dom] Add EventListenerOptions and passive event listeners (#82)
- Re: [dom] Add EventListenerOptions and passive event listeners (#82)
- Re: [dom] Add EventListenerOptions and passive event listeners (#82)
- Re: [dom] Add EventListenerOptions and passive event listeners (#82)
- Re: [dom] Add EventListenerOptions and passive event listeners (#82)
- Re: [dom] Add EventListenerOptions and passive event listeners (#82)
- Re: [dom] Add EventListenerOptions and passive event listeners (#82)
- Re: [dom] Add EventListenerOptions and passive event listeners (#82)
- Re: [dom] Add EventListenerOptions and passive event listeners (#82)
- Re: [dom] Add EventListenerOptions and passive event listeners (#82)
- Re: [dom] Add EventListenerOptions and passive event listeners (#82)
- Re: [dom] Add EventListenerOptions and passive event listeners (#82)
- Re: [dom] Add EventListenerOptions and passive event listeners (#82)
- Re: [dom] Add EventListenerOptions and passive event listeners (#82)
- Re: [dom] Add EventListenerOptions and passive event listeners (#82)
- Re: [dom] Add EventListenerOptions and passive event listeners (#82)
- Re: [dom] Add EventListenerOptions and passive event listeners (#82)
Re: [dom] Fix #119: Merge DOMSettableTokenList into DOMTokenList (#120)
- Re: [dom] Fix #119: Merge DOMSettableTokenList into DOMTokenList (#120)
- Re: [dom] Fix #119: Merge DOMSettableTokenList into DOMTokenList (#120)
- Re: [dom] Fix #119: Merge DOMSettableTokenList into DOMTokenList (#120)
- Re: [dom] Fix #119: Merge DOMSettableTokenList into DOMTokenList (#120)
- Re: [dom] Fix #119: Merge DOMSettableTokenList into DOMTokenList (#120)
- Re: [dom] Fix #119: Merge DOMSettableTokenList into DOMTokenList (#120)
- Re: [dom] Fix #119: Merge DOMSettableTokenList into DOMTokenList (#120)
- Re: [dom] Fix #119: Merge DOMSettableTokenList into DOMTokenList (#120)
- Re: [dom] Fix #119: Merge DOMSettableTokenList into DOMTokenList (#120)
Re: [dom] Document.documentURI and Document.URL attributes behaviour (#118)
- Re: [dom] Document.documentURI and Document.URL attributes behaviour (#118)
- Re: [dom] Document.documentURI and Document.URL attributes behaviour (#118)
- Re: [dom] Document.documentURI and Document.URL attributes behaviour (#118)
- Re: [dom] Document.documentURI and Document.URL attributes behaviour (#118)
Re: [dom] Node#baseURI need not be nullable (#131)
Re: [dom] Clarify what Document constructor does? (#137)
Re: [dom] Small correct for Mutation observers (#132)
Re: [dom] setAttributeNode should not change order of existing attributes (#116)
- Re: [dom] setAttributeNode should not change order of existing attributes (#116)
- Re: [dom] setAttributeNode should not change order of existing attributes (#116)
- Re: [dom] setAttributeNode should not change order of existing attributes (#116)
Re: [dom] Fix a typo in the replace algorithm (#138)
Re: [dom] Fix the set an attribute algorithm (#139)
- Re: [dom] Fix the set an attribute algorithm (#139)
- Re: [dom] Fix the set an attribute algorithm (#139)
- Re: [dom] Fix the set an attribute algorithm (#139)
- Re: [dom] Fix the set an attribute algorithm (#139)
- Re: [dom] Fix the set an attribute algorithm (#139)
Re: [dom] fix minor typo (#135)
- Re: [dom] fix minor typo (#135)
- Re: [dom] fix minor typo (#135)
- Re: [dom] fix minor typo (#135)
- Re: [dom] fix minor typo (#135)
Re: [fetch] Handling of data URLs (#111)
Re: [webcomponents] [Shadow]: Need an equivalent definition of 'in a Document' for shadow trees (bugzilla: 26365) (#57)
Re: [ServiceWorker] Allow custom cache keys for request caching (#805)
- Re: [ServiceWorker] Allow custom cache keys for request caching (#805)
- Re: [ServiceWorker] Allow custom cache keys for request caching (#805)
Re: [dom] rename before() and after() of ChildNode (#134)
- Re: [dom] rename before() and after() of ChildNode (#134)
- Re: [dom] rename before() and after() of ChildNode (#134)
- Re: [dom] rename before() and after() of ChildNode (#134)
Re: [xhr] Status 0 is missing a message (#35)
Re: [webidl] All supported property names should be enumerable or none of them (#82)
- Re: [webidl] All supported property names should be enumerable or none of them (#82)
- Re: [webidl] All supported property names should be enumerable or none of them (#82)
- Re: [webidl] All supported property names should be enumerable or none of them (#82)
- Re: [webidl] All supported property names should be enumerable or none of them (#82)
- Re: [webidl] All supported property names should be enumerable or none of them (#82)
- Re: [webidl] All supported property names should be enumerable or none of them (#82)
- Re: [webidl] All supported property names should be enumerable or none of them (#82)
- Re: [webidl] All supported property names should be enumerable or none of them (#82)
- Re: [webidl] All supported property names should be enumerable or none of them (#82)
- Re: [webidl] All supported property names should be enumerable or none of them (#82)
- Re: [webidl] All supported property names should be enumerable or none of them (#82)
- Re: [webidl] All supported property names should be enumerable or none of them (#82)