Adam Klein
Alex Russell
aliams
Andrea Marchesini
Andrew Betts
Andrew Sutherland
Andy Earnshaw
Anne van Kesteren
- Re: [whatwg/dom] "In a document" confusion (#238) (Thursday, 30 June)
- Re: [whatwg/fullscreen] root element background propagation issue (#40) (Thursday, 30 June)
- Re: [whatwg/fullscreen] root element background propagation issue (#40) (Thursday, 30 June)
- Re: [whatwg/dom] "In a document" confusion (#238) (Thursday, 30 June)
- Re: [whatwg/fetch] Add steps to intercept requests using foreign fetch. (#329) (Thursday, 30 June)
- Re: [whatwg/fetch] Add steps to intercept requests using foreign fetch. (#329) (Wednesday, 29 June)
- Re: [whatwg/url] Origin of blob URLs doesn't match what implementations do (#127) (Wednesday, 29 June)
- Re: [whatwg/dom] "In a document" confusion (#238) (Tuesday, 28 June)
- Re: [whatwg/fetch] Link to definition of BufferSource (#316) (Tuesday, 28 June)
- Re: [whatwg/fetch] Link to definition of BufferSource (#316) (Tuesday, 28 June)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 28 June)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 28 June)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 28 June)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 28 June)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 28 June)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 28 June)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 28 June)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 28 June)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 28 June)
- Re: [whatwg/dom] "In a document" confusion (#238) (Tuesday, 28 June)
- Re: [whatwg/url] Origin of blob URLs doesn't match what implementations do (#127) (Tuesday, 28 June)
- Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Tuesday, 28 June)
- Re: [whatwg/url] Origin of blob URLs doesn't match what implementations do (#127) (Monday, 27 June)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304) (Monday, 27 June)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304) (Monday, 27 June)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304) (Monday, 27 June)
- Re: [whatwg/xhr] FormData's append method does not match browsers (#73) (Monday, 27 June)
- Re: [slightlyoff/ServiceWorker] Need to review the algorithms for creating a new environment settings object (#919) (Monday, 27 June)
- Re: [slightlyoff/ServiceWorker] Need to review the algorithms for creating a new environment settings object (#919) (Monday, 27 June)
- Re: [whatwg/url] https://url.spec.whatwg.org/#idl-index (#129) (Monday, 27 June)
- Re: [whatwg/xhr] FormData's append method does not match browsers (#73) (Monday, 27 June)
- Re: [whatwg/storage] Exposing cross-origin resource size (#31) (Saturday, 25 June)
- Re: [whatwg/fetch] Sentence fragment when making CORS preflight request (#328) (Saturday, 25 June)
- Re: [whatwg/storage] Miscellaneous editorial feedback (#23) (Saturday, 25 June)
- Re: [whatwg/storage] Miscellaneous editorial feedback (#23) (Saturday, 25 June)
- [whatwg/storage] Create explicit security/privacy section (#35) (Saturday, 25 June)
- Re: [whatwg/dom] "In a document" confusion (#238) (Saturday, 25 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Saturday, 25 June)
- Re: [whatwg/dom] Meta: add advice on using the Bikeshed HTTP API (#274) (Saturday, 25 June)
- Re: [whatwg/storage] Miscellaneous editorial feedback (#23) (Saturday, 25 June)
- Re: [whatwg/dom] Shadow: Define "in the same shadow-including document" (#273) (Friday, 24 June)
- Re: [slightlyoff/ServiceWorker] Need to review the algorithms for creating a new environment settings object (#919) (Friday, 24 June)
- Re: [whatwg/fetch] how can i implement a global Interceptor of error with fetchjs (#327) (Friday, 24 June)
- Re: [whatwg/fetch] how can i implement a global Interceptor of error with fetchjs (#327) (Friday, 24 June)
- Re: [whatwg/storage] The term "site" is confusing (#32) (Friday, 24 June)
- Re: [whatwg/storage] eTLD -> public suffix? (#33) (Friday, 24 June)
- Re: [whatwg/storage] The term "site" is confusing (#32) (Friday, 24 June)
- Re: [whatwg/storage] Classify 'Application Cache' as site storage (#30) (Friday, 24 June)
- Re: [whatwg/storage] Classify 'Application Cache' as site storage (#30) (Friday, 24 June)
- Re: [whatwg/storage] Feedback on the persist() algorithm. (#26) (Friday, 24 June)
- Re: [whatwg/storage] Feedback on the persist() algorithm. (#26) (Friday, 24 June)
- Re: [whatwg/storage] Define the behavior when calling persist() if the resource has been already used (#25) (Friday, 24 June)
- Re: [whatwg/storage] Define the behavior when calling persist() if the resource has been already used (#25) (Friday, 24 June)
- Re: [whatwg/storage] Miscellaneous editorial feedback (#23) (Friday, 24 June)
- Re: [whatwg/storage] Prevent usage in combination with document.domain (#12) (Friday, 24 June)
- Re: [whatwg/storage] Prevent usage in combination with document.domain (#12) (Friday, 24 June)
- Re: [slightlyoff/ServiceWorker] Need to review the algorithms for creating a new environment settings object (#919) (Friday, 24 June)
- Re: [slightlyoff/ServiceWorker] Need to review the algorithms for creating a new environment settings object (#919) (Friday, 24 June)
- Re: [slightlyoff/ServiceWorker] Should WindowClient.navigate(url) navigate with "replacement enabled"? (#918) (Friday, 24 June)
- Re: [w3c/webcomponents] [Shadow]: rename <content> to <slot> (bugzilla: 28561) (#92) (Friday, 24 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 24 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 24 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 24 June)
- Re: [whatwg/fetch] Mark Accept-* request headers as simple / safe (#326) (Friday, 24 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Thursday, 23 June)
- Re: [whatwg/fetch] Mark Accept-* request headers as simple / safe (#326) (Thursday, 23 June)
- Re: [whatwg/fetch] Mark Accept-* request headers as simple / safe (#326) (Thursday, 23 June)
- Re: [whatwg/fetch] Mark Accept-* request headers as simple / safe (#326) (Thursday, 23 June)
- Re: [whatwg/fetch] Mark Accept-* request headers as simple / safe (#326) (Thursday, 23 June)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Wednesday, 22 June)
- Re: [w3c/touch-events] Fix #66. Make all touch events composed events (#67) (Wednesday, 22 June)
- Re: [whatwg/url] Origin of blob URLs doesn't match what implementations do (#127) (Wednesday, 22 June)
- Re: [whatwg/xhr] Kill the progress event when readyState is 4 (#72) (Tuesday, 21 June)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Tuesday, 21 June)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Tuesday, 21 June)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Tuesday, 21 June)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Tuesday, 21 June)
- Re: [whatwg/encoding] Handle EUDC before the index in Shift_JIS (#54) (Tuesday, 21 June)
- Re: [whatwg/encoding] Editorial optimization: Move EUDC before index lookup (#52) (Tuesday, 21 June)
- Re: [whatwg/encoding] Shift-JIS encoding/decoding support (#61) (Tuesday, 21 June)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 21 June)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 21 June)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 21 June)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 21 June)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Tuesday, 21 June)
- [whatwg/dom] Note that about:blank also results in quirks mode (#272) (Tuesday, 21 June)
- Re: [w3c/webcomponents] Should innerHTML propagate custom element constructor exceptions? (#525) (Tuesday, 21 June)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Tuesday, 21 June)
- Re: [w3c/webcomponents] Should innerHTML propagate custom element constructor exceptions? (#525) (Tuesday, 21 June)
- Re: [w3c/webcomponents] Should innerHTML propagate custom element constructor exceptions? (#525) (Tuesday, 21 June)
- Re: [whatwg/dom] selectionchange possible improvements (#271) (Monday, 20 June)
- Re: [whatwg/dom] selectionchange possible improvements (#271) (Monday, 20 June)
- Re: [whatwg/encoding] GBK encoding/decoding support (#56) (Monday, 20 June)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Monday, 20 June)
- Re: [whatwg/fetch] Handling Partial Content / 206 (#144) (Monday, 20 June)
- Re: [slightlyoff/ServiceWorker] When does the openWindow promise resolve? (#728) (Monday, 20 June)
- Re: [w3c/webcomponents] Is custom elements constructor allowed to attachShadow? (#524) (Monday, 20 June)
- [whatwg/storage] UI and origins <> origin groups (#34) (Monday, 20 June)
- Re: [whatwg/storage] The term "site" is confusing (#32) (Monday, 20 June)
- Re: [whatwg/url] Non-Windows-file URL definition (#128) (Monday, 20 June)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Monday, 20 June)
- Re: [whatwg/url] Origin of blob URLs doesn't match what implementations do (#127) (Friday, 17 June)
- Re: [whatwg/fullscreen] root element background propagation issue (#40) (Friday, 17 June)
- Re: [whatwg/url] Origin of blob URLs doesn't match what implementations do (#127) (Friday, 17 June)
- Re: [whatwg/url] Origin of blob URLs doesn't match what implementations do (#127) (Thursday, 16 June)
- Re: [whatwg/dom] Clarify that the namespace check in "create an element" is redundant (#269) (Thursday, 16 June)
- Re: [whatwg/dom] Clarify that the namespace check in "create an element" is redundant (#269) (Thursday, 16 June)
- Re: [whatwg/url] Origin of blob URLs doesn't match what implementations do (#127) (Thursday, 16 June)
- Re: [whatwg/url] Origin of blob URLs doesn't match what implementations do (#127) (Thursday, 16 June)
- Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Thursday, 16 June)
- Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Thursday, 16 June)
- Re: [w3c/webcomponents] Allow or prohibit observedAttributes to observe 'style' attribute? (#521) (Thursday, 16 June)
- Re: [w3c/webcomponents] Allow or prohibit observedAttributes to observe 'style' attribute? (#521) (Wednesday, 15 June)
- Re: [w3c/webcomponents] Allow or prohibit observedAttributes to observe 'style' attribute? (#521) (Wednesday, 15 June)
- Re: [whatwg/fetch] Model HSTS and Upgrade-Insecure-Request as a redirect. (#324) (Tuesday, 14 June)
- Re: [whatwg/url] Allow for a URL record's object to be a MediaSource or MediaStream (#126) (Friday, 10 June)
- Re: [whatwg/url] Allow for a URL record's object to be a MediaSource or MediaStream (#126) (Friday, 10 June)
- Re: [whatwg/url] Allow for a URL record's object to be a MediaSource or MediaStream (#126) (Friday, 10 June)
- [whatwg/dom] Point out that initial about:blank also results in quirks mode (#268) (Friday, 10 June)
- Re: [whatwg/dom] querySelector/All can accidentally return the scoping element (#263) (Friday, 10 June)
- Re: [whatwg/dom] querySelector/All can accidentally return the scoping element (#263) (Friday, 10 June)
- Re: [whatwg/fetch] no-referrer should not set referer header (#323) (Friday, 10 June)
- Re: [w3c/webcomponents] Disabling tabindex across potentially many shadow roots (#520) (Friday, 10 June)
- Re: [whatwg/fetch] RFC: a mechanism to bypass CORS preflight (#210) (Friday, 10 June)
- Re: [whatwg/url] Allow for a URL record's object to be a MediaSource or MediaStream (#126) (Thursday, 9 June)
- Re: [whatwg/fetch] Make sure all responses have a URL list (#322) (Thursday, 9 June)
- Re: [whatwg/fetch] Non-http fetch doesn't set response URL (#312) (Thursday, 9 June)
- Re: [whatwg/url] Allow for a URL record's object to be a MediaSource or MediaStream (#126) (Thursday, 9 June)
- Re: [whatwg/fetch] Preserve fragment in Request/Response URLs (#214) (Thursday, 9 June)
- Re: [whatwg/fetch] Make sure all responses have a URL list (#322) (Thursday, 9 June)
- [whatwg/fetch] Make sure all responses have a URL list (#322) (Thursday, 9 June)
- Re: [whatwg/fetch] Non-http fetch doesn't set response URL (#312) (Thursday, 9 June)
- Re: [whatwg/dom] toggleEventListener (#251) (Thursday, 9 June)
- Re: [whatwg/dom] toggleEventListener (#251) (Thursday, 9 June)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 9 June)
- Re: [whatwg/dom] Rename rootNode to getRootNode() and add composed argument (#248) (Thursday, 9 June)
- Re: [whatwg/dom] Rename rootNode to getRootNode() and add composed argument (#248) (Thursday, 9 June)
- Re: [whatwg/dom] Rename rootNode to getRootNode() and add composed argument (#248) (Thursday, 9 June)
- Re: [whatwg/dom] querySelector/All can accidentally return the scoping element (#263) (Thursday, 9 June)
- Re: [w3c/webcomponents] To notify mutation observers should make a copy of signalList before delivering mutation records (#518) (Thursday, 9 June)
- Re: [w3c/webcomponents] To notify mutation observers should make a copy of signalList before delivering mutation records (#518) (Thursday, 9 June)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 9 June)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 9 June)
- Re: [slightlyoff/ServiceWorker] Access to fragment identifiers (#854) (Wednesday, 8 June)
- [slightlyoff/ServiceWorker] Expose fragments cross-origin for subresources (#910) (Wednesday, 8 June)
- Re: [whatwg/dom] Markup "synthetic events" term as a proper <dfn> (#254) (Wednesday, 8 June)
- Re: [whatwg/dom] querySelector/All can accidentally return the scoping element (#263) (Wednesday, 8 June)
- Re: [w3c/webcomponents] Add <a> to safelist of elements that can call attachShadowRoot (#511) (Wednesday, 8 June)
- Re: [whatwg/dom] UAs create elements in HTML namespace when context object is an HTML … (#267) (Wednesday, 8 June)
- Re: [whatwg/dom] UAs create elements in HTML namespace when context object is an HTML … (#267) (Wednesday, 8 June)
- Re: [whatwg/dom] .createElement's namespace handling doesn't seem to match what UAs do (#264) (Wednesday, 8 June)
- Re: [slightlyoff/ServiceWorker] Access to fragment identifiers (#854) (Wednesday, 8 June)
- Re: [w3c/webcomponents] To notify mutation observers should make a copy of signalList before delivering mutation records (#518) (Wednesday, 8 June)
- Re: [whatwg/fetch] json() function does not support anti-json hijacking techniques (#321) (Wednesday, 8 June)
- Re: [whatwg/fetch] json() function does not support anti-json hijacking techniques (#321) (Wednesday, 8 June)
- Re: [slightlyoff/ServiceWorker] CORS pre-flight for foreign fetch (#880) (Tuesday, 7 June)
- Re: [heycam/webidl] Should probably spec a hasInstance for DOM interface objects (#129) (Tuesday, 7 June)
- Re: [heycam/webidl] Should probably spec a hasInstance for DOM interface objects (#129) (Tuesday, 7 June)
- Re: [slightlyoff/ServiceWorker] CORS pre-flight for foreign fetch (#880) (Tuesday, 7 June)
- Re: [slightlyoff/ServiceWorker] Access to fragment identifiers (#854) (Tuesday, 7 June)
- Re: [slightlyoff/ServiceWorker] CORS pre-flight for foreign fetch (#880) (Tuesday, 7 June)
- Re: [whatwg/dom] What happens if a 'once' eventListener dispatches a similar event? (#265) (Tuesday, 7 June)
- Re: [whatwg/dom] Fix example of "undefined" custom element state (#266) (Tuesday, 7 June)
- Re: [whatwg/fetch] HTTP-redirect-fetch preserves all pre-redirect headers for post-redirect request (#320) (Tuesday, 7 June)
- Re: [whatwg/fetch] HTTP-redirect-fetch preserves all pre-redirect headers for post-redirect request (#320) (Tuesday, 7 June)
- Re: [whatwg/dom] What happens if a 'once' eventListener dispatches a similar event? (#265) (Tuesday, 7 June)
- Re: [whatwg/dom] What happens if a 'once' eventListener dispatches a similar event? (#265) (Tuesday, 7 June)
- Re: [slightlyoff/ServiceWorker] Access to fragment identifiers (#854) (Tuesday, 7 June)
- Re: [whatwg/xhr] Sort headers lexicographically in getAllResponseHeaders and combine values too (#50) (Tuesday, 7 June)
- Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Tuesday, 7 June)
- Re: [whatwg/xhr] Should XHR store and send HTTP header names in lower case? (#34) (Tuesday, 7 June)
- Re: [w3c/webcomponents] Shadow DOM and the Fullscreen API (#180) (Tuesday, 7 June)
- Re: [whatwg/fetch] Consider adding HTML's 401 verbiage (#311) (Tuesday, 7 June)
- Re: [whatwg/fetch] same origin requests should allow credentials if credentials mode is sameorigin (#319) (Tuesday, 7 June)
- Re: [whatwg/fetch] same origin requests should allow credentials if credentials mode is sameorigin (#319) (Tuesday, 7 June)
- Re: [whatwg/fetch] same origin requests should allow credentials if credentials mode is sameorigin (#319) (Tuesday, 7 June)
- Re: [whatwg/xhr] "subresource" destination doesn't exist (#71) (Tuesday, 7 June)
- Re: [whatwg/xhr] "subresource" destination doesn't exist (#71) (Tuesday, 7 June)
- Re: [whatwg/fetch] autolink fix: Typo of concept-client-hints-list (#314) (Tuesday, 7 June)
- Re: [whatwg/fetch] autolink fix: Typo of concept-client-hints-list (#314) (Tuesday, 7 June)
- Re: [whatwg/fetch] Remove an unused variable (#318) (Tuesday, 7 June)
- Re: [whatwg/fetch] Meaningless stream variable assignment (#317) (Tuesday, 7 June)
- Re: [whatwg/fetch] Remove an unused variable (#318) (Tuesday, 7 June)
- Re: [whatwg/dom] What happens if a 'once' eventListener dispatches a similar event? (#265) (Tuesday, 7 June)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Tuesday, 7 June)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Tuesday, 7 June)
- Re: [whatwg/dom] Rename rootNode to getRootNode() and add composed argument (#248) (Tuesday, 7 June)
- Re: [whatwg/dom] Rename rootNode to getRootNode() and add composed argument (#248) (Tuesday, 7 June)
- Re: [w3c/webcomponents] Shadow DOM and the Fullscreen API (#180) (Tuesday, 7 June)
- Re: [whatwg/fetch] Link to definition of BufferSource (#316) (Tuesday, 7 June)
- Re: [w3c/webcomponents] I find <slot slot="..."> confusing (#514) (Tuesday, 7 June)
- Re: [slightlyoff/ServiceWorker] CORS pre-flight for foreign fetch (#880) (Tuesday, 7 June)
- Re: [whatwg/dom] Repeatedly inserting a custom element may upgrade it twice (#261) (Tuesday, 7 June)
- Re: [slightlyoff/ServiceWorker] CORS pre-flight for foreign fetch (#880) (Tuesday, 7 June)
- Re: [slightlyoff/ServiceWorker] Authenticated PWA ? (#909) (Tuesday, 7 June)
- Re: [w3c/webcomponents] I find <slot slot="..."> confusing (#514) (Tuesday, 7 June)
- Re: [whatwg/fetch] Listing headers safe only for certain values is a bad idea (#313) (Monday, 6 June)
- Re: [whatwg/fetch] Is is possible to read the response before the whole request body is sent? (#315) (Monday, 6 June)
- Re: [whatwg/fetch] Is is possible to read the response before the whole request body is sent? (#315) (Monday, 6 June)
- [whatwg/fetch] Meaningless stream variable assignment (#317) (Monday, 6 June)
- Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Monday, 6 June)
- Re: [whatwg/fullscreen] Reserved keyboard shortcut behaviour in fullscreen (#39) (Monday, 6 June)
- Re: [w3c/webcomponents] Add <a> to safelist of elements that can call attachShadowRoot (#511) (Monday, 6 June)
- Re: [w3c/webcomponents] Add <a> to safelist of elements that can call attachShadowRoot (#511) (Monday, 6 June)
- Re: [w3c/webcomponents] Add <a> to safelist of elements that can call attachShadowRoot (#511) (Monday, 6 June)
- Re: [whatwg/fetch] Non-http fetch doesn't set response URL (#312) (Friday, 3 June)
- Re: [whatwg/fetch] Non-http fetch doesn't set response URL (#312) (Friday, 3 June)
- Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Friday, 3 June)
- Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Friday, 3 June)
- Re: [whatwg/dom] Save the is="" value an element was created with (#262) (Friday, 3 June)
- [whatwg/encoding] Editorial: avoid upsetting lazy compilers (#55) (Wednesday, 1 June)
- Re: [whatwg/encoding] Group constants together in half-width math (#49) (Wednesday, 1 June)
- Re: [whatwg/encoding] Group constants together in half-width math (#49) (Wednesday, 1 June)
- Re: [whatwg/encoding] Editorial: Exclude index entries instead of just pointers (#51) (Wednesday, 1 June)
- Re: [whatwg/encoding] Edititorial: Add a note about duplicates to "index Shift_JIS pointer" (#50) (Wednesday, 1 June)
- Re: [whatwg/encoding] Handle EUDC before the index in Shift_JIS (#54) (Wednesday, 1 June)
- [whatwg/encoding] Handle EUDC before the index in Shift_JIS (#54) (Wednesday, 1 June)
- Re: [whatwg/encoding] Please double-check the end of the EUDC range (#53) (Wednesday, 1 June)
- Re: [whatwg/dom] Use HTML's 'document base URL' concept. (#258) (Wednesday, 1 June)
- Re: [whatwg/dom] Use HTML's 'document base URL' concept. (#258) (Wednesday, 1 June)
- Re: [whatwg/dom] Un-customify adopted elements (#260) (Wednesday, 1 June)
- Re: [whatwg/dom] Don't set custom element state redundantly (#253) (Wednesday, 1 June)
- Re: [whatwg/dom] Don't set custom element state redundantly (#253) (Wednesday, 1 June)
- Re: [w3c/webcomponents] Shadow DOM and the Fullscreen API (#180) (Wednesday, 1 June)
- Re: [w3c/webcomponents] Shadow DOM and the Fullscreen API (#180) (Wednesday, 1 June)
- Re: [whatwg/fetch] Grammar change: "that is check" to that checks" (#310) (Wednesday, 1 June)
- Re: [whatwg/fetch] Grammar change: "that is check" to that checks" (#310) (Wednesday, 1 June)
Anssi Kostiainen
Anthony Ramine
ArkadiuszMichalski
Arthur Stolyar
- Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Thursday, 30 June)
- Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Thursday, 30 June)
- Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Thursday, 30 June)
- Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Thursday, 30 June)
- Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Wednesday, 29 June)
- Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Tuesday, 28 June)
- Re: [slightlyoff/ServiceWorker] Why doesn't cache.match support `cacheName` (#917) (Saturday, 25 June)
- Re: [slightlyoff/ServiceWorker] Should WindowClient.navigate(url) navigate with "replacement enabled"? (#918) (Friday, 24 June)
- Re: [slightlyoff/ServiceWorker] Why doesn't cache.match support `cacheName` (#917) (Wednesday, 22 June)
- Re: [slightlyoff/ServiceWorker] More clarity around waiting for an active worker to finish (#916) (Friday, 17 June)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 9 June)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Wednesday, 8 June)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Monday, 6 June)
beidson
Ben
Ben Kelly
- Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Thursday, 30 June)
- Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Thursday, 30 June)
- Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Thursday, 30 June)
- Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Thursday, 30 June)
- Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Thursday, 30 June)
- Re: [slightlyoff/ServiceWorker] More clarity around waiting for an active worker to finish (#916) (Thursday, 30 June)
- Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Thursday, 30 June)
- Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Thursday, 30 June)
- Re: [slightlyoff/ServiceWorker] More clarity around waiting for an active worker to finish (#916) (Thursday, 30 June)
- Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Wednesday, 29 June)
- Re: [w3c/manifest] Add beforeinstallprompt event (#417) (Wednesday, 29 June)
- Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Tuesday, 28 June)
- Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Tuesday, 28 June)
- Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Tuesday, 28 June)
- Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Tuesday, 28 June)
- [whatwg/streams] ReadableByteStreamControllerClose accesses first element of pendingPullIntos without checking array length (#470) (Monday, 27 June)
- Re: [slightlyoff/ServiceWorker] More clarity around waiting for an active worker to finish (#916) (Monday, 27 June)
- Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304) (Monday, 27 June)
- Re: [slightlyoff/ServiceWorker] Why doesn't cache.match support `cacheName` (#917) (Saturday, 25 June)
- Re: [slightlyoff/ServiceWorker] More clarity around waiting for an active worker to finish (#916) (Friday, 24 June)
- Re: [slightlyoff/ServiceWorker] Should WindowClient.navigate(url) navigate with "replacement enabled"? (#918) (Friday, 24 June)
- Re: [whatwg/streams] Communication between workers/windows via Streams API (#244) (Thursday, 23 June)
- Re: [whatwg/streams] Communication between workers/windows via Streams API (#244) (Thursday, 23 June)
- Re: [slightlyoff/ServiceWorker] Why doesn't cache.match support `cacheName` (#917) (Thursday, 23 June)
- Re: [slightlyoff/ServiceWorker] More clarity around waiting for an active worker to finish (#916) (Saturday, 18 June)
- Re: [slightlyoff/ServiceWorker] More clarity around waiting for an active worker to finish (#916) (Friday, 17 June)
- Re: [slightlyoff/ServiceWorker] More clarity around waiting for an active worker to finish (#916) (Friday, 17 June)
- Re: [slightlyoff/ServiceWorker] More clarity around waiting for an active worker to finish (#916) (Friday, 17 June)
- Re: [slightlyoff/ServiceWorker] More clarity around waiting for an active worker to finish (#916) (Friday, 17 June)
- [whatwg/fullscreen] root element background propagation issue (#40) (Thursday, 16 June)
- Re: [slightlyoff/ServiceWorker] service worker not working for localhost (#915) (Thursday, 16 June)
- Re: [slightlyoff/ServiceWorker] cache.match should create partial responses if given a range request (#913) (Wednesday, 15 June)
- Re: [slightlyoff/ServiceWorker] ServiceWorkerContainer spec lists `onerror` as an event handler (#912) (Tuesday, 14 June)
- [whatwg/streams] 3.11.4.3. respondWithNewView(view) references `chunk` (#467) (Thursday, 9 June)
- Re: [whatwg/fetch] Preserve fragment in Request/Response URLs (#214) (Thursday, 9 June)
- Re: [whatwg/fetch] Make sure all responses have a URL list (#322) (Thursday, 9 June)
- Re: [whatwg/fetch] json() function does not support anti-json hijacking techniques (#321) (Tuesday, 7 June)
- Re: [slightlyoff/ServiceWorker] CORS pre-flight for foreign fetch (#880) (Tuesday, 7 June)
- Re: [slightlyoff/ServiceWorker] CORS pre-flight for foreign fetch (#880) (Tuesday, 7 June)
- Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Tuesday, 7 June)
- Re: [slightlyoff/ServiceWorker] CORS pre-flight for foreign fetch (#880) (Tuesday, 7 June)
- Re: [slightlyoff/ServiceWorker] CORS pre-flight for foreign fetch (#880) (Tuesday, 7 June)
- Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Tuesday, 7 June)
- Re: [whatwg/streams] Convert internal slot accesses in the reference implementation to use symbols (#443) (Monday, 6 June)
- Re: [whatwg/streams] Convert internal slot accesses in the reference implementation to use symbols (#443) (Monday, 6 June)
- Re: [slightlyoff/ServiceWorker] Receivers of ranged responses must ensure all ranges come from the same underlying resource (#703) (Saturday, 4 June)
- Re: [slightlyoff/ServiceWorker] potential http cache issues with importScripts() (#894) (Friday, 3 June)
- Re: [slightlyoff/ServiceWorker] Receivers of ranged responses must ensure all ranges come from the same underlying resource (#703) (Friday, 3 June)
- [whatwg/streams] tighten ReadableStreamReaderGenericRelease assertion (#466) (Wednesday, 1 June)
Benjamin Gruenbaum
Bevis Tseng
bmaurer
Boris Zbarsky
- Re: [heycam/webidl] Add forEach to disallowed member names for iterable (#132) (Friday, 24 June)
- Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Thursday, 16 June)
- Re: [heycam/webidl] Should probably spec a hasInstance for DOM interface objects (#129) (Thursday, 16 June)
- Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Thursday, 16 June)
- Re: [heycam/webidl] A non-optional dictionary argument makes sense at times. (#130) (Thursday, 16 June)
- Re: [heycam/webidl] A non-optional dictionary argument makes sense at times. (#130) (Wednesday, 15 June)
- Re: [heycam/webidl] Fix incumbent settings object handling (#128) (Wednesday, 15 June)
- Re: [heycam/webidl] A non-optional dictionary argument makes sense at times. (#130) (Tuesday, 14 June)
- Re: [heycam/webidl] Fix incumbent settings object handling (#128) (Thursday, 9 June)
- Re: [heycam/webidl] Should probably spec a hasInstance for DOM interface objects (#129) (Tuesday, 7 June)
- Re: [heycam/webidl] Should probably spec a hasInstance for DOM interface objects (#129) (Tuesday, 7 June)
- Re: [heycam/webidl] Should probably spec a hasInstance for DOM interface objects (#129) (Tuesday, 7 June)
- Re: [heycam/webidl] Should probably spec a hasInstance for DOM interface objects (#129) (Tuesday, 7 June)
- [heycam/webidl] Should probably spec a hasInstance for DOM interface objects (#129) (Tuesday, 7 June)
- Re: [whatwg/streams] Convert internal slot accesses in the reference implementation to use symbols (#443) (Monday, 6 June)
- Re: [whatwg/streams] Convert internal slot accesses in the reference implementation to use symbols (#443) (Monday, 6 June)
- Re: [whatwg/streams] Convert internal slot accesses in the reference implementation to use symbols (#443) (Monday, 6 June)
- Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Friday, 3 June)
Brandon Jones
Brent
Brian Kardell
Brian Raymor
C. Scott Ananian
Cameron McCormack
chaals
- Re: [w3c/WebPlatformWG] Update 16-07-28-29SW.md (#41) (Thursday, 23 June)
- Re: [w3c/pointerlock] pointerlockchange and the accessibility tree (#1) (Friday, 17 June)
- Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) (Saturday, 11 June)
- Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) (Saturday, 11 June)
- Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) (Saturday, 11 June)
- Re: [w3c/WebPlatformWG] Update attendee list for the July SW meeting. (#39) (Wednesday, 8 June)
- Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496) (Friday, 3 June)
- Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496) (Wednesday, 1 June)
- Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496) (Wednesday, 1 June)
- Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496) (Wednesday, 1 June)
Chieh-Ting Yeh
Chong Zhang
Chris Dickinson
Chris Dumez
Chris Dumoulin
Chris Palmer
Chris Rebert
chris van wiemeersch
Chris Wilson
cynthia
Cyril Auburtin
Daniel Appelquist
Daniel Herr
Daniel Murphy
Dave Herman
Dave Tapuska
David Ford
ddorwin
Denis Ah-Kang
Domenic Denicola
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Thursday, 30 June)
- Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Thursday, 30 June)
- Re: [w3c/webcomponents] Should innerHTML propagate custom element constructor exceptions? (#525) (Thursday, 30 June)
- Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Thursday, 30 June)
- Re: [slightlyoff/ServiceWorker] Eliminate usage of entry and incumbent settings objects (#922) (Thursday, 30 June)
- Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Thursday, 30 June)
- [slightlyoff/ServiceWorker] Eliminate usage of entry and incumbent settings objects (#922) (Wednesday, 29 June)
- Re: [w3c/webcomponents] Integrate callback invocation with IDL (#186) (Wednesday, 29 June)
- Re: [w3c/webcomponents] Web Components and Form Submit Fields (#529) (Wednesday, 29 June)
- Re: [w3c/webcomponents] Web Components and Form Submit Fields (#529) (Wednesday, 29 June)
- [whatwg/streams] Tweak ReadableByteStreamControllerEnqueue algorithm structure (#473) (Tuesday, 28 June)
- Re: [whatwg/streams] [WritableStream] Shouldn't the state after writer.abort() be closed? (#464) (Tuesday, 28 June)
- Re: [whatwg/streams] Tighten the assertion on the owner stream in ReadableStreamReaderGene… (#472) (Tuesday, 28 June)
- Re: [whatwg/streams] tighten ReadableStreamReaderGenericRelease assertion (#466) (Tuesday, 28 June)
- Re: [whatwg/streams] ReadableByteStreamControllerClose accesses first element of pendingPullIntos without checking array length (#470) (Tuesday, 28 June)
- Re: [whatwg/streams] Fix pendingPullIntos access in ReadableByteStreamControllerClose() (#471) (Tuesday, 28 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Tuesday, 28 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Tuesday, 28 June)
- Re: [whatwg/dom] "In a document" confusion (#238) (Tuesday, 28 June)
- Re: [w3c/manifest] Tidy up the install event specification (#473) (Tuesday, 28 June)
- Re: [slightlyoff/ServiceWorker] Need to review the algorithms for creating a new environment settings object (#919) (Monday, 27 June)
- [whatwg/xhr] FormData's append method does not match browsers (#73) (Sunday, 26 June)
- Re: [w3c/webcomponents] [idea] Allowing custom element registrations on per-shadow-root basis. (#488) (Saturday, 25 June)
- Re: [whatwg/dom] "In a document" confusion (#238) (Friday, 24 June)
- [whatwg/dom] Meta: add advice on using the Bikeshed HTTP API (#274) (Friday, 24 June)
- Re: [whatwg/dom] Shadow: Define "in the same shadow-including document" (#273) (Friday, 24 June)
- Re: [whatwg/dom] Shadow: Define "in the same shadow-including document" (#273) (Friday, 24 June)
- Re: [whatwg/dom] Shadow: Define "in the same shadow-including document" (#273) (Friday, 24 June)
- Re: [slightlyoff/ServiceWorker] Need to review the algorithms for creating a new environment settings object (#919) (Friday, 24 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 24 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 24 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 24 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 24 June)
- Re: [whatwg/streams] Communication between workers/windows via Streams API (#244) (Thursday, 23 June)
- Re: [whatwg/streams] Should ReadableStreams with pull sources call pull until full? (#469) (Thursday, 23 June)
- Re: [whatwg/streams] Should ReadableStreams with pull sources call pull until full? (#469) (Thursday, 23 June)
- Re: [whatwg/streams] [WritableStream] Shouldn't the state after writer.abort() be closed? (#464) (Thursday, 23 June)
- Re: [whatwg/fetch] Mark Accept-* request headers as simple / safe (#326) (Thursday, 23 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Thursday, 23 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Thursday, 23 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Thursday, 23 June)
- Re: [w3c/webcomponents] Why does upgrade-an-element queue attribute, connected reactions before exiting early? (#523) (Thursday, 23 June)
- Re: [whatwg/url] Origin of blob URLs doesn't match what implementations do (#127) (Wednesday, 22 June)
- Re: [whatwg/streams] Internal promises that can be rejected need to be handled (#468) (Tuesday, 21 June)
- Re: [whatwg/streams] Internal promises that can be rejected need to be handled (#468) (Tuesday, 21 June)
- Re: [whatwg/streams] Internal promises that can be rejected need to be handled (#468) (Tuesday, 21 June)
- Re: [whatwg/fetch] Aborting a fetch (#27) (Tuesday, 21 June)
- Re: [whatwg/fetch] Aborting a fetch (#27) (Tuesday, 21 June)
- Re: [whatwg/fetch] Aborting a fetch (#27) (Tuesday, 21 June)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Tuesday, 21 June)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Tuesday, 21 June)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Tuesday, 21 June)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Tuesday, 21 June)
- Re: [w3c/webcomponents] Is custom elements constructor allowed to attachShadow? (#524) (Tuesday, 21 June)
- Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Tuesday, 21 June)
- Re: [w3c/webcomponents] Should innerHTML propagate custom element constructor exceptions? (#525) (Tuesday, 21 June)
- Re: [w3c/webcomponents] Should innerHTML propagate custom element constructor exceptions? (#525) (Monday, 20 June)
- [w3c/webcomponents] Should innerHTML propagate custom element constructor exceptions? (#525) (Monday, 20 June)
- Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Monday, 20 June)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Monday, 20 June)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Monday, 20 June)
- Re: [w3c/webcomponents] Is custom elements constructor allowed to attachShadow? (#524) (Monday, 20 June)
- Re: [w3c/webcomponents] Is custom elements constructor allowed to attachShadow? (#524) (Monday, 20 June)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Monday, 20 June)
- Re: [w3c/webcomponents] Why does upgrade-an-element queue attribute, connected reactions before exiting early? (#523) (Thursday, 16 June)
- Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Thursday, 16 June)
- Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Thursday, 16 June)
- Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Wednesday, 15 June)
- Re: [w3c/webcomponents] When to invoke custom element reactions that were enqueued outside of DOM operations? (#522) (Wednesday, 15 June)
- Re: [heycam/webidl] Fix incumbent settings object handling (#128) (Wednesday, 15 June)
- [whatwg/dom] Clarify that the namespace check in "create an element" is redundant (#269) (Tuesday, 14 June)
- Re: [w3c/webcomponents] Allow or prohibit observedAttributes to observe 'style' attribute? (#521) (Tuesday, 14 June)
- Re: [whatwg/streams] Convert internal slot accesses in the reference implementation to use symbols (#443) (Monday, 13 June)
- Re: [whatwg/streams] [WritableStream] Shouldn't the state after writer.abort() be closed? (#464) (Wednesday, 8 June)
- Re: [heycam/webidl] Proposal: allow subclasses of constructible built-ins to be constructed (#125) (Wednesday, 8 June)
- Re: [heycam/webidl] Proposal: allow subclasses of constructible built-ins to be constructed (#125) (Wednesday, 8 June)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Wednesday, 8 June)
- Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Wednesday, 8 June)
- Re: [whatwg/streams] Synchronous (or asynchronous) state probing on WritableStream (#463) (Tuesday, 7 June)
- [whatwg/dom] Fix example of "undefined" custom element state (#266) (Tuesday, 7 June)
- Re: [heycam/webidl] Should probably spec a hasInstance for DOM interface objects (#129) (Tuesday, 7 June)
- Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Tuesday, 7 June)
- Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) (Tuesday, 7 June)
- Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) (Tuesday, 7 June)
- Re: [whatwg/streams] Convert internal slot accesses in the reference implementation to use symbols (#443) (Monday, 6 June)
- Re: [whatwg/streams] Convert internal slot accesses in the reference implementation to use symbols (#443) (Monday, 6 June)
- Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Saturday, 4 June)
- Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Friday, 3 June)
- Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Friday, 3 June)
- [heycam/webidl] Fix incumbent settings object handling (#128) (Friday, 3 June)
- Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Thursday, 2 June)
- Re: [whatwg/streams] [WritableStream] Shouldn't the state after writer.abort() be closed? (#464) (Thursday, 2 June)
- Re: [whatwg/streams] light weight transformations (#461) (Wednesday, 1 June)
- Re: [whatwg/streams] Synchronous queue draining for WritableStream (#465) (Wednesday, 1 June)
- Re: [whatwg/streams] [WritableStream] Shouldn't the state after writer.abort() be closed? (#464) (Wednesday, 1 June)
- Re: [whatwg/streams] Synchronous (or asynchronous) state probing on WritableStream (#463) (Wednesday, 1 June)
- Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Wednesday, 1 June)
- Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Wednesday, 1 June)
- Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Wednesday, 1 June)
- Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Wednesday, 1 June)
- [whatwg/dom] Save the is="" value an element was created with (#262) (Wednesday, 1 June)
- Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496) (Wednesday, 1 June)
- [whatwg/fetch] Consider adding HTML's 401 verbiage (#311) (Wednesday, 1 June)
- Re: [whatwg/dom] Repeatedly inserting a custom element may upgrade it twice (#261) (Wednesday, 1 June)
- Re: [whatwg/dom] Why can't Node's nodeValue use [TreatNullAs=EmptyString]? (#259) (Wednesday, 1 June)
- Re: [whatwg/dom] Why can't Node's nodeValue use [TreatNullAs=EmptyString]? (#259) (Wednesday, 1 June)
Dominic Cooney
- Re: [w3c/webcomponents] Should innerHTML propagate custom element constructor exceptions? (#525) (Monday, 20 June)
- [w3c/webcomponents] Why does upgrade-an-element queue attribute, connected reactions before exiting early? (#523) (Thursday, 16 June)
- Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Thursday, 16 June)
- Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Thursday, 16 June)
- Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Friday, 10 June)
- Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Friday, 3 June)
- [whatwg/dom] Repeatedly inserting a custom element may upgrade it twice (#261) (Wednesday, 1 June)
Dominic Tarr
Dominick Ng
Dominique Hazael-Massieux
Dru Knox
Duan Yao
Elliott Sprehn
Erik Isaksen
Gary Kacmarcik
Guilherme
Guillaume Gomez
Hallvord R. M. Steen
Harald Alvestrand
Hayato Ito
- Re: [whatwg/dom] "In a document" confusion (#238) (Thursday, 30 June)
- Re: [whatwg/dom] Shadow: Define "in the same shadow-including document" (#273) (Thursday, 30 June)
- Re: [whatwg/dom] Shadow: Define "in the same shadow-including document" (#273) (Thursday, 30 June)
- Re: [whatwg/dom] "In a document" confusion (#238) (Thursday, 30 June)
- Re: [w3c/uievents] Support Event.composed (#89) (Thursday, 30 June)
- Re: [whatwg/dom] "In a document" confusion (#238) (Wednesday, 29 June)
- Re: [w3c/touch-events] Fix #66. Make all touch events composed events (#67) (Tuesday, 28 June)
- Re: [w3c/uievents] Fix #89. Make some of UI Events composed events (#91) (Monday, 27 June)
- Re: [w3c/webcomponents] ShadowRoot.styleSheets should return an empty StyleSheetList if the shadow root is not in a shadow-including document (#526) (Monday, 27 June)
- Re: [w3c/webcomponents] ShadowRoot.styleSheets should return an empty StyleSheetList if the shadow root is not in a shadow-including document (#526) (Monday, 27 June)
- Re: [w3c/webcomponents] ShadowRoot.styleSheets should return an empty StyleSheetList if the shadow root is not in a shadow-including document (#526) (Monday, 27 June)
- Re: [w3c/webcomponents] ShadowRoot.styleSheets should return an empty StyleSheetList if the shadow root is not in a shadow-including document (#526) (Monday, 27 June)
- Re: [whatwg/dom] Shadow: Define "in the same shadow-including document" (#273) (Monday, 27 June)
- Re: [whatwg/dom] "In a document" confusion (#238) (Monday, 27 June)
- Re: [w3c/webcomponents] ShadowRoot.styleSheets should return an empty StyleSheetList if the shadow root is not in a shadow-including document (#526) (Friday, 24 June)
- Re: [w3c/webcomponents] ShadowRoot.styleSheets should return an empty StyleSheetList if the shadow root is not in a shadow-including document (#526) (Friday, 24 June)
- [w3c/webcomponents] ShadowRoot.styleSheets should return an empty StyleSheetList if the shadow root is not in a shadow-including document (#526) (Friday, 24 June)
- Re: [whatwg/dom] Shadow: Define "in the same shadow-including document" (#273) (Friday, 24 June)
- [whatwg/dom] Shadow: Define "in the same shadow-including document" (#273) (Friday, 24 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 24 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 24 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 24 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 24 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 24 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 24 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 24 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 24 June)
- Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496) (Friday, 24 June)
- Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496) (Thursday, 23 June)
- Re: [w3c/uievents] Support Event.composed (#89) (Thursday, 23 June)
- [w3c/uievents] Fix #89. Make some of UI Events composed events (#91) (Thursday, 23 June)
- Re: [w3c/touch-events] Fix #66. Make all touch events composed events (#67) (Thursday, 23 June)
- Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Thursday, 23 June)
- Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Wednesday, 22 June)
- Re: [w3c/touch-events] Fix #66. Make all touch events composed events (#67) (Wednesday, 22 June)
- Re: [w3c/webcomponents] [Shadow]: rename <content> to <slot> (bugzilla: 28561) (#92) (Wednesday, 22 June)
- Re: [w3c/touch-events] Support Event.composed in Touch Events (#66) (Tuesday, 21 June)
- [w3c/touch-events] Fix #66. Make all touch events composed events (#67) (Tuesday, 21 June)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Monday, 20 June)
- Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496) (Monday, 20 June)
- Re: [w3c/webcomponents] Shadow DOM and the Fullscreen API (#180) (Monday, 20 June)
- Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496) (Monday, 20 June)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Monday, 20 June)
- Re: [w3c/webcomponents] HTMLElement.prototype.offsetParent leaks a node inside a shadow tree (#497) (Monday, 20 June)
- Re: [w3c/webcomponents] HTMLElement.prototype.offsetParent leaks a node inside a shadow tree (#497) (Monday, 20 June)
- Re: [w3c/webcomponents] I find <slot slot="..."> confusing (#514) (Monday, 20 June)
- Re: [w3c/webcomponents] I find <slot slot="..."> confusing (#514) (Monday, 20 June)
- Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Monday, 20 June)
- [w3c/touch-events] Support Event.composed in Touch Events (#66) (Monday, 20 June)
- Re: [w3c/webcomponents] Idea: ComposedTreeProxy (#516) (Monday, 13 June)
- Re: [w3c/webcomponents] Disabling tabindex across potentially many shadow roots (#520) (Friday, 10 June)
- Re: [w3c/webcomponents] Disabling tabindex across potentially many shadow roots (#520) (Friday, 10 June)
- Re: [w3c/webcomponents] Disabling tabindex across potentially many shadow roots (#520) (Friday, 10 June)
- Re: [w3c/webcomponents] Disabling tabindex across potentially many shadow roots (#520) (Friday, 10 June)
- Re: [w3c/webcomponents] Disabling tabindex across potentially many shadow roots (#520) (Friday, 10 June)
- Re: [w3c/webcomponents] Idea: ComposedTreeProxy (#516) (Friday, 10 June)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 9 June)
- Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Wednesday, 8 June)
- [w3c/uievents] Support Event.composed (#89) (Wednesday, 8 June)
- Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Wednesday, 8 June)
- Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Wednesday, 8 June)
- Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Wednesday, 8 June)
- Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Wednesday, 8 June)
- Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Wednesday, 8 June)
- Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Wednesday, 8 June)
- Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Wednesday, 8 June)
- Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Wednesday, 8 June)
- Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Tuesday, 7 June)
- Re: [w3c/webcomponents] Shadow DOM and the Fullscreen API (#180) (Tuesday, 7 June)
- Re: [w3c/webcomponents] I find <slot slot="..."> confusing (#514) (Tuesday, 7 June)
- Re: [w3c/webcomponents] I find <slot slot="..."> confusing (#514) (Tuesday, 7 June)
- Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Tuesday, 7 June)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Tuesday, 7 June)
- Re: [w3c/webcomponents] Idea: ComposedTreeProxy (#516) (Tuesday, 7 June)
- Re: [w3c/webcomponents] When is `slotchange` handler fired? (#515) (Tuesday, 7 June)
- Re: [w3c/webcomponents] When is `slotchange` handler fired? (#515) (Tuesday, 7 June)
- Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Monday, 6 June)
- Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree? (#504) (Monday, 6 June)
- Re: [w3c/webcomponents] Add <a> to safelist of elements that can call attachShadowRoot (#511) (Monday, 6 June)
- Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Friday, 3 June)
- Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Friday, 3 June)
- [w3c/webcomponents] Events whose composed flag should be true (#513) (Friday, 3 June)
- Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree? (#504) (Friday, 3 June)
- Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree? (#504) (Friday, 3 June)
- Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496) (Thursday, 2 June)
- Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496) (Wednesday, 1 June)
- Re: [w3c/webcomponents] Shadow DOM and the Fullscreen API (#180) (Wednesday, 1 June)
- Re: [w3c/webcomponents] Shadow DOM and requestPointerLock(), fullscreenElement (#192) (Wednesday, 1 June)
- Re: [w3c/webcomponents] Shadow DOM and the Fullscreen API (#180) (Wednesday, 1 June)
- Re: [w3c/webcomponents] Shadow DOM and the Fullscreen API (#180) (Wednesday, 1 June)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493) (Wednesday, 1 June)
- Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493) (Wednesday, 1 June)
- Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496) (Wednesday, 1 June)
- Re: [w3c/webcomponents] HTMLElement.prototype.offsetParent leaks a node inside a shadow tree (#497) (Wednesday, 1 June)
- Re: [w3c/webcomponents] What happens in these slot/content scenarios? (#508) (Wednesday, 1 June)
- Re: [w3c/webcomponents] What happens in these slot/content scenarios? (#508) (Wednesday, 1 June)
Henri Sivonen
- [whatwg/encoding] Editorial: Clean up gb18030 math (#63) (Tuesday, 28 June)
- Re: [whatwg/encoding] Group constants together in half-width math (#49) (Tuesday, 21 June)
- Re: [whatwg/encoding] Editorial: avoid upsetting lazy compilers (#55) (Tuesday, 21 June)
- Re: [whatwg/encoding] Editorial: avoid upsetting lazy compilers (#55) (Tuesday, 21 June)
- Re: [whatwg/encoding] Handle EUDC before the index in Shift_JIS (#54) (Tuesday, 21 June)
- Re: [whatwg/encoding] Handle EUDC before the index in Shift_JIS (#54) (Tuesday, 21 June)
- [whatwg/encoding] Please double-check the end of the EUDC range (#53) (Wednesday, 1 June)
- [whatwg/encoding] Editorial optimization: Move EUDC before index lookup (#52) (Wednesday, 1 June)
- [whatwg/encoding] Editorial: Exclude index entries instead of just pointers (#51) (Wednesday, 1 June)
- [whatwg/encoding] Edititorial: Add a note about duplicates to "index Shift_JIS pointer" (#50) (Wednesday, 1 June)
- Re: [whatwg/encoding] index-jis0208.txt should be JIS X 0208 and add another index file (#47) (Wednesday, 1 June)
hober
I-Maps
Ian Kilpatrick
Ilya Grigorik
isonmad
Ivan Herman
Iván Sánchez Ortega
J.C. Jones
Jake Archibald
- Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921) (Wednesday, 29 June)
- Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Wednesday, 29 June)
- Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Tuesday, 28 June)
- Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Tuesday, 28 June)
- Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Tuesday, 28 June)
- Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Tuesday, 28 June)
- Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920) (Tuesday, 28 June)
- Re: [slightlyoff/ServiceWorker] More clarity around waiting for an active worker to finish (#916) (Monday, 27 June)
- Re: [slightlyoff/ServiceWorker] More clarity around waiting for an active worker to finish (#916) (Friday, 24 June)
- Re: [whatwg/fetch] Handling Partial Content / 206 (#144) (Monday, 20 June)
- Re: [slightlyoff/ServiceWorker] cache.match should create partial responses if given a range request (#913) (Friday, 17 June)
- Re: [slightlyoff/ServiceWorker] Service worker not working when tested on mobile using local ip. (#914) (Thursday, 16 June)
- Re: [slightlyoff/ServiceWorker] Service worker not working when tested on mobile using local ip. (#914) (Thursday, 16 June)
- Re: [slightlyoff/ServiceWorker] cache.match should create partial responses if given a range request (#913) (Thursday, 16 June)
- Re: [slightlyoff/ServiceWorker] cache.match should create partial responses if given a range request (#913) (Thursday, 16 June)
- [slightlyoff/ServiceWorker] cache.match should create partial responses if given a range request (#913) (Wednesday, 15 June)
- Re: [whatwg/fetch] Handling Partial Content / 206 (#144) (Wednesday, 15 June)
- Re: [whatwg/fetch] Handling Partial Content / 206 (#144) (Wednesday, 15 June)
- Re: [slightlyoff/ServiceWorker] New Push API Capable of handling and/or matching Facebook Message and Apple iMessage (#911) (Tuesday, 14 June)
- Re: [slightlyoff/ServiceWorker] New Push API Capable of handling and/or matching Facebook Message and Apple iMessage (#911) (Tuesday, 14 June)
- Re: [slightlyoff/ServiceWorker] Access to fragment identifiers (#854) (Wednesday, 8 June)
- Re: [slightlyoff/ServiceWorker] Access to fragment identifiers (#854) (Wednesday, 8 June)
- Re: [slightlyoff/ServiceWorker] Access to fragment identifiers (#854) (Wednesday, 8 June)
- [w3c/WebPlatformWG] I'm attending (#40) (Wednesday, 8 June)
- Re: [slightlyoff/ServiceWorker] need AsyncLocalStorage (was #904) (#906) (Monday, 6 June)
- Re: [slightlyoff/ServiceWorker] need AsyncLocalStorage (was #904) (#906) (Monday, 6 June)
- Re: [whatwg/fetch] Is is possible to read the response before the whole request body is sent? (#315) (Saturday, 4 June)
- Re: [slightlyoff/ServiceWorker] Auto-cache imported scripts (#908) (Friday, 3 June)
- Re: [slightlyoff/ServiceWorker] potential http cache issues with importScripts() (#894) (Friday, 3 June)
- [slightlyoff/ServiceWorker] Auto-cache imported scripts (#908) (Friday, 3 June)
- Re: [slightlyoff/ServiceWorker] Receivers of ranged responses must ensure all ranges come from the same underlying resource (#703) (Friday, 3 June)
- Re: [whatwg/fetch] Handling Partial Content / 206 (#144) (Friday, 3 June)
- Re: [slightlyoff/ServiceWorker] Secure Client-Subscribed 1:M Broadcast message delivery (#901) (Thursday, 2 June)
- Re: [slightlyoff/ServiceWorker] Secure Client-Subscribed 1:M Broadcast message delivery (#901) (Thursday, 2 June)
Jan Miksovsky
jan-ivar
- Re: [whatwg/fetch] Aborting a fetch (#27) (Tuesday, 21 June)
- Re: [whatwg/fetch] Aborting a fetch (#27) (Tuesday, 21 June)
- Re: [w3c/permissions] Only allow permissions.request() during user interaction (#77) (Monday, 13 June)
- Re: [w3c/permissions] Only allow permissions.request() during user interaction (#77) (Friday, 10 June)
- Re: [w3c/permissions] Only allow permissions.request() during user interaction (#77) (Friday, 3 June)
- Re: [w3c/permissions] Only allow permissions.request() during user interaction (#77) (Friday, 3 June)
- Re: [w3c/permissions] Only allow permissions.request() during user interaction (#77) (Thursday, 2 June)
- Re: [w3c/permissions] Only allow permissions.request() during user interaction (#77) (Thursday, 2 June)
- Re: [w3c/permissions] Only allow permissions.request() during user interaction (#77) (Wednesday, 1 June)
- Re: [w3c/permissions] Only allow permissions.request() during user interaction (#77) (Wednesday, 1 June)
Jeffrey Yasskin
- Re: [w3c/permissions] Give the UA permission to return anything it wants from query(). (#97) (Wednesday, 8 June)
- Re: [w3c/permissions] Define an algorithm to update the permission storage. (#91) (Wednesday, 8 June)
- Re: [w3c/permissions] Allow UAs to maintain zero or multiple permission stores. (#95) (Wednesday, 8 June)
- Re: [w3c/permissions] Allow UAs to maintain zero or multiple permission stores. (#95) (Wednesday, 8 June)
- Re: [w3c/permissions] Describe the permission store using constraints instead of a full model. (#96) (Wednesday, 8 June)
- Re: [w3c/permissions] Describe the permission store using constraints instead of a full model. (#96) (Wednesday, 8 June)
- Re: [w3c/permissions] Define an algorithm to update the permission storage. (#91) (Wednesday, 8 June)
- Re: [w3c/permissions] Only allow permissions.request() during user interaction (#77) (Friday, 3 June)
- Re: [w3c/permissions] Only allow permissions.request() during user interaction (#77) (Thursday, 2 June)
- Re: [w3c/permissions] Only allow permissions.request() during user interaction (#77) (Wednesday, 1 June)
Jimmy Karl Roland Wärting
JoeArizona
Joey Smith
Johannes Wilm
- Re: [w3c/editing] beforeinput should be fired only when the DOM change is caused by direct input by keypress or composition (#43) (Monday, 20 June)
- Re: [w3c/editing] beforeinput should be fired only when the DOM change is caused by direct input by keypress or composition (#43) (Monday, 20 June)
- Re: [w3c/editing] beforeinput should be fired only when the DOM change is caused by direct input by keypress or composition (#43) (Monday, 20 June)
- Re: [w3c/editing] beforeinput should be fired only when the DOM change is caused by direct input by keypress or composition (#43) (Monday, 20 June)
- Re: [w3c/editing] Add a mechanism to opt-in/opt-out editing features (#93) (Saturday, 11 June)
- Re: [w3c/editing] should not use the shadow DOM for beforeInput (#76) (Saturday, 11 June)
- Re: [w3c/editing] should not use the shadow DOM for beforeInput (#76) (Saturday, 11 June)
- Re: [w3c/editing] Add a mechanism to opt-in/opt-out editing features (#93) (Wednesday, 8 June)
- Re: [w3c/editing] When should UA synthesize heights of an element? (#70) (Wednesday, 8 June)
- Re: [w3c/editing] should not use the shadow DOM for beforeInput (#76) (Tuesday, 7 June)
- Re: [w3c/editing] list all required editTypes for beforeEdit/Edit events (#79) (Tuesday, 7 June)
- Re: [w3c/editing] list all required editTypes for beforeEdit/Edit events (#79) (Tuesday, 7 June)
- Re: [w3c/editing] inputType should be tied to the command names and having that tied to a way of declaring what you support (#110) (Tuesday, 7 June)
- Re: [w3c/editing] We need a new static range API (#91) (Tuesday, 7 June)
- Re: [w3c/editing] We need a new static range API (#91) (Tuesday, 7 June)
- Re: [w3c/editing] Cancelable attribute should be removed from the spec because it already referenced in Event.idl (#100) (Saturday, 4 June)
- Re: [w3c/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) (Saturday, 4 June)
- Re: [w3c/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) (Saturday, 4 June)
- Re: [w3c/editing] [beforeinput] Should we allow canceling the committed text from IME? (#128) (Saturday, 4 June)
- Re: [w3c/editing] New API: Selection#makeVisible() (#129) (Saturday, 4 June)
John Schulz
Jon Walsh
Jonas Sicking
- Re: [w3c/IndexedDB] Return number of records deleted (#32) (Wednesday, 22 June)
- Re: [w3c/IndexedDB] Allow delete() on index (#68) (Thursday, 9 June)
- Re: [w3c/IndexedDB] Allow delete() on index (#68) (Thursday, 9 June)
- Re: [w3c/IndexedDB] Return number of records deleted (#32) (Wednesday, 8 June)
- Re: [whatwg/fetch] Listing headers safe only for certain values is a bad idea (#313) (Tuesday, 7 June)
- Re: [whatwg/fetch] Listing headers safe only for certain values is a bad idea (#313) (Tuesday, 7 June)
- Re: [whatwg/fetch] Listing headers safe only for certain values is a bad idea (#313) (Friday, 3 June)
- [whatwg/fetch] Listing headers safe only for certain values is a bad idea (#313) (Thursday, 2 June)
- Re: [w3c/IndexedDB] Return number of records deleted (#32) (Thursday, 2 June)
- Re: [w3c/IndexedDB] Return number of records deleted (#32) (Wednesday, 1 June)
- Re: [w3c/IndexedDB] Return number of records deleted (#32) (Wednesday, 1 June)
Joseph Orbegoso Pea
- Re: [w3c/webcomponents] When is `slotchange` handler fired? (#515) (Wednesday, 29 June)
- Re: [w3c/webcomponents] [idea] Ability to define Custom Element attributes (and optionally enable getters/setters for those attributes). (#517) (Wednesday, 29 June)
- Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Wednesday, 29 June)
- Re: [w3c/webcomponents] [idea] Allowing custom element registrations on per-shadow-root basis. (#488) (Tuesday, 28 June)
- Re: [w3c/webcomponents] [idea] Allowing custom element registrations on per-shadow-root basis. (#488) (Tuesday, 28 June)
- Re: [w3c/webcomponents] [idea] Allowing custom element registrations on per-shadow-root basis. (#488) (Tuesday, 28 June)
- Re: [w3c/webcomponents] [idea] Allowing custom element registrations on per-shadow-root basis. (#488) (Tuesday, 28 June)
- Re: [w3c/webcomponents] [idea] distributedCallback for Custom Elements (#527) (Tuesday, 28 June)
- Re: [w3c/webcomponents] [idea] distributedCallback for Custom Elements (#527) (Tuesday, 28 June)
- Re: [w3c/webcomponents] [idea] distributedCallback for Custom Elements (#527) (Tuesday, 28 June)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Tuesday, 28 June)
- [w3c/webcomponents] Event retargetting in layman's terms? (#528) (Tuesday, 28 June)
- Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Tuesday, 28 June)
- Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Saturday, 25 June)
- [w3c/webcomponents] [idea] distributedCallback (#527) (Saturday, 25 June)
- Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Saturday, 25 June)
- Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Saturday, 25 June)
- Re: [w3c/webcomponents] [idea] Allowing custom element registrations on per-shadow-root basis. (#488) (Saturday, 25 June)
- Re: [w3c/webcomponents] Is or how can Shadow DOM be 'SEO friendly'? (#500) (Monday, 13 June)
- Re: [w3c/webcomponents] Is or how can Shadow DOM be 'SEO friendly'? (#500) (Monday, 13 June)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Monday, 13 June)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Monday, 13 June)
- Re: [w3c/webcomponents] [idea] Allow HTML Element attributes to accept any type of value, not just strings. (#519) (Sunday, 12 June)
- Re: [w3c/webcomponents] Idea: ComposedTreeProxy (#516) (Sunday, 12 June)
- Re: [w3c/webcomponents] [idea] Ability to define Custom Element attributes (and optionally enable getters/setters for those attributes). (#517) (Sunday, 12 June)
- Re: [w3c/webcomponents] [idea] Allow HTML Element attributes to accept any type of value, not just strings. (#519) (Sunday, 12 June)
- Re: [w3c/webcomponents] [idea] Allow HTML Element attributes to accept any type of value, not just strings. (#519) (Sunday, 12 June)
- Re: [w3c/webcomponents] [idea] Allow HTML Element attributes to accept any type of value, not just strings. (#519) (Sunday, 12 June)
- Re: [w3c/webcomponents] [idea] Allow HTML Element attributes to accept any type of value, not just strings. (#519) (Sunday, 12 June)
- Re: [w3c/webcomponents] [idea] Allow HTML Element attributes to accept any type of value, not just strings. (#519) (Sunday, 12 June)
- Re: [w3c/webcomponents] [idea] Allow HTML Element attributes to accept any type of value, not just strings. (#519) (Sunday, 12 June)
- Re: [w3c/webcomponents] [idea] Allow HTML Element attributes to accept any type of value, not just strings. (#519) (Sunday, 12 June)
- Re: [w3c/webcomponents] [idea] Allow HTML Element attributes to accept any type of value, not just strings. (#519) (Sunday, 12 June)
- Re: [w3c/webcomponents] [idea] Allow HTML Element attributes to accept any type of value, not just strings. (#519) (Sunday, 12 June)
- Re: [w3c/webcomponents] [idea] Allow HTML Element attributes to accept any type of value, not just strings. (#519) (Sunday, 12 June)
- Re: [w3c/webcomponents] Idea: ComposedTreeProxy (#516) (Thursday, 9 June)
- Re: [w3c/webcomponents] When is `slotchange` handler fired? (#515) (Thursday, 9 June)
- Re: [w3c/webcomponents] idea: easy way to specify attributes (and optionally enable getters/setters). (#517) (Thursday, 9 June)
- [w3c/webcomponents] [idea] Allow HTML Element attributes to accept any type of value, not just strings. (#519) (Thursday, 9 June)
- Re: [w3c/webcomponents] idea: easy way to specify attributes (and optionally enable getters/setters). (#517) (Thursday, 9 June)
- Re: [w3c/webcomponents] idea: easy way to specify attributes (and optionally enable getters/setters). (#517) (Thursday, 9 June)
- Re: [w3c/webcomponents] idea: easy way to specify attributes (and optionally enable getters/setters). (#517) (Wednesday, 8 June)
- Re: [w3c/webcomponents] idea: easy way to specify attributes (and optionally enable getters/setters). (#517) (Tuesday, 7 June)
- Re: [w3c/webcomponents] idea: easy way to specify attributes (and optionally enable getters/setters). (#517) (Tuesday, 7 June)
- Re: [w3c/webcomponents] idea: easy way to specify attributes (and optionally enable getters/setters). (#517) (Tuesday, 7 June)
- [w3c/webcomponents] idea: easy way to specify attributes (and optionally enable getters/setters). (#517) (Tuesday, 7 June)
- [w3c/webcomponents] Idea: ComposedTreeProxy (#516) (Tuesday, 7 June)
- Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) (Tuesday, 7 June)
- Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) (Tuesday, 7 June)
- Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) (Tuesday, 7 June)
- Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Monday, 6 June)
- Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Monday, 6 June)
- Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Monday, 6 June)
- Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Monday, 6 June)
- Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Monday, 6 June)
- [w3c/webcomponents] When is `slotchange` handler fired? (#515) (Monday, 6 June)
- Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree? (#504) (Monday, 6 June)
- Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree? (#504) (Monday, 6 June)
- Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree? (#504) (Friday, 3 June)
- Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree? (#504) (Friday, 3 June)
Josh Matthews
Joshua Bell
- Re: [w3c/IndexedDB] Specify IDBOpenDBRequest processing as a queue? (#79) (Sunday, 26 June)
- Re: [w3c/IndexedDB] Specify IDBOpenDBRequest processing as a queue? (#79) (Saturday, 25 June)
- [w3c/IndexedDB] Specify IDBOpenDBRequest processing as a queue? (#79) (Friday, 24 June)
- [w3c/IndexedDB] deleteDatabase's "versionchange" should be deferred if upgrade is running (#78) (Wednesday, 22 June)
- Re: [w3c/IndexedDB] Return number of records deleted (#32) (Wednesday, 22 June)
- Re: [w3c/IndexedDB] Allow expressions in addition to keyPaths when creating indexes (#33) (Tuesday, 21 June)
- Re: [w3c/IndexedDB] Support N-dimensional queries on indexes (#40) (Tuesday, 21 June)
- Re: [w3c/IndexedDB] Allow expressions in addition to keyPaths when creating indexes (#33) (Monday, 20 June)
- Re: [w3c/FileAPI] Remove the / -> : replacement from the File constructor (#41) (Friday, 17 June)
- Re: [w3c/IndexedDB] Enforce transaction commit ordering more strictly (#77) (Thursday, 9 June)
- Re: [w3c/IndexedDB] Support batch cursors (#54) (Wednesday, 8 June)
- Re: [w3c/IndexedDB] Support batch cursors (#54) (Wednesday, 8 June)
- Re: [w3c/IndexedDB] Rewindable cursors (#55) (Wednesday, 8 June)
- Re: [w3c/IndexedDB] Rewindable cursors (#55) (Wednesday, 8 June)
- Re: [w3c/IndexedDB] Enforce transaction commit ordering more strictly (#77) (Wednesday, 8 June)
- Re: [w3c/IndexedDB] Support N-dimensional queries on indexes (#40) (Wednesday, 8 June)
- Re: [w3c/IndexedDB] Support Files stored by reference (#56) (Wednesday, 8 June)
- Re: [w3c/IndexedDB] Why is delete() disallowed for key cursors? (#62) (Wednesday, 8 June)
- Re: [w3c/IndexedDB] Allow delete() on index (#68) (Wednesday, 8 June)
- Re: [w3c/IndexedDB] Return number of records deleted (#32) (Wednesday, 8 June)
- Re: [w3c/IndexedDB] Return number of records deleted (#32) (Thursday, 2 June)
- Re: [w3c/IndexedDB] Return number of records deleted (#32) (Wednesday, 1 June)
jplaisted
JR Conlin
Jungkee Song
- Re: [slightlyoff/ServiceWorker] Eliminate usage of entry and incumbent settings objects (#922) (Thursday, 30 June)
- Re: [slightlyoff/ServiceWorker] Need to review the algorithms for creating a new environment settings object (#919) (Tuesday, 28 June)
- Re: [slightlyoff/ServiceWorker] Need to review the algorithms for creating a new environment settings object (#919) (Monday, 27 June)
- Re: [slightlyoff/ServiceWorker] Need to review the algorithms for creating a new environment settings object (#919) (Monday, 27 June)
- Re: [slightlyoff/ServiceWorker] Need to review the algorithms for creating a new environment settings object (#919) (Friday, 24 June)
- Re: [slightlyoff/ServiceWorker] When does the openWindow promise resolve? (#728) (Tuesday, 14 June)
- Re: [slightlyoff/ServiceWorker] what should the document base URI for an intercepted navigation (#787) (Thursday, 9 June)
- Re: [slightlyoff/ServiceWorker] what should the document base URI for an intercepted navigation (#787) (Thursday, 9 June)
- Re: [slightlyoff/ServiceWorker] Access to fragment identifiers (#854) (Thursday, 9 June)
- Re: [slightlyoff/ServiceWorker] Access to fragment identifiers (#854) (Thursday, 9 June)
- Re: [slightlyoff/ServiceWorker] Access to fragment identifiers (#854) (Wednesday, 8 June)
- Re: [slightlyoff/ServiceWorker] Access to fragment identifiers (#854) (Wednesday, 8 June)
- Re: [slightlyoff/ServiceWorker] Access to fragment identifiers (#854) (Tuesday, 7 June)
- Re: [slightlyoff/ServiceWorker] Allow waitUntil to be called multiple times, async (#771) (Thursday, 2 June)
Justin Fagnani
Kagami Sascha Rosylight
Kenneth Rohde Christiansen
- Re: [w3c/manifest] Add beforeinstallprompt event (#417) (Thursday, 30 June)
- Re: [w3c/manifest] Add beforeinstallprompt event (#417) (Thursday, 30 June)
- Re: [w3c/manifest] Add beforeinstallprompt event (#417) (Tuesday, 28 June)
- Re: [w3c/manifest] Add beforeinstallprompt event (#417) (Tuesday, 28 June)
- Re: [w3c/manifest] Add beforeinstallprompt event (#417) (Tuesday, 28 June)
- Re: [w3c/manifest] Fix(installation): clarify installation event (closes #473) (4fa1775) (Tuesday, 28 June)
- Re: [w3c/manifest] https://w3c.github.io/manifest/ redirects to http://manifest.sysapps.org/ (#469) (Wednesday, 8 June)
- Re: [w3c/webcomponents] I find <slot slot="..."> confusing (#514) (Tuesday, 7 June)
- Re: [w3c/webcomponents] I find <slot slot="..."> confusing (#514) (Tuesday, 7 June)
- [w3c/webcomponents] I find <slot slot="..."> confusing (#514) (Monday, 6 June)
Kevin Suttle
Kinna
Kit Cambridge
Koji Ishii
- Re: [w3c/webcomponents] Should innerHTML propagate custom element constructor exceptions? (#525) (Tuesday, 21 June)
- [w3c/webcomponents] Is custom elements constructor allowed to attachShadow? (#524) (Monday, 20 June)
- Re: [w3c/webcomponents] Why does upgrade-an-element queue attribute, connected reactions before exiting early? (#523) (Thursday, 16 June)
- Re: [w3c/webcomponents] Allow or prohibit observedAttributes to observe 'style' attribute? (#521) (Thursday, 16 June)
- Re: [w3c/webcomponents] When to invoke custom element reactions that were enqueued outside of DOM operations? (#522) (Thursday, 16 June)
- Re: [w3c/webcomponents] When to invoke custom element reactions that were enqueued outside of DOM operations? (#522) (Thursday, 16 June)
- Re: [w3c/webcomponents] When to invoke custom element reactions that were enqueued outside of DOM operations? (#522) (Wednesday, 15 June)
- [w3c/webcomponents] When to invoke custom element reactions that were enqueued outside of DOM operations? (#522) (Wednesday, 15 June)
- Re: [w3c/webcomponents] Allow or prohibit observedAttributes to observe 'style' attribute? (#521) (Wednesday, 15 June)
- Re: [w3c/webcomponents] Allow or prohibit observedAttributes to observe 'style' attribute? (#521) (Wednesday, 15 June)
- [w3c/webcomponents] Allow or prohibit observedAttributes to observe 'style' attribute? (#521) (Tuesday, 14 June)
Kris Siegel
liebrand
lostmsu
Léonie Watson
Manish Goregaokar
Marcos Cáceres
- Re: [w3c/manifest] Add beforeinstallprompt event (#417) (Thursday, 30 June)
- Re: [w3c/manifest] Add beforeinstallprompt event (#417) (Thursday, 30 June)
- Re: [w3c/manifest] Add beforeinstallprompt event (#417) (Thursday, 30 June)
- Re: [w3c/manifest] Add beforeinstallprompt event (#417) (Wednesday, 29 June)
- Re: [w3c/manifest] Tidy up the install event specification (#473) (Wednesday, 29 June)
- Re: [w3c/manifest] Tidy up the install event specification (#473) (Wednesday, 29 June)
- Re: [w3c/manifest] Tidy up the install event specification (#473) (Wednesday, 29 June)
- Re: [w3c/manifest] Fix(installation): clarify installation event (closes #473) (#474) (Wednesday, 29 June)
- Re: [w3c/manifest] Fix(installation): clarify installation event (closes #473) (#474) (Wednesday, 29 June)
- Re: [w3c/manifest] Include Minimal Store/Catalog MetaData in Manifest (#448) (Tuesday, 28 June)
- Re: [w3c/manifest] Include Minimal Store/Catalog MetaData in Manifest (#448) (Tuesday, 28 June)
- Re: [w3c/manifest] Support registering "actions" (#442) (Tuesday, 28 June)
- Re: [w3c/manifest] Support registering "actions" (#442) (Tuesday, 28 June)
- Re: [w3c/manifest] Support registering "actions" (#442) (Tuesday, 28 June)
- Re: [w3c/manifest] Fix(installation): clarify installation event (closes #473) (4fa1775) (Tuesday, 28 June)
- Re: [w3c/manifest] Include Minimal Store/Catalog MetaData in Manifest (#448) (Tuesday, 28 June)
- Re: [w3c/manifest] Include Minimal Store/Catalog MetaData in Manifest (#448) (Tuesday, 28 June)
- Re: [w3c/manifest] Tidy up the install event specification (#473) (Tuesday, 28 June)
- Re: [w3c/manifest] Fix(installation): clarify installation event (closes #473) (#474) (Tuesday, 28 June)
- [w3c/manifest] Fix(installation): clarify installation event (closes #473) (#474) (Tuesday, 28 June)
- Re: [w3c/manifest] Tidy up the install event specification (#473) (Tuesday, 28 June)
- Re: [w3c/manifest] Tidy up the install event specification (#473) (Tuesday, 28 June)
- Re: [w3c/manifest] Define core web manifest to enable extensions (#471) (Monday, 27 June)
- Re: [w3c/manifest] Define core web manifest to enable extensions (#471) (Monday, 27 June)
- Re: [w3c/manifest] Define core web manifest to enable extensions (#471) (Monday, 27 June)
- Re: [w3c/manifest] Need to specify client of image objects when fetching (an environment settings object) (#465) (Monday, 27 June)
- Re: [w3c/manifest] Need to specify client of image objects when fetching... (#465) (Monday, 27 June)
- Re: [w3c/manifest] Define core web manifest to enable extensions (#471) (Thursday, 23 June)
- Re: [w3c/manifest] Allow unique start_url for subdomains (#470) (Thursday, 23 June)
- [w3c/manifest] Expose API for managing Web App aspects (#472) (Thursday, 23 June)
- Re: [w3c/manifest] Define core web manifest to enable extensions (#471) (Thursday, 23 June)
- Re: [w3c/manifest-csp] Change status to unofficial (closes #8) (#9) (Thursday, 23 June)
- [w3c/manifest-csp] fix(index): shortname clash (#10) (Thursday, 23 June)
- [w3c/manifest-csp] Change status to unofficial (closes #8) (#9) (Thursday, 23 June)
- [w3c/manifest-csp] Change to unofficial draft (#8) (Thursday, 23 June)
- Re: [w3c/manifest] Define core web manifest to enable extensions (#471) (Thursday, 23 June)
- Re: [w3c/manifest] Define core web manifest to enable extensions (#471) (Monday, 20 June)
- [WICG/modality] Next steps? (#25) (Monday, 20 June)
- Re: [w3ctag/spec-reviews] Progressive Web Apps (#123) (Friday, 10 June)
- Re: [w3c/manifest] https://w3c.github.io/manifest/ redirects to http://manifest.sysapps.org/ (#469) (Thursday, 9 June)
- Re: [w3c/manifest] https://w3c.github.io/manifest/ redirects to http://manifest.sysapps.org/ (#469) (Thursday, 9 June)
- Re: [w3c/manifest] https://w3c.github.io/manifest/ redirects to http://manifest.sysapps.org/ (#469) (Wednesday, 8 June)
- Re: [w3c/manifest] https://w3c.github.io/manifest/ redirects to http://manifest.sysapps.org/ (#469) (Wednesday, 8 June)
- Re: [w3c/WebPlatformWG] Different ways to run a CFC? (#38) (Tuesday, 7 June)
- Re: [w3ctag/spec-reviews] Progressive Web Apps (#123) (Monday, 6 June)
Marijn Kruisselbrink
- Re: [whatwg/fetch] Add steps to intercept requests using foreign fetch. (#329) (Wednesday, 29 June)
- Re: [whatwg/fetch] Add steps to intercept requests using foreign fetch. (#329) (Wednesday, 29 June)
- [whatwg/fetch] Add steps to intercept requests using foreign fetch. (#329) (Tuesday, 28 June)
- Re: [slightlyoff/ServiceWorker] Specify serviceworker link type for link element and link header. (#828) (Tuesday, 28 June)
- Re: [slightlyoff/ServiceWorker] Don't associate a job with a client, instead just have a referrer. (#889) (Tuesday, 28 June)
- Re: [slightlyoff/ServiceWorker] Don't associate a job with a client, instead just have a referrer. (#889) (Tuesday, 28 June)
- Re: [whatwg/url] Origin of blob URLs doesn't match what implementations do (#127) (Tuesday, 28 June)
- Re: [slightlyoff/ServiceWorker] Change "validate the response" to "process the response" to match HTML (#876) (Thursday, 23 June)
- [slightlyoff/ServiceWorker] Need to review the algorithms for creating a new environment settings object (#919) (Thursday, 23 June)
- [slightlyoff/ServiceWorker] Should WindowClient.navigate(url) navigate with "replacement enabled"? (#918) (Thursday, 23 June)
- [w3c/WebPlatformWG] Update 16-07-28-29SW.md (#41) (Wednesday, 22 June)
- Re: [whatwg/url] Origin of blob URLs doesn't match what implementations do (#127) (Wednesday, 22 June)
- Re: [whatwg/url] Origin of blob URLs doesn't match what implementations do (#127) (Friday, 17 June)
- Re: [whatwg/url] Origin of blob URLs doesn't match what implementations do (#127) (Thursday, 16 June)
- Re: [whatwg/url] Origin of blob URLs doesn't match what implementations do (#127) (Thursday, 16 June)
- Re: [whatwg/url] Origin of blob URLs doesn't match what implementations do (#127) (Thursday, 16 June)
- [whatwg/url] Origin of blob URLs doesn't match what implementations do (#127) (Wednesday, 15 June)
- Re: [slightlyoff/ServiceWorker] Access to fragment identifiers (#854) (Wednesday, 8 June)
- Re: [slightlyoff/ServiceWorker] Should foreign fetch work same-origin? (#826) (Wednesday, 8 June)
- Re: [slightlyoff/ServiceWorker] Should foreign fetch work same-origin? (#826) (Wednesday, 8 June)
- Re: [slightlyoff/ServiceWorker] CORS pre-flight for foreign fetch (#880) (Tuesday, 7 June)
- Re: [slightlyoff/ServiceWorker] CORS pre-flight for foreign fetch (#880) (Tuesday, 7 June)
- Re: [slightlyoff/ServiceWorker] Should foreign fetch work same-origin? (#826) (Tuesday, 7 June)
- Re: [slightlyoff/ServiceWorker] Access to fragment identifiers (#854) (Tuesday, 7 June)
- Re: [slightlyoff/ServiceWorker] Auto-cache imported scripts (#908) (Friday, 3 June)
- Re: [slightlyoff/ServiceWorker] Auto-cache imported scripts (#908) (Friday, 3 June)
Mark Nottingham
Martin Thomson
Matt Falkenhagen
Matt Giuca
- Re: [w3c/manifest] Add beforeinstallprompt event (#417) (Thursday, 30 June)
- Re: [w3c/manifest] Add beforeinstallprompt event (#417) (Thursday, 30 June)
- Re: [w3c/manifest] Add beforeinstallprompt event (#417) (Wednesday, 29 June)
- Re: [w3c/manifest] Tidy up the install event specification (#473) (Wednesday, 29 June)
- Re: [w3c/manifest] Install event definition is missing some details (#475) (Wednesday, 29 June)
- Re: [w3c/manifest] Add beforeinstallprompt event (#417) (Wednesday, 29 June)
- Re: [w3c/manifest] Add beforeinstallprompt event (#417) (Tuesday, 28 June)
- Re: [w3c/manifest] Fix(installation): clarify installation event (closes #473) (#474) (Tuesday, 28 June)
- Re: [w3c/manifest] Fix(installation): clarify installation event (closes #473) (#474) (Tuesday, 28 June)
- Re: [w3c/manifest] Tidy up the install event specification (#473) (Tuesday, 28 June)
- Re: [w3c/manifest] Add beforeinstallprompt event (#417) (Tuesday, 28 June)
- [w3c/manifest] Tidy up the install event specification (#473) (Tuesday, 28 June)
Matt N.
Michael van Ouwerkerk
Michael[tm] Smith
Michiel Bijl
Mihai Potra
Mike West
Mohamed Hafez
- Re: [w3c/push-api] Pass removed subscriptions as a property of the `pushsubscriptionchange` event (#193) (Tuesday, 14 June)
- Re: [w3c/push-api] Pass removed subscriptions as a property of the `pushsubscriptionchange` event (#193) (Sunday, 12 June)
- Re: [w3c/push-api] Pass removed subscriptions as a property of the `pushsubscriptionchange` event (#193) (Sunday, 12 June)
- Re: [w3c/push-api] Pass removed subscriptions as a property of the `pushsubscriptionchange` event (#193) (Sunday, 12 June)
- Re: [w3c/push-api] Describe process for subscription updates (#132) (Saturday, 11 June)
- Re: [w3c/push-api] Auto-retrying Webhook for re-subscribing in ServiceWorker (#197) (Saturday, 11 June)
- Re: [w3c/push-api] Auto-retrying Webhook for re-subscribing in ServiceWorker (#197) (Saturday, 11 June)
- Re: [w3c/push-api] Describe process for subscription updates (#132) (Saturday, 11 June)
- Re: [w3c/push-api] Pass removed subscriptions as a property of the `pushsubscriptionchange` event (#193) (Saturday, 11 June)
- [w3c/push-api] Auto-retrying webhook for re-subscribing in ServiceWorker (#197) (Friday, 10 June)
- Re: [w3c/push-api] Describe process for subscription updates (#132) (Friday, 10 June)
Mounir Lamouri
Ms2ger
Owen Campbell-Moore
Patrick H. Lauke
Paul Kinlan
Pedram Emrouznejad
Peter Linss
Philip Jägenstedt
- Re: [whatwg/fullscreen] Propose to always render elements in the top layer as if it is fixed positioned (#19) (Thursday, 30 June)
- Re: [whatwg/fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) (Thursday, 30 June)
- Re: [whatwg/fullscreen] Propose to always render elements in the top layer as if it is fixed positioned (#19) (Wednesday, 29 June)
- Re: [whatwg/fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) (Tuesday, 28 June)
- Re: [whatwg/fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) (Tuesday, 28 June)
- Re: [whatwg/url] Allow for a URL record's object to be a MediaSource or MediaStream (#126) (Monday, 13 June)
- Re: [whatwg/url] Allow for a URL record's object to be a MediaSource or MediaStream (#126) (Thursday, 9 June)
- [whatwg/url] Allow for a URL record's object to be a MediaSource or MediaStream (#126) (Thursday, 9 June)
- Re: [w3c/manifest] https://w3c.github.io/manifest/ redirects to http://manifest.sysapps.org/ (#469) (Thursday, 9 June)
- Re: [w3c/manifest] https://w3c.github.io/manifest/ redirects to http://manifest.sysapps.org/ (#469) (Wednesday, 8 June)
- Re: [w3c/manifest] https://w3c.github.io/manifest/ redirects to http://manifest.sysapps.org/ (#469) (Wednesday, 8 June)
- [w3c/manifest] https://w3c.github.io/manifest/ redirects to http://manifest.sysapps.org/ (#469) (Wednesday, 8 June)
PhistucK
publicocean0
Pyry Kovanen
r12a
Rafał Ruciński
raymeskhoury
Remy Sharp
Richard Maher
Rick Byers
- Re: [w3c/touch-events] Fix #66. Make all touch events composed events (#67) (Wednesday, 29 June)
- Re: [w3c/touch-events] Support Event.composed in Touch Events (#66) (Wednesday, 29 June)
- Re: [w3c/touch-events] Fix #66. Make all touch events composed events (#67) (Wednesday, 29 June)
- Re: [w3c/manifest] Tidy up the install event specification (#473) (Wednesday, 29 June)
- Re: [w3c/manifest] Tidy up the install event specification (#473) (Wednesday, 29 June)
- Re: [w3c/manifest] Install event definition is missing some details (#475) (Wednesday, 29 June)
- Re: [w3c/manifest] Install event definition is missing some details (#475) (Wednesday, 29 June)
- [w3c/manifest] Install event definition is missing some details (#475) (Wednesday, 29 June)
- [w3c/touch-events] Define interactions with `contextmenu` event? (#68) (Monday, 27 June)
- Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Thursday, 23 June)
- Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Wednesday, 22 June)
- Re: [w3c/uievents] Gamepad-specific DOM keys / location? (#79) (Tuesday, 21 June)
- Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Tuesday, 21 June)
- Re: [w3c/uievents] Support Event.composed (#89) (Tuesday, 21 June)
- Re: [w3c/touch-events] Fix #66. Make all touch events composed events (#67) (Tuesday, 21 June)
- Re: [whatwg/dom] What happens if a 'once' eventListener dispatches a similar event? (#265) (Monday, 6 June)
- Re: [w3c/uievents] Expose ticks in wheel events (#17) (Friday, 3 June)
Rick Lee
Rob Dodson
Rob Dolin (MSFT)
roryhewitt
Ruben Verborgh
Russell Bicknell
Ryosuke Niwa
- Re: [w3c/webcomponents] [idea] Allowing custom element registrations on per-shadow-root basis. (#488) (Tuesday, 28 June)
- Re: [whatwg/dom] "In a document" confusion (#238) (Tuesday, 28 June)
- Re: [w3c/webcomponents] ShadowRoot.styleSheets should return an empty StyleSheetList if the shadow root is not in a shadow-including document (#526) (Monday, 27 June)
- Re: [w3c/webcomponents] ShadowRoot.styleSheets should return an empty StyleSheetList if the shadow root is not in a shadow-including document (#526) (Monday, 27 June)
- Re: [w3c/webcomponents] ShadowRoot.styleSheets should return an empty StyleSheetList if the shadow root is not in a shadow-including document (#526) (Monday, 27 June)
- Re: [w3c/webcomponents] [idea] Allowing custom element registrations on per-shadow-root basis. (#488) (Saturday, 25 June)
- Re: [w3c/webcomponents] [idea] Allowing custom element registrations on per-shadow-root basis. (#488) (Saturday, 25 June)
- Re: [w3c/webcomponents] ShadowRoot.styleSheets should return an empty StyleSheetList if the shadow root is not in a shadow-including document (#526) (Friday, 24 June)
- Re: [w3c/webcomponents] ShadowRoot.styleSheets should return an empty StyleSheetList if the shadow root is not in a shadow-including document (#526) (Friday, 24 June)
- Re: [w3c/webcomponents] ShadowRoot.styleSheets should return an empty StyleSheetList if the shadow root is not in a shadow-including document (#526) (Friday, 24 June)
- Re: [whatwg/dom] "In a document" confusion (#238) (Friday, 24 June)
- Re: [w3c/webcomponents] Should innerHTML propagate custom element constructor exceptions? (#525) (Tuesday, 21 June)
- Re: [w3c/webcomponents] Should innerHTML propagate custom element constructor exceptions? (#525) (Tuesday, 21 June)
- Re: [w3c/webcomponents] Is custom elements constructor allowed to attachShadow? (#524) (Tuesday, 21 June)
- Re: [w3c/webcomponents] Is custom elements constructor allowed to attachShadow? (#524) (Tuesday, 21 June)
- Re: [w3c/webcomponents] Is custom elements constructor allowed to attachShadow? (#524) (Tuesday, 21 June)
- Re: [w3c/webcomponents] Is custom elements constructor allowed to attachShadow? (#524) (Tuesday, 21 June)
- Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Tuesday, 21 June)
- Re: [w3c/webcomponents] Should innerHTML propagate custom element constructor exceptions? (#525) (Tuesday, 21 June)
- Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Thursday, 16 June)
- Re: [w3c/webcomponents] Allow or prohibit observedAttributes to observe 'style' attribute? (#521) (Wednesday, 15 June)
- Re: [w3c/webcomponents] Declarative syntax for custom elements (#136) (Friday, 10 June)
- Re: [w3c/webcomponents] Disabling tabindex across potentially many shadow roots (#520) (Friday, 10 June)
- Re: [w3c/webcomponents] Disabling tabindex across potentially many shadow roots (#520) (Thursday, 9 June)
- Re: [w3c/webcomponents] When is `slotchange` handler fired? (#515) (Thursday, 9 June)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Thursday, 9 June)
- Re: [w3c/webcomponents] To notify mutation observers should make a copy of signalList before delivering mutation records (#518) (Thursday, 9 June)
- Re: [w3c/webcomponents] idea: easy way to specify attributes (and optionally enable getters/setters). (#517) (Thursday, 9 June)
- Re: [w3c/webcomponents] To notify mutation observers should make a copy of signalList before delivering mutation records (#518) (Wednesday, 8 June)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Wednesday, 8 June)
- Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Wednesday, 8 June)
- Re: [w3c/webcomponents] To notify mutation observers should make a copy of signalList before delivering mutation records (#518) (Wednesday, 8 June)
- [w3c/webcomponents] To notify mutation observers should make a copy of signalList before delivering mutation records (#518) (Wednesday, 8 June)
- Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Wednesday, 8 June)
- Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Wednesday, 8 June)
- Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Tuesday, 7 June)
- Re: [w3c/webcomponents] idea: easy way to specify attributes (and optionally enable getters/setters). (#517) (Tuesday, 7 June)
- Re: [w3c/webcomponents] Shadow DOM and the Fullscreen API (#180) (Tuesday, 7 June)
- Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Tuesday, 7 June)
- Re: [w3c/webcomponents] Shadow DOM and the Fullscreen API (#180) (Tuesday, 7 June)
- Re: [w3c/DOM-Parsing] innerHTML needs special case for <template> (#1) (Tuesday, 7 June)
- Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) (Tuesday, 7 June)
- Re: [w3c/webcomponents] When is `slotchange` handler fired? (#515) (Tuesday, 7 June)
- Re: [w3c/webcomponents] Idea: ComposedTreeProxy (#516) (Tuesday, 7 June)
- Re: [w3c/webcomponents] I find <slot slot="..."> confusing (#514) (Tuesday, 7 June)
- Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241) (Monday, 6 June)
- Re: [w3c/DOM-Parsing] innerHTML needs special case for <template> (#1) (Monday, 6 June)
- Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Monday, 6 June)
- Re: [w3c/DOM-Parsing] innerHTML needs special case for <template> (#1) (Monday, 6 June)
- Re: [w3c/webcomponents] Add <a> to safelist of elements that can call attachShadowRoot (#511) (Monday, 6 June)
- Re: [w3c/webcomponents] Add <a> to safelist of elements that can call attachShadowRoot (#511) (Monday, 6 June)
- Re: [w3c/webcomponents] Add <a> to safelist of elements that can call attachShadowRoot (#511) (Monday, 6 June)
- Re: [w3c/webcomponents] Best practices for styling web components (#510) (Saturday, 4 June)
- Re: [w3c/webcomponents] Best practices for styling web components (#510) (Saturday, 4 June)
- Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree? (#504) (Saturday, 4 June)
- Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Saturday, 4 June)
- Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78) (Friday, 3 June)
- Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Friday, 3 June)
- Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Friday, 3 June)
- Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Friday, 3 June)
- Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Friday, 3 June)
- Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78) (Friday, 3 June)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Friday, 3 June)
- Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Friday, 3 June)
- Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Thursday, 2 June)
- [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512) (Thursday, 2 June)
- Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78) (Thursday, 2 June)
- Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496) (Thursday, 2 June)
- Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496) (Wednesday, 1 June)
- Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78) (Wednesday, 1 June)
- Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) (Wednesday, 1 June)
- Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78) (Wednesday, 1 June)
Salvador de la Puente González
- Re: [slightlyoff/ServiceWorker] More clarity around waiting for an active worker to finish (#916) (Wednesday, 29 June)
- Re: [slightlyoff/ServiceWorker] service worker not working for localhost (#915) (Friday, 17 June)
- Re: [slightlyoff/ServiceWorker] service worker not working for localhost (#915) (Thursday, 16 June)
- Re: [slightlyoff/ServiceWorker] service worker not working for localhost (#915) (Thursday, 16 June)
- Re: [slightlyoff/ServiceWorker] Should foreign fetch work same-origin? (#826) (Wednesday, 8 June)
- Re: [slightlyoff/ServiceWorker] openWindow with a WebApp manifests (#720) (Tuesday, 7 June)
- Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Tuesday, 7 June)
- Re: [slightlyoff/ServiceWorker] CORS pre-flight for foreign fetch (#880) (Tuesday, 7 June)
- Re: [slightlyoff/ServiceWorker] CORS pre-flight for foreign fetch (#880) (Tuesday, 7 June)
- Re: [slightlyoff/ServiceWorker] How are unloaded tabs represented? (#626) (Tuesday, 7 June)
- Re: [slightlyoff/ServiceWorker] Preventing server-forced updates (#822) (Tuesday, 7 June)
- Re: [slightlyoff/ServiceWorker] Installing a foreign SW as part of a subresource request (#825) (Tuesday, 7 June)
- Re: [slightlyoff/ServiceWorker] Should foreign fetch work same-origin? (#826) (Tuesday, 7 June)
- Re: [slightlyoff/ServiceWorker] Allow preventing the update process to finish (#761) (Tuesday, 7 June)
- Re: [slightlyoff/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Tuesday, 7 June)
- Re: [slightlyoff/ServiceWorker] Introduce `Service-Worker-Max-Age` header (#721) (Tuesday, 7 June)
- Re: [slightlyoff/ServiceWorker] CORS pre-flight for foreign fetch (#880) (Tuesday, 7 June)
- Re: [slightlyoff/ServiceWorker] Never fail for navigation requests (#892) (Monday, 6 June)
- Re: [slightlyoff/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Monday, 6 June)
- Re: [slightlyoff/ServiceWorker] what is the best way to save Request while offline ? (#904) (Monday, 6 June)
- Re: [slightlyoff/ServiceWorker] need AsyncLocalStorage (was #904) (#906) (Monday, 6 June)
Sebastian Markbåge
shans
Shashank Parekh
smaug----
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Tuesday, 28 June)
- Re: [WICG/directory-upload] It is unclear how FormData object gets populated when Upload API is used (#40) (Monday, 20 June)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Monday, 20 June)
- Re: [WICG/directory-upload] It is unclear how FormData object gets populated when Upload API is used (#40) (Monday, 20 June)
- Re: [WICG/directory-upload] It is unclear how FormData object gets populated when Upload API is used (#40) (Monday, 20 June)
- Re: [w3c/uievents] Figure out what to do with focusin/focusout (#88) (Monday, 20 June)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Monday, 20 June)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Monday, 20 June)
- Re: [WICG/directory-upload] It is unclear how FormData object gets populated when Upload API is used (#40) (Sunday, 19 June)
- [WICG/directory-upload] It is unclear how FormData object gets populated when Upload API is used (#40) (Sunday, 19 June)
- [whatwg/dom] UAs create elements in HTML namespace when context object is an HTML … (#267) (Tuesday, 7 June)
- [whatwg/dom] .createElement's namespace handling doesn't seem to match what UAs do (#264) (Monday, 6 June)
- Re: [whatwg/dom] Change .createElement() namespace to match UAs (#213) (Monday, 6 June)
sourdieselOG
staktrace
Steven Lambert
Tab Atkins Jr.
Takayoshi Kochi
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Thursday, 30 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Thursday, 30 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Thursday, 30 June)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Thursday, 30 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Tuesday, 28 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Monday, 27 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 24 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 24 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 24 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 24 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 24 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 24 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Friday, 24 June)
- Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496) (Friday, 24 June)
- Re: [w3c/pointerlock] Update for Shadow DOM (#4) (Thursday, 23 June)
- [w3c/pointerlock] Update for Shadow DOM (#4) (Thursday, 23 June)
- [w3c/pointerlock] PointerLock and Shadow DOM (#3) (Thursday, 23 June)
- Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496) (Thursday, 23 June)
- Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496) (Thursday, 23 June)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Monday, 20 June)
- Re: [w3c/webcomponents] <iframe> and the History API (#184) (Monday, 20 June)
- Re: [w3c/webcomponents] Shadow DOM and the Fullscreen API (#180) (Monday, 20 June)
- Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496) (Monday, 20 June)
- Re: [w3c/webcomponents] Disabling tabindex across potentially many shadow roots (#520) (Friday, 10 June)
- Re: [w3c/webcomponents] Disabling tabindex across potentially many shadow roots (#520) (Friday, 10 June)
- Re: [w3c/webcomponents] Shadow DOM and requestPointerLock() (#192) (Tuesday, 7 June)
- Re: [w3c/webcomponents] Shadow DOM and the Fullscreen API (#180) (Tuesday, 7 June)
- Re: [w3c/webcomponents] Shadow DOM and the Fullscreen API (#180) (Tuesday, 7 June)
- Re: [w3c/webcomponents] Shadow DOM and the Fullscreen API (#180) (Tuesday, 7 June)
- Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496) (Friday, 3 June)
- Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496) (Friday, 3 June)
Takeshi Yoshino
- Re: [whatwg/streams] Tweak ReadableByteStreamControllerEnqueue algorithm structure (#473) (Wednesday, 29 June)
- Re: [whatwg/streams] Tweak ReadableByteStreamControllerEnqueue algorithm structure (#473) (Wednesday, 29 June)
- Re: [whatwg/streams] tighten ReadableStreamReaderGenericRelease assertion (#466) (Tuesday, 28 June)
- [whatwg/streams] Tighten the assertion on the owner stream in ReadableStreamReaderGene… (#472) (Tuesday, 28 June)
- Re: [whatwg/streams] ReadableByteStreamControllerClose accesses first element of pendingPullIntos without checking array length (#470) (Tuesday, 28 June)
- [whatwg/streams] Fix pendingPullIntos access in ReadableByteStreamControllerClose() (#471) (Tuesday, 28 June)
- Re: [whatwg/streams] [WritableStream] Shouldn't the state after writer.abort() be closed? (#464) (Monday, 27 June)
- Re: [whatwg/streams] [WritableStream] Shouldn't the state after writer.abort() be closed? (#464) (Monday, 27 June)
- Re: [whatwg/streams] [WritableStream] Shouldn't the state after writer.abort() be closed? (#464) (Monday, 27 June)
- Re: [whatwg/streams] [WritableStream] Shouldn't the state after writer.abort() be closed? (#464) (Monday, 27 June)
- Re: [whatwg/streams] can streams be transferred via postMessage()? (#276) (Thursday, 23 June)
- Re: [whatwg/streams] Communication between workers/windows via Streams API (#244) (Thursday, 23 June)
- Re: [whatwg/streams] More concrete examples of "optimization" of pipeTo (#359) (Thursday, 23 June)
- Re: [whatwg/streams] Ensure the JS thread doesn't have to get hit when piping two streams to each other (#97) (Thursday, 23 June)
- Re: [whatwg/streams] [WritableStream] Shouldn't the state after writer.abort() be closed? (#464) (Thursday, 16 June)
- Re: [whatwg/streams] 3.11.4.3. respondWithNewView(view) references `chunk` (#467) (Friday, 10 June)
- Re: [whatwg/streams] 3.11.4.3. respondWithNewView(view) references `chunk` (#467) (Friday, 10 June)
- Re: [whatwg/streams] Synchronous (or asynchronous) state probing on WritableStream (#463) (Thursday, 9 June)
- Re: [whatwg/streams] [WritableStream] Shouldn't the state after writer.abort() be closed? (#464) (Thursday, 9 June)
- Re: [whatwg/streams] Synchronous (or asynchronous) state probing on WritableStream (#463) (Tuesday, 7 June)
- Re: [whatwg/streams] Convert internal slot accesses in the reference implementation to use symbols (#443) (Monday, 6 June)
- Re: [whatwg/streams] Convert internal slot accesses in the reference implementation to use symbols (#443) (Monday, 6 June)
- Re: [whatwg/streams] Convert internal slot accesses in the reference implementation to use symbols (#443) (Monday, 6 June)
- Re: [whatwg/streams] Convert internal slot accesses in the reference implementation to use symbols (#443) (Monday, 6 June)
- Re: [whatwg/streams] [WritableStream] Shouldn't the state after writer.abort() be closed? (#464) (Friday, 3 June)
- Re: [whatwg/fetch] autolink fix: Typo of concept-client-hints-list (#314) (Friday, 3 June)
- [whatwg/fetch] autolink fix: Typo of concept-client-hints-list (#314) (Friday, 3 June)
- Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Thursday, 2 June)
- Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Thursday, 2 June)
- Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Thursday, 2 June)
- Re: [whatwg/streams] [WritableStream] Shouldn't the state after writer.abort() be closed? (#464) (Thursday, 2 June)
- Re: [whatwg/streams] [WritableStream] Shouldn't the state after writer.abort() be closed? (#464) (Thursday, 2 June)
- Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Wednesday, 1 June)
- Re: [whatwg/streams] light weight transformations (#461) (Wednesday, 1 June)
- Re: [whatwg/streams] Synchronous queue draining for WritableStream (#465) (Wednesday, 1 June)
- Re: [whatwg/streams] Align WritableStream structure with ReadableStream structure (#462) (Wednesday, 1 June)
- [whatwg/streams] Synchronous queue draining for WritableStream (#465) (Wednesday, 1 June)
Ted Mielczarek
Till Schneidereit
Timothy Guan-tin Chien
Tobie Langel
Tom Van Goethem
Tomek Wytrębowicz
Tony Trinh
toriningen
Travis Leithead
- Re: [w3c/uievents] Probably remove 3.5 -- very redundant with HTML at the moment. (#90) (Friday, 17 June)
- [w3c/uievents] Probably remove 3.5 -- very redundant with HTML at the moment. (#90) (Friday, 17 June)
- [w3c/DOM-Parsing] Significant normative and editorial updates (#16) (Friday, 17 June)
- Re: [heycam/webidl] Should probably spec a hasInstance for DOM interface objects (#129) (Wednesday, 15 June)
- Re: [w3ctag/spec-reviews] Review FIDO spec (#97) (Wednesday, 8 June)
- Re: [w3ctag/spec-reviews] Credential Management API (#49) (Wednesday, 8 June)
- Re: [w3c/DOM-Parsing] Special case innerHTML for template parsing; note for outerHTML (#12) (Wednesday, 8 June)
- Re: [w3c/DOM-Parsing] innerHTML needs special case for <template> (#1) (Wednesday, 8 June)
- Re: [w3c/DOM-Parsing] innerHTML needs special case for <template> (#1) (Wednesday, 8 June)
- Re: [w3c/DOM-Parsing] Special case innerHTML for template parsing; note for outerHTML (#12) (Wednesday, 8 June)
- Re: [w3c/DOM-Parsing] innerHTML needs special case for <template> (#1) (Monday, 6 June)
- Re: [w3c/DOM-Parsing] innerHTML needs special case for <template> (#1) (Monday, 6 June)
- Re: [w3c/DOM-Parsing] Special case innerHTML for template parsing; note for outerHTML (#12) (Monday, 6 June)
- Re: [w3c/DOM-Parsing] Special case innerHTML for template parsing; note for outerHTML (#12) (Monday, 6 June)
- [w3c/DOM-Parsing] Apply serialization algorithm fixes based on testing (#14) (Friday, 3 June)
- Re: [w3c/DOM-Parsing] Document serialization steps are wrong (#11) (Friday, 3 June)
- Re: [w3c/DOM-Parsing] Fix document serialization (#13) (Friday, 3 June)
- [w3c/DOM-Parsing] Fix document serialization (#13) (Friday, 3 June)
- Re: [w3c/DOM-Parsing] innerHTML needs special case for <template> (#1) (Friday, 3 June)
- [w3c/DOM-Parsing] Special case innerHTML for template parsing; note for outerHTML (#12) (Friday, 3 June)
- [w3c/DOM-Parsing] Document serialization steps are wrong (#11) (Friday, 3 June)
- Re: [w3c/DOM-Parsing] Editorial refactoring (#10) (Friday, 3 June)
- Re: [w3c/DOM-Parsing] Test suite link doesn't link to all the relevant tests (#3) (Friday, 3 June)
- Re: [w3c/DOM-Parsing] Test suite link doesn't link to all the relevant tests (#3) (Friday, 3 June)
- Re: [w3c/DOM-Parsing] Trim unused Respec configuration flags; add additional test suite links (#9) (Friday, 3 June)
- [w3c/DOM-Parsing] Editorial refactoring (#10) (Friday, 3 June)
- [w3c/DOM-Parsing] Trim unused Respec configuration flags; add additional test suite links (#9) (Friday, 3 June)
Trey Shugart
- Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Wednesday, 29 June)
- Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Wednesday, 29 June)
- Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Sunday, 26 June)
- Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499) (Monday, 13 June)
- Re: [w3c/webcomponents] [idea] Allow HTML Element attributes to accept any type of value, not just strings. (#519) (Monday, 13 June)
- Re: [w3c/webcomponents] [idea] Ability to define Custom Element attributes (and optionally enable getters/setters for those attributes). (#517) (Monday, 13 June)
- Re: [w3c/webcomponents] [idea] Ability to define Custom Element attributes (and optionally enable getters/setters for those attributes). (#517) (Friday, 10 June)
- Re: [w3c/webcomponents] idea: easy way to specify attributes (and optionally enable getters/setters). (#517) (Wednesday, 8 June)
- Re: [w3c/webcomponents] I find <slot slot="..."> confusing (#514) (Tuesday, 7 June)
- Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree (slotchange)? (#504) (Monday, 6 June)
- Re: [w3c/webcomponents] How can a custom element detect when it is transcluded into a shadow tree? (#504) (Wednesday, 1 June)
- Re: [w3c/webcomponents] What happens in these slot/content scenarios? (#508) (Wednesday, 1 June)
Tzviya
vanupam
Vincent Scheib
wifiextender
Xiaoqian Wu
Xidorn Quan
- Re: [whatwg/fullscreen] root element background propagation issue (#40) (Thursday, 30 June)
- Re: [whatwg/fullscreen] root element background propagation issue (#40) (Thursday, 30 June)
- Re: [whatwg/fullscreen] Propose to always render elements in the top layer as if it is fixed positioned (#19) (Thursday, 30 June)
- Re: [whatwg/fullscreen] Propose to always render elements in the top layer as if it is fixed positioned (#19) (Thursday, 30 June)
- Re: [whatwg/fullscreen] Propose to always render elements in the top layer as if it is fixed positioned (#19) (Thursday, 30 June)
- Re: [whatwg/fullscreen] Propose to always render elements in the top layer as if it is fixed positioned (#19) (Thursday, 30 June)
- Re: [whatwg/fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) (Wednesday, 29 June)
- [w3c/screen-orientation] Timing of triggering change event doesn't look right (#89) (Wednesday, 29 June)
- Re: [whatwg/fullscreen] root element background propagation issue (#40) (Friday, 17 June)
- Re: [whatwg/fullscreen] root element background propagation issue (#40) (Friday, 17 June)
- Re: [whatwg/fullscreen] Reserved keyboard shortcut behaviour in fullscreen (#39) (Thursday, 2 June)
- Re: [whatwg/fullscreen] Reserved keyboard shortcut behaviour in fullscreen (#39) (Thursday, 2 June)
- Re: [whatwg/fullscreen] Reserved keyboard shortcut behaviour in fullscreen (#39) (Thursday, 2 June)
Yehuda Katz
- Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Wednesday, 22 June)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Wednesday, 22 June)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Wednesday, 22 June)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Tuesday, 21 June)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Tuesday, 21 June)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Tuesday, 21 June)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Monday, 20 June)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Monday, 20 June)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Monday, 20 June)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Monday, 20 June)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Monday, 20 June)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Monday, 20 June)
- Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Monday, 20 June)
- [whatwg/dom] Proposal: DOMChangeList (#270) (Monday, 20 June)
Yoav Weiss
youennf
Yutaka Hirano
Yves Lafon
Zambonifofex
- Re: [w3c/webcomponents] [idea] Allow HTML Element attributes to accept any type of value, not just strings. (#519) (Sunday, 12 June)
- Re: [w3c/webcomponents] [idea] Allow HTML Element attributes to accept any type of value, not just strings. (#519) (Sunday, 12 June)
- Re: [w3c/webcomponents] [idea] Allow HTML Element attributes to accept any type of value, not just strings. (#519) (Sunday, 12 June)
- Re: [w3c/webcomponents] [idea] Allow HTML Element attributes to accept any type of value, not just strings. (#519) (Sunday, 12 June)
- Re: [w3c/webcomponents] [idea] Allow HTML Element attributes to accept any type of value, not just strings. (#519) (Sunday, 12 June)
- Re: [w3c/webcomponents] [idea] Allow HTML Element attributes to accept any type of value, not just strings. (#519) (Sunday, 12 June)
- Re: [w3c/webcomponents] [idea] Allow HTML Element attributes to accept any type of value, not just strings. (#519) (Sunday, 12 June)
- Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) (Sunday, 12 June)
- Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) (Sunday, 12 June)
- Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) (Saturday, 11 June)
- Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) (Saturday, 11 June)
- Re: [w3c/webcomponents] Declarative syntax for custom elements (#136) (Friday, 10 June)
- Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509) (Friday, 10 June)
- Re: [w3c/webcomponents] Declarative syntax for custom elements (#136) (Friday, 10 June)
- Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Friday, 10 June)
- Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Thursday, 9 June)
Last message date: Thursday, 30 June 2016 21:22:41 UTC