public-webapps-github@w3.org from March 2016 by author

Adam Klein

• Re: [w3c/webcomponents] Need "slotchange" event (#288) (Monday, 28 March)

Adam Lavin

• Re: [fetch] Add examples for PATCH and PatcH (or some such) (#260) (Wednesday, 23 March)
• Re: [fetch] PATCH verb (#50) (Wednesday, 23 March)

Ade Bateman

• Re: [WebPlatformWG] Update 11-12aprSW.md (#19) (Tuesday, 22 March)
• Re: [WebPlatformWG] Added Alex Danilo as attendee (#20) (Tuesday, 22 March)
• Re: [WebPlatformWG] Add jungkees to SW F2F attendees/agenda (#18) (Tuesday, 22 March)
• Re: [WebPlatformWG] Add jungkees to SW F2F attendees/agenda (#18) (Tuesday, 22 March)
• Re: [WebPlatformWG] Added Alex Danilo as attendee (#20) (Tuesday, 22 March)
• Re: [WebPlatformWG] Update 11-12aprSW.md (#19) (Tuesday, 22 March)
• Re: [WebPlatformWG] Add falken to attendees (#17) (Tuesday, 22 March)
• Re: [WebPlatformWG] Add falken to attendees (#17) (Tuesday, 22 March)
• Re: [WebPlatformWG] Add self to SW F2F attendees/agenda (#16) (Tuesday, 22 March)

AJ Klein

• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Monday, 7 March)

Akash Goel

• [FileAPI] Update Typed Array spec URL (#34) (Sunday, 20 March)

Alberto Torres

• Re: [fetch] Add timeout option (#20) (Monday, 14 March)

alcat2008

• Re: [fetch] Add timeout option (#20) (Monday, 14 March)

Alex Danilo

• [WebPlatformWG] Added Alex Danilo as attendee (#20) (Friday, 18 March)

Alex Russell

• Re: [w3ctag/spec-reviews] Indexed DB getAll(), openKeyCursor() and objectStoreNames (#84) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] Write up the Secure Stop issue for ddorwin (#73) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] Review WAPA (Accessibility) proposal (#63) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] Performance Observer Review (formerly Navigation Timing 2 concepts) (#18) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] Create a "advice for spec authors" page (#78) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] ARIA (#107) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] Ambient Light Sensor API (#115) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] Storage persistence (#85) (Wednesday, 30 March)
• [whatwg/storage] Lack of example and Explainer document (#16) (Wednesday, 30 March)
• [whatwg/storage] `estimate()` and `persistentEstimate()` incompatible with whole-origin persistence (#15) (Wednesday, 30 March)
• [whatwg/storage] Permissions API reflection for Persistent Permission (#14) (Wednesday, 30 March)
• Re: [w3ctag/spec-reviews] Review FIDO spec (#97) (Wednesday, 30 March)

aliams

• Re: [WICG/directory-upload] Consider to remove HTMLInputElement.getFilesAndDirectories andHTMLInputElement.getFiles (#33) (Tuesday, 29 March)
• Re: [WICG/directory-upload] Consider to remove HTMLInputElement.getFilesAndDirectories andHTMLInputElement.getFiles (#33) (Monday, 28 March)
• Re: [directory-upload] Consider renaming getDirectoriesAndFiles to fsitems or getFSItems (#32) (Wednesday, 23 March)
• Re: [directory-upload] input.files shouldn't be null if directory attribute is used (or at least not if webkitdirectory attribute is also set) (#29) (Wednesday, 23 March)
• Re: [directory-upload] Consider renaming getDirectoriesAndFiles to fsitems or getFSItems (#32) (Wednesday, 23 March)
• Re: [directory-upload] Consider renaming getDirectoriesAndFiles to fsitems or getFSItems (#32) (Wednesday, 23 March)
• Re: [directory-upload] input.files shouldn't be null if directory attribute is used (or at least not if webkitdirectory attribute is also set) (#29) (Wednesday, 23 March)
• Re: [directory-upload] input.files shouldn't be null if directory attribute is used (or at least not if webkitdirectory attribute is also set) (#29) (Tuesday, 22 March)
• Re: [directory-upload] input.files shouldn't be null if directory attribute is used (or at least not if webkitdirectory attribute is also set) (#29) (Tuesday, 22 March)
• Re: [directory-upload] input.files shouldn't be null if directory attribute is used (or at least not if webkitdirectory attribute is also set) (#29) (Tuesday, 22 March)
• Re: [directory-upload] input.files shouldn't be null if directory attribute is used (or at least not if webkitdirectory attribute is also set) (#29) (Tuesday, 22 March)
• Re: [directory-upload] input.files shouldn't be null if directory attribute is used (or at least not if webkitdirectory attribute is also set) (#29) (Tuesday, 22 March)
• Re: [directory-upload] Changed drop event listener to use EventTarget (#28) (Tuesday, 15 March)
• Re: [directory-upload] Changed drop event listener to use EventTarget (#28) (Tuesday, 15 March)

Andrea Giammarchi

• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Thursday, 3 March)

Andrea Marchesini

• Re: [WICG/directory-upload] Consider to remove HTMLInputElement.getFilesAndDirectories andHTMLInputElement.getFiles (#33) (Tuesday, 29 March)
• [directory-upload] Consider to remove HTMLInputElement.getFilesAndDirectories andHTMLInputElement.getFiles (#33) (Thursday, 24 March)
• Re: [directory-upload] input.files shouldn't be null if directory attribute is used (or at least not if webkitdirectory attribute is also set) (#29) (Thursday, 24 March)
• Re: [directory-upload] input.files shouldn't be null if directory attribute is used (or at least not if webkitdirectory attribute is also set) (#29) (Thursday, 24 March)
• Re: [directory-upload] input.files shouldn't be null if directory attribute is used (or at least not if webkitdirectory attribute is also set) (#29) (Thursday, 24 March)
• [directory-upload] HTMLInputElement.directory should be a Directory attribute and not a boolean (#31) (Tuesday, 22 March)
• Re: [directory-upload] Should Directory be cloneable? (#27) (Tuesday, 22 March)

Andreas Selenwall

• [fetch] Support for CSRF? (#256) (Friday, 18 March)

Andres Rios

• Re: [webcomponents] Permit retrieval of registered classes from window.customElements (#445) (Thursday, 24 March)
• Re: [webcomponents] Fix typo (#453) (Tuesday, 22 March)
• [webcomponents] Fix typo (#453) (Tuesday, 22 March)
• Re: [webcomponents] Permit retrieval of registered classes from window.customElements (#445) (Monday, 21 March)
• Re: [webcomponents] Permit retrieval of registered classes from window.customElements (#445) (Monday, 21 March)
• Re: [webcomponents] Permit retrieval of registered classes from window.customElements (#445) (Monday, 21 March)
• Re: [webcomponents] Permit retrieval of registered classes from window.customElements (#445) (Monday, 21 March)
• Re: [webcomponents] Permit retrieval of registered classes from window.customElements (#445) (Monday, 21 March)
• [webcomponents] Fix typo in "2.1.1" for attributeChangedCallback (#448) (Friday, 18 March)
• Re: [webcomponents] Fix typo in '2.1.1 Creating a custom tag' (#446) (Thursday, 17 March)
• Re: [webcomponents] Fix typo in '2.1.1 Creating a custom tag' (#446) (Thursday, 17 March)
• [webcomponents] Fix typo in '2.1.1 Creating a custom tag' (#446) (Thursday, 17 March)
• Re: [webcomponents] Move defineElement elsewhere? (#431) (Wednesday, 16 March)

Andrew Betts

• Re: [w3ctag/spec-reviews] Payments Drafts Review (#109) (Wednesday, 30 March)
• Re: [w3ctag/spec-reviews] Payments Drafts Review (#109) (Wednesday, 30 March)
• Re: [w3ctag/spec-reviews] Payments Drafts Review (#109) (Tuesday, 29 March)
• Re: [spec-reviews] WebVR (#106) (Friday, 18 March)

Andrew Sutherland

• Re: [slightlyoff/ServiceWorker] Cache transactions & fixing `addAll` (#823) (Thursday, 31 March)

Andy Earnshaw

• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Wednesday, 30 March)
• Re: [webcomponents] Consider exposing Shadom DOM and Custom Elements only in secure contexts (#449) (Tuesday, 22 March)
• Re: [webcomponents] Consider exposing Shadom DOM and Custom Elements only in secure contexts (#449) (Monday, 21 March)
• Re: [webcomponents] Fix typo in '2.1.1 Creating a custom tag' (#446) (Thursday, 17 March)
• Re: [webcomponents] On-demand custom elements using modules (#444) (Thursday, 17 March)
• Re: [webcomponents] On-demand custom elements using modules (#444) (Thursday, 17 March)
• Re: [webcomponents] On-demand custom elements using modules (#444) (Wednesday, 16 March)
• [webcomponents] On-demand custom elements using modules (#444) (Wednesday, 16 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Wednesday, 16 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Thursday, 10 March)

Anne van Kesteren

• Re: [whatwg/dom] "origin alias" doesn't seem to exist in HTML anymore (#200) (Thursday, 31 March)
• Re: [whatwg/dom] "origin alias" doesn't seem to exist in HTML anymore (#200) (Thursday, 31 March)
• Re: [whatwg/fetch] URLs with username/password (#26) (Thursday, 31 March)
• Re: [whatwg/fetch] URLs with username/password (#26) (Thursday, 31 March)
• Re: [whatwg/dom] Spec for DOMTokenList stringifier disagrees with every single implementation (#105) (Thursday, 31 March)
• Re: [whatwg/url] Good defaults on URL() (#71) (Thursday, 31 March)
• Re: [whatwg/storage] Use PermissionState instead of PersistentStoragePermission (#10) (Thursday, 31 March)
• [whatwg/storage] Box hooks (#18) (Thursday, 31 March)
• Re: [whatwg/storage] Add API to allow origin to purge all storage (#4) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76) (Thursday, 31 March)
• Re: [whatwg/storage] Lack of example and Explainer document (#16) (Thursday, 31 March)
• Re: [whatwg/storage] Lack of example and Explainer document (#16) (Thursday, 31 March)
• Re: [whatwg/fetch] Provide more information in the spec on how withCredentials and Access-Control-Allow-Credentials interact (#264) (Thursday, 31 March)
• [whatwg/storage] Rename requestPersistent() to persist() (#17) (Thursday, 31 March)
• Re: [whatwg/fetch] Referrer policy: Should request's referrer policy be updated in the main fetch? (#266) (Thursday, 31 March)
• Re: [heycam/webidl] Add a [SecureContext] operator attribute (#65) (Thursday, 31 March)
• Re: [whatwg/storage] Allow script to request permission only if there would be no prompt (#9) (Thursday, 31 March)
• Re: [whatwg/encoding] Avoid teaching bad UTF-8 math. (#38) (Thursday, 31 March)
• Re: [whatwg/storage] `estimate()` and `persistentEstimate()` incompatible with whole-origin persistence (#15) (Thursday, 31 March)
• Re: [whatwg/fetch] Referrer policy: Should request's referrer policy be updated in the main fetch? (#266) (Thursday, 31 March)
• Re: [whatwg/storage] Allow script to request permission only if there would be no prompt (#9) (Thursday, 31 March)
• Re: [whatwg/encoding] Avoid teaching bad UTF-8 math. (#38) (Thursday, 31 March)
• Re: [whatwg/fetch] Referrer policy: Should request's referrer policy be updated in the main fetch? (#266) (Thursday, 31 March)
• Re: [whatwg/fullscreen] Document state change should be synced with dimensions change (#37) (Thursday, 31 March)
• Re: [whatwg/storage] Use PermissionState instead of PersistentStoragePermission (#10) (Thursday, 31 March)
• Re: [whatwg/storage] Add API to allow origin to purge all storage (#4) (Thursday, 31 March)
• Re: [whatwg/storage] Permissions API reflection for Persistent Permission (#14) (Thursday, 31 March)
• Re: [whatwg/storage] Use PermissionState instead of PersistentStoragePermission (#10) (Thursday, 31 March)
• Re: [w3c/webcomponents] Rename getAssignedNodes()? (#451) (Thursday, 31 March)
• Re: [w3c/webcomponents] Rename getAssignedNodes()? (#451) (Thursday, 31 March)
• Re: [whatwg/storage] Add API to allow origin to purge all storage (#4) (Thursday, 31 March)
• Re: [whatwg/storage] Add API to allow origin to purge all storage (#4) (Thursday, 31 March)
• Re: [whatwg/fetch] Referrer policy: Should request's referrer policy be updated in the main fetch? (#266) (Thursday, 31 March)
• Re: [whatwg/storage] Logo is not in a circle (#13) (Thursday, 31 March)
• Re: [whatwg/storage] Logo is not in a circle (#13) (Thursday, 31 March)
• Re: [whatwg/storage] Prevent usage in combination with document.domain (#12) (Thursday, 31 March)
• Re: [whatwg/storage] Classify cookies as site storage (#8) (Thursday, 31 March)
• Re: [whatwg/storage] Add API to allow origin to purge all storage (#4) (Thursday, 31 March)
• Re: [whatwg/fullscreen] Document state change should be synced with dimensions change (#37) (Thursday, 31 March)
• Re: [w3c/webcomponents] node.isConnected (#81) (Thursday, 31 March)
• Re: [whatwg/fullscreen] Document state change should be synced with dimensions change (#37) (Thursday, 31 March)
• Re: [whatwg/fetch] Referrer policy: Should request's referrer policy be updated in the main fetch? (#266) (Thursday, 31 March)
• Re: [whatwg/fetch] Integrate Client-Hints with Fetch (#258) (Thursday, 31 March)
• Re: [whatwg/fetch] Integrate Client-Hints with Fetch (#258) (Thursday, 31 March)
• Re: [whatwg/fetch] Integrate Client-Hints with Fetch (#258) (Thursday, 31 March)
• Re: [whatwg/fetch] Integrate Client-Hints with Fetch (#258) (Thursday, 31 March)
• Re: [whatwg/fetch] Integrate Client-Hints with Fetch (#258) (Thursday, 31 March)
• Re: [whatwg/fetch] Integrate Client-Hints with Fetch (#258) (Thursday, 31 March)
• Re: [w3c/webcomponents] node.isConnected (#81) (Thursday, 31 March)
• Re: [w3c/webcomponents] node.isConnected (#81) (Thursday, 31 March)
• Re: [whatwg/fullscreen] Document state change should be synced with dimensions change (#37) (Thursday, 31 March)
• Re: [whatwg/fetch] Change how CORS filtered response filters the headers. (#265) (Thursday, 31 March)
• Re: [whatwg/fetch] Change how CORS filtered response filters the headers. (#265) (Thursday, 31 March)
• Re: [whatwg/url] Give optional argument to constructor a sane default (#108) (Thursday, 31 March)
• Re: [whatwg/url] Give optional argument to constructor a sane default (#108) (Thursday, 31 March)
• Re: [whatwg/url] Give optional argument to constructor a sane default (#108) (Thursday, 31 March)
• Re: [w3c/webcomponents] node.isConnected (#81) (Thursday, 31 March)
• Re: [w3c/FileAPI] Update Typed Array spec URL (#34) (Wednesday, 30 March)
• Re: [w3c/webcomponents] Define order for attributeChangedCallback invocation? (#474) (Wednesday, 30 March)
• Re: [w3c/webcomponents] Element interfaces (#472) (Wednesday, 30 March)
• Re: [w3c/webcomponents] Editorial: inconsistent use of authors/developers (#470) (Wednesday, 30 March)
• Re: [w3c/webcomponents] Define order for attributeChangedCallback invocation? (#474) (Wednesday, 30 March)
• Re: [whatwg/fetch] Referrer policy: Should request's referrer policy be updated in the main fetch? (#266) (Wednesday, 30 March)
• Re: [whatwg/storage] `estimate()` and `persistentEstimate()` incompatible with whole-origin persistence (#15) (Wednesday, 30 March)
• Re: [whatwg/storage] `estimate()` and `persistentEstimate()` incompatible with whole-origin persistence (#15) (Wednesday, 30 March)
• Re: [whatwg/storage] Lack of example and Explainer document (#16) (Wednesday, 30 March)
• Re: [w3ctag/spec-reviews] Storage persistence (#85) (Wednesday, 30 March)
• Re: [whatwg/storage] `estimate()` and `persistentEstimate()` incompatible with whole-origin persistence (#15) (Wednesday, 30 March)
• Re: [w3c/webcomponents] Define order for attributeChangedCallback invocation? (#474) (Wednesday, 30 March)
• Re: [w3c/webcomponents] Need "slotchange" event (#288) (Wednesday, 30 March)
• [w3c/webcomponents] Editorial: "Remove the first element of actions, letting action be the result" (#476) (Wednesday, 30 March)
• Re: [w3c/webcomponents] Need "slotchange" event (#288) (Wednesday, 30 March)
• Re: [w3c/webcomponents] define() could use [[GetPrototypeOf]]? (#473) (Wednesday, 30 March)
• Re: [w3c/webcomponents] define() could use [[GetPrototypeOf]]? (#473) (Wednesday, 30 March)
• [w3c/webcomponents] Editorial: "When it becomes" (#475) (Wednesday, 30 March)
• [w3c/webcomponents] Define order for attributeChangedCallback invocation? (#474) (Wednesday, 30 March)
• [w3c/webcomponents] define() could use [[GetPrototypeOf]]? (#473) (Wednesday, 30 March)
• [w3c/webcomponents] Element interfaces (#472) (Wednesday, 30 March)
• [w3c/webcomponents] define()'s context object is not a document (#471) (Wednesday, 30 March)
• [w3c/webcomponents] Editorial: inconsistent use of authors/developers (#470) (Wednesday, 30 March)
• Re: [whatwg/encoding] org (#37) (Wednesday, 30 March)
• Re: [w3c/webcomponents] Need "slotchange" event (#288) (Wednesday, 30 March)
• Re: [whatwg/fetch] Change how CORS filtered response filters the headers. (#265) (Wednesday, 30 March)
• Re: [whatwg/fetch] Change how CORS filtered response filters the headers. (#265) (Wednesday, 30 March)
• Re: [w3c/webcomponents] Create an element type extension path with sync flag set should not enqueue upgrade; it should just upgrade (#469) (Wednesday, 30 March)
• Re: [w3c/webcomponents] createElement and createElementNS() should check is attribute (#466) (Wednesday, 30 March)
• Re: [w3c/webcomponents] Editorial: create an element's "new element" step (#463) (Tuesday, 29 March)
• Re: [w3c/webcomponents] create an element does not always return result (#467) (Tuesday, 29 March)
• [w3c/webcomponents] create an element does not always return result (#467) (Tuesday, 29 March)
• Re: [whatwg/dom] Comment out query/queryAll/Elements for now (10b6cf1) (Tuesday, 29 March)
• Re: [whatwg/dom] Comment out query/queryAll/Elements for now (10b6cf1) (Tuesday, 29 March)
• Re: [w3c/webcomponents] Custom element callback naming (#460) (Tuesday, 29 March)
• Re: [w3c/webcomponents] Custom element callback naming (#460) (Tuesday, 29 March)
• Re: [whatwg/dom] Back to previous definition for Element.getAttributeNS() (#197) (Tuesday, 29 March)
• Re: [whatwg/dom] Back to previous definition for Element.getAttributeNS() (#197) (Tuesday, 29 March)
• Re: [whatwg/dom] Back to previous definition for Element.getAttributeNS() (#197) (Tuesday, 29 March)
• Re: [w3c/webcomponents] createElement and createElementNS() should check is attribute (#466) (Tuesday, 29 March)
• [w3c/webcomponents] createElement and createElementNS() should check is attribute (#466) (Tuesday, 29 March)
• Re: [w3c/webcomponents] Mutation: insert (#465) (Tuesday, 29 March)
• Re: [w3c/webcomponents] Need "slotchange" event (#288) (Tuesday, 29 March)
• [w3c/webcomponents] Mutation: insert (#465) (Tuesday, 29 March)
• [w3c/webcomponents] Cloning (#464) (Tuesday, 29 March)
• [w3c/webcomponents] Editorial: create an element's "new element" step (#463) (Tuesday, 29 March)
• [w3c/webcomponents] create an element has no context object (#462) (Tuesday, 29 March)
• Re: [w3c/webcomponents] Need "slotchange" event (#288) (Tuesday, 29 March)
• [w3c/webcomponents] Note about "custom" is misleading (#461) (Tuesday, 29 March)
• Re: [w3c/webcomponents] defineElement should not cache lifecycle callbacks and prototype of a custom element class (#417) (Tuesday, 29 March)
• [w3c/webcomponents] Custom element callback naming (#460) (Tuesday, 29 March)
• [w3c/webcomponents] Editorial: create an element step 3.4 (#459) (Tuesday, 29 March)
• Re: [whatwg/fetch] Change how CORS filtered response filters the headers. (#265) (Tuesday, 29 March)
• Re: [whatwg/fetch] Change how CORS filtered response filters the headers. (#265) (Tuesday, 29 March)
• Re: [whatwg/fetch] Change how CORS filtered response filters the headers. (#265) (Tuesday, 29 March)
• Re: [whatwg/fetch] Change how CORS filtered response filters the headers. (#265) (Tuesday, 29 March)
• Re: [whatwg/fetch] Change how CORS filtered response filters the headers. (#265) (Tuesday, 29 March)
• Re: [whatwg/fetch] Change how CORS filtered response filters the headers. (#265) (Tuesday, 29 March)
• Re: [w3c/webcomponents] Need "slotchange" event (#288) (Tuesday, 29 March)
• Re: [w3c/webcomponents] Need "slotchange" event (#288) (Tuesday, 29 March)
• Re: [w3c/permissions] Define a PermissionStorage type for each permission to store data with. (#73) (Tuesday, 29 March)
• Re: [w3c/webcomponents] Need "slotchange" event (#288) (Tuesday, 29 March)
• Re: [webcomponents] deepPath's definition is ambiguous when the event path contains a non-Node EventTarget (#432) (Monday, 28 March)
• Re: [streams] Investigate merging RS and RBS (#379) (Monday, 28 March)
• Re: [webcomponents] Need "slotchange" event (#288) (Monday, 28 March)
• Re: [webcomponents] Parse <slot> like <template> (#59) (Monday, 28 March)
• Re: [webcomponents] deepPath's definition is ambiguous when the event path contains a non-Node EventTarget (#432) (Monday, 28 March)
• Re: [webcomponents] Exposing a CanvasImageSource hidden by a Shadow Tree (#388) (Monday, 28 March)
• Re: [webcomponents] Exposing a CanvasImageSource hidden by a Shadow Tree (#388) (Monday, 28 March)
• Re: [webcomponents] deepPath's definition is ambiguous when the event path contains a non-Node EventTarget (#432) (Monday, 28 March)
• Re: [webcomponents] defineElement should not cache lifecycle callbacks and prototype of a custom element class (#417) (Monday, 28 March)
• Re: [fetch] Allow * for Access-Control-Allow-Headers and Access-Control-Allow-Methods (#251) (Monday, 28 March)
• Re: [webcomponents] deepPath's definition is ambiguous when the event path contains a non-Node EventTarget (#432) (Monday, 28 March)
• Re: [webcomponents] Use a parent/child relationship in the flat tree in the definition of some elements, i.e. <tr>/<td> (#404) (Monday, 28 March)
• Re: [webcomponents] Type extensions in SVG use shadow trees--specify, or add a note if no specification is necessary (#335) (Monday, 28 March)
• Re: [webcomponents] Type extensions in SVG use shadow trees--specify, or add a note if no specification is necessary (#335) (Monday, 28 March)
• Re: [webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354) (Monday, 28 March)
• Re: [webcomponents] Shadow dom: use css containment features by default (#355) (Monday, 28 March)
• Re: [webcomponents] Styling of elements where attachShadow(...) not allowed (#376) (Monday, 28 March)
• Re: [webcomponents] When is the slotting algorithm run (#401) (Monday, 28 March)
• Re: [webcomponents] When is the slotting algorithm run (#401) (Monday, 28 March)
• Re: [webcomponents] Use a parent/child relationship in the flat tree in the definition of some elements, i.e. <tr>/<td> (#404) (Monday, 28 March)
• Re: [webcomponents] deepPath's definition is ambiguous when the event path contains a non-Node EventTarget (#432) (Monday, 28 March)
• Re: [webcomponents] Consider exposing Shadom DOM and Custom Elements only in secure contexts (#449) (Monday, 28 March)
• Re: [webcomponents] Rename getAssignedNodes()? (#451) (Monday, 28 March)
• Re: [webcomponents] What was the "element is being created" flag for? (#458) (Saturday, 26 March)
• Re: [webcomponents] What DOM content category do custom elements belong to? (#454) (Saturday, 26 March)
• Re: [webcomponents] What was the "element is being created" flag for? (#458) (Saturday, 26 March)
• Re: [webidl] Should we match the ES spelling of "unscopable" (#103) (Saturday, 26 March)
• Re: [fetch] Use `,` rather than `, ` for combine operation (#207) (Friday, 25 March)
• Re: [xhr] Only set state to unsent when true (#58) (Friday, 25 March)
• Re: [xhr] abort() handling of state is busted (#54) (Friday, 25 March)
• Re: [fullscreen] Fullscreen on non-HTML elements? (#22) (Friday, 25 March)
• [fullscreen] Integration with HTML's event loop (#35) (Friday, 25 March)
• Re: [fetch] Stop hardcoding the list of schemes that inherit HTTPS state (#255) (Friday, 25 March)
• Re: [fetch] Use `,` rather than ` ,` for combine operation (#207) (Friday, 25 March)
• Re: [fetch] The reason why Access-Control-Request-Headers includes simple headers (#249) (Friday, 25 March)
• Re: [fetch] The reason why Access-Control-Request-Headers includes simple headers (#249) (Friday, 25 March)
• Re: [fetch] Allow * for Access-Control-Expose-Headers (#252) (Friday, 25 March)
• Re: [fetch] Add new Access-Control-Suppress-Headers CORS response header (#253) (Friday, 25 March)
• Re: [fetch] Add new Access-Control-Suppress-Headers CORS response header (#253) (Friday, 25 March)
• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Friday, 25 March)
• Re: [fetch] Update Access-Control-Expose-Headers CORS response header to allow * (allow-all) (#252) (Friday, 25 March)
• Re: [fetch] Redirect on preflighted CORS requests generally impossible (#204) (Friday, 25 March)
• Re: [fetch] Support for CSRF? (#256) (Friday, 25 March)
• Re: [fetch] Support for CSRF? (#256) (Friday, 25 March)
• Re: [fetch] Support full-duplex HTTP streaming (#229) (Friday, 25 March)
• Re: [fetch] Support full-duplex HTTP streaming (#229) (Friday, 25 March)
• Re: [fetch] Tight coupling between JS engine and browser engine (#263) (Friday, 25 March)
• Re: [webcomponents] Define the timing when distribution happens (#73) (Friday, 25 March)
• Re: [fetch] Provide more information in the spec on how withCredentials and Access-Control-Allow-Credentials interact (#264) (Friday, 25 March)
• Re: [fetch] RFC: a mechanism to bypass CORS preflight (#210) (Friday, 25 March)
• Re: [webcomponents] When does the base element queue matter? (#457) (Friday, 25 March)
• Re: [webcomponents] When does the base element queue matter? (#457) (Friday, 25 March)
• Re: [webcomponents] Define the timing when distribution happens (#73) (Friday, 25 March)
• Re: [webcomponents] When does the base element queue matter? (#457) (Friday, 25 March)
• Re: [webcomponents] When does the base element queue matter? (#457) (Friday, 25 March)
• Re: [webcomponents] Rename custom tag (#434) (Friday, 25 March)
• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Thursday, 24 March)
• Re: [webcomponents] What DOM content category do custom elements belong to? (#454) (Thursday, 24 March)
• Re: [fetch] Block 'image/*' resources loaded as script. (#261) (Thursday, 24 March)
• Re: [webcomponents] What DOM content category do custom elements belong to? (#454) (Thursday, 24 March)
• Re: [fetch] Block 'image/*' resources loaded as script. (#261) (Thursday, 24 March)
• Re: [fetch] Block 'image/*' resources loaded as script. (#261) (Thursday, 24 March)
• Re: [url] input can be empty string if url is not special (#106) (Thursday, 24 March)
• Re: [url] input can be empty string if url is not special (#106) (Thursday, 24 March)
• Re: [fetch] Block 'image/*' resources loaded as script. (#261) (Thursday, 24 March)
• Re: [fetch] Block 'image/*' resources loaded as script. (#261) (Thursday, 24 March)
• Re: [fetch] Block 'image/*' resources loaded as script. (#261) (Thursday, 24 March)
• Re: [fetch] Block 'image/*' resources loaded as script. (#261) (Thursday, 24 March)
• Re: [webcomponents] [Custom]: Add the possibility to extend the custom element (bugzilla: 26583) (#201) (Thursday, 24 March)
• Re: [webcomponents] [Custom]: Add the possibility to extend the custom element (bugzilla: 26583) (#201) (Thursday, 24 March)
• Re: [webcomponents] Define the timing when distribution happens (#73) (Thursday, 24 March)
• Re: [webcomponents] What DOM content category do custom elements belong to? (#454) (Thursday, 24 March)
• Re: [ServiceWorker] Access to fragment identifiers (#854) (Thursday, 24 March)
• Re: [url] Rename non-relative to cannot-be-a-base-URL. (#105) (Thursday, 24 March)
• Re: [url] Rename non-relative to cannot-be-a-base-URL. (#105) (Thursday, 24 March)
• Re: [url] Rename non-relative-flag (#89) (Thursday, 24 March)
• Re: [fetch] Tight coupling between JS engine and browser engine (#263) (Thursday, 24 March)
• Re: [webcomponents] Rename getAssignedNodes()? (#451) (Thursday, 24 March)
• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Wednesday, 23 March)
• Re: [url] Rename non-relative-flag (#89) (Wednesday, 23 March)
• Re: [url] Rename non-relative-flag (#89) (Wednesday, 23 March)
• Re: [url] Rename non-relative-flag (#89) (Wednesday, 23 March)
• Re: [fetch] Should fetch(evt.request) send original RequestDestination and RequestType? (#262) (Wednesday, 23 March)
• Re: [fetch] Should fetch(evt.request) send original RequestDestination and RequestType? (#262) (Wednesday, 23 March)
• Re: [fetch] URLs with username/password (#26) (Wednesday, 23 March)
• Re: [webcomponents] Parse <slot> like <template> (#59) (Wednesday, 23 March)
• Re: [webcomponents] Extend the slotting algorithm so that a slot can select an element which doesn't have slot attribute. (#343) (Wednesday, 23 March)
• Re: [webcomponents] Extend the slotting algorithm so that a slot can select an element which doesn't have slot attribute. (#343) (Wednesday, 23 March)
• Re: [fetch] Encourage console warning for method normalization (#259) (Wednesday, 23 March)
• Re: [fetch] Add new Access-Control-Suppress-Headers CORS response header (#253) (Wednesday, 23 March)
• Re: [fetch] Treat Last-Event-ID and Client-Hints headers as simple headers (#258) (Wednesday, 23 March)
• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Wednesday, 23 March)
• Re: [webcomponents] Extend the slotting algorithm so that a slot can select an element which doesn't have slot attribute. (#343) (Wednesday, 23 March)
• Re: [webcomponents] Rename getAssignedNodes()? (#451) (Wednesday, 23 March)
• Re: [dom] Fix #193: Shadow: Fix shadow-including root (#194) (Wednesday, 23 March)
• Re: [dom] Fix #193: Shadow: Fix shadow-including root (#194) (Wednesday, 23 March)
• Re: [dom] "shadow-including root" should be a recursive definition. (#193) (Wednesday, 23 March)
• Re: [fetch] Add examples for PATCH and PatcH (or some such) (#260) (Wednesday, 23 March)
• Re: [fetch] PATCH verb (#50) (Wednesday, 23 March)
• [fetch] Add examples for PATCH and PatcH (or some such) (#260) (Wednesday, 23 March)
• [fetch] Encourage console warning for method normalization (#259) (Wednesday, 23 March)
• Re: [webcomponents] Extend the slotting algorithm so that a slot can select an element which doesn't have slot attribute. (#343) (Wednesday, 23 March)
• Re: [webcomponents] Shadow DOM and requestPointerLock() (#192) (Wednesday, 23 March)
• Re: [fetch] Treat Last-Event-ID and Client-Hints headers as simple headers (#258) (Tuesday, 22 March)
• Re: [fetch] Treat Last-Event-ID and Client-Hints headers as simple headers (#258) (Tuesday, 22 March)
• Re: [webcomponents] Fix typo (#453) (Tuesday, 22 March)
• [webcomponents] <slot> rendering (#452) (Tuesday, 22 March)
• Re: [webcomponents] Parse <slot> like <template> (#59) (Tuesday, 22 March)
• Re: [webcomponents] Extend the slotting algorithm so that a slot can select an element which doesn't have slot attribute. (#343) (Tuesday, 22 March)
• Re: [webcomponents] 'in a Document' for shadow trees (#57) (Tuesday, 22 March)
• Re: [webcomponents] [Shadow]: Method for selecting data inside closed shadow root (#378) (Tuesday, 22 March)
• [webcomponents] Rename getAssignedNodes()? (#451) (Tuesday, 22 March)
• Re: [fetch] Setting strategy to control ReadableStream's internal buffer (#257) (Tuesday, 22 March)
• Re: [url] URL.pathname getter for file URLs produces odd result on Windows (#103) (Tuesday, 22 March)
• Re: [xhr] Replace byte stream with ReadableStream (#61) (Tuesday, 22 March)
• Re: [xhr] Replace byte stream with ReadableStream (#61) (Tuesday, 22 March)
• Re: [xhr] Replace byte stream with ReadableStream (#61) (Tuesday, 22 March)
• Re: [webcomponents] node.isConnected (#81) (Tuesday, 22 March)
• Re: [fetch] URLs with username/password (#26) (Tuesday, 22 March)
• Re: [dom] "ProcessingInstruction" (#192) (Tuesday, 22 March)
• Re: [fetch] ReadableStream constructor call is not quite right (#250) (Tuesday, 22 March)
• Re: [webcomponents] Upstream Shadow DOM spec to DOM/HTML Standard (#377) (Tuesday, 22 March)
• Re: [webcomponents] node.connectedToDocument (#81) (Monday, 21 March)
• Re: [webcomponents] Consider exposing Shadom DOM and Custom Elements only in secure contexts (#449) (Monday, 21 March)
• Re: [webidl] Please rename things that are legacy so it's clear they are (#100) (Monday, 21 March)
• Re: [webcomponents] Upstream Shadow DOM spec to DOM/HTML Standard (#377) (Monday, 21 March)
• Re: [webcomponents] Figure out terminology for Shadow DOM that everyone agrees on (#382) (Monday, 21 March)
• Re: [webcomponents] When is the slotting algorithm run (#401) (Monday, 21 March)
• Re: [webcomponents] Expose ShadowRoot object's encapsulation mode (#275) (Monday, 21 March)
• Re: [webcomponents] Expose ShadowRoot object's encapsulation mode (#275) (Monday, 21 March)
• Re: [dom] Specify for='' on the couple of bare <a>root</a> autolinks. (#191) (Monday, 21 March)
• Re: [dom] Specify for='' on the couple of bare <a>root</a> autolinks. (#191) (Monday, 21 March)
• Re: [webcomponents] node.connectedToDocument (#81) (Monday, 21 March)
• Re: [webcomponents] Permit retrieval of registered classes from window.customElements (#445) (Monday, 21 March)
• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Monday, 21 March)
• [webidl] Please rename things that are legacy so it's clear they are (#100) (Monday, 21 March)
• Re: [dom] Specify for='' on the couple of bare <a>root</a> autolinks. (#191) (Sunday, 20 March)
• Re: [dom] Specify for='' on the couple of bare <a>root</a> autolinks. (#191) (Sunday, 20 March)
• Re: [dom] Specify for='' on the couple of bare <a>root</a> autolinks. (#191) (Sunday, 20 March)
• Re: [FileAPI] Update Typed Array spec URL (#34) (Sunday, 20 March)
• Re: [fetch] Add new Access-Control-Suppress-Headers CORS response header (#253) (Sunday, 20 March)
• Re: [webcomponents] Expose ShadowRoot object's encapsulation mode (#275) (Saturday, 19 March)
• Re: [fetch] Support for CSRF? (#256) (Saturday, 19 March)
• Re: [fetch] Stop hardcoding the list of schemes that inherit HTTPS state (#255) (Friday, 18 March)
• Re: [fetch] Stop hardcoding the list of schemes that inherit HTTPS state (#255) (Friday, 18 March)
• Re: [fetch] Stop hardcoding the list of schemes that inherit HTTPS state (#255) (Friday, 18 March)
• Re: [fetch] Stop hardcoding the list of schemes that inherit HTTPS state (#255) (Friday, 18 March)
• Re: [fetch] Stop hardcoding the list of schemes that inherit HTTPS state (#255) (Friday, 18 March)
• Re: [webcomponents] Expose ShadowRoot object's encapsulation mode (#275) (Friday, 18 March)
• Re: [webcomponents] Expose ShadowRoot object's encapsulation mode (#275) (Friday, 18 March)
• Re: [webcomponents] node.connectedToDocument (#81) (Friday, 18 March)
• Re: [webcomponents] [Shadow] How should various document internal references work when SVG is being used in shadow DOM (bugzilla: 27380) (#179) (Friday, 18 March)
• Re: [encoding] Fix #18: remove UTF-16 support from TextEncoder (#36) (Friday, 18 March)
• Re: [encoding] Consider removing TextEncoder support for UTF-16 (#18) (Friday, 18 March)
• Re: [ServiceWorker] FetchEvent.respondWith does something weird with the body of a response (#850) (Friday, 18 March)
• Re: [xhr] Replace byte stream with ReadableStream (#61) (Friday, 18 March)
• Re: [xhr] Replace byte stream with ReadableStream (#61) (Friday, 18 March)
• Re: [xhr] Replace byte stream with ReadableStream (#61) (Friday, 18 March)
• Re: [xhr] Replace byte stream with ReadableStream (#61) (Friday, 18 March)
• Re: [xhr] Replace byte stream with ReadableStream (#61) (Friday, 18 March)
• Re: [xhr] Replace byte stream with ReadableStream (#61) (Friday, 18 March)
• Re: [xhr] Replace byte stream with ReadableStream (#61) (Friday, 18 March)
• Re: [fetch] Update Access-Control-Expose-Headers CORS response header to allow * (allow-all) (#252) (Friday, 18 March)
• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Friday, 18 March)
• Re: [xhr] Unclear algorithm used in step 4 of text response (#62) (Friday, 18 March)
• Re: [fetch] Add new Access-Control-Suppress-Headers CORS response header (#253) (Friday, 18 March)
• Re: [fetch] Update Access-Control-Expose-Headers CORS response header to allow * (allow-all) (#252) (Friday, 18 March)
• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Friday, 18 March)
• Re: [webcomponents] [Shadow] How should various document internal references work when SVG is being used in shadow DOM (bugzilla: 27380) (#179) (Friday, 18 March)
• Re: [ServiceWorker] FetchEvent.respondWith does something weird with the body of a response (#850) (Thursday, 17 March)
• Re: [ServiceWorker] FetchEvent.respondWith does something weird with the body of a response (#850) (Thursday, 17 March)
• Re: [webcomponents] Upstream Shadow DOM spec to DOM/HTML Standard (#377) (Thursday, 17 March)
• Re: [webcomponents] Upstream Shadow DOM spec to DOM/HTML Standard (#377) (Thursday, 17 March)
• Re: [webcomponents] Shadow DOM and "insertion steps" / "removing steps" (#438) (Thursday, 17 March)
• Re: [webcomponents] Shadow DOM and "insertion steps" / "removing steps" (#438) (Thursday, 17 March)
• Re: [webcomponents] Shadow DOM and "insertion steps" / "removing steps" (#438) (Thursday, 17 March)
• Re: [webcomponents] Define how shadow DOM should be handled when host is adopted to a new document (#182) (Thursday, 17 March)
• Re: [webcomponents] Shadow DOM and "insertion steps" / "removing steps" (#438) (Thursday, 17 March)
• Re: [ServiceWorker] FetchEvent.respondWith does something weird with the body of a response (#850) (Thursday, 17 March)
• Re: [ServiceWorker] Define some way for foreign fetch to decide on opaqueness of responses (#841) (Thursday, 17 March)
• Re: [webcomponents] Define how shadow DOM should be handled when host is adopted to a new document (bugzilla: 27366) (#182) (Thursday, 17 March)
• Re: [webcomponents] scoped and relatedTargetScoped attributes are useless in Event, so remove then from Event interface (#442) (Thursday, 17 March)
• Re: [xhr] Fix Fetch integration (#57) (Thursday, 17 March)
• Re: [webcomponents] [Shadow] How should various document internal references work when SVG is being used in shadow DOM (bugzilla: 27380) (#179) (Thursday, 17 March)
• Re: [webcomponents] deepRelatedTargets and touch.deepTargets (#76) (Thursday, 17 March)
• Re: [webcomponents] Shadow DOM and requestPointerLock() (#192) (Thursday, 17 March)
• Re: [webcomponents] Permit retrieval of registered classes from window.customElements (#445) (Thursday, 17 March)
• Re: [xhr] Fix Fetch integration (#57) (Thursday, 17 March)
• Re: [xhr] Rephrase "Synchronous XMLHttpRequest" warning (#59) (Thursday, 17 March)
• Re: [xhr] Rephrase "Synchronous XMLHttpRequest" warning (#59) (Thursday, 17 March)
• Re: [xhr] Synchronous XMLHttpRequest outside of workers deprecation is not a good idea. (#60) (Thursday, 17 March)
• Re: [xhr] Synchronous XMLHttpRequest outside of workers deprecation is not a good idea. (#60) (Thursday, 17 March)
• Re: [fetch] The reason why Access-Control-Request-Headers includes simple headers (#249) (Wednesday, 16 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Wednesday, 16 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Wednesday, 16 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Wednesday, 16 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Wednesday, 16 March)
• Re: [webcomponents] [Shadow] investigate if there should be deepRelatedTargets and touch.deepTargets (bugzilla: 28560) (#76) (Wednesday, 16 March)
• Re: [webcomponents] [Shadow] investigate if there should be deepRelatedTargets and touch.deepTargets (bugzilla: 28560) (#76) (Wednesday, 16 March)
• Re: [fetch] The reason why Access-Control-Request-Headers includes simple headers (#249) (Wednesday, 16 March)
• Re: [ServiceWorker] DOMParser within ServiceWorkers (#846) (Wednesday, 16 March)
• Re: [webcomponents] scoped and relatedTargetScoped attributes are useless in Event, so remove then from Event interface (#442) (Wednesday, 16 March)
• Re: [encoding] Fix #18: remove UTF-16 support from TextEncoder (#36) (Wednesday, 16 March)
• Re: [webcomponents] Shadow DOM and "insertion steps" / "removing steps" (#438) (Wednesday, 16 March)
• Re: [dom] "callback (an EventListener" (#189) (Wednesday, 16 March)
• [webcomponents] ShadowRoot innerHTML different from Element innerHTML (#443) (Wednesday, 16 March)
• Re: [webcomponents] Move innerHTML from ShadowRoot to DocumentFragment? (#441) (Wednesday, 16 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Wednesday, 16 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Wednesday, 16 March)
• Re: [webcomponents] scoped and relatedTargetScoped attributes are useless in Event, so remove then from Event interface (#442) (Wednesday, 16 March)
• Re: [ServiceWorker] DOMParser within ServiceWorkers (#846) (Wednesday, 16 March)
• Re: [fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) (Tuesday, 15 March)
• Re: [encoding] Fix #18: remove UTF-16 support from TextEncoder (#36) (Tuesday, 15 March)
• Re: [encoding] Consider removing TextEncoder support for UTF-16 (#18) (Tuesday, 15 March)
• [encoding] Fix #18: remove UTF-16 support from TextEncoder (#36) (Tuesday, 15 March)
• Re: [fetch] referrer same-origin constraint is a footgun for people trying to "copy" a Request (#245) (Tuesday, 15 March)
• Re: [fetch] referrer same-origin constraint is a footgun for people trying to "copy" a Request (#245) (Tuesday, 15 March)
• Re: [fetch] referrer same-origin constraint is a footgun for people trying to "copy" a Request (#245) (Tuesday, 15 March)
• [dom] List subclasses explicitly or not (#190) (Tuesday, 15 March)
• Re: [fetch] referrer same-origin constraint is a footgun for people trying to "copy" a Request (#245) (Tuesday, 15 March)
• Re: [webcomponents] Move innerHTML from ShadowRoot to DocumentFragment? (#441) (Tuesday, 15 March)
• [webcomponents] Move innerHTML from ShadowRoot to DocumentFragment? (#441) (Tuesday, 15 March)
• Re: [webcomponents] Shared mixin for Document and ShadowRoot (#91) (Tuesday, 15 March)
• Re: [webcomponents] <iframe> and the History API (#184) (Tuesday, 15 March)
• Re: [dom] Shadow: add shadow root (b2ee400) (Tuesday, 15 March)
• Re: [webcomponents] Upstream Shadow DOM spec to DOM/HTML Standard (#377) (Tuesday, 15 March)
• [webcomponents] Open/closed is associated with ShadowRoot, not shadow tree (#440) (Tuesday, 15 March)
• [fetch] Standardize .onion DNS lookup blocking? (#248) (Tuesday, 15 March)
• Re: [webcomponents] Rename custom tag (#434) (Tuesday, 15 March)
• Re: [fetch] referrer same-origin constraint is a footgun for people trying to "copy" a Request (#245) (Tuesday, 15 March)
• Re: [webcomponents] Unclear on how to define :defined in CSS + HTML (#439) (Tuesday, 15 March)
• Re: [webcomponents] Unclear on how to define :defined in CSS + HTML (#439) (Tuesday, 15 March)
• Re: [webcomponents] Rename custom tag (#434) (Monday, 14 March)
• Re: [fetch] Support full-duplex HTTP streaming (#229) (Monday, 14 March)
• Re: [dom] Editorial: clone a range → clone the contents of a range (#188) (Monday, 14 March)
• Re: [dom] Editorial: clone a range → clone the contents of a range (#188) (Monday, 14 March)
• Re: [fetch] error types too vague for TLS certificate error (#205) (Monday, 14 March)
• Re: [fetch] referrer same-origin constraint is a footgun for people trying to "copy" a Request (#245) (Monday, 14 March)
• [DOM-Parsing] insertAdjacentHTML is broken (#4) (Monday, 14 March)
• Re: [dom] Why remove CDataSection? (#142) (Monday, 14 March)
• Re: [dom] Why remove CDataSection? (#142) (Monday, 14 March)
• Re: [dom] Export the term "target override" (#187) (Monday, 14 March)
• Re: [fetch] Support full-duplex HTTP streaming (#229) (Monday, 14 March)
• Re: [fetch] Support full-duplex HTTP streaming (#229) (Monday, 14 March)
• Re: [fetch] Content-Length on HEAD (#135) (Monday, 14 March)
• Re: [fetch] Content-Length on HEAD (#135) (Monday, 14 March)
• Re: [fetch] Replace "flags" with "booleans" (#175) (Monday, 14 March)
• Re: [fetch] Replace "flags" with "booleans" (#175) (Monday, 14 March)
• Re: [fetch] error types too vague for TLS certificate error (#205) (Monday, 14 March)
• Re: [fetch] error types too vague for TLS certificate error (#205) (Monday, 14 March)
• Re: [fetch] Clarify obtain a connection with respect to client certificates (#222) (Monday, 14 March)
• Re: [fetch] Support full-duplex HTTP streaming (#229) (Monday, 14 March)
• Re: [fetch] Improve HSTS language (#244) (Monday, 14 March)
• Re: [fetch] Specify cache mode and permessage-deflate for WebSocket (#247) (Monday, 14 March)
• Re: [fetch] Handling of empty bodies (#246) (Monday, 14 March)
• Re: [url] Simply return the port for a URL's origin, not its default port (#102) (Monday, 14 March)
• [url] Simply return the port for a URL's origin, not its default port (#102) (Monday, 14 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Monday, 14 March)
• Re: [webcomponents] Rename custom tag (#434) (Monday, 14 March)
• [fetch] Specify cache mode and permessage-deflate for WebSocket (#247) (Saturday, 12 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Saturday, 12 March)
• Re: [fetch] referrer same-origin constraint is a footgun for people trying to "copy" a Request (#245) (Saturday, 12 March)
• Re: [webcomponents] Rename custom tag (#434) (Saturday, 12 March)
• Re: [fetch] Handling of empty bodies (#246) (Saturday, 12 March)
• Re: [ServiceWorker] spec should be more explicit about accessing internal body on opaque Responses (#710) (Friday, 11 March)
• Re: [webcomponents] ARIA custom element API (#159) (Friday, 11 March)
• Re: [webcomponents] ARIA custom element API (#159) (Friday, 11 March)
• Re: [webcomponents] ARIA custom element API (#159) (Friday, 11 March)
• Re: [webcomponents] ARIA custom element API (#159) (Friday, 11 March)
• Re: [webcomponents] [Accessibility]: Custom element should allow declaration of default accessibility features, such as role and other ARIA attributes. (bugzilla: 20466) (#159) (Friday, 11 March)
• Re: [webcomponents] [Accessibility]: Custom element should allow declaration of default accessibility features, such as role and other ARIA attributes. (bugzilla: 20466) (#159) (Friday, 11 March)
• Re: [webcomponents] [Accessibility]: Custom element should allow declaration of default accessibility features, such as role and other ARIA attributes. (bugzilla: 20466) (#159) (Friday, 11 March)
• Re: [webcomponents] [Accessibility]: Custom element should allow declaration of default accessibility features, such as role and other ARIA attributes. (bugzilla: 20466) (#159) (Friday, 11 March)
• [webcomponents] Shadow DOM and "insertion steps" / "removing steps" (#438) (Friday, 11 March)
• [webcomponents] Group registry related terminology under a heading (#437) (Friday, 11 March)
• [webcomponents] Mention that no new elements with a hyphen will be added to SVG and MathML either (#436) (Friday, 11 March)
• [webcomponents] Define the syntax of the PotentialCustomElementName (#435) (Friday, 11 March)
• [webcomponents] Rename custom tag (#434) (Friday, 11 March)
• Re: [webcomponents] ES5 consideration for custom elements (#423) (Friday, 11 March)
• Re: [webcomponents] Support renaming, aliasing, or namespacing imported elements (#344) (Friday, 11 March)
• Re: [webcomponents] Support renaming, aliasing, or namespacing imported elements (#344) (Friday, 11 March)
• Re: [webcomponents] [Custom Elements] Import module (#329) (Friday, 11 March)
• Re: [webcomponents] [Custom Elements] Import module (#329) (Friday, 11 March)
• Re: [webcomponents] Proposal: Add namespace property to ElementRegistrationOptions parameter of Document.registerElement (#328) (Friday, 11 March)
• Re: [webcomponents] Proposal: Add namespace property to ElementRegistrationOptions parameter of Document.registerElement (#328) (Friday, 11 March)
• Re: [webcomponents] [Custom]: Consider turning processing stack + queues into its own primitive (bugzilla: 24655) (#226) (Friday, 11 March)
• Re: [webcomponents] [Custom]: Consider turning processing stack + queues into its own primitive (bugzilla: 24655) (#226) (Friday, 11 March)
• Re: [webcomponents] [Custom]: Add the possibility to extend the custom element (bugzilla: 26583) (#201) (Friday, 11 March)
• Re: [webcomponents] [Accessibility]: Custom element should allow declaration of default accessibility features, such as role and other ARIA attributes. (bugzilla: 20466) (#159) (Friday, 11 March)
• Re: [webcomponents] registerElement() should be scoped to modules (bugzilla: 27835) (#156) (Friday, 11 March)
• Re: [webcomponents] registerElement() should be scoped to modules (bugzilla: 27835) (#156) (Friday, 11 March)
• Re: [webcomponents] [Custom]: define registry primitive; ("namespace" support needed?) (bugzilla: 24578) (#154) (Friday, 11 March)
• Re: [webcomponents] [Custom]: define registry primitive; ("namespace" support needed?) (bugzilla: 24578) (#154) (Friday, 11 March)
• Re: [webcomponents] [Custom]: mixin pattern: custom elements should be able to extend any base tag with is= (bugzilla: 27977) (#153) (Friday, 11 March)
• Re: [webcomponents] Consider a src/href-like attribute for easy integration? (bugzilla: 17761) (#146) (Friday, 11 March)
• Re: [webcomponents] Consider a src/href-like attribute for easy integration? (bugzilla: 17761) (#146) (Friday, 11 March)
• Re: [webcomponents] [Custom]: inflexible extends as fixed element type (bugzilla: 28158) (#143) (Friday, 11 March)
• Re: [webcomponents] document.registerElement should take a template as an argument (bugzilla: 28546) (#135) (Friday, 11 March)
• Re: [webcomponents] [Shadow]: Define the impact of ordering on relevant HTML elements (bugzilla: 25563) (#183) (Friday, 11 March)
• Re: [webcomponents] [Shadow]: How should Element.requestPointerLock() work in shadow DOM? (bugzilla: 26934) (#192) (Friday, 11 March)
• Re: [webcomponents] Composition Algorithm shouldn't unwrap slots (#308) (Friday, 11 March)
• Re: [webcomponents] "component tree" is just "node tree" (#384) (Friday, 11 March)
• Re: [webcomponents] "component tree" is just "node tree" (#384) (Friday, 11 March)
• Re: [ServiceWorker] spec should be more explicit about accessing internal body on opaque Responses (#710) (Friday, 11 March)
• Re: [webcomponents] Move defineElement elsewhere? (#431) (Friday, 11 March)
• Re: [webcomponents] Remove some semicolons (51fd7cd) (Friday, 11 March)
• Re: [webcomponents] defineElement should not cache lifecycle callbacks and prototype of a custom element class (#417) (Friday, 11 March)
• [webidl] Add [[PlatformBrand]] internal slot to all platform objects (#97) (Friday, 11 March)
• Re: [dom] Export the term "target override" (#187) (Friday, 11 March)
• Re: [fetch] Define the WebSocket subprotocol check as part of response validation (#242) (Thursday, 10 March)
• [fetch] Improve HSTS language (#244) (Thursday, 10 March)
• Re: [ServiceWorker] spec should be more explicit about accessing internal body on opaque Responses (#710) (Thursday, 10 March)
• [fetch] Define the WebSocket subprotocol check as part of response validation (#242) (Thursday, 10 March)
• Re: [ServiceWorker] spec should be more explicit about accessing internal body on opaque Responses (#710) (Thursday, 10 March)
• Re: [ServiceWorker] spec should be more explicit about accessing internal body on opaque Responses (#710) (Thursday, 10 March)
• Re: [ServiceWorker] spec should be more explicit about accessing internal body on opaque Responses (#710) (Thursday, 10 March)
• Re: [fetch] Merge HTML5 and Fetch definitions of 'HTTPS state' (#241) (Thursday, 10 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Thursday, 10 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Thursday, 10 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Thursday, 10 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Thursday, 10 March)
• Re: [webcomponents] Integrate events with "get the parent" model (#429) (Thursday, 10 March)
• Re: [fetch] "For each protocol in protocols, combine `Sec-We..." (#240) (Thursday, 10 March)
• Re: [fetch] "For each protocol in protocols, combine `Sec-We..." (#240) (Thursday, 10 March)
• Re: [ServiceWorker] spec should be more explicit about accessing internal body on opaque Responses (#710) (Thursday, 10 March)
• Re: [webcomponents] Should shadow host have `display: block` by default? (#426) (Thursday, 10 March)
• Re: [webcomponents] Shadow DOM and the Fullscreen API (#180) (Thursday, 10 March)
• Re: [webcomponents] Parse <slot> like <template> (#59) (Thursday, 10 March)
• Re: [ServiceWorker] spec should be more explicit about accessing internal body on opaque Responses (#710) (Thursday, 10 March)
• Re: [ServiceWorker] spec should be more explicit about accessing internal body on opaque Responses (#710) (Thursday, 10 March)
• Re: [webcomponents] Figure out how form owner should work in shadow DOM (#196) (Wednesday, 9 March)
• Re: [webcomponents] MutationObserver and attachShadow() (#390) (Wednesday, 9 March)
• Re: [webcomponents] MutationObserver and attachShadow() (#390) (Wednesday, 9 March)
• Re: [webcomponents] Shadow DOM and the Fullscreen API (#180) (Wednesday, 9 March)
• Re: [webcomponents] [Shadow] Need Document.deepActiveElement (bugzilla:28652) (#104) (Wednesday, 9 March)
• Re: [webcomponents] [Shadow]: There's isn't a way to append shadow elements in SVG (bugzilla: 24181) (#96) (Wednesday, 9 March)
• Re: [webcomponents] [Shadow]: There's isn't a way to append shadow elements in SVG (bugzilla: 24181) (#96) (Wednesday, 9 March)
• Re: [webcomponents] Shared mixin for Document and ShadowRoot (#91) (Wednesday, 9 March)
• Re: [webcomponents] [Shadow]: Isolated Shadow trees (bugzilla: 28442) (#72) (Wednesday, 9 March)
• Re: [webcomponents] [Shadow]: Declarative Shadow DOM (bugzilla: 28441) (#71) (Wednesday, 9 March)
• Re: [webcomponents] [Shadow]: Isolated Shadow trees (bugzilla: 28442) (#72) (Wednesday, 9 March)
• Re: [webcomponents] [Shadow]: Declarative Shadow DOM (bugzilla: 28441) (#71) (Wednesday, 9 March)
• Re: [webcomponents] [Shadow]: Fully explore composition (bugzilla: 27401) (#69) (Wednesday, 9 March)
• Re: [webcomponents] [Shadow]: Fully explore composition (bugzilla: 27401) (#69) (Wednesday, 9 March)
• Re: [webcomponents] [Shadow]: url fragment identifiers should be followed into ShadowDOM (bugzilla: 23161) (#66) (Wednesday, 9 March)
• Re: [webcomponents] [Shadow]: url fragment identifiers should be followed into ShadowDOM (bugzilla: 23161) (#66) (Wednesday, 9 March)
• Re: [webcomponents] [Shadow]: Shadow trees should somehow contain base URL information (bugzilla: 22255) (#63) (Wednesday, 9 March)
• Re: [webcomponents] [Shadow]: Shadow trees should somehow contain base URL information (bugzilla: 22255) (#63) (Wednesday, 9 March)
• Re: [webcomponents] [Shadow]: Shadow DOM-based components could benefit from a way to detect when light DOM contents change (bugzilla: 21149) (#62) (Wednesday, 9 March)
• Re: [webcomponents] [Shadow]: Shadow DOM-based components could benefit from a way to detect when light DOM contents change (bugzilla: 21149) (#62) (Wednesday, 9 March)
• Re: [webcomponents] [Shadow]: Specify imperative API for node distribution (bugzilla: 18429) (#60) (Wednesday, 9 March)
• Re: [webcomponents] [Shadow]: Specify imperative API for node distribution (bugzilla: 18429) (#60) (Wednesday, 9 March)
• Re: [webcomponents] Parse <slot> like <template> (#59) (Wednesday, 9 March)
• Re: [webcomponents] [Shadow]: Style element should specify when to create and add style sheet in shadow DOM (bugzilla: 26850) (#56) (Wednesday, 9 March)
• Re: [fetch] Set content-length header of FormData requests? (#239) (Wednesday, 9 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Wednesday, 9 March)
• [webcomponents] Make ShadowRoot objects use DocumentFragment object's host concept (#430) (Wednesday, 9 March)
• [webcomponents] Integrate events with "get the parent" model (#429) (Wednesday, 9 March)
• Re: [fetch] WebSocket nits (#238) (Wednesday, 9 March)
• Re: [fetch] WebSocket nits (#238) (Wednesday, 9 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Wednesday, 9 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Wednesday, 9 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Wednesday, 9 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Wednesday, 9 March)
• Re: [fetch] Removed promise antipattern from code example (#227) (Wednesday, 9 March)
• Re: [fetch] Removed promise antipattern from code example (#227) (Wednesday, 9 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Wednesday, 9 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Wednesday, 9 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Wednesday, 9 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Wednesday, 9 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Wednesday, 9 March)
• Re: [fetch] Define how WebSocket "fetching" works (#235) (Wednesday, 9 March)
• Re: [fetch] Define the WebSocket client handshake in terms of Fetch (#236) (Wednesday, 9 March)
• Re: [fetch] Define the WebSocket client handshake in terms of Fetch (#236) (Wednesday, 9 March)
• Re: [webcomponents] Use FrozenArray<T> in WebIDL (#361) (Wednesday, 9 March)
• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Wednesday, 9 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Wednesday, 9 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Tuesday, 8 March)
• Re: [webcomponents] Change createElement(ln, typeExtension) to createElement(ln, { is }) (0abc10e) (Tuesday, 8 March)
• Re: [webcomponents] Change createElement(ln, typeExtension) to createElement(ln, { is }) (0abc10e) (Tuesday, 8 March)
• Re: [webcomponents] [Custom] Should attachedCallback/detachedCallback callbacks be called when element is added to / removed from shadom dom which is attached to a in-document host? (bugzilla: 26943) (#191) (Tuesday, 8 March)
• Re: [webcomponents] [Custom] Should attachedCallback/detachedCallback callbacks be called when element is added to / removed from shadom dom which is attached to a in-document host? (bugzilla: 26943) (#191) (Tuesday, 8 March)
• Re: [webcomponents] "Creating an element" needs to be more precise, for upgrades (#424) (Tuesday, 8 March)
• Re: [webcomponents] Replace attached/detached callbacks with insertedIntoDocument/removedFromDocument (#362) (Tuesday, 8 March)
• Re: [webcomponents] [Custom] Should attachedCallback/detachedCallback callbacks be called when element is added to / removed from shadom dom which is attached to a in-document host? (bugzilla: 26943) (#191) (Tuesday, 8 March)
• Re: [webcomponents] Upstream Shadow DOM spec to DOM/HTML Standard (#377) (Tuesday, 8 March)
• Re: [webcomponents] Custom elements need an explicit "upgraded" or "resolved" flag (#425) (Tuesday, 8 March)
• Re: [webcomponents] "Creating an element" needs to be more precise, for upgrades (#424) (Tuesday, 8 March)
• Re: [webcomponents] [Custom] Should attachedCallback/detachedCallback callbacks be called when element is added to / removed from shadom dom which is attached to a in-document host? (bugzilla: 26943) (#191) (Tuesday, 8 March)
• Re: [webcomponents] [Custom] Should attachedCallback/detachedCallback callbacks be called when element is added to / removed from shadom dom which is attached to a in-document host? (bugzilla: 26943) (#191) (Tuesday, 8 March)
• Re: [webcomponents] Replace attached/detached callbacks with insertedIntoDocument/removedFromDocument (#362) (Tuesday, 8 March)
• Re: [webcomponents] Replace attached/detached callbacks with insertedIntoDocument/removedFromDocument (#362) (Tuesday, 8 March)
• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Tuesday, 8 March)
• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Tuesday, 8 March)
• Re: [webcomponents] :unresolved vs :not(:upgraded) (#418) (Tuesday, 8 March)
• Re: [webcomponents] Define the behavior when a custom element constructor returns an element with a parent node. (#412) (Tuesday, 8 March)
• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)
• Re: [dom] Element.matches and pseudo-elements (#185) (Tuesday, 8 March)
• Re: [fetch] Removed promise antipattern from code example (#227) (Tuesday, 8 March)
• Re: [fetch] Handle an ArrayBuffer allocation failure (#228) (Tuesday, 8 March)
• Re: [fetch] Define the WebSocket client handshake in terms of Fetch (#236) (Tuesday, 8 March)
• Re: [dom] The NodeFilter callback interface doesn't make sense (#186) (Tuesday, 8 March)
• Re: [webcomponents] defineElement should not cache lifecycle callbacks and prototype of a custom element class (#417) (Monday, 7 March)
• Re: [url] Fix #101: always strip U+0009, U+000A, and U+000D (7b40216) (Monday, 7 March)
• Re: [url] Strip whitespace in the scheme too (#101) (Monday, 7 March)
• Re: [webcomponents] Replace attached/detached callbacks with insertedIntoDocument/removedFromDocument (#362) (Monday, 7 March)
• [url] Strip whitespace in the scheme too (#101) (Monday, 7 March)
• Re: [fetch] Define the WebSocket client handshake in terms of Fetch (#236) (Monday, 7 March)
• [fetch] Define the WebSocket client handshake in terms of Fetch (#236) (Monday, 7 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Monday, 7 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Monday, 7 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Monday, 7 March)
• Re: [webcomponents] The algorithm "invoke callbacks" must halt as soon as one of callbacks throw an exception (#421) (Monday, 7 March)
• Re: [webcomponents] Should :unresolved apply to elements that failed to upgrade? (#422) (Monday, 7 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Monday, 7 March)
• Re: [webcomponents] Replace attached/detached callbacks with insertedIntoDocument/removedFromDocument (#362) (Monday, 7 March)
• Re: [webcomponents] [Shadow]: Node should expose their scope so that shared state can be scoped to components. (bugzilla: 22080) (#80) (Monday, 7 March)
• Re: [webcomponents] [Shadow]: Node should expose their scope so that shared state can be scoped to components. (bugzilla: 22080) (#80) (Monday, 7 March)
• Re: [webcomponents] [Shadow]: Node should expose their scope so that shared state can be scoped to components. (bugzilla: 22080) (#80) (Monday, 7 March)
• Re: [webcomponents] [Shadow]: Node should expose their scope so that shared state can be scoped to components. (bugzilla: 22080) (#80) (Monday, 7 March)
• Re: [webcomponents] Replace attached/detached callbacks with insertedIntoDocument/removedFromDocument (#362) (Monday, 7 March)
• Re: [fullscreen] Compute sticky position? (#21) (Monday, 7 March)
• Re: [fullscreen] Fullscreen on non-HTML elements? (#22) (Sunday, 6 March)
• Re: [fetch] Define how WebSocket "fetching" works (#235) (Saturday, 5 March)
• Re: [fetch] Define how WebSocket "fetching" works (#235) (Saturday, 5 March)
• [fetch] Define how WebSocket "fetching" works (#235) (Saturday, 5 March)
• [storage] Prevent usage in combination with document.domain (#12) (Saturday, 5 March)
• Re: [dom] Element.matches and pseudo-elements (#185) (Saturday, 5 March)
• Re: [ServiceWorker] Add cookie accessor/setter methods? (#707) (Saturday, 5 March)
• Re: [webcomponents] Rename the first argument of defineElement from type to localName (#416) (Saturday, 5 March)
• Re: [fetch] Support full-duplex HTTP streaming (#229) (Saturday, 5 March)
• Re: [dom] Fix #34: invoke insertion/removing steps for descendants (#184) (Friday, 4 March)
• Re: [dom] insert/remove hooks need to be invoked for ancestor changes too (#34) (Friday, 4 March)
• Re: [fullscreen] `position` value of `::backdrop` pseudo-element (#27) (Friday, 4 March)
• Re: [fullscreen] Fullscreen on non-HTML elements? (#22) (Friday, 4 March)
• Re: [fullscreen] Fullscreen element with `display: contents` (#28) (Friday, 4 March)
• Re: [fullscreen] Compute sticky position? (#21) (Friday, 4 March)
• [dom] Fix #34: invoke insertion/removing steps for descendants (#184) (Friday, 4 March)
• Re: [fetch] [DATAURL] is no longer a (quasi-)spec (#234) (Friday, 4 March)
• Re: [fetch] Redirect on preflighted CORS requests generally impossible (#204) (Friday, 4 March)
• Re: [fetch] Add "must-revalidate" to RequestCache enumeration (#165) (Friday, 4 March)
• Re: [fetch] "force-cache" RequestCache type should not bypass validation for responses that would vary (#233) (Friday, 4 March)
• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Friday, 4 March)
• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Friday, 4 March)
• Re: [webcomponents] Shadow DOM and comment nodes (#411) (Friday, 4 March)
• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Friday, 4 March)
• Re: [webcomponents] Figure out terminology for Shadow DOM that everyone agrees on (#382) (Friday, 4 March)
• Re: [fetch] Support full-duplex HTTP streaming (#229) (Friday, 4 March)
• Re: [fetch] Removed promise antipattern from code example (#227) (Friday, 4 March)
• Re: [webcomponents] Shadow DOM and comment nodes (#411) (Friday, 4 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Thursday, 3 March)
• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Thursday, 3 March)
• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Thursday, 3 March)
• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Thursday, 3 March)
• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Thursday, 3 March)
• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Thursday, 3 March)
• Re: [fetch] Support full-duplex HTTP streaming (#229) (Thursday, 3 March)
• Re: [fetch] RequestCache "no-cache" type must also set the right headers (#232) (Thursday, 3 March)
• Re: [fetch] RequestCache "no-store" type must also set no-cache headers (#231) (Thursday, 3 March)
• Re: [fetch] RequestCache "no-store" type must also set no-cache headers (#231) (Thursday, 3 March)
• Re: [fetch] RequestCache "no-cache" type must also set the right headers (#232) (Thursday, 3 March)
• Re: [webcomponents] Remove `Callback` suffix from custom elements callbacks (#414) (Thursday, 3 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Thursday, 3 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Thursday, 3 March)
• Re: [webcomponents] Remove `Callback` suffix from custom elements callbacks (#414) (Thursday, 3 March)
• Re: [webcomponents] Add authoring guidance for writing custom element constructors (#409) (Thursday, 3 March)
• Re: [webcomponents] Replace attached/detached callbacks with insertedIntoDocument/removedFromDocument (#362) (Thursday, 3 March)
• Re: [webcomponents] Remove `Callback` suffix from custom elements callbacks (#414) (Thursday, 3 March)
• Re: [fetch] Support full-duplex HTTP streaming (#229) (Thursday, 3 March)
• Re: [webcomponents] Replace attached/detached callbacks with insertedIntoDocument/removedFromDocument (#362) (Thursday, 3 March)
• Re: [webcomponents] Shadow DOM and comment nodes (#411) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: Restrict custom elements to NCName (bugzilla: 20973) (#177) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: Restrict custom elements to NCName (bugzilla: 20973) (#177) (Thursday, 3 March)
• Re: [fetch] Support full-duplex HTTP streaming (#229) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Thursday, 3 March)
• Re: [webcomponents] Replace attached/detached callbacks with insertedIntoDocument/removedFromDocument (#362) (Thursday, 3 March)
• Re: [webcomponents] Define the behavior when a custom element constructor returns an in-document element to parser (#412) (Thursday, 3 March)
• Re: [fetch] Support full-duplex HTTP streaming (#229) (Thursday, 3 March)
• Re: [webcomponents] Shadow DOM and comment nodes (#411) (Thursday, 3 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Thursday, 3 March)
• Re: [fetch] Support full-duplex HTTP streaming (#229) (Thursday, 3 March)
• Re: [webcomponents] Change createElement(localName, typeExtension) to createElement(localName, { is }) (#408) (Wednesday, 2 March)
• Re: [fetch] Support full-duplex HTTP streaming (#229) (Wednesday, 2 March)
• [url] Disallow "!" in host (#98) (Wednesday, 2 March)
• Re: [webcomponents] Handle constructors that abuse return-override (4a09d96) (Wednesday, 2 March)
• Re: [webcomponents] Should HTML parser instantiate custom elements inside a template element? (#406) (Wednesday, 2 March)
• Re: [webcomponents] Handle constructors that abuse return-override (4a09d96) (Wednesday, 2 March)
• Re: [webcomponents] Should HTML parser instantiate custom elements inside a template element? (#406) (Wednesday, 2 March)
• Re: [webcomponents] Should HTML parser instantiate custom elements inside a template element? (#406) (Wednesday, 2 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Wednesday, 2 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Wednesday, 2 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Wednesday, 2 March)
• Re: [webcomponents] Handle constructors that abuse return-override (4a09d96) (Wednesday, 2 March)
• Re: [FileAPI] Use `optional` for the Blob constructor (#33) (Wednesday, 2 March)
• Re: [fetch] Support full-duplex HTTP streaming (#229) (Wednesday, 2 March)
• Re: [webcomponents] Figure out terminology for Shadow DOM that everyone agrees on (#382) (Wednesday, 2 March)
• Re: [webcomponents] Figure out terminology for Shadow DOM that everyone agrees on (#382) (Wednesday, 2 March)
• Re: [webcomponents] Figure out terminology for Shadow DOM that everyone agrees on (#382) (Wednesday, 2 March)
• Re: [webcomponents] Figure out terminology for Shadow DOM that everyone agrees on (#382) (Wednesday, 2 March)
• Re: [webcomponents] When is the slotting algorithm run (#401) (Wednesday, 2 March)
• Re: [webcomponents] Figure out terminology for Shadow DOM that everyone agrees on (#382) (Wednesday, 2 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Wednesday, 2 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Wednesday, 2 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Wednesday, 2 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Wednesday, 2 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Wednesday, 2 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Wednesday, 2 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Wednesday, 2 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Wednesday, 2 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Wednesday, 2 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Wednesday, 2 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Wednesday, 2 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Wednesday, 2 March)
• Re: [dom] Proposal to improve the DOM creation api (#150) (Wednesday, 2 March)
• Re: [webcomponents] Handle constructors that abuse return-override (4a09d96) (Wednesday, 2 March)
• Re: [webcomponents] Handle constructors that abuse return-override (4a09d96) (Wednesday, 2 March)
• Re: [fetch] Support full-duplex HTTP streaming (#229) (Wednesday, 2 March)
• Re: [fetch] Reviver param for response.json() (#230) (Wednesday, 2 March)
• Re: [fetch] Reviver param for response.json() (#230) (Wednesday, 2 March)
• Re: [dom] className setter is not defined? (#183) (Tuesday, 1 March)
• Re: [dom] className setter is not defined? (#183) (Tuesday, 1 March)
• Re: [dom] Hyperlink "get the parent" in override defs for easier x-referencing (#182) (Tuesday, 1 March)
• Re: [dom] Properly check event's stop immediate propagation flag in "inner invoke" (#180) (Tuesday, 1 March)
• Re: [dom] Hyperlink "get the parent" in override defs for easier x-referencing (#182) (Tuesday, 1 March)
• Re: [dom] Properly check event's stop immediate propagation flag in "inner invoke" (#180) (Tuesday, 1 March)
• Re: [dom] className setter is not defined? (#183) (Tuesday, 1 March)
• Re: [dom] Properly check event's stop immediate propagation flag in "inner invoke" (#180) (Tuesday, 1 March)
• Re: [webcomponents] Custom elements need da (microtask) hookup (bugzilla: 22409) (#225) (Tuesday, 1 March)
• Re: [webcomponents] Custom elements need da (microtask) hookup (bugzilla: 22409) (#225) (Tuesday, 1 March)
• Re: [webcomponents] [Custom Elements]: When is "created" callback invoked? (bugzilla: 14987) (#262) (Tuesday, 1 March)
• Re: [webcomponents] [Custom Elements]: When is "created" callback invoked? (bugzilla: 14987) (#262) (Tuesday, 1 March)
• Re: [webcomponents] [Custom Elements] Write-up proposal for using a "state object" (#287) (Tuesday, 1 March)
• Re: [webcomponents] [Custom Elements] Write-up proposal for using a "state object" (#287) (Tuesday, 1 March)
• Re: [webcomponents] Custom element callbacks for builtins (#291) (Tuesday, 1 March)
• Re: [webcomponents] Custom element callbacks for builtins (#291) (Tuesday, 1 March)
• Re: [webcomponents] Use a parent/child relationship in the flat tree in the definition of some elements, i.e. <tr>/<td> (#404) (Tuesday, 1 March)
• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (bugzilla: 24876) (#224) (Tuesday, 1 March)
• Re: [webcomponents] When is the slotting algorithm run (#401) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: Need adopted callback (bugzilla: 24577) (#210) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: Clarify in informative note that cloning/importing also enqueues created callback (bugzilla: 28092) (#144) (Tuesday, 1 March)
• Re: [webcomponents] [Meta]: Specify how custom elements work (bugzilla: 14968) (#132) (Tuesday, 1 March)
• Re: [webcomponents] [Meta]: Specify how custom elements work (bugzilla: 14968) (#132) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (bugzilla: 22056) (#239) (Tuesday, 1 March)
• Re: [webcomponents] When is the slotting algorithm run (#401) (Tuesday, 1 March)
• Re: [dom] className setter is not defined? (#183) (Tuesday, 1 March)
• Re: [fetch] Handle an ArrayBuffer allocation failure (#228) (Tuesday, 1 March)
• Re: [fetch] Handle an ArrayBuffer allocation failure (#228) (Tuesday, 1 March)
• Re: [fetch] Removed promise antipattern from code example (#227) (Tuesday, 1 March)
• Re: [fetch] Removed promise antipattern from code example (#227) (Tuesday, 1 March)

Anssi Kostiainen

• Re: [manifest] Allow developers to detect when the user has added the site to their home screen (or equivalent) (#417) (Wednesday, 23 March)

Anthony Ramine

• Re: [dom] Fix #34: invoke insertion/removing steps for descendants (#184) (Friday, 4 March)

aphillips

• Re: [manifest] Feat (dir member): Add dir member (closes #334) (#433) (Tuesday, 22 March)
• Re: [manifest] Feat (dir member): Add dir member (closes #334) (#433) (Tuesday, 22 March)
• Re: [manifest] Feat (dir member): Add dir member (closes #334) (#433) (Tuesday, 22 March)
• Re: [manifest] Feat (dir member): Add dir member (closes #334) (#433) (Tuesday, 22 March)

ArkadiuszMichalski

• Re: [whatwg/dom] Spec for DOMTokenList stringifier disagrees with every single implementation (#105) (Thursday, 31 March)
• [whatwg/dom] Future for unique tokens in DOMTokenList (#201) (Thursday, 31 March)
• Re: [whatwg/dom] Spec for DOMTokenList stringifier disagrees with every single implementation (#105) (Thursday, 31 March)
• Re: [whatwg/dom] Comment out query/queryAll/Elements for now (10b6cf1) (Tuesday, 29 March)
• Re: [whatwg/dom] Comment out query/queryAll/Elements for now (10b6cf1) (Tuesday, 29 March)
• [whatwg/dom] Back to previous definition for Element.getAttributeNS() (#197) (Tuesday, 29 March)
• Re: [dom] The NodeFilter callback interface doesn't make sense (#186) (Tuesday, 8 March)
• Re: [webidl] Check if NodeFilter.length is defined correctly. (#83) (Tuesday, 8 March)
• Re: [dom] className setter is not defined? (#183) (Tuesday, 1 March)
• Re: [dom] className setter is not defined? (#183) (Tuesday, 1 March)

Arun Ranganathan

• Re: [w3c/FileAPI] Update Typed Array spec URL (#34) (Wednesday, 30 March)
• Re: [w3c/FileAPI] Make the Blob URL creating/revoking methods not be exposed on the ser… (#31) (Wednesday, 30 March)
• Re: [directory-upload] Consider renaming getDirectoriesAndFiles to fsitems or getFSItems (#32) (Monday, 28 March)
• Re: [directory-upload] Consider how we could avoid the I/O blocking for FILE picking in addition to directory picking (#11) (Monday, 28 March)
• Re: [directory-upload] Consider changing the boolean param of getFiles to a dictionary (#34) (Monday, 28 March)

Axel Nennker

• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Wednesday, 9 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Wednesday, 9 March)

Ayumi Hamasaki

• [w3c/manifest] Poorly coded example on w3c (#437) (Tuesday, 29 March)
• Re: [ServiceWorker] Service Worker Error (#858) (Monday, 28 March)
• [ServiceWorker] Service Worker Error (#858) (Sunday, 27 March)

baby9999

• [url] e549999@yahoo.com.tw (#100) (Monday, 7 March)
• Re: [url] e549999@yahoo.com.tw (#99) (Monday, 7 March)
• Re: [url] e549999@yahoo.com.tw (#99) (Monday, 7 March)
• [url] e549999@yahoo.com.tw (#99) (Monday, 7 March)

Bede Overend

• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)

Ben

• Re: [w3c/manifest] Allow developers to detect when the user has added the site to their home screen (or equivalent) (#417) (Tuesday, 29 March)

Ben Christensen

• Re: [fetch] Support full-duplex HTTP streaming (#229) (Wednesday, 2 March)

Ben Francis

• Re: [w3c/manifest] Support registering "actions" (#442) (Thursday, 31 March)
• Re: [w3c/manifest] Deep linking - need proper use cases and requirements analysis (#363) (Thursday, 31 March)
• [w3c/manifest] Support registering "actions" (#442) (Thursday, 31 March)
• Re: [manifest] Remove reference to RFC5988. (#428) (Monday, 7 March)

Ben Kelly

• Re: [slightlyoff/ServiceWorker] Cache transactions & fixing `addAll` (#823) (Thursday, 31 March)
• Re: [slightlyoff/ServiceWorker] Allow caches to opt-in to granular cleanup (#863) (Thursday, 31 March)
• Re: [slightlyoff/ServiceWorker] `caches.match` search order (#862) (Thursday, 31 March)
• Re: [slightlyoff/ServiceWorker] should update() during top level script evaluation be ignored? (#800) (Thursday, 31 March)
• Re: [slightlyoff/ServiceWorker] be more explicit that jobs always run asynchronously (#861) (Tuesday, 29 March)
• [slightlyoff/ServiceWorker] be more explicit that jobs always run asynchronously (#861) (Tuesday, 29 March)
• Re: [slightlyoff/ServiceWorker] "Wait for all the tasks queued by Update State" language is problematic (#848) (Tuesday, 29 March)
• Re: [slightlyoff/ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851) (Tuesday, 29 March)
• [slightlyoff/ServiceWorker] spec should queue tasks to expose attribute changes on ServiceWorker and ServiceWorkerRegistration (#860) (Tuesday, 29 March)
• [w3c/WebPlatformWG] Add Ben Kelly to attendees. (#23) (Monday, 28 March)
• Re: [ServiceWorker] ServiceWorkerMessageEvent.origin spec text is confusing (#859) (Monday, 28 March)
• Re: [ServiceWorker] ServiceWorkerMessageEvent.origin spec text is confusing (#859) (Monday, 28 March)
• [ServiceWorker] ServiceWorkerMessageEvent.origin spec text is confusing (#859) (Monday, 28 March)
• Re: [ServiceWorker] if service-worker-allowed header changes should active worker be potentially unregistered? (#857) (Monday, 28 March)
• Re: [ServiceWorker] why does Register algorithm step 5.3.1 check for an active worker? (#856) (Monday, 28 March)
• Re: [ServiceWorker] Service Worker Error (#858) (Sunday, 27 March)
• [ServiceWorker] if service-worker-allowed header changes should active worker be potentially unregistered? (#857) (Friday, 25 March)
• Re: [ServiceWorker] why does Register algorithm step 5.3.1 check for an active worker? (#856) (Friday, 25 March)
• [ServiceWorker] why does Register algorithm step 5.3.1 check for an active worker? (#856) (Friday, 25 March)
• [ServiceWorker] Unregister algorithm step 6.1 is no longer necessary (#855) (Friday, 25 March)
• Re: [ServiceWorker] should update() during top level script evaluation be ignored? (#800) (Friday, 25 March)
• Re: [ServiceWorker] Race in Schedule Job algorithm handling of equivalent job promises (#853) (Thursday, 24 March)
• Re: [ServiceWorker] Race in Schedule Job algorithm handling of equivalent job promises (#853) (Thursday, 24 March)
• Re: [ServiceWorker] Race in Schedule Job algorithm handling of equivalent job promises (#853) (Wednesday, 23 March)
• [ServiceWorker] Race in Schedule Job algorithm handling of equivalent job promises (#853) (Wednesday, 23 March)
• Re: [fetch] Should fetch(evt.request) send original RequestDestination and RequestType? (#262) (Wednesday, 23 March)
• Re: [fetch] Should fetch(evt.request) send original RequestDestination and RequestType? (#262) (Wednesday, 23 March)
• Re: [fetch] Should fetch(evt.request) send original RequestDestination and RequestType? (#262) (Wednesday, 23 March)
• [fetch] Should fetch(evt.request) send original RequestDestination and RequestType? (#262) (Wednesday, 23 March)
• Re: [ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851) (Wednesday, 23 March)
• Re: [ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851) (Tuesday, 22 March)
• Re: [ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851) (Tuesday, 22 March)
• [ServiceWorker] Update step 4 fails to fulfill job promise (#852) (Monday, 21 March)
• Re: [ServiceWorker] "Wait for all the tasks queued by Update State" language is problematic (#848) (Monday, 21 March)
• Re: [ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851) (Monday, 21 March)
• Re: [ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851) (Friday, 18 March)
• Re: [ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851) (Friday, 18 March)
• [ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851) (Friday, 18 March)
• Re: [ServiceWorker] DOMParser within ServiceWorkers (#846) (Friday, 18 March)
• Re: [fetch] referrer same-origin constraint is a footgun for people trying to "copy" a Request (#245) (Friday, 18 March)
• Re: [ServiceWorker] FetchEvent.respondWith does something weird with the body of a response (#850) (Thursday, 17 March)
• Re: [ServiceWorker] FetchEvent.respondWith does something weird with the body of a response (#850) (Thursday, 17 March)
• Re: [ServiceWorker] FetchEvent.respondWith does something weird with the body of a response (#850) (Thursday, 17 March)
• Re: [ServiceWorker] Spec uses incorrect settings object when fetching a module worker (#849) (Wednesday, 16 March)
• Re: [fetch] The reason why Access-Control-Request-Headers includes simple headers (#249) (Wednesday, 16 March)
• Re: [ServiceWorker] "Wait for all the tasks queued by Update State" language is problematic (#848) (Wednesday, 16 March)
• Re: [ServiceWorker] What is the "Doom Installing Worker" algorithm supposed to be doing? (#847) (Tuesday, 15 March)
• Re: [ServiceWorker] What is the "Doom Installing Worker" algorithm supposed to be doing? (#847) (Tuesday, 15 March)
• Re: [ServiceWorker] What is the "Doom Installing Worker" algorithm supposed to be doing? (#847) (Tuesday, 15 March)
• [ServiceWorker] "Wait for all the tasks queued by Update State" language is problematic (#848) (Tuesday, 15 March)
• [ServiceWorker] What is the "Doom Installing Worker" algorithm supposed to be doing? (#847) (Tuesday, 15 March)
• Re: [fetch] referrer same-origin constraint is a footgun for people trying to "copy" a Request (#245) (Tuesday, 15 March)
• Re: [fetch] referrer same-origin constraint is a footgun for people trying to "copy" a Request (#245) (Tuesday, 15 March)
• Re: [fetch] referrer same-origin constraint is a footgun for people trying to "copy" a Request (#245) (Tuesday, 15 March)
• Re: [fetch] referrer same-origin constraint is a footgun for people trying to "copy" a Request (#245) (Tuesday, 15 March)
• Re: [fetch] referrer same-origin constraint is a footgun for people trying to "copy" a Request (#245) (Tuesday, 15 March)
• Re: [fetch] referrer same-origin constraint is a footgun for people trying to "copy" a Request (#245) (Monday, 14 March)
• Re: [fetch] referrer same-origin constraint is a footgun for people trying to "copy" a Request (#245) (Friday, 11 March)
• [fetch] referrer same-origin constraint is a footgun for people trying to "copy" a Request (#245) (Friday, 11 March)
• Re: [ServiceWorker] Fetch API respondWith's implicit RETURN (#844) (Friday, 11 March)
• Re: [ServiceWorker] spec should be more explicit about accessing internal body on opaque Responses (#710) (Friday, 11 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Friday, 11 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Thursday, 10 March)
• Re: [ServiceWorker] spec should be more explicit about accessing internal body on opaque Responses (#710) (Thursday, 10 March)
• Re: [ServiceWorker] spec should be more explicit about accessing internal body on opaque Responses (#710) (Thursday, 10 March)
• Re: [ServiceWorker] spec should be more explicit about accessing internal body on opaque Responses (#710) (Thursday, 10 March)
• Re: [ServiceWorker] spec should be more explicit about accessing internal body on opaque Responses (#710) (Thursday, 10 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Thursday, 10 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Thursday, 10 March)
• Re: [ServiceWorker] spec should be more explicit about accessing internal body on opaque Responses (#710) (Thursday, 10 March)
• Re: [ServiceWorker] spec should be more explicit about accessing internal body on opaque Responses (#710) (Thursday, 10 March)
• Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808) (Monday, 7 March)
• Re: [ServiceWorker] Support modifying cookies on an intercepted fetch (#837) (Friday, 4 March)
• Re: [ServiceWorker] setTimeout/setInterval are unreliable in ServiceWorkers (#838) (Tuesday, 1 March)

Benjamin C. Wiley Sittler

• Re: [ServiceWorker] Add cookie accessor/setter methods? (#707) (Friday, 4 March)

Bergi

• Re: [fetch] Removed promise antipattern from code example (#227) (Wednesday, 9 March)
• Re: [fetch] Removed promise antipattern from code example (#227) (Friday, 4 March)
• [fetch] Removed promise antipattern from code example (#227) (Tuesday, 1 March)

bifurcation

• Re: [fetch] error types too vague for TLS certificate error (#205) (Tuesday, 15 March)

Boris Zbarsky

• Re: [w3c/webcomponents] Define order for attributeChangedCallback invocation? (#474) (Wednesday, 30 March)
• Re: [w3c/webcomponents] Define order for attributeChangedCallback invocation? (#474) (Wednesday, 30 March)
• Re: [w3c/webcomponents] Define order for attributeChangedCallback invocation? (#474) (Wednesday, 30 March)
• Re: [heycam/webidl] What should the property descriptor for @@unscopeable look like? (#102) (Tuesday, 29 March)
• Re: [webidl] Should we match the ES spelling of "unscopable" (#103) (Saturday, 26 March)
• [webidl] Fix https://github.com/heycam/webidl/issues/103 by aligning the spelling of [Unscopable] with ES6. (#104) (Saturday, 26 March)
• [webidl] Should we match the ES spelling of "unscopable" (#103) (Friday, 25 March)
• Re: [webidl] What should the property descriptor for @@unscopeable look like? (#102) (Friday, 25 March)
• [webidl] What should the property descriptor for @@unscopeable look like? (#102) (Friday, 25 March)
• Re: [webidl] Allow constructor<ClassType> as a type accepted by functions. (#101) (Thursday, 24 March)
• Re: [webidl] Allow constructor<ClassType> as a type accepted by functions. (#101) (Thursday, 24 March)
• Re: [webidl] Please rename things that are legacy so it's clear they are (#100) (Monday, 21 March)
• Re: [webidl] Please rename things that are legacy so it's clear they are (#100) (Monday, 21 March)
• Re: [fetch] Stop hardcoding the list of schemes that inherit HTTPS state (#255) (Friday, 18 March)
• Re: [fetch] Stop hardcoding the list of schemes that inherit HTTPS state (#255) (Friday, 18 March)
• Re: [fetch] Stop hardcoding the list of schemes that inherit HTTPS state (#255) (Friday, 18 March)
• Re: [fetch] Stop hardcoding the list of schemes that inherit HTTPS state (#255) (Friday, 18 March)
• Re: [fetch] Stop hardcoding the list of schemes that inherit HTTPS state (#255) (Friday, 18 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Thursday, 10 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Thursday, 10 March)
• Re: [webcomponents] defineElement should not cache lifecycle callbacks and prototype of a custom element class (#417) (Monday, 7 March)
• Re: [webcomponents] Handle constructors that abuse return-override (4a09d96) (Wednesday, 2 March)
• Re: [webcomponents] Handle constructors that abuse return-override (4a09d96) (Wednesday, 2 March)
• Re: [FileAPI] Use `optional` for the Blob constructor (#33) (Wednesday, 2 March)
• Re: [webcomponents] Handle constructors that abuse return-override (4a09d96) (Wednesday, 2 March)
• Re: [webcomponents] Handle constructors that abuse return-override (4a09d96) (Wednesday, 2 March)

Brad Hill

• Re: [fetch] Redirect on preflighted CORS requests generally impossible (#204) (Wednesday, 9 March)

Brian Kardell

• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)

Cameron McCormack

• Re: [webidl] Add a [SecureContext] operator attribute (#65) (Wednesday, 23 March)
• Re: [webidl] Clarify [LegacyUnenumerableNamedProperties] with derived interfaces (#94) (Tuesday, 22 March)
• Re: [webidl] Clarify [LegacyUnenumerableNamedProperties] with derived interfaces (#94) (Tuesday, 22 March)
• Re: [webidl] Add a [SecureContext] operator attribute (#65) (Tuesday, 22 March)
• Re: [webcomponents] [Custom]: Clarify in informative note that cloning/importing also enqueues created callback (bugzilla: 28092) (#144) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: Clarify in informative note that cloning/importing also enqueues created callback (bugzilla: 28092) (#144) (Tuesday, 1 March)

chaals

• Re: [w3ctag/spec-reviews] Review WAPA (Accessibility) proposal (#63) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] ARIA (#107) (Thursday, 31 March)
• Re: [spec-reviews] ARIA (#107) (Monday, 28 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Tuesday, 1 March)

Chong Zhang

• [uievents] Clarify expected DomKey for Shift+AltGr+0 on Windows with fr-FR layout (#78) (Monday, 14 March)
• [uievents] Clarify expected DomKey for Ctrl+Alt+c on Android with default layout (#77) (Monday, 14 March)
• Re: [touch-events] Add tests for TouchEvent and Touch constructors (#27) (Tuesday, 8 March)
• Re: [touch-events] Need tests for ontouch*, the GlobalEventHandlers (#44) (Tuesday, 8 March)
• Re: [uievents] Request 'inputType' field in Keyboard Event Viewer (#71) (Friday, 4 March)
• Re: [uievents] Request 'inputType' field in Keyboard Event Viewer (#71) (Friday, 4 March)
• [uievents] Use https://rawgit.com URL for Keyboard Event Viewer (#72) (Tuesday, 1 March)

Chris Rebert

• Re: [whatwg/fetch] [DATAURL] is no longer a (quasi-)spec (#234) (Thursday, 31 March)
• [w3c/uievents-key] Mention modern usage of Esc (#23) (Thursday, 31 March)
• Re: [w3c/uievents-key] CONTRIBUTING.md suggestions (#21) (Thursday, 31 March)
• [w3c/uievents-key] Hyperlink mention of compositionupdate event (#22) (Thursday, 31 March)
• [w3c/uievents-key] CONTRIBUTING.md suggestions (#21) (Thursday, 31 March)
• Re: [w3c/uievents-key] Fix syntax error in description of FnLock (#19) (Thursday, 31 March)
• Re: [w3c/uievents-key] Test (#20) (Thursday, 31 March)
• [w3c/uievents-key] Test (#20) (Thursday, 31 March)
• Re: [w3c/uievents-key] Fix syntax error in description of FnLock (#19) (Thursday, 31 March)
• Re: [w3c/uievents-key] Fix syntax error in description of FnLock (#19) (Thursday, 31 March)
• [w3c/uievents-key] Fix syntax error in description of FnLock (#19) (Thursday, 31 March)
• [w3c/uievents-key] "ISO Level 3 shift modifier" is unclear (#18) (Thursday, 31 March)
• [w3c/uievents-key] Grammar fix: "it's" => "its" (possessive adjective) (#17) (Thursday, 31 March)
• [w3c/uievents-key] Fix typo: "Sktep" [sic] => "Step" (#16) (Thursday, 31 March)
• [w3c/uievents-code] Typo in Tab key description? (#10) (Thursday, 31 March)
• Re: [w3c/uievents] Clarify or change the use of "default action" to avoid confusion (#22) (Tuesday, 29 March)
• [w3c/uievents] Extraneous <code> in & after §12.1.2. Changes to DOM Level 2 event types (#82) (Tuesday, 29 March)
• [w3c/uievents] Explain that mousedown focuses form controls (#81) (Tuesday, 29 March)
• [w3c/uievents] Set (#80) (Tuesday, 29 March)
• Re: [dom] Add caniuse info boxes like the HTML spec (#69) (Sunday, 27 March)
• Re: [dom] Export the term "target override" (#187) (Tuesday, 15 March)
• Re: [uievents] The `resize` event isn't a UIEvent (#76) (Friday, 11 March)
• Re: [dom] Export the term "target override" (#187) (Friday, 11 March)
• [dom] Export the term "target override" (#187) (Friday, 11 March)
• Re: [uievents] The `resize` event isn't a UIEvent (#76) (Thursday, 10 March)
• [uievents] The `resize` event isn't a UIEvent (#76) (Thursday, 10 March)
• [uievents] Some list items not rendered properly (#74) (Sunday, 6 March)
• [uievents] Fix minor syntax errors (#73) (Sunday, 6 March)
• Re: [fetch] [DATAURL] is no longer a (quasi-)spec (#234) (Friday, 4 March)
• [fetch] [DATAURL] is no longer a (quasi-)spec (#234) (Friday, 4 March)

Christopher Darroch

• Re: [webcomponents] Consider exposing Shadom DOM and Custom Elements only in secure contexts (#449) (Monday, 21 March)

Cory Benfield

• Re: [fetch] Support full-duplex HTTP streaming (#229) (Tuesday, 15 March)

Craig Francis

• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Thursday, 24 March)
• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Tuesday, 22 March)
• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Monday, 21 March)
• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Sunday, 20 March)

cynthia

• Re: [touch-events] Reformat code (#2) (Tuesday, 15 March)

Cyril Auburtin

• Re: [dom] Text nodes .closest (#161) (Thursday, 3 March)

Cyril Concolato

• [ServiceWorker] Access to fragment identifiers (#854) (Thursday, 24 March)

Daniel Appelquist

• Re: [w3ctag/spec-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] Question: Should spec-review discussions live inside respective spec's repository? (#112) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] Question: Should spec-review discussions live inside respective spec's repository? (#112) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] Unblocking the HTTPS Transitions (#74) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] CSS font-display (#71) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] Review WAPA (Accessibility) proposal (#63) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] Review WAPA (Accessibility) proposal (#63) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] Cross-spec device identification & association (#64) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] contributing.md document needed for tag reviews (#53) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] contributing.md document needed for tag reviews (#53) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] Browser Fingerprinting Document (#38) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] Browser Fingerprinting Document (#38) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] WebRTC (#14) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] Streams General issue (#92) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] WICG Issue on Improving AccessKey (#113) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] ARIA (#107) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] ARIA (#107) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] Generic Sensor API & Ambient Light Sensor (#110) (Thursday, 31 March)
• [w3ctag/spec-reviews] Ambient Light Sensor API (#115) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] Generic Sensor API & Ambient Light Sensor (#110) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] Payments Drafts Review (#109) (Wednesday, 30 March)
• Re: [w3ctag/spec-reviews] Question: Should spec-review discussions live inside respective spec's repository? (#112) (Wednesday, 30 March)
• Re: [w3ctag/spec-reviews] Question: Should spec-review discussions live inside respective spec's repository? (#112) (Wednesday, 30 March)
• Re: [w3ctag/spec-reviews] WebUSB (#108) (Wednesday, 30 March)
• [w3ctag/spec-reviews] First Party Cookies (#114) (Wednesday, 30 March)
• Re: [w3ctag/spec-reviews] WebUSB (#108) (Wednesday, 30 March)
• [w3ctag/spec-reviews] WICG Issue on Improving AccessKey (#113) (Wednesday, 30 March)
• Re: [w3ctag/spec-reviews] Review FIDO spec (#97) (Wednesday, 30 March)
• [w3ctag/spec-reviews] TV Control Feedback (#111) (Wednesday, 30 March)
• Re: [w3ctag/spec-reviews] Payments Drafts Review (#109) (Tuesday, 29 March)
• Re: [w3ctag/spec-reviews] Payments Drafts Review (#109) (Tuesday, 29 March)
• [spec-reviews] Payments Drafts Review (#109) (Tuesday, 22 March)
• [spec-reviews] ARIA (#107) (Thursday, 17 March)
• [spec-reviews] WebVR (#106) (Wednesday, 16 March)
• [spec-reviews] TV-Specific Web Subsetting (#105) (Wednesday, 16 March)
• Re: [spec-reviews] IntersectionObserver (#104) (Wednesday, 9 March)
• Re: [spec-reviews] IntersectionObserver (#104) (Wednesday, 9 March)
• Re: [spec-reviews] IntersectionObserver (#104) (Wednesday, 9 March)

Daniel Buchner

• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Thursday, 3 March)

Daniel Freedman

• Re: [webcomponents] Should shadow host have `display: block` by default? (#426) (Thursday, 24 March)

Daniel X Moore

• [directory-upload] Changed drop event listener to use EventTarget (#28) (Tuesday, 15 March)

David

• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)

David Baron

• Re: [w3ctag/spec-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] contributing.md document needed for tag reviews (#53) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] Privacy Mode (#101) (Thursday, 31 March)

Dimitri Glazkov

• Re: [webcomponents] What was the "element is being created" flag for? (#458) (Friday, 25 March)
• Re: [webcomponents] When does the base element queue matter? (#457) (Thursday, 24 March)
• Re: [webcomponents] Consider exposing Shadom DOM and Custom Elements only in secure contexts (#449) (Monday, 21 March)
• Re: [webcomponents] ShadowRoot innerHTML different from Element innerHTML (#443) (Wednesday, 16 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Wednesday, 16 March)
• Re: [webcomponents] Parse <slot> like <template> (#59) (Wednesday, 9 March)
• Re: [webcomponents] defineElement should not cache lifecycle callbacks and prototype of a custom element class (#417) (Monday, 7 March)
• Re: [webcomponents] defineElement should not cache lifecycle callbacks and prototype of a custom element class (#417) (Monday, 7 March)
• Re: [webcomponents] defineElement should not cache lifecycle callbacks and prototype of a custom element class (#417) (Monday, 7 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Monday, 7 March)
• Re: [webcomponents] Should HTML parser instantiate custom elements inside a template element? (#406) (Wednesday, 2 March)
• Re: [webcomponents] Should HTML parser instantiate custom elements inside a template element? (#406) (Wednesday, 2 March)
• Re: [webcomponents] Should HTML parser instantiate custom elements inside a template element? (#406) (Wednesday, 2 March)

Domenic Denicola

• Re: [whatwg/streams] Visualize the internal state machines (#29) (Thursday, 31 March)
• Re: [whatwg/streams] In the output, sometimes we end up with <b> when we should use <emu-val> (#428) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] Indexed DB getAll(), openKeyCursor() and objectStoreNames (#84) (Thursday, 31 March)
• Re: [w3c/webcomponents] define()'s context object is not a document (#471) (Wednesday, 30 March)
• Re: [w3c/webcomponents] Note about "custom" is misleading (#461) (Wednesday, 30 March)
• Re: [w3c/webcomponents] Editorial: "Remove the first element of actions, letting action be the result" (#476) (Wednesday, 30 March)
• Re: [w3c/webcomponents] Editorial: inconsistent use of authors/developers (#470) (Wednesday, 30 March)
• Re: [w3c/webcomponents] Editorial: "When it becomes" (#475) (Wednesday, 30 March)
• Re: [w3c/webcomponents] Element interfaces (#472) (Wednesday, 30 March)
• Re: [w3c/webcomponents] Editorial: inconsistent use of authors/developers (#470) (Wednesday, 30 March)
• Re: [w3c/webcomponents] Create an element type extension path with sync flag set should not enqueue upgrade; it should just upgrade (#469) (Wednesday, 30 March)
• [w3c/webcomponents] Create an element type extension path with sync flag set should not enqueue upgrade; it should just upgrade (#469) (Tuesday, 29 March)
• Re: [w3c/webcomponents] Cloning (#464) (Tuesday, 29 March)
• Re: [w3c/webcomponents] create an element does not always return result (#467) (Tuesday, 29 March)
• Re: [w3c/webcomponents] createElement and createElementNS() should check is attribute (#466) (Tuesday, 29 March)
• Re: [w3c/webcomponents] create an element has no context object (#462) (Tuesday, 29 March)
• Re: [w3c/webcomponents] Editorial: create an element step 3.4 (#459) (Tuesday, 29 March)
• Re: [w3c/webcomponents] Mutation: insert (#465) (Tuesday, 29 March)
• Re: [whatwg/streams] What should we call ReadableByteStream.prototype.getBYOBReader()? (#294) (Tuesday, 29 March)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Tuesday, 29 March)
• Re: [w3c/webcomponents] createElement and createElementNS() should check is attribute (#466) (Tuesday, 29 March)
• Re: [w3c/webcomponents] Cloning (#464) (Tuesday, 29 March)
• Re: [w3c/webcomponents] Editorial: create an element's "new element" step (#463) (Tuesday, 29 March)
• Re: [w3c/webcomponents] Note about "custom" is misleading (#461) (Tuesday, 29 March)
• Re: [w3c/webcomponents] Custom element callback naming (#460) (Tuesday, 29 March)
• Re: [streams] What should we call ReadableByteStream.prototype.getBYOBReader()? (#294) (Monday, 28 March)
• Re: [dom] Add caniuse info boxes like the HTML spec (#69) (Sunday, 27 March)
• Re: [webcomponents] What was the "element is being created" flag for? (#458) (Saturday, 26 March)
• Re: [webcomponents] What was the "element is being created" flag for? (#458) (Saturday, 26 March)
• Re: [webcomponents] What DOM content category do custom elements belong to? (#454) (Friday, 25 March)
• Re: [webcomponents] Typo in semantics (#349) (Friday, 25 March)
• Re: [webcomponents] What was the "element is being created" flag for? (#458) (Friday, 25 March)
• Re: [webcomponents] What was the "element is being created" flag for? (#458) (Friday, 25 March)
• Re: [webcomponents] What was the "element is being created" flag for? (#458) (Friday, 25 March)
• [webcomponents] What was the "element is being created" flag for? (#458) (Friday, 25 March)
• Re: [webidl] What should the property descriptor for @@unscopeable look like? (#102) (Friday, 25 March)
• Re: [webidl] What should the property descriptor for @@unscopeable look like? (#102) (Friday, 25 March)
• Re: [streams] Merge ReadableByteStream into ReadableStream (#430) (Friday, 25 March)
• Re: [streams] Merge ReadableByteStream into ReadableStream (#430) (Friday, 25 March)
• Re: [streams] Merge ReadableByteStream into ReadableStream (#430) (Friday, 25 March)
• Re: [webcomponents] When does the base element queue matter? (#457) (Friday, 25 March)
• Re: [webcomponents] When does the base element queue matter? (#457) (Friday, 25 March)
• Re: [webcomponents] When does the base element queue matter? (#457) (Friday, 25 March)
• Re: [webcomponents] When does the base element queue matter? (#457) (Friday, 25 March)
• Re: [webcomponents] When does the base element queue matter? (#457) (Thursday, 24 March)
• Re: [webcomponents] When does the base element queue matter? (#457) (Thursday, 24 March)
• Re: [webcomponents] Rename custom tag (#434) (Thursday, 24 March)
• Re: [webidl] Allow constructor<ClassType> as a type accepted by functions. (#101) (Thursday, 24 March)
• Re: [webidl] Allow constructor<ClassType> as a type accepted by functions. (#101) (Thursday, 24 March)
• Re: [webcomponents] Things to definitely document in non-normative notes (#368) (Thursday, 24 March)
• [webcomponents] When does the base element queue matter? (#457) (Thursday, 24 March)
• Re: [webidl] Allow constructor<ClassType> as a type accepted by functions. (#101) (Thursday, 24 March)
• Re: [webcomponents] Permit retrieval of registered classes from window.customElements (#445) (Thursday, 24 March)
• Re: [webidl] Allow constructor<ClassType> as a type accepted by functions. (#101) (Thursday, 24 March)
• Re: [webcomponents] Permit retrieval of registered classes from window.customElements (#445) (Thursday, 24 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Thursday, 24 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Thursday, 24 March)
• Re: [webcomponents] Upgrades need to run attributeChangedCallbacks and connectedCallback (#450) (Thursday, 24 March)
• Re: [webcomponents] Fix various typos (#456) (Thursday, 24 March)
• Re: [webcomponents] Fix various typos (#456) (Thursday, 24 March)
• Re: [webcomponents] What DOM content category do custom elements belong to? (#454) (Thursday, 24 March)
• Re: [fetch] Block 'image/*' resources loaded as script. (#261) (Thursday, 24 March)
• Re: [webcomponents] [Custom]: Add the possibility to extend the custom element (bugzilla: 26583) (#201) (Thursday, 24 March)
• Re: [webcomponents] What DOM content category do custom elements belong to? (#454) (Thursday, 24 March)
• Re: [fetch] Tight coupling between JS engine and browser engine (#263) (Thursday, 24 March)
• [dom] Reminder to update document's origin definition after HTML updates (#195) (Wednesday, 23 March)
• Re: [fetch] Block 'image/*' resources loaded as script. (#261) (Wednesday, 23 March)
• Re: [webcomponents] ES5 consideration for custom elements (#423) (Wednesday, 23 March)
• Re: [webcomponents] What DOM content category do custom elements belong to? (#454) (Wednesday, 23 March)
• Re: [webcomponents] ES5 consideration for custom elements (#423) (Tuesday, 22 March)
• Re: [webcomponents] ES5 consideration for custom elements (#423) (Tuesday, 22 March)
• Re: [webcomponents] Consider exposing Shadom DOM and Custom Elements only in secure contexts (#449) (Tuesday, 22 March)
• Re: [webcomponents] Consider exposing Shadom DOM and Custom Elements only in secure contexts (#449) (Tuesday, 22 March)
• Re: [streams] Merge ReadableByteStream into ReadableStream (#430) (Tuesday, 22 March)
• Re: [streams] Merge ReadableByteStream into ReadableStream (#430) (Tuesday, 22 March)
• Re: [streams] Merge ReadableByteStream into ReadableStream (#430) (Tuesday, 22 March)
• Re: [streams] Merge ReadableByteStream into ReadableStream (#430) (Tuesday, 22 March)
• Re: [streams] Merge ReadableByteStream into ReadableStream (#430) (Tuesday, 22 March)
• Re: [streams] Merge ReadableByteStream into ReadableStream (#430) (Tuesday, 22 March)
• Re: [streams] Merge ReadableByteStream into ReadableStream (#430) (Tuesday, 22 March)
• Re: [fetch] Setting strategy to control ReadableStream's internal buffer (#257) (Tuesday, 22 March)
• Re: [webcomponents] Fix typo (#453) (Tuesday, 22 March)
• Re: [webcomponents] Fix typo (#453) (Tuesday, 22 March)
• Re: [webcomponents] Parse <slot> like <template> (#59) (Tuesday, 22 March)
• Re: [webcomponents] Upstream Shadow DOM spec to DOM/HTML Standard (#377) (Tuesday, 22 March)
• [webcomponents] Upgrades need to run attributeChangedCallbacks and connectedCallback (#450) (Monday, 21 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Monday, 21 March)
• Re: [webcomponents] Define the behavior for sync element creation when a custom element constructor does various bad things (#412) (Monday, 21 March)
• Re: [webcomponents] Define the behavior for sync element creation when a custom element constructor does various bad things (#412) (Monday, 21 March)
• Re: [webcomponents] Unclear on how to define :defined in CSS + HTML (#439) (Monday, 21 March)
• Re: [webcomponents] Unclear on how to define :defined in CSS + HTML (#439) (Monday, 21 March)
• Re: [webcomponents] node.connectedToDocument (#81) (Monday, 21 March)
• Re: [webcomponents] Permit retrieval of registered classes from window.customElements (#445) (Monday, 21 March)
• Re: [webcomponents] Permit retrieval of registered classes from window.customElements (#445) (Monday, 21 March)
• Re: [webcomponents] Fix typo in "2.1.1" for attributeChangedCallback (#448) (Friday, 18 March)
• Re: [webcomponents] Fix typo in "2.1.1" for attributeChangedCallback (#448) (Friday, 18 March)
• Re: [webcomponents] node.connectedToDocument (#81) (Friday, 18 March)
• Re: [webcomponents] node.connectedToDocument (#81) (Friday, 18 March)
• Re: [webcomponents] node.connectedToDocument (#81) (Friday, 18 March)
• Re: [webcomponents] node.connectedToDocument (#81) (Friday, 18 March)
• Re: [webcomponents] node.connectedToDocument (#81) (Friday, 18 March)
• Re: [fetch] Give strategy as the second argument of ReadableStream (#254) (Friday, 18 March)
• Re: [xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Thursday, 17 March)
• Re: [xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Thursday, 17 March)
• Re: [webcomponents] Upstream Shadow DOM spec to DOM/HTML Standard (#377) (Thursday, 17 March)
• Re: [webcomponents] Permit retrieval of registered classes from window.customElements (#445) (Thursday, 17 March)
• Re: [webcomponents] Move defineElement elsewhere? (#431) (Thursday, 17 March)
• Re: [webcomponents] Fix typo in '2.1.1 Creating a custom tag' (#446) (Thursday, 17 March)
• Re: [webcomponents] Fix typo in '2.1.1 Creating a custom tag' (#446) (Thursday, 17 March)
• [fetch] ReadableStream constructor call is not quite right (#250) (Thursday, 17 March)
• [manifest] Editorial: some messed-up normative references (#431) (Thursday, 17 March)
• Re: [webcomponents] On-demand custom elements using modules (#444) (Thursday, 17 March)
• Re: [webcomponents] Permit retrieval of registered classes from window.customElements (#445) (Wednesday, 16 March)
• Re: [webcomponents] Move defineElement elsewhere? (#431) (Wednesday, 16 March)
• Re: [webcomponents] Move defineElement elsewhere? (#431) (Wednesday, 16 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Wednesday, 16 March)
• Re: [webidl] Bug (sort of) (#98) (Wednesday, 16 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Wednesday, 16 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Wednesday, 16 March)
• Re: [webcomponents] On-demand custom elements using modules (#444) (Wednesday, 16 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Wednesday, 16 March)
• Re: [ServiceWorker] DOMParser within ServiceWorkers (#846) (Wednesday, 16 March)
• Re: [ServiceWorker] FetchEvent.respondWith does something weird with the body of a response (#850) (Wednesday, 16 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Tuesday, 15 March)
• Re: [encoding] Fix #18: remove UTF-16 support from TextEncoder (#36) (Tuesday, 15 March)
• Re: [fetch] referrer same-origin constraint is a footgun for people trying to "copy" a Request (#245) (Tuesday, 15 March)
• Re: [dom] List subclasses explicitly or not (#190) (Tuesday, 15 March)
• Re: [webcomponents] Move innerHTML from ShadowRoot to DocumentFragment? (#441) (Tuesday, 15 March)
• Re: [webcomponents] Move innerHTML from ShadowRoot to DocumentFragment? (#441) (Tuesday, 15 March)
• [webcomponents] Unclear on how to define :defined in CSS + HTML (#439) (Tuesday, 15 March)
• Re: [webcomponents] Group registry related terminology under a heading (#437) (Tuesday, 15 March)
• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Tuesday, 15 March)
• Re: [webcomponents] Move defineElement elsewhere? (#431) (Tuesday, 15 March)
• Re: [webcomponents] Move defineElement elsewhere? (#431) (Tuesday, 15 March)
• Re: [webcomponents] Group registry related terminology under a heading (#437) (Tuesday, 15 March)
• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Tuesday, 15 March)
• Re: [fetch] referrer same-origin constraint is a footgun for people trying to "copy" a Request (#245) (Tuesday, 15 March)
• Re: [storage] Logo is not in a circle (#13) (Monday, 14 March)
• Re: [storage] Logo is not in a circle (#13) (Monday, 14 March)
• Re: [webcomponents] Rename custom tag (#434) (Monday, 14 March)
• Re: [webcomponents] Rename custom tag (#434) (Monday, 14 March)
• Re: [webcomponents] Rename custom tag (#434) (Monday, 14 March)
• Re: [webcomponents] Rename custom tag (#434) (Monday, 14 March)
• Re: [webcomponents] Rename custom tag (#434) (Monday, 14 March)
• Re: [webcomponents] Rename custom tag (#434) (Monday, 14 March)
• Re: [webcomponents] Rename custom tag (#434) (Monday, 14 March)
• Re: [webcomponents] Rename custom tag (#434) (Monday, 14 March)
• Re: [webcomponents] Rename custom tag (#434) (Monday, 14 March)
• Re: [webcomponents] Rename custom tag (#434) (Sunday, 13 March)
• Re: [webcomponents] Move defineElement elsewhere? (#431) (Friday, 11 March)
• Re: [webcomponents] Move defineElement elsewhere? (#431) (Friday, 11 March)
• Re: [webcomponents] Rename custom tag (#434) (Friday, 11 March)
• Re: [webcomponents] Define the syntax of the PotentialCustomElementName (#435) (Friday, 11 March)
• Re: [webcomponents] Mention that no new elements with a hyphen will be added to SVG and MathML either (#436) (Friday, 11 March)
• Re: [permissions] Let each permission refine its algorithms and store data. (#66) (Friday, 11 March)
• Re: [permissions] Let each permission refine its algorithms and store data. (#66) (Friday, 11 March)
• Re: [permissions] Let each permission refine its algorithms and store data. (#66) (Friday, 11 March)
• Re: [permissions] Let each permission refine its algorithms and store data. (#66) (Friday, 11 March)
• Re: [permissions] Let each permission refine its algorithms and store data. (#66) (Friday, 11 March)
• Re: [permissions] Let each permission refine its algorithms and store data. (#66) (Friday, 11 March)
• Re: [permissions] Let each permission refine its algorithms and store data. (#66) (Friday, 11 March)
• Re: [permissions] Let each permission refine its algorithms and store data. (#66) (Friday, 11 March)
• Re: [permissions] Let each permission refine its algorithms and store data. (#66) (Friday, 11 March)
• Re: [permissions] Let each permission refine its algorithms and store data. (#66) (Friday, 11 March)
• Re: [permissions] Let each permission refine its algorithms and store data. (#66) (Friday, 11 March)
• Re: [permissions] Let each permission refine its algorithms and store data. (#66) (Friday, 11 March)
• Re: [webcomponents] ARIA custom element API (#159) (Friday, 11 March)
• Re: [webcomponents] Move defineElement elsewhere? (#431) (Friday, 11 March)
• Re: [webcomponents] ARIA custom element API (#159) (Friday, 11 March)
• Re: [webcomponents] ARIA custom element API (#159) (Friday, 11 March)
• Re: [xhr] "Synchronous XMLHttpRequest outside of workers i..." (#59) (Friday, 11 March)
• Re: [webcomponents] ARIA custom element API (#159) (Friday, 11 March)
• Re: [xhr] "Synchronous XMLHttpRequest outside of workers i..." (#59) (Friday, 11 March)
• Re: [xhr] "Synchronous XMLHttpRequest outside of workers i..." (#59) (Friday, 11 March)
• Re: [xhr] "Synchronous XMLHttpRequest outside of workers i..." (#59) (Friday, 11 March)
• Re: [webcomponents] [Accessibility]: Custom element should allow declaration of default accessibility features, such as role and other ARIA attributes. (bugzilla: 20466) (#159) (Friday, 11 March)
• Re: [webcomponents] Group registry related terminology under a heading (#437) (Friday, 11 March)
• Re: [webcomponents] [Accessibility]: Custom element should allow declaration of default accessibility features, such as role and other ARIA attributes. (bugzilla: 20466) (#159) (Friday, 11 March)
• Re: [webcomponents] ES5 consideration for custom elements (#423) (Friday, 11 March)
• Re: [webcomponents] ES5 consideration for custom elements (#423) (Friday, 11 March)
• Re: [webcomponents] [Accessibility]: Custom element should allow declaration of default accessibility features, such as role and other ARIA attributes. (bugzilla: 20466) (#159) (Friday, 11 March)
• Re: [webcomponents] [Accessibility]: Custom element should allow declaration of default accessibility features, such as role and other ARIA attributes. (bugzilla: 20466) (#159) (Friday, 11 March)
• Re: [webcomponents] [Custom]: inflexible extends as fixed element type (bugzilla: 28158) (#143) (Friday, 11 March)
• Re: [webcomponents] [Custom]: inflexible extends as fixed element type (bugzilla: 28158) (#143) (Friday, 11 March)
• Re: [webcomponents] [Custom]: mixin pattern: custom elements should be able to extend any base tag with is= (bugzilla: 27977) (#153) (Friday, 11 March)
• Re: [webcomponents] [Custom]: mixin pattern: custom elements should be able to extend any base tag with is= (bugzilla: 27977) (#153) (Friday, 11 March)
• Re: [streams] Merge ReadableByteStream into ReadableStream (#430) (Friday, 11 March)
• Re: [webcomponents] Add authoring guidance for writing custom element constructors (#409) (Friday, 11 March)
• [webcomponents] Move defineElement elsewhere? (#431) (Friday, 11 March)
• Re: [webcomponents] Add conformance requirements for custom element constructors (00ed64f) (Friday, 11 March)
• Re: [webcomponents] defineElement should not cache lifecycle callbacks and prototype of a custom element class (#417) (Friday, 11 March)
• Re: [webcomponents] Add authoring guidance for writing custom element constructors (#409) (Friday, 11 March)
• Re: [webcomponents] Changes to element creation during parsing per F2F (#366) (Thursday, 10 March)
• Re: [webcomponents] Changes to element creation during parsing per F2F (#366) (Thursday, 10 March)
• Re: [webcomponents] [Custom]: Integrate with the HTML Parser (#165) (Thursday, 10 March)
• Re: [webcomponents] Make sure the parser delivers exceptions during element creation to "report an exception" (#151) (Thursday, 10 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Thursday, 10 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Thursday, 10 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Thursday, 10 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Thursday, 10 March)
• Re: [fetch] Merge HTML5 and Fetch definitions of 'HTTPS state' (#241) (Thursday, 10 March)
• Re: [webcomponents] defined promise (#427) (Thursday, 10 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Thursday, 10 March)
• Re: [webcomponents] Should shadow host have `display: block` by default? (#426) (Thursday, 10 March)
• Re: [webcomponents] Should shadow host have `display: block` by default? (#426) (Thursday, 10 March)
• Re: [webcomponents] Should shadow host have `display: block` by default? (#426) (Thursday, 10 March)
• Re: [webcomponents] Parse <slot> like <template> (#59) (Thursday, 10 March)
• Re: [webcomponents] defined promise (#427) (Thursday, 10 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Thursday, 10 March)
• Re: [streams] Merge ReadableByteStream into ReadableStream (#430) (Thursday, 10 March)
• Re: [streams] Merge ReadableByteStream into ReadableStream (#430) (Thursday, 10 March)
• Re: [streams] Merge ReadableByteStream into ReadableStream (#430) (Thursday, 10 March)
• Re: [streams] Merge ReadableByteStream into ReadableStream (#430) (Thursday, 10 March)
• Re: [streams] Merge ReadableByteStream into ReadableStream (#430) (Thursday, 10 March)
• Re: [streams] Merge ReadableByteStream into ReadableStream (#430) (Thursday, 10 March)
• Re: [streams] Merge ReadableByteStream into ReadableStream (#430) (Wednesday, 9 March)
• Re: [streams] Merge ReadableByteStream into ReadableStream (#430) (Wednesday, 9 March)
• Re: [streams] Merge ReadableByteStream into ReadableStream (#430) (Wednesday, 9 March)
• Re: [streams] Change [[Invalidate]] to be an abstract operation (8cb0c82) (Wednesday, 9 March)
• Re: [streams] Move BYOBRequest after BYOBController and add FS example (b430f33) (Wednesday, 9 March)
• Re: [streams] Use Symbols for defining internal methods (1a8399f) (Wednesday, 9 March)
• [fetch] "For each protocol in protocols, combine `Sec-We..." (#240) (Wednesday, 9 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Wednesday, 9 March)
• Re: [webcomponents] Define the behavior for sync element creation when a custom element constructor does various bad things (#412) (Tuesday, 8 March)
• Re: [webcomponents] Add a developer-facing note explaining why is="" is necessary (#147) (Tuesday, 8 March)
• Re: [webcomponents] [Custom]: suggest note on requirements (bugzilla: 27751) (#166) (Tuesday, 8 March)
• Re: [webcomponents] [Custom]: Add support for focus navigation similar to input type=date (bugzilla: 25473) (#150) (Tuesday, 8 March)
• Re: [webcomponents] [Custom]: No way to unregister a component (bugzilla: 27975) (#152) (Tuesday, 8 March)
• Re: [webcomponents] [Custom]: No way to unregister a component (bugzilla: 27975) (#152) (Tuesday, 8 March)
• Re: [webcomponents] [Custom]: Tone of note doesn't reflect severity (bugzilla: 27538) (#171) (Tuesday, 8 March)
• Re: [webcomponents] [Custom]: Tone of note doesn't reflect severity (bugzilla: 27538) (#171) (Tuesday, 8 March)
• Re: [webcomponents] [Custom]: Make unresolved state an explicit flag. (bugzilla: 27762) (#160) (Tuesday, 8 March)
• Re: [webcomponents] [Custom]: Make unresolved state an explicit flag. (bugzilla: 27762) (#160) (Tuesday, 8 March)
• Re: [webcomponents] [Custom]: No way to differentiate attribute namespaces in attributeChanged callback (bugzilla: 24178) (#168) (Tuesday, 8 March)
• Re: [webcomponents] [Custom]: No way to differentiate attribute namespaces in attributeChanged callback (bugzilla: 24178) (#168) (Tuesday, 8 March)
• Re: [webcomponents] [Custom]: Be clear about whether attached callback should be enqueued when setting prototype (bugzilla: 27437) (#175) (Tuesday, 8 March)
• Re: [webcomponents] [Custom]: Be clear about whether attached callback should be enqueued when setting prototype (bugzilla: 27437) (#175) (Tuesday, 8 March)
• Re: [webcomponents] [Explainer]: attachedCallback / detachedCallback are now enteredView and leftView? (bugzilla: 24629) (#227) (Tuesday, 8 March)
• Re: [webcomponents] [Explainer]: attachedCallback / detachedCallback are now enteredView and leftView? (bugzilla: 24629) (#227) (Tuesday, 8 March)
• Re: [webcomponents] [Custom Elements] the `extends` property cannot be replaced (#326) (Tuesday, 8 March)
• Re: [webcomponents] [Custom Elements] the `extends` property cannot be replaced (#326) (Tuesday, 8 March)
• Re: [webcomponents] Custom elements' upgrade order is ambiguous in the case of a detached node (#420) (Tuesday, 8 March)
• Re: [webcomponents] Custom elements' upgrade order is ambiguous in the case of a detached node (#420) (Tuesday, 8 March)
• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)
• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)
• Re: [webcomponents] :unresolved vs :not(:upgraded) (#418) (Tuesday, 8 March)
• Re: [webcomponents] Custom elements need an explicit "upgraded" or "resolved" flag (#425) (Tuesday, 8 March)
• Re: [webcomponents] :unresolved vs :not(:upgraded) (#418) (Tuesday, 8 March)
• Re: [webcomponents] Custom elements need an explicit "upgraded" or "resolved" flag (#425) (Tuesday, 8 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Tuesday, 8 March)
• Re: [webcomponents] Change createElement(ln, typeExtension) to createElement(ln, { is }) (0abc10e) (Tuesday, 8 March)
• Re: [webcomponents] Change createElement(ln, typeExtension) to createElement(ln, { is }) (0abc10e) (Tuesday, 8 March)
• Re: [webcomponents] Change createElement(ln, typeExtension) to createElement(ln, { is }) (0abc10e) (Tuesday, 8 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Tuesday, 8 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Tuesday, 8 March)
• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)
• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)
• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Tuesday, 8 March)
• Re: [webcomponents] Define the behavior when a custom element constructor returns an element with a parent node. (#412) (Tuesday, 8 March)
• Re: [webcomponents] Add attributeFilter (#367) (Tuesday, 8 March)
• Re: [webcomponents] Add attributeFilter (#367) (Tuesday, 8 March)
• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)
• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)
• Re: [webcomponents] attributeChanged callback should be invoked on every attribute upon creation (#364) (Tuesday, 8 March)
• Re: [webcomponents] Change createElement(localName, typeExtension) to createElement(localName, { is }) (#408) (Tuesday, 8 March)
• Re: [webcomponents] "Creating an element" needs to be more precise, for upgrades (#424) (Tuesday, 8 March)
• Re: [webcomponents] "Creating an element" needs to be more precise, for upgrades (#424) (Tuesday, 8 March)
• Re: [fetch] Define the WebSocket client handshake in terms of Fetch (#236) (Tuesday, 8 March)
• Re: [webcomponents] [Custom] Should attachedCallback/detachedCallback callbacks be called when element is added to / removed from shadom dom which is attached to a in-document host? (bugzilla: 26943) (#191) (Tuesday, 8 March)
• Re: [webcomponents] [Custom] Should attachedCallback/detachedCallback callbacks be called when element is added to / removed from shadom dom which is attached to a in-document host? (bugzilla: 26943) (#191) (Tuesday, 8 March)
• Re: [webcomponents] [Custom] Should attachedCallback/detachedCallback callbacks be called when element is added to / removed from shadom dom which is attached to a in-document host? (bugzilla: 26943) (#191) (Tuesday, 8 March)
• Re: [webcomponents] Replace attached/detached callbacks with insertedIntoDocument/removedFromDocument (#362) (Tuesday, 8 March)
• Re: [webcomponents] Replace attached/detached callbacks with insertedIntoDocument/removedFromDocument (#362) (Tuesday, 8 March)
• Re: [webcomponents] [Custom] Should attachedCallback/detachedCallback callbacks be called when element is added to / removed from shadom dom which is attached to a in-document host? (bugzilla: 26943) (#191) (Tuesday, 8 March)
• Re: [webcomponents] "Creating an element" needs to be more precise, for upgrades (#424) (Tuesday, 8 March)
• Re: [webcomponents] Replace attached/detached callbacks with insertedIntoDocument/removedFromDocument (#362) (Tuesday, 8 March)
• Re: [webcomponents] [Custom] Should attachedCallback/detachedCallback callbacks be called when element is added to / removed from shadom dom which is attached to a in-document host? (bugzilla: 26943) (#191) (Tuesday, 8 March)
• Re: [dom] Make Attr a Node again (#102) (Tuesday, 8 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Tuesday, 8 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Tuesday, 8 March)
• Re: [webcomponents] Should :unresolved apply to elements that failed to upgrade? (#422) (Tuesday, 8 March)
• Re: [webcomponents] Should :unresolved apply to elements that failed to upgrade? (#422) (Tuesday, 8 March)
• Re: [webcomponents] Define the behavior when a custom element constructor returns an element with a parent node. (#412) (Tuesday, 8 March)
• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)
• Re: [webcomponents] :unresolved vs :not(:upgraded) (#418) (Tuesday, 8 March)
• [webcomponents] Custom elements need an explicit "upgraded" or "resolved" flag (#425) (Tuesday, 8 March)
• Re: [webcomponents] Should :unresolved apply to elements that failed to upgrade? (#422) (Tuesday, 8 March)
• Re: [webcomponents] Should :unresolved apply to elements that failed to upgrade? (#422) (Tuesday, 8 March)
• Re: [webcomponents] Custom elements' upgrade order is ambiguous in the case of a detached node (#420) (Tuesday, 8 March)
• Re: [webcomponents] Should HTML parser instantiate custom elements inside a template element? (#406) (Tuesday, 8 March)
• Re: [webcomponents] Should HTML parser instantiate custom elements inside a template element? (#406) (Tuesday, 8 March)
• Re: [webcomponents] Define the behavior when a custom element constructor returns an element with a parent node. (#412) (Monday, 7 March)
• Re: [webcomponents] [Custom] Should attachedCallback/detachedCallback callbacks be called when element is added to / removed from shadom dom which is attached to a in-document host? (bugzilla: 26943) (#191) (Monday, 7 March)
• Re: [webcomponents] [Custom] Should attachedCallback/detachedCallback callbacks be called when element is added to / removed from shadom dom which is attached to a in-document host? (bugzilla: 26943) (#191) (Monday, 7 March)
• Re: [webcomponents] "Creating an element" needs to be more precise, for upgrades (#424) (Monday, 7 March)
• Re: [webcomponents] "Creating an element" needs to be more precise, for upgrades (#424) (Monday, 7 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Monday, 7 March)
• [webcomponents] "Creating an element" needs to be more precise, for upgrades (#424) (Monday, 7 March)
• Re: [webcomponents] Replace attached/detached callbacks with insertedIntoDocument/removedFromDocument (#362) (Monday, 7 March)
• Re: [webcomponents] Replace attached/detached callbacks with insertedIntoDocument/removedFromDocument (#362) (Monday, 7 March)
• Re: [webcomponents] Should :unresolved apply to elements that failed to upgrade? (#422) (Monday, 7 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Monday, 7 March)
• Re: [webcomponents] [Custom]: Clarify in informative note that cloning/importing also enqueues created callback (bugzilla: 28092) (#144) (Monday, 7 March)
• Re: [webcomponents] [Custom]: callbacks don't deal with exceptions (#174) (Monday, 7 March)
• Re: [webcomponents] The algorithm "invoke callbacks" must halt as soon as one of callbacks throw an exception (#421) (Monday, 7 March)
• Re: [webcomponents] :unresolved vs :not(:upgraded) (#418) (Monday, 7 March)
• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Monday, 7 March)
• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Monday, 7 March)
• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Monday, 7 March)
• Re: [webcomponents] Rename the first argument of defineElement from type to localName (#416) (Monday, 7 March)
• Re: [webcomponents] [Custom]: sorted element queue definition is not in sync with Imports (bugzilla: 26638) (#200) (Monday, 7 March)
• Re: [webcomponents] Decouple custom elements from HTML imports (#413) (Monday, 7 March)
• Re: [webcomponents] Custom elements' upgrade order is ambiguous in the case of a detached node (#420) (Monday, 7 March)
• Re: [webcomponents] :unresolved vs :not(:upgraded) (#418) (Monday, 7 March)
• Re: [fetch] Define the WebSocket client handshake in terms of Fetch (#236) (Monday, 7 March)
• Re: [webcomponents] defineElement should not cache lifecycle callbacks and prototype of a custom element class (#417) (Monday, 7 March)
• Re: [url] Fix #101: always strip U+0009, U+000A, and U+000D (7b40216) (Monday, 7 March)
• Re: [webcomponents] I need clarity on the document license before I can continue editing (#415) (Monday, 7 March)
• Re: [webcomponents] I need clarity on the document license before I can continue editing (#415) (Monday, 7 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Monday, 7 March)
• Re: [webcomponents] The algorithm "invoke callbacks" must halt as soon as one of callbacks throw an exception (#421) (Monday, 7 March)
• Re: [webcomponents] Should :unresolved apply to elements that failed to upgrade? (#422) (Monday, 7 March)
• Re: [uievents] D3E and corelation with DOM4(W3C)/DOM(WHATWAG) and DOM3 Core (#19) (Monday, 7 March)
• Re: [uievents] D3E and corelation with DOM4(W3C)/DOM(WHATWAG) and DOM3 Core (#19) (Sunday, 6 March)
• Re: [webcomponents] defineElement should not cache lifecycle callbacks and prototype of a custom element class (#417) (Saturday, 5 March)
• Re: [webcomponents] Rename the first argument of defineElement from type to localName (#416) (Saturday, 5 March)
• Re: [streams] Merge ReadableByteStream into ReadableStream (#430) (Friday, 4 March)
• Re: [streams] Merge ReadableByteStream into ReadableStream (#430) (Friday, 4 March)
• Re: [streams] Merge ReadableByteStream into ReadableStream (#430) (Friday, 4 March)
• [webcomponents] I need clarity on the document license before I can continue editing (#415) (Friday, 4 March)
• Re: [fetch] Removed promise antipattern from code example (#227) (Friday, 4 March)
• Re: [streams] Merge ReadableByteStream into ReadableStream (#430) (Thursday, 3 March)
• Re: [streams] Merge ReadableByteStream into ReadableStream (#430) (Thursday, 3 March)
• Re: [streams] Merge ReadableByteStream into ReadableStream (#430) (Thursday, 3 March)
• Re: [streams] Merge ReadableByteStream into ReadableStream (#430) (Thursday, 3 March)
• Re: [streams] Merge ReadableByteStream into ReadableStream (#430) (Thursday, 3 March)
• Re: [streams] Merge ReadableByteStream into ReadableStream (#430) (Thursday, 3 March)
• Re: [streams] Merge ReadableByteStream into ReadableStream (#430) (Thursday, 3 March)
• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Thursday, 3 March)
• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Thursday, 3 March)
• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Thursday, 3 March)
• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Thursday, 3 March)
• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Thursday, 3 March)
• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Thursday, 3 March)
• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Thursday, 3 March)
• Re: [webcomponents] Remove `Callback` suffix from custom elements callbacks (#414) (Thursday, 3 March)
• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: Typo instantation ---> instantiation (bugzilla: 27914) (#155) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: Typo instantation ---> instantiation (bugzilla: 27914) (#155) (Thursday, 3 March)
• [webcomponents] Decouple custom elements from HTML imports (#413) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: Add informative text about importNode (bugzilla: 26576) (#202) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: Add informative text about importNode (bugzilla: 26576) (#202) (Thursday, 3 March)
• Re: [webcomponents] #dfn-set-prototype is unused (#283) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: Section 10 prototype is not defined (bugzilla: 27643) (#169) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: Make ES6 prose normative when ES6 ships (bugzilla: 25669) (#162) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: "All Algorithms in One Diagram" (bugzilla: 27780) (#158) (Thursday, 3 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Thursday, 3 March)
• Re: [webcomponents] Rewrite Custom Element Construction Algorithm (#403) (Thursday, 3 March)
• Re: [webcomponents] Rename registerElement and change API slightly (#365) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: SVG diagram accessibility (bugzilla: 27611) (#170) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: Convert all ES5 references to ES6 (bugzilla: 27405) (#163) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: Need to define global/Realm handling for registerElement (bugzilla: 27260) (#185) (Thursday, 3 March)
• Re: [webcomponents] Custom elements should not upgrade elements by setting prototype (bugzilla: 28544) (#134) (Thursday, 3 March)
• Re: [webcomponents] Remove the support for inherting from builtin subclasses of HTMLElement and SVGElement (bugzilla: 28547) (#133) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: Improve the wording in element upgrade algorithm (bugzilla: 27770) (#161) (Thursday, 3 March)
• Re: [webcomponents] Custom elements should call user defined constructor synchronously (bugzilla: 28543) (#137) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: Specify preference of localName and typeExtension in createElement (bugzilla: 26852) (#167) (Thursday, 3 March)
• Re: [fetch] Support full-duplex HTTP streaming (#229) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Thursday, 3 March)
• Re: [webcomponents] Should HTML parser instantiate custom elements inside a template element? (#406) (Wednesday, 2 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Wednesday, 2 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Wednesday, 2 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Wednesday, 2 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Wednesday, 2 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Wednesday, 2 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Wednesday, 2 March)
• Re: [fetch] Support full-duplex HTTP streaming (#229) (Wednesday, 2 March)
• Re: [webcomponents] Travis build is always broken and seems completely useless (#407) (Wednesday, 2 March)
• Re: [webcomponents] Travis build is always broken and seems completely useless (#407) (Wednesday, 2 March)
• [webcomponents] Add authoring guidance for writing custom element constructors (#409) (Wednesday, 2 March)
• [webcomponents] Change createElement(localName, typeExtension) to createElement(localName, { is }) (#408) (Wednesday, 2 March)
• [webcomponents] Travis build is always broken and seems completely useless (#407) (Wednesday, 2 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Wednesday, 2 March)
• Re: [fetch] Support full-duplex HTTP streaming (#229) (Wednesday, 2 March)
• Re: [webcomponents] Should HTML parser instantiate custom elements inside a template element? (#406) (Wednesday, 2 March)
• Re: [webcomponents] Should HTML parser instantiate custom elements inside a template element? (#406) (Wednesday, 2 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Wednesday, 2 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Wednesday, 2 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Wednesday, 2 March)
• Re: [fetch] Support full-duplex HTTP streaming (#229) (Wednesday, 2 March)
• Re: [webcomponents] Handle constructors that abuse return-override (4a09d96) (Wednesday, 2 March)
• Re: [webcomponents] Handle constructors that abuse return-override (4a09d96) (Wednesday, 2 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Wednesday, 2 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Tuesday, 1 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Tuesday, 1 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Tuesday, 1 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Tuesday, 1 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Tuesday, 1 March)
• [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Tuesday, 1 March)
• Re: [webcomponents] Rewrite Custom Element Construction Algorithm (#403) (Tuesday, 1 March)
• Re: [webcomponents] Rewrite Custom Element Construction Algorithm (#403) (Tuesday, 1 March)
• Re: [fetch] Removed promise antipattern from code example (#227) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: Clarify in informative note that cloning/importing also enqueues created callback (bugzilla: 28092) (#144) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: Clarify in informative note that cloning/importing also enqueues created callback (bugzilla: 28092) (#144) (Tuesday, 1 March)
• Re: [fetch] Removed promise antipattern from code example (#227) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: Consider creating registries for HTML documents created through DOMImplementation in some cases (bugzilla: 23018) (#236) (Tuesday, 1 March)
• [dom] className setter is not defined? (#183) (Tuesday, 1 March)

Dominique Hazael-Massieux

• Re: [w3ctag/spec-reviews] WebRTC (#14) (Thursday, 31 March)
• Re: [permissions] Run Tidy and fix ReSpec errors. (#69) (Thursday, 24 March)

Doug Schepers

• [touch-events] Changed license, changed WG info to CG, used CG stylesheet (#61) (Friday, 18 March)

Duan Yao

• Re: [whatwg/fullscreen] Allow fullscreen on initial load of a page (#36) (Thursday, 31 March)
• Re: [whatwg/fullscreen] Allow fullscreen on initial load of a page (#36) (Wednesday, 30 March)
• Re: [whatwg/fullscreen] Allow fullscreen on initial load of a page (#36) (Wednesday, 30 March)
• [whatwg/fullscreen] Allow fullscreen on initial load of a page (#36) (Wednesday, 30 March)

Duarte Cunha Leão

• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Thursday, 17 March)

Ehsan Akhgari

• [WebPlatformWG] Add ehsan to the list of SW f2f attendees (#21) (Monday, 28 March)
• Re: [fetch] Add "must-revalidate" to RequestCache enumeration (#165) (Thursday, 3 March)
• [fetch] "force-cache" RequestCache type should not bypass validation for responses that would vary (#233) (Wednesday, 2 March)
• [fetch] RequestCache "no-cache" type must also set the right headers (#232) (Wednesday, 2 March)
• [fetch] RequestCache "no-store" type must also set no-cache headers (#231) (Wednesday, 2 March)

Eli Grey

• Re: [ServiceWorker] WebRTC and getUserMedia within Service Worker (#670) (Wednesday, 2 March)

Elliott Sprehn

• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Tuesday, 8 March)
• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Tuesday, 8 March)
• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Tuesday, 8 March)
• Re: [webcomponents] defineElement should not cache lifecycle callbacks and prototype of a custom element class (#417) (Monday, 7 March)

Eric Bidelman

• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)
• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)

falsandtru

• Re: [IndexedDB] Ways to detect database manual deletions (#73) (Tuesday, 22 March)
• [IndexedDB] Ways to detect database manual deletions (#73) (Tuesday, 22 March)

Frederik

• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Sunday, 20 March)

Gary Kacmarcik

• Re: [w3c/uievents-key] CONTRIBUTING.md suggestions (#21) (Thursday, 31 March)
• Re: [w3c/uievents] Proposal for UIEvent "role" property (#21) (Thursday, 31 March)
• Re: [w3c/uievents] Proposal for UIEvent "role" property (#21) (Thursday, 31 March)
• Re: [w3c/uievents-key] CONTRIBUTING.md suggestions (#21) (Thursday, 31 March)
• Re: [w3c/uievents] Proposal for UIEvent "role" property (#21) (Thursday, 31 March)
• Re: [w3c/uievents-key] Grammar fix: "it's" => "its" (possessive adjective) (#17) (Thursday, 31 March)
• Re: [w3c/uievents-key] Fix typo: "Sktep" [sic] => "Step" (#16) (Thursday, 31 March)
• Re: [w3c/uievents-key] Fix syntax error in description of FnLock (#19) (Thursday, 31 March)
• Re: [w3c/uievents-key] Fix syntax error in description of FnLock (#19) (Thursday, 31 March)
• Re: [w3c/uievents-key] Fix syntax error in description of FnLock (#19) (Thursday, 31 March)
• Re: [w3c/uievents-key] Fix syntax error in description of FnLock (#19) (Thursday, 31 March)
• Re: [w3c/uievents-code] Typo in Tab key description? (#10) (Thursday, 31 March)
• Re: [w3c/uievents] Extraneous <code> in & after §12.1.2. Changes to DOM Level 2 event types (#82) (Tuesday, 29 March)
• Re: [uievents] The `resize` event isn't a UIEvent (#76) (Friday, 11 March)
• Re: [uievents] The `resize` event isn't a UIEvent (#76) (Friday, 11 March)
• Re: [uievents] The `resize` event isn't a UIEvent (#76) (Thursday, 10 March)
• Re: [uievents] The `resize` event isn't a UIEvent (#76) (Thursday, 10 March)
• Re: [uievents] For synthetic activation, should the original event still be dispatched? (#34) (Monday, 7 March)
• Re: [uievents] For synthetic activation, should the original event still be dispatched? (#34) (Monday, 7 March)
• Re: [uievents] Specify MouseEvent.which (#35) (Monday, 7 March)
• Re: [uievents] CompositionEvent constructor arguments name are atypical (#42) (Monday, 7 March)
• Re: [uievents] D3E and corelation with DOM4(W3C)/DOM(WHATWAG) and DOM3 Core (#19) (Sunday, 6 March)
• Re: [uievents] Fix minor syntax errors (#73) (Sunday, 6 March)
• Re: [uievents] Fire keydown/keyup during composition (#75) (Sunday, 6 March)
• Re: [uievents] Some list items not rendered properly (#74) (Sunday, 6 March)
• [uievents] Fire keydown/keyup during composition (#75) (Sunday, 6 March)
• Re: [uievents] "Modifier Keys" link in KeyboardEvent.getModifierState description is a 404 (#63) (Sunday, 6 March)
• Re: [uievents] "Modifier Keys" link in KeyboardEvent.getModifierState description is a 404 (#63) (Sunday, 6 March)
• Re: [uievents] D3E and corelation with DOM4(W3C)/DOM(WHATWAG) and DOM3 Core (#19) (Sunday, 6 March)
• Re: [uievents] D3E and corelation with DOM4(W3C)/DOM(WHATWAG) and DOM3 Core (#19) (Sunday, 6 March)
• Re: [uievents] #event-type-input and #event-type-beforeinput appear to have gone missing (#2) (Sunday, 6 March)
• Re: [uievents] Don't list modifier keys in the uievents spec (link to uievents-key instead) (#69) (Sunday, 6 March)
• Re: [uievents] Don't list modifier keys in the uievents spec (link to uievents-key instead) (#69) (Sunday, 6 March)
• Re: [uievents] Mechanism to differentiate pointer input from multiple users/devices missing (#16) (Sunday, 6 March)
• Re: [uievents] Mechanism to differentiate pointer input from multiple users/devices missing (#16) (Sunday, 6 March)
• Re: [uievents] #event-type-input and #event-type-beforeinput appear to have gone missing (#2) (Sunday, 6 March)
• Re: [uievents] Need to define UIEvent or link to where it's normatively defined (#30) (Sunday, 6 March)
• Re: [uievents] Need to define UIEvent or link to where it's normatively defined (#30) (Sunday, 6 March)
• Re: [uievents] When .getModifierState("OS") should be true? (#28) (Sunday, 6 March)
• Re: [uievents] When .getModifierState("OS") should be true? (#28) (Sunday, 6 March)
• Re: [uievents] Need to remove input/beforeinput event info from D3E and point to input event spec (#38) (Sunday, 6 March)
• Re: [uievents] Need to remove input/beforeinput event info from D3E and point to input event spec (#38) (Sunday, 6 March)
• Re: [uievents] CompositionEvent constructor arguments name are atypical (#42) (Sunday, 6 March)
• Re: [uievents] CompositionEvent constructor arguments name are atypical (#42) (Sunday, 6 March)
• Re: [uievents] "Introduced in this specification" in IDL not helpful (#46) (Sunday, 6 March)
• Re: [uievents] "Introduced in this specification" in IDL not helpful (#46) (Sunday, 6 March)
• Re: [uievents] Update refs to uievents-key and -code (#60) (Sunday, 6 March)
• Re: [uievents-code] Need 'Unspecified' value for KeyboardEvent.code (#3) (Sunday, 6 March)
• Re: [uievents-code] Need 'Unspecified' value for KeyboardEvent.code (#3) (Sunday, 6 March)
• Re: [uievents-code] [code] KeyboardEvent code spec should have featurephone section (#5) (Sunday, 6 March)
• Re: [uievents-key] Odd definition of '0' in Multimedia Numpad Keys section (#13) (Saturday, 5 March)
• Re: [uievents] Request 'inputType' field in Keyboard Event Viewer (#71) (Friday, 4 March)
• Re: [uievents] Request 'inputType' field in Keyboard Event Viewer (#71) (Friday, 4 March)
• Re: [uievents] Partial interfaces must not inherit (#36) (Friday, 4 March)
• Re: [uievents] Partial interfaces must not inherit (#36) (Friday, 4 March)
• Re: [uievents] Request 'inputType' field in Keyboard Event Viewer (#71) (Friday, 4 March)
• Re: [uievents] Request 'inputType' field in Keyboard Event Viewer (#71) (Friday, 4 March)
• Re: [clipboard-apis] Be explicit about before* events (#24) (Friday, 4 March)
• Re: [uievents] Use https://rawgit.com URL for Keyboard Event Viewer (#72) (Tuesday, 1 March)
• Re: [uievents] Use https://rawgit.com URL for Keyboard Event Viewer (#72) (Tuesday, 1 March)
• Re: [uievents] Request example for DomKey when Ctrl and CapsLock are both down (#70) (Tuesday, 1 March)

Gilmore Davidson

• Re: [webcomponents] Consider exposing Shadom DOM and Custom Elements only in secure contexts (#449) (Tuesday, 22 March)

gked

• Re: [selection-api] setBaseAndExtent() and setPositon() should be marked as "deprecated" (#67) (Wednesday, 16 March)
• [editing] CTRL+BACKSPACE or its equivalent behavior when deleting block elements (#117) (Thursday, 10 March)
• Re: [editing] Cancelable attribute should be removed from the spec because it already referenced in Event.idl (#100) (Friday, 4 March)

grmocg

• Re: [fetch] Support full-duplex HTTP streaming (#229) (Thursday, 3 March)
• Re: [fetch] Support full-duplex HTTP streaming (#229) (Thursday, 3 March)

Hadley Beeman

• Re: [w3ctag/spec-reviews] Geofencing FPWD (#89) (Thursday, 31 March)

Hallvord R. M. Steen

• Re: [fetch] Use `,` rather than `, ` for combine operation (#207) (Friday, 25 March)
• Re: [fetch] Use `,` rather than `, ` for combine operation (#207) (Friday, 25 March)
• Re: [fetch] Use `,` rather than `, ` for combine operation (#207) (Friday, 25 March)
• Re: [fetch] Use `,` rather than ` ,` for combine operation (#207) (Friday, 25 March)
• [clipboard-apis] Make sure examples and tests know that ClipboardEvent constructor is useless (#27) (Friday, 11 March)
• Re: [clipboard-apis] The ClipboardEvent constructor is strange (#10) (Friday, 11 March)
• Re: [clipboard-apis] The ClipboardEvent constructor is strange (#10) (Friday, 11 March)
• Re: [clipboard-apis] The ClipboardEvent constructor is strange (#10) (Friday, 11 March)
• Re: [clipboard-apis] The ClipboardEvent constructor is strange (#10) (Friday, 11 March)
• Re: [clipboard-apis] How should focus be managed? (#26) (Friday, 11 March)
• Re: [clipboard-apis] The ClipboardEvent constructor is strange (#10) (Tuesday, 8 March)
• Re: [editing] Add a mechanism to opt-in/opt-out editing features (#93) (Tuesday, 8 March)
• [clipboard-apis] Kill onbeforecopy, onbeforecut and onbeforepaste events (#25) (Tuesday, 8 March)
• Re: [clipboard-apis] Definition of editing host (#20) (Monday, 7 March)
• Re: [clipboard-apis] Expand explanation of UI state logic (#22) (Friday, 4 March)
• Re: [clipboard-apis] Add intro to 4. APIs from other specifications (#19) (Friday, 4 March)
• Re: [clipboard-apis] Add intro to 4. APIs from other specifications (#19) (Friday, 4 March)
• Re: [clipboard-apis] Be explicit about before* events (#24) (Friday, 4 March)

Harald Alvestrand

• Re: [webidl] Need an error for "User refused permission" (#95) (Saturday, 19 March)
• Re: [permissions] Need information about whether a permission is persistent or temporary (#63) (Wednesday, 16 March)
• Re: [permissions] Need information about whether a permission is persistent or temporary (#63) (Wednesday, 16 March)
• Re: [permissions] Add getUserMedia permissions (#10) (Wednesday, 16 March)
• [permissions] Re-entering agreed fixes to Media permissions (#68) (Tuesday, 15 March)
• [webidl] Need an error for "User refused permission" (#95) (Thursday, 3 March)
• [permissions] Need information about whether a permission is persistent or temporary (#63) (Wednesday, 2 March)
• [permissions] Need a procedure reference for "request permission" (#62) (Wednesday, 2 March)
• Re: [permissions] Mediacapture permissions (#57) (Tuesday, 1 March)

Hayato Ito

• Re: [w3c/webcomponents] Slots in a flat tree (#308) (Thursday, 31 March)
• Re: [w3c/webcomponents] Rename getAssignedNodes()? (#451) (Thursday, 31 March)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Thursday, 31 March)
• Re: [w3c/webcomponents] Slots in a flat tree (#308) (Thursday, 31 March)
• Re: [w3c/webcomponents] [Shadow] activeElement behavior seems to break encapsulation (#358) (Thursday, 31 March)
• Re: [w3c/webcomponents] Add delegatesFocus to the spec (#455) (Thursday, 31 March)
• Re: [w3c/webcomponents] Add delegatesFocus to the spec (#455) (Thursday, 31 March)
• Re: [w3c/webcomponents] Add delegatesFocus to the spec (#455) (Thursday, 31 March)
• Re: [w3c/webcomponents] Add delegatesFocus to the spec (#455) (Thursday, 31 March)
• Re: [w3c/webcomponents] Add delegatesFocus to the spec (#455) (Thursday, 31 March)
• Re: [w3c/webcomponents] Shadow DOM and requestPointerLock() (#192) (Thursday, 31 March)
• Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468) (Wednesday, 30 March)
• Re: [webcomponents] deepPath's definition is ambiguous when the event path contains a non-Node EventTarget (#432) (Monday, 28 March)
• Re: [webcomponents] deepPath's definition is ambiguous when the event path contains a non-Node EventTarget (#432) (Monday, 28 March)
• Re: [webcomponents] deepPath's definition is ambiguous when the event path contains a non-Node EventTarget (#432) (Monday, 28 March)
• Re: [webcomponents] deepPath's definition is ambiguous when the event path contains a non-Node EventTarget (#432) (Monday, 28 March)
• Re: [webcomponents] deepPath's definition is ambiguous when the event path contains a non-Node EventTarget (#432) (Monday, 28 March)
• Re: [webcomponents] deepPath's definition is ambiguous when the event path contains a non-Node EventTarget (#432) (Monday, 28 March)
• Re: [webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354) (Monday, 28 March)
• Re: [webcomponents] Use a parent/child relationship in the flat tree in the definition of some elements, i.e. <tr>/<td> (#404) (Monday, 28 March)
• Re: [webcomponents] Use a parent/child relationship in the flat tree in the definition of some elements, i.e. <tr>/<td> (#404) (Monday, 28 March)
• Re: [webcomponents] [Shadow] activeElement behavior seems to break encapsulation (#358) (Monday, 28 March)
• Re: [webcomponents] [Shadow] activeElement behavior seems to break encapsulation (#358) (Monday, 28 March)
• Re: [webcomponents] [Shadow] activeElement behavior seems to break encapsulation (#358) (Monday, 28 March)
• Re: [webcomponents] [Shadow] activeElement behavior seems to break encapsulation (#358) (Monday, 28 March)
• Re: [webcomponents] Slots in a flat tree (#308) (Monday, 28 March)
• Re: [webcomponents] Proposed change for Focus Navigation (#447) (Monday, 28 March)
• Re: [webcomponents] Proposed change for Focus Navigation (#447) (Monday, 28 March)
• Re: [webcomponents] [Shadow] activeElement behavior seems to break encapsulation (#358) (Monday, 28 March)
• Re: [webcomponents] [Shadow] activeElement behavior seems to break encapsulation (#358) (Saturday, 26 March)
• Re: [webcomponents] Define the timing when distribution happens (#73) (Friday, 25 March)
• Re: [webcomponents] Define the timing when distribution happens (#73) (Friday, 25 March)
• Re: [webcomponents] Composition Algorithm shouldn't unwrap slots (#308) (Thursday, 24 March)
• Re: [webcomponents] Composition Algorithm shouldn't unwrap slots (#308) (Thursday, 24 March)
• Re: [webcomponents] Rename getAssignedNodes()? (#451) (Thursday, 24 March)
• Re: [webcomponents] Proposed change for Focus Navigation (#447) (Thursday, 24 March)
• Re: [webcomponents] Proposed change for Focus Navigation (#447) (Thursday, 24 March)
• Re: [webcomponents] Figure out terminology for Shadow DOM that everyone agrees on (#382) (Thursday, 24 March)
• Re: [webcomponents] Figure out terminology for Shadow DOM that everyone agrees on (#382) (Thursday, 24 March)
• Re: [webcomponents] Composition Algorithm shouldn't unwrap slots (#308) (Thursday, 24 March)
• Re: [webcomponents] Should shadow host have `display: block` by default? (#426) (Thursday, 24 March)
• Re: [webcomponents] Rename getAssignedNodes()? (#451) (Thursday, 24 March)
• Re: [webcomponents] Input to flat tree children calculation algorithm seems wrong (#387) (Wednesday, 23 March)
• Re: [webcomponents] Figure out terminology for Shadow DOM that everyone agrees on (#382) (Wednesday, 23 March)
• Re: [webcomponents] Extend the slotting algorithm so that a slot can select an element which doesn't have slot attribute. (#343) (Wednesday, 23 March)
• Re: [webcomponents] Extend the slotting algorithm so that a slot can select an element which doesn't have slot attribute. (#343) (Wednesday, 23 March)
• [dom] Fix #193: Shadow: Fix shadow-including root (#194) (Wednesday, 23 March)
• [dom] "shadow-including root" should be recursive definition. (#193) (Wednesday, 23 March)
• Re: [webcomponents] Rename getAssignedNodes()? (#451) (Wednesday, 23 March)
• Re: [webcomponents] <slot> rendering (#452) (Wednesday, 23 March)
• Re: [webcomponents] <slot> rendering (#452) (Wednesday, 23 March)
• Re: [webcomponents] Upstream Shadow DOM spec to DOM/HTML Standard (#377) (Wednesday, 23 March)
• Re: [webcomponents] Extend the slotting algorithm so that a slot can select an element which doesn't have slot attribute. (#343) (Wednesday, 23 March)
• Re: [webcomponents] node.isConnected (#81) (Tuesday, 22 March)
• Re: [webcomponents] Upstream Shadow DOM spec to DOM/HTML Standard (#377) (Tuesday, 22 March)
• Re: [webcomponents] Proposed change for Focus Navigation (#447) (Tuesday, 22 March)
• Re: [webcomponents] Upstream Shadow DOM spec to DOM/HTML Standard (#377) (Tuesday, 22 March)
• Re: [webcomponents] When is the slotting algorithm run (#401) (Tuesday, 22 March)
• Re: [webcomponents] Consider exposing Shadom DOM and Custom Elements only in secure contexts (#449) (Tuesday, 22 March)
• Re: [webcomponents] Open/closed is associated with ShadowRoot, not shadow tree (#440) (Friday, 18 March)
• Re: [webcomponents] Open/closed is associated with ShadowRoot, not shadow tree (#440) (Friday, 18 March)
• Re: [webcomponents] [Fix #430] Use DocumentFragment's host concept (aa05726) (Friday, 18 March)
• Re: [webcomponents] Make ShadowRoot objects use DocumentFragment object's host concept (#430) (Friday, 18 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Friday, 18 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Friday, 18 March)
• Re: [webcomponents] Upstream Shadow DOM spec to DOM/HTML Standard (#377) (Thursday, 17 March)
• Re: [webcomponents] Shadow DOM and "insertion steps" / "removing steps" (#438) (Thursday, 17 March)
• Re: [webcomponents] Shadow DOM and "insertion steps" / "removing steps" (#438) (Thursday, 17 March)
• Re: [webcomponents] ShadowRoot innerHTML different from Element innerHTML (#443) (Thursday, 17 March)
• Re: [webcomponents] caretPositionFromPoint, elementFromPoint, and elementsFromPoint should respect shadow boundary (#313) (Thursday, 17 March)
• Re: [webcomponents] caretPositionFromPoint, elementFromPoint, and elementsFromPoint should respect shadow boundary (#313) (Thursday, 17 March)
• Re: [webcomponents] Shared mixin for Document and ShadowRoot (#91) (Thursday, 17 March)
• Re: [webcomponents] Define how shadow DOM should be handled when host is adopted to a new document (#182) (Thursday, 17 March)
• Re: [webcomponents] [Shadow] How should various document internal references work when SVG is being used in shadow DOM (bugzilla: 27380) (#179) (Thursday, 17 March)
• Re: [webcomponents] [Shadow]: inappropriate reference to CSS3-UI nav-index spec in focus navigation order (bugzilla: 28079) (#88) (Thursday, 17 March)
• Re: [webcomponents] [Shadow]: inappropriate reference to CSS3-UI nav-index spec in focus navigation order (bugzilla: 28079) (#88) (Thursday, 17 March)
• Re: [webcomponents] Define how shadow DOM should be handled when host is adopted to a new document (bugzilla: 27366) (#182) (Thursday, 17 March)
• Re: [webcomponents] scoped and relatedTargetScoped attributes are useless in Event, so remove then from Event interface (#442) (Thursday, 17 March)
• Re: [webcomponents] [Shadow] How should various document internal references work when SVG is being used in shadow DOM (bugzilla: 27380) (#179) (Thursday, 17 March)
• Re: [webcomponents] [Shadow]: Consider a notion of shared stylesheet (bugzilla: 15818) (#99) (Thursday, 17 March)
• Re: [webcomponents] [Shadow]: Consider a notion of shared stylesheet (bugzilla: 15818) (#99) (Thursday, 17 March)
• Re: [webcomponents] FKA: No defined way to get keyboard focus into and out of a shadow DOM component (bugzilla: 24106) (#228) (Thursday, 17 March)
• Re: [webcomponents] FKA: No defined way to get keyboard focus into and out of a shadow DOM component (bugzilla: 24106) (#228) (Thursday, 17 March)
• Re: [webcomponents] Sharing styles across custom elements (#282) (Thursday, 17 March)
• Re: [webcomponents] [Shadow]: Consider explicitly exporting CSS Variables across a shadow boundary (bugzilla: 17143) (#94) (Thursday, 17 March)
• Re: [webcomponents] [Shadow]: Consider explicitly exporting CSS Variables across a shadow boundary (bugzilla: 17143) (#94) (Thursday, 17 March)
• Re: [webcomponents] [Shadow]: Inheritance Model for Shadow DOM (bugzilla: 28587) (#93) (Thursday, 17 March)
• Re: [webcomponents] [Shadow]: Inheritance Model for Shadow DOM (bugzilla: 28587) (#93) (Thursday, 17 March)
• Re: [webcomponents] [Shadow]: Make event retargeting optional (bugzilla: 28444) (#89) (Thursday, 17 March)
• Re: [webcomponents] [Shadow]: Make event retargeting optional (bugzilla: 28444) (#89) (Thursday, 17 March)
• Re: [webcomponents] [Shadow] investigate if there should be deepRelatedTargets and touch.deepTargets (bugzilla: 28560) (#76) (Thursday, 17 March)
• Re: [webcomponents] [Shadow]: Focus navigation in distributed content (#103) (Thursday, 17 March)
• Re: [webcomponents] [Shadow]: Focus navigation in distributed content (#103) (Thursday, 17 March)
• Re: [webcomponents] [Shadow] investigate if there should be deepRelatedTargets and touch.deepTargets (bugzilla: 28560) (#76) (Thursday, 17 March)
• Re: [webcomponents] [Shadow]: <content> usage in a place where non-flow content is expected (bugzilla: 22107) (#95) (Wednesday, 16 March)
• Re: [webcomponents] [Shadow]: <content> usage in a place where non-flow content is expected (bugzilla: 22107) (#95) (Wednesday, 16 March)
• Re: [webcomponents] [Shadow]: Define the impact of ordering on relevant HTML elements (bugzilla: 25563) (#183) (Wednesday, 16 March)
• Re: [webcomponents] [Shadow]: Define the impact of ordering on relevant HTML elements (bugzilla: 25563) (#183) (Wednesday, 16 March)
• Re: [webcomponents] Bikeshed: Nice to have a standard notation to explain a structure of a tree of trees. (#348) (Wednesday, 16 March)
• Re: [webcomponents] Bikeshed: Nice to have a standard notation to explain a structure of a tree of trees. (#348) (Wednesday, 16 March)
• Re: [webcomponents] [Shadow] investigate if there should be deepRelatedTargets and touch.deepTargets (bugzilla: 28560) (#76) (Wednesday, 16 March)
• Re: [webcomponents] [Shadow] investigate if there should be deepRelatedTargets and touch.deepTargets (bugzilla: 28560) (#76) (Wednesday, 16 March)
• Re: [webcomponents] [Shadow]: Add support for external stylesheets using link rel="stylesheet" (bugzilla: 22539) (#82) (Wednesday, 16 March)
• Re: [webcomponents] [Shadow]: Each section on the spec needs examples (bugzilla: 24639) (#84) (Wednesday, 16 March)
• Re: [webcomponents] [Shadow]: Each section on the spec needs examples (bugzilla: 24639) (#84) (Wednesday, 16 March)
• Re: [webcomponents] scoped and relatedTargetScoped attributes are useless in Event, so remove then from Event interface (#442) (Wednesday, 16 March)
• Re: [webcomponents] ShadowRoot innerHTML different from Element innerHTML (#443) (Wednesday, 16 March)
• Re: [webcomponents] Move innerHTML from ShadowRoot to DocumentFragment? (#441) (Wednesday, 16 March)
• Re: [webcomponents] Move innerHTML from ShadowRoot to DocumentFragment? (#441) (Wednesday, 16 March)
• Re: [webcomponents] Move innerHTML from ShadowRoot to DocumentFragment? (#441) (Wednesday, 16 March)
• Re: [webcomponents] Styling of elements where attachShadow(...) not allowed (#376) (Wednesday, 16 March)
• Re: [webcomponents] Figure out how form owner should work in shadow DOM (#196) (Wednesday, 16 March)
• Re: [webcomponents] Move innerHTML from ShadowRoot to DocumentFragment? (#441) (Wednesday, 16 March)
• Re: [dom] List subclasses explicitly or not (#190) (Wednesday, 16 March)
• Re: [webcomponents] scoped and relatedTargetScoped attributes are useless in Event, so remove then from Event interface (#442) (Wednesday, 16 March)
• Re: [webcomponents] <iframe> and the History API (#184) (Tuesday, 15 March)
• Re: [webcomponents] <iframe> and the History API (#184) (Tuesday, 15 March)
• Re: [webcomponents] <iframe> and the History API (#184) (Tuesday, 15 March)
• Re: [webcomponents] Open/closed is associated with ShadowRoot, not shadow tree (#440) (Tuesday, 15 March)
• Re: [dom] Shadow: add shadow root (b2ee400) (Tuesday, 15 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Monday, 14 March)
• Re: [webcomponents] Should relatedTargetScoped flag be set on mousedown/mouseup events? (#433) (Friday, 11 March)
• Re: [webcomponents] Should relatedTargetScoped flag be set on mousedown/mouseup events? (#433) (Friday, 11 March)
• Re: [webcomponents] Should relatedTargetScoped flag be set on mousedown/mouseup events? (#433) (Friday, 11 March)
• Re: [webcomponents] Integrate events with "get the parent" model (#429) (Thursday, 10 March)
• Re: [webcomponents] Integrate events with "get the parent" model (#429) (Thursday, 10 March)
• Re: [webcomponents] Integrate events with "get the parent" model (#429) (Thursday, 10 March)
• Re: [webcomponents] Shadow DOM, <style>, and document.styleSheets (#56) (Thursday, 10 March)
• Re: [webcomponents] Define the behavior of '::slotted' (the former name is '::content'). (#331) (Thursday, 10 March)
• Re: [webcomponents] cloneNode on ShadowRoot interface should throw NotSupportedError instead of DATA_CLONE_ERR (#393) (Thursday, 10 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Thursday, 10 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Thursday, 10 March)
• Re: [webcomponents] Should shadow host have `display: block` by default? (#426) (Thursday, 10 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Thursday, 10 March)
• Re: [webcomponents] Parse <slot> like <template> (#59) (Thursday, 10 March)
• Re: [webcomponents] Should shadow host have `display: block` by default? (#426) (Thursday, 10 March)
• Re: [webcomponents] Shared mixin for Document and ShadowRoot (#91) (Thursday, 10 March)
• Re: [webcomponents] Figure out how form owner should work in shadow DOM (#196) (Thursday, 10 March)
• Re: [webcomponents] Parse <slot> like <template> (#59) (Thursday, 10 March)
• Re: [webcomponents] Parse <slot> like <template> (#59) (Thursday, 10 March)
• Re: [webcomponents] Upstream Shadow DOM spec to DOM/HTML Standard (#377) (Wednesday, 9 March)
• Re: [webcomponents] Should shadow host have `display: block` by default? (#426) (Wednesday, 9 March)
• Re: [webcomponents] [Shadow]: Form elements crossing shadow boundary (bugzilla: 22443) (#65) (Tuesday, 8 March)
• Re: [webcomponents] [Shadow]: Form elements crossing shadow boundary (bugzilla: 22443) (#65) (Tuesday, 8 March)
• Re: [webcomponents] [Shadow]: Update constraints around stopping events (bugzilla: 20247) (#61) (Tuesday, 8 March)
• Re: [webcomponents] A negative tabindex on shadow host should be respected (#399) (Tuesday, 8 March)
• Re: [webcomponents] Shadow DOM and comment nodes (#411) (Tuesday, 8 March)
• Re: [webcomponents] Shadow DOM and comment nodes (#411) (Tuesday, 8 March)
• Re: [webcomponents] Shadow DOM and comment nodes (#411) (Tuesday, 8 March)
• Re: [webcomponents] Shadow DOM and comment nodes (#411) (Tuesday, 8 March)
• Re: [webcomponents] Shadow DOM and comment nodes (#411) (Tuesday, 8 March)
• Re: [webcomponents] [Shadow]: Node should expose their scope so that shared state can be scoped to components. (bugzilla: 22080) (#80) (Monday, 7 March)
• Re: [webcomponents] [Shadow]: Node should expose their scope so that shared state can be scoped to components. (bugzilla: 22080) (#80) (Monday, 7 March)
• Re: [webcomponents] [Shadow]: Node should expose their scope so that shared state can be scoped to components. (bugzilla: 22080) (#80) (Monday, 7 March)
• Re: [webcomponents] [Shadow]: Node should expose their scope so that shared state can be scoped to components. (bugzilla: 22080) (#80) (Monday, 7 March)
• Re: [webcomponents] [Shadow]: Node should expose their scope so that shared state can be scoped to components. (bugzilla: 22080) (#80) (Monday, 7 March)
• Re: [webcomponents] [Shadow]: Update constraints around stopping events (bugzilla: 20247) (#61) (Monday, 7 March)
• Re: [webcomponents] Clarify shadow DOM algorithms (#410) (Friday, 4 March)
• Re: [webcomponents] Clarify shadow DOM algorithms (#410) (Friday, 4 March)
• Re: [webcomponents] Clarify shadow DOM algorithms (#410) (Friday, 4 March)
• Re: [webcomponents] Shadow DOM and comment nodes (#411) (Friday, 4 March)
• Re: [webcomponents] Shadow DOM and comment nodes (#411) (Friday, 4 March)
• Re: [webcomponents] Figure out terminology for Shadow DOM that everyone agrees on (#382) (Friday, 4 March)
• Re: [webcomponents] I need clarity on the document license before I can continue editing (#415) (Friday, 4 March)
• Re: [webcomponents] Shadow DOM and comment nodes (#411) (Friday, 4 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Thursday, 3 March)
• Re: [webcomponents] Shadow DOM and comment nodes (#411) (Thursday, 3 March)
• Re: [webcomponents] Figure out terminology for Shadow DOM that everyone agrees on (#382) (Wednesday, 2 March)
• Re: [webcomponents] Figure out terminology for Shadow DOM that everyone agrees on (#382) (Wednesday, 2 March)
• Re: [webcomponents] Figure out terminology for Shadow DOM that everyone agrees on (#382) (Wednesday, 2 March)
• Re: [webcomponents] Figure out terminology for Shadow DOM that everyone agrees on (#382) (Wednesday, 2 March)
• Re: [webcomponents] When is the slotting algorithm run (#401) (Wednesday, 2 March)
• Re: [webcomponents] Figure out terminology for Shadow DOM that everyone agrees on (#382) (Wednesday, 2 March)
• Re: [webcomponents] Figure out terminology for Shadow DOM that everyone agrees on (#382) (Wednesday, 2 March)
• Re: [webcomponents] Add a non-normative note stating elements in shadow trees aren't exposed as named properties (#304) (Wednesday, 2 March)
• Re: [webcomponents] When is the slotting algorithm run (#401) (Wednesday, 2 March)
• Re: [webcomponents] "(Window is omitted)" (#389) (Tuesday, 1 March)
• Re: [webcomponents] Add dfn.js (#402) (Tuesday, 1 March)
• Re: [webcomponents] Ignore title attributes on style elements in shadow trees (#391) (Tuesday, 1 March)
• [webcomponents] Use a parent/child relationship in the flat tree in the definition of some elements, i.e. <tr>/<td> (#404) (Tuesday, 1 March)
• Re: [webcomponents] Add dfn.js (#402) (Tuesday, 1 March)

Henri Sivonen

• Re: [whatwg/encoding] Avoid teaching bad UTF-8 math. (#38) (Thursday, 31 March)
• [whatwg/encoding] Avoid teaching bad UTF-8 math. (#38) (Thursday, 31 March)

Henry Story

• Re: [fetch] error types too vague for TLS certificate error (#205) (Monday, 14 March)

hmottestad

• Re: [whatwg/fetch] URLs with username/password (#26) (Thursday, 31 March)
• Re: [fetch] URLs with username/password (#26) (Wednesday, 23 March)
• Re: [fetch] URLs with username/password (#26) (Wednesday, 23 March)
• Re: [fetch] URLs with username/password (#26) (Tuesday, 22 March)

hober

• [w3c/WebPlatformWG] I'll be at the upcoming SW F2F. (#22) (Monday, 28 March)

howientc

• Re: [fetch] Setting strategy to control ReadableStream's internal buffer (#257) (Tuesday, 22 March)
• Re: [fetch] Setting strategy to control ReadableStream's internal buffer (#257) (Tuesday, 22 March)
• [fetch] Setting strategy to control ReadableStream's internal buffer (#257) (Monday, 21 March)

Ian Kilpatrick

• Re: [webidl] Allow constructor<ClassType> as a type accepted by functions. (#101) (Thursday, 24 March)
• Re: [webidl] Allow constructor<ClassType> as a type accepted by functions. (#101) (Thursday, 24 March)
• Re: [webidl] Allow constructor<ClassType> as a type accepted by functions. (#101) (Thursday, 24 March)
• [webidl] Allow constructor<ClassType> as a type accepted by functions. (#101) (Thursday, 24 March)

ianbjacobs

• Re: [w3ctag/spec-reviews] Payments Drafts Review (#109) (Tuesday, 29 March)

Ilya Grigorik

• Re: [whatwg/fetch] Treat Last-Event-ID and Client-Hints headers as simple headers (#258) (Wednesday, 30 March)
• Re: [fetch] Treat Last-Event-ID and Client-Hints headers as simple headers (#258) (Tuesday, 22 March)
• Re: [fetch] Treat Last-Event-ID and Client-Hints headers as simple headers (#258) (Tuesday, 22 March)
• [fetch] Treat Last-Event-ID and Client-Hints headers as simple headers (#258) (Tuesday, 22 March)

in vacation

• Re: [w3c/manifest] Support window preferred/initial sizes (#436) (Wednesday, 30 March)

Jake Archibald

• Re: [slightlyoff/ServiceWorker] Allow caches to opt-in to granular cleanup (#863) (Thursday, 31 March)
• Re: [slightlyoff/ServiceWorker] `caches.match` search order (#862) (Thursday, 31 March)
• Re: [w3c/manifest] Privacy Review: how to handle navigation to a fullscreen'd application? (#402) (Thursday, 31 March)
• [slightlyoff/ServiceWorker] Allow caches to opt-in to granular cleanup (#863) (Thursday, 31 March)
• Re: [slightlyoff/ServiceWorker] `caches.match` search order (#862) (Thursday, 31 March)
• Re: [slightlyoff/ServiceWorker] `caches.match` search order (#862) (Thursday, 31 March)
• [w3c/manifest] Clarify how image objects should be fetched (#443) (Thursday, 31 March)
• Re: [whatwg/storage] Add API to allow origin to purge all storage (#4) (Thursday, 31 March)
• Re: [whatwg/storage] Allow all storage types to expire, not just cookies (#11) (Thursday, 31 March)
• Re: [whatwg/storage] Add API to allow origin to purge all storage (#4) (Thursday, 31 March)
• Re: [w3c/manifest] Support window preferred/initial sizes (#436) (Wednesday, 30 March)
• Re: [slightlyoff/ServiceWorker] Background caching (#574) (Wednesday, 30 March)
• Re: [slightlyoff/ServiceWorker] Background caching (#574) (Wednesday, 30 March)
• [WebPlatformWG] Update 11-12aprSW.md (#19) (Wednesday, 16 March)
• Re: [ServiceWorker] HTML5's Offline-first Council of Trent (#845) (Tuesday, 15 March)
• Re: [ServiceWorker] HTML5's Offline-first Council of Trent (#845) (Tuesday, 15 March)
• Re: [ServiceWorker] Fetch API respondWith's implicit RETURN (#844) (Monday, 14 March)
• Re: [ServiceWorker] Fetch API respondWith's implicit RETURN (#844) (Sunday, 13 March)
• Re: [ServiceWorker] Fetch API respondWith's implicit RETURN (#844) (Sunday, 13 March)
• Re: [ServiceWorker] Fetch API respondWith's implicit RETURN (#844) (Sunday, 13 March)
• Re: [ServiceWorker] Fetch API respondWith's implicit RETURN (#844) (Saturday, 12 March)
• Re: [ServiceWorker] Fetch API respondWith's implicit RETURN (#844) (Friday, 11 March)
• Re: [ServiceWorker] Fetch API respondWith's implicit RETURN (#844) (Friday, 11 March)
• Re: [ServiceWorker] Fetch API respondWith's implicit RETURN (#844) (Friday, 11 March)
• Re: [ServiceWorker] Fetch API respondWith's implicit RETURN (#844) (Friday, 11 March)
• Re: [ServiceWorker] Fetch API respondWith's implicit RETURN (#844) (Friday, 11 March)
• Re: [ServiceWorker] Fetch API respondWith's implicit RETURN (#844) (Friday, 11 March)
• Re: [ServiceWorker] Fetch API respondWith's implicit RETURN (#844) (Friday, 11 March)
• Re: [ServiceWorker] Fetch API respondWith's implicit RETURN (#844) (Friday, 11 March)
• Re: [ServiceWorker] Fetch API respondWith's implicit RETURN (#844) (Friday, 11 March)
• Re: [webcomponents] defined promise (#427) (Thursday, 10 March)
• [webcomponents] defined promise (#427) (Wednesday, 9 March)
• Re: [webcomponents] Custom elements need an explicit "upgraded" or "resolved" flag (#425) (Tuesday, 8 March)
• Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808) (Monday, 7 March)
• Re: [ServiceWorker] Is a new property to get the navigation's target client needed? (#817) (Friday, 4 March)
• Re: [ServiceWorker] setTimeout/setInterval are unreliable in ServiceWorkers (#838) (Wednesday, 2 March)
• Re: [ServiceWorker] setTimeout/setInterval are unreliable in ServiceWorkers (#838) (Wednesday, 2 March)
• Re: [ServiceWorker] WebRTC and getUserMedia within Service Worker (#670) (Wednesday, 2 March)
• Re: [ServiceWorker] WebRTC and getUserMedia within Service Worker (#670) (Wednesday, 2 March)
• Re: [fetch] Removed promise antipattern from code example (#227) (Tuesday, 1 March)
• Re: [fetch] Removed promise antipattern from code example (#227) (Tuesday, 1 March)
• Re: [ServiceWorker] setTimeout/setInterval are unreliable in ServiceWorkers (#838) (Tuesday, 1 March)
• Re: [fetch] Removed promise antipattern from code example (#227) (Tuesday, 1 March)

Jake Champion

• Re: [w3ctag/spec-reviews] Question: Should spec-review discussions live inside respective spec's repository? (#112) (Wednesday, 30 March)
• [w3ctag/spec-reviews] Question: Should spec-review discussions live inside respective spec's repository? (#112) (Wednesday, 30 March)

Jan Miksovsky

• Re: [w3c/webcomponents] Need "slotchange" event (#288) (Wednesday, 30 March)
• Re: [webcomponents] Rename getAssignedNodes()? (#451) (Thursday, 24 March)
• Re: [webcomponents] What DOM content category do custom elements belong to? (#454) (Tuesday, 22 March)
• [webcomponents] What DOM content category do custom elements belong to? (#454) (Tuesday, 22 March)
• Re: [webcomponents] Permit retrieval of registered classes from window.customElements (#445) (Friday, 18 March)
• [webcomponents] Permit retrieval of registered classes from window.customElements (#445) (Wednesday, 16 March)
• Re: [webcomponents] Move defineElement elsewhere? (#431) (Friday, 11 March)
• Re: [webcomponents] Add authoring guidance for writing custom element constructors (#409) (Friday, 11 March)
• Re: [webcomponents] Add authoring guidance for writing custom element constructors (#409) (Friday, 11 March)
• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)
• Re: [webcomponents] :unresolved vs :not(:upgraded) (#418) (Monday, 7 March)
• Re: [webcomponents] :unresolved vs :not(:upgraded) (#418) (Monday, 7 March)

Jan Prachař

• Re: [url] input can be empty string if url is not special (#106) (Thursday, 24 March)
• Re: [url] input can be empty string if url is not special (#106) (Thursday, 24 March)
• [url] input can be empty string if url is not special (#106) (Thursday, 24 March)

jan-ivar

• Re: [webidl] Please rename things that are legacy so it's clear they are (#100) (Monday, 21 March)
• Re: [webidl] Please rename things that are legacy so it's clear they are (#100) (Monday, 21 March)
• Re: [webidl] Need an error for "User refused permission" (#95) (Friday, 18 March)

Jarek Foksa

• Re: [webcomponents] Rename custom tag (#434) (Thursday, 24 March)
• Re: [webcomponents] Rename custom tag (#434) (Thursday, 24 March)
• Re: [webcomponents] Consider exposing Shadom DOM and Custom Elements only in secure contexts (#449) (Thursday, 24 March)
• Re: [webcomponents] Permit retrieval of registered classes from window.customElements (#445) (Thursday, 24 March)
• Re: [webcomponents] Permit retrieval of registered classes from window.customElements (#445) (Thursday, 24 March)
• Re: [webcomponents] defined promise (#427) (Thursday, 10 March)
• Re: [webcomponents] Should shadow host have `display: block` by default? (#426) (Wednesday, 9 March)

Jason Stewart

• Re: [xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Thursday, 24 March)
• Re: [xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Wednesday, 23 March)
• Re: [xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Tuesday, 22 March)
• Re: [xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Monday, 21 March)
• Re: [xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Monday, 21 March)
• Re: [xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Sunday, 20 March)
• Re: [xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Thursday, 17 March)
• Re: [xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Thursday, 17 March)
• Re: [xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Thursday, 17 March)
• Re: [xhr] Synchronous XMLHttpRequest outside of workers deprecation is not a good idea. (#60) (Thursday, 17 March)
• [xhr] Synchronous XMLHttpRequest outside of workers deprecation is not a good idea. (#60) (Wednesday, 16 March)

Jasum

• [dom] E (#196) (Friday, 25 March)

Jeff Burtoft

• Re: [w3c/manifest] Privacy Review: how to handle navigation to a fullscreen'd application? (#402) (Thursday, 31 March)
• Re: [w3c/manifest] Support window preferred/initial sizes (#436) (Wednesday, 30 March)
• Re: [w3c/manifest] Add description field to Manifest (#435) (Wednesday, 30 March)
• Re: [manifest] Integration with service workers (#161) (Tuesday, 22 March)

Jeffrey Yasskin

• Re: [w3c/permissions] Name the query, request, and revoke a permission algorithms. (#70) (Thursday, 31 March)
• Re: [w3c/permissions] Make Permissions.request() only take a single descriptor. (#72) (Thursday, 31 March)
• Re: [w3c/permissions] Define the 'get a permission storage identifier' algorithm. (#71) (Thursday, 31 March)
• Re: [w3c/permissions] Need a procedure reference for "request permission" (#62) (Thursday, 31 March)
• Re: [w3c/permissions] Name the query, request, and revoke a permission algorithms. (#70) (Wednesday, 30 March)
• Re: [w3c/permissions] Define a PermissionStorage type for each permission to store data with. (#73) (Tuesday, 29 March)
• Re: [w3c/permissions] Define a PermissionStorage type for each permission to store data with. (#73) (Tuesday, 29 March)
• Re: [w3c/permissions] Define a PermissionStorage type for each permission to store data with. (#73) (Tuesday, 29 March)
• Re: [w3c/permissions] Define a PermissionStorage type for each permission to store data with. (#73) (Tuesday, 29 March)
• Re: [w3c/permissions] Let each permission refine its algorithms and store data. (#66) (Monday, 28 March)
• Re: [permissions] Name the query, request, and revoke a permission algorithms. (#70) (Thursday, 24 March)
• Re: [permissions] Run Tidy and fix ReSpec errors. (#69) (Thursday, 24 March)
• Re: [permissions] Run Tidy and fix ReSpec errors. (#69) (Thursday, 24 March)
• Re: [permissions] Name the query, request, and revoke a permission algorithms. (68ab77e) (Thursday, 24 March)
• Re: [permissions] Name the query, request, and revoke a permission algorithms. (68ab77e) (Thursday, 24 March)
• Re: [permissions] Name the query, request, and revoke a permission algorithms. (#70) (Thursday, 24 March)
• Re: [permissions] Name the query, request, and revoke a permission algorithms. (#70) (Wednesday, 23 March)
• Re: [permissions] Name the query, request, and revoke a permission algorithms. (#70) (Wednesday, 23 March)
• Re: [permissions] Let each permission refine its algorithms and store data. (#66) (Wednesday, 23 March)
• [permissions] Define a PermissionStorage type for each permission to store data with. (#73) (Wednesday, 23 March)
• [permissions] Make Permissions.request() only take a single descriptor. (#72) (Wednesday, 23 March)
• [permissions] Define the 'get a permission storage identifier' algorithm. (#71) (Wednesday, 23 March)
• [permissions] Name the query, request, and revoke a permission algorithms. (#70) (Wednesday, 23 March)
• [permissions] Run Tidy and fix ReSpec errors. (#69) (Wednesday, 23 March)
• Re: [permissions] Let each permission refine its algorithms and store data. (#66) (Friday, 18 March)
• Re: [permissions] Let each permission refine its algorithms and store data. (#66) (Monday, 14 March)
• Re: [permissions] Let each permission refine its algorithms and store data. (#66) (Saturday, 12 March)
• Re: [permissions] Let each permission refine its algorithms and store data. (#66) (Friday, 11 March)
• Re: [permissions] Let each permission refine its algorithms and store data. (#66) (Friday, 11 March)
• Re: [permissions] Let each permission refine its algorithms and store data. (#66) (Friday, 11 March)
• Re: [permissions] Let each permission refine its algorithms and store data. (#66) (Friday, 11 March)
• Re: [permissions] Let each permission refine its algorithms and store data. (#66) (Friday, 11 March)
• Re: [permissions] Let each permission refine its algorithms and store data. (#66) (Friday, 11 March)
• Re: [permissions] Let each permission refine its algorithms and store data. (#66) (Friday, 11 March)
• Re: [permissions] Let each permission refine its algorithms and store data. (#66) (Friday, 11 March)
• Re: [permissions] Let each permission refine its algorithms and store data. (#66) (Friday, 11 March)
• Re: [permissions] Let each permission refine its algorithms and store data. (#66) (Friday, 11 March)
• Re: [permissions] Let each permission refine its algorithms and store data. (#66) (Friday, 11 March)
• [permissions] Let each permission refine its algorithms and store data. (#66) (Thursday, 10 March)
• Re: [permissions] Changing FATAL/WARNING signalling a little bit (#65) (Wednesday, 9 March)
• [permissions] Add terms to Shepherd (#64) (Wednesday, 9 March)

jeisinger

• Re: [whatwg/fetch] Referrer policy: Should request's referrer policy be updated in the main fetch? (#266) (Thursday, 31 March)
• Re: [whatwg/fetch] Referrer policy: Should request's referrer policy be updated in the main fetch? (#266) (Wednesday, 30 March)

jeremy

• [whatwg/encoding] org (#37) (Wednesday, 30 March)

Johannes Wilm

• Re: [selection-api] Need an API to get the current caret rects (#58) (Wednesday, 16 March)
• Re: [editing] Base definition and ordering of beforeInput/input events should be in UI events, but the editing specific stuff should be in a separate editing spec. (#99) (Monday, 7 March)

John Tregoning

• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)
• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)

Jonas Sicking

• Re: [whatwg/storage] Permissions API reflection for Persistent Permission (#14) (Thursday, 31 March)
• Re: [whatwg/storage] Use PermissionState instead of PersistentStoragePermission (#10) (Thursday, 31 March)
• Re: [whatwg/fetch] Allow * for Access-Control-Expose-Headers (#252) (Monday, 28 March)
• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Thursday, 24 March)
• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Thursday, 24 March)
• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Thursday, 24 March)
• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Wednesday, 23 March)
• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Wednesday, 23 March)
• Re: [fetch] Add new Access-Control-Suppress-Headers CORS response header (#253) (Wednesday, 23 March)
• Re: [fetch] Add new Access-Control-Suppress-Headers CORS response header (#253) (Wednesday, 23 March)
• Re: [fetch] Add new Access-Control-Suppress-Headers CORS response header (#253) (Tuesday, 22 March)
• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Tuesday, 22 March)
• Re: [fetch] Add new Access-Control-Suppress-Headers CORS response header (#253) (Tuesday, 22 March)
• Re: [IndexedDB] Consider adding a completion event or callback to the IDBDatabase.close() operation (#72) (Tuesday, 22 March)
• Re: [fetch] Add new Access-Control-Suppress-Headers CORS response header (#253) (Friday, 18 March)
• Re: [fetch] Add new Access-Control-Suppress-Headers CORS response header (#253) (Friday, 18 March)
• Re: [fetch] Add new Access-Control-Suppress-Headers CORS response header (#253) (Friday, 18 March)
• Re: [fetch] Update Access-Control-Expose-Headers CORS response header to allow * (allow-all) (#252) (Friday, 18 March)
• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Friday, 18 March)
• Re: [fetch] The reason why Access-Control-Request-Headers includes simple headers (#249) (Wednesday, 16 March)
• Re: [fetch] Handling of empty bodies (#246) (Tuesday, 15 March)
• Re: [fetch] Handling of empty bodies (#246) (Tuesday, 15 March)
• Re: [fetch] Handling of empty bodies (#246) (Monday, 14 March)
• Re: [fetch] Handling of empty bodies (#246) (Monday, 14 March)
• Re: [fetch] Handling of empty bodies (#246) (Saturday, 12 March)
• [fetch] Handling of empty bodies (#246) (Saturday, 12 March)

Jonathan Watt

• Re: [WICG/directory-upload] Consider to remove HTMLInputElement.getFilesAndDirectories andHTMLInputElement.getFiles (#33) (Wednesday, 30 March)
• Re: [WICG/directory-upload] Consider to remove HTMLInputElement.getFilesAndDirectories andHTMLInputElement.getFiles (#33) (Wednesday, 30 March)
• Re: [directory-upload] Consider how we could avoid the I/O blocking for FILE picking in addition to directory picking (#11) (Thursday, 24 March)
• Re: [directory-upload] Consider how we could avoid the I/O blocking for FILE picking in addition to directory picking (#11) (Thursday, 24 March)
• Re: [directory-upload] input.files shouldn't be null if directory attribute is used (or at least not if webkitdirectory attribute is also set) (#29) (Thursday, 24 March)
• Re: [directory-upload] input.files shouldn't be null if directory attribute is used (or at least not if webkitdirectory attribute is also set) (#29) (Thursday, 24 March)
• Re: [directory-upload] Consider renaming getDirectoriesAndFiles to getFSItems (#32) (Wednesday, 23 March)
• Re: [directory-upload] Consider renaming getDirectoriesAndFiles to getFSItems (#32) (Wednesday, 23 March)
• [directory-upload] Consider renaming getDirectoriesAndFiles to getFSItems (#32) (Wednesday, 23 March)
• Re: [directory-upload] easier way to determine if something is a directory? (#24) (Wednesday, 23 March)
• Re: [directory-upload] Should Directory be cloneable? (#27) (Wednesday, 23 March)
• Re: [directory-upload] Consider adding webkitrelativepath to the spec to be compatible with the web (#30) (Wednesday, 23 March)
• Re: [directory-upload] input.files shouldn't be null if directory attribute is used (or at least not if webkitdirectory attribute is also set) (#29) (Wednesday, 23 March)
• Re: [directory-upload] input.files shouldn't be null if directory attribute is used (or at least not if webkitdirectory attribute is also set) (#29) (Tuesday, 22 March)
• Re: [directory-upload] input.files shouldn't be null if directory attribute is used (or at least not if webkitdirectory attribute is also set) (#29) (Tuesday, 22 March)
• Re: [directory-upload] HTMLInputElement.directory should be a Directory attribute and not a boolean (#31) (Tuesday, 22 March)
• Re: [directory-upload] Easier way to get files without complicated asynchronous traversal code (#26) (Tuesday, 22 March)
• Re: [directory-upload] input.files shouldn't be null if directory attribute is used (or at least not if webkitdirectory attribute is also set) (#29) (Tuesday, 22 March)
• Re: [directory-upload] input.files shouldn't be null if directory attribute is used (or at least not if webkitdirectory attribute is also set) (#29) (Tuesday, 22 March)
• Re: [directory-upload] input.files shouldn't be null if directory attribute is used (or at least not if webkitdirectory attribute is also set) (#29) (Tuesday, 22 March)
• Re: [directory-upload] input.files shouldn't be null if directory attribute is used (or at least not if webkitdirectory attribute is also set) (#29) (Tuesday, 22 March)
• Re: [directory-upload] input.files shouldn't be null if directory attribute is used (or at least not if webkitdirectory attribute is also set) (#29) (Tuesday, 22 March)
• Re: [directory-upload] input.files shouldn't be null if directory attribute is used (or at least not if webkitdirectory attribute is also set) (#29) (Tuesday, 22 March)
• [fetch] Stop hardcoding the list of schemes that inherit HTTPS state (#255) (Friday, 18 March)
• Re: [webidl] Add a [SecureContext] operator attribute (#65) (Thursday, 10 March)
• Re: [fetch] Give user entered data: URI documents the HTTPS state 'modern' (#243) (Thursday, 10 March)
• [fetch] Give user entered data: URI documents the HTTPS state 'modern' (#243) (Thursday, 10 March)
• Re: [fetch] Merge HTML5 and Fetch definitions of 'HTTPS state' (#241) (Thursday, 10 March)
• [fetch] Merge HTML5 and Fetch definitions of 'HTTPS state' (#241) (Thursday, 10 March)

Josh Matthews

• Re: [ServiceWorker] Fetch API respondWith's implicit RETURN (#844) (Friday, 11 March)

Joshua Bell

• Re: [whatwg/storage] Classify cookies as site storage (#8) (Thursday, 31 March)
• Re: [whatwg/storage] Add API to allow origin to purge all storage (#4) (Thursday, 31 March)
• Re: [whatwg/storage] `estimate()` and `persistentEstimate()` incompatible with whole-origin persistence (#15) (Wednesday, 30 March)
• Re: [directory-upload] Consider renaming getDirectoriesAndFiles to fsitems or getFSItems (#32) (Wednesday, 23 March)
• Re: [IndexedDB] Consider adding a completion event or callback to the IDBDatabase.close() operation (#72) (Tuesday, 22 March)
• Re: [IndexedDB] Consider adding a completion event or callback to the IDBDatabase.close() operation (#72) (Tuesday, 22 March)
• Re: [IndexedDB] Ways to detect database manual deletions (#73) (Tuesday, 22 March)
• Re: [IndexedDB] Ways to detect database manual deletions (#73) (Tuesday, 22 March)
• Re: [IndexedDB] Consider adding a completion event or callback to the IDBDatabase.close() operation (#72) (Tuesday, 22 March)
• Re: [IndexedDB] Consider adding a completion event or callback to the IDBDatabase.close() operation (#72) (Monday, 21 March)
• Re: [IndexedDB] Consider adding a completion event or callback to the IDBDatabase.close() operation (#72) (Monday, 21 March)
• Re: [IndexedDB] Consider adding a completion event or callback to the IDBDatabase.close() operation (#72) (Monday, 21 March)
• Re: [IndexedDB] Key Paths: Support iteration step operator (#35) (Thursday, 17 March)
• Re: [encoding] Consider removing TextEncoder support for UTF-16 (#18) (Wednesday, 16 March)
• Re: [encoding] Consider removing TextEncoder support for UTF-16 (#18) (Wednesday, 16 March)
• Re: [encoding] Fix #18: remove UTF-16 support from TextEncoder (#36) (Tuesday, 15 March)
• Re: [storage] Logo is not in a circle (#13) (Monday, 14 March)
• Re: [encoding] Consider removing TextEncoder support for UTF-16 (#18) (Monday, 14 March)
• Re: [ServiceWorker] Fetch API respondWith's implicit RETURN (#844) (Saturday, 12 March)
• [WebPlatformWG] Add self to SW F2F attendees/agenda (#16) (Friday, 11 March)
• [IndexedDB] Add FileAPI reference (#70) (Thursday, 10 March)
• Re: [FileAPI] Blob.close() has several problems (#10) (Wednesday, 9 March)
• Re: [FileAPI] Controlling Blob URL's (#8) (Wednesday, 9 March)
• Re: [FileAPI] Controlling Blob URL's (#8) (Wednesday, 9 March)
• Re: [FileAPI] Bikeshedding the spec (#5) (Wednesday, 9 March)
• Re: [FileAPI] .msg MimeType Not Recognized (#15) (Wednesday, 9 March)
• Re: [FileAPI] .msg MimeType Not Recognized (#15) (Wednesday, 9 March)
• Re: [FileAPI] Persistent blob urls (#27) (Wednesday, 9 March)
• Re: [FileAPI] Persistent blob urls (#27) (Wednesday, 9 March)
• Re: [FileAPI] Consider using USVString for the Blob constructor (#30) (Wednesday, 9 March)
• [directory-upload] Should Directory be cloneable? (#27) (Tuesday, 1 March)

Joshua Nelson

• Re: [webcomponents] Consider exposing Shadom DOM and Custom Elements only in secure contexts (#449) (Monday, 21 March)

jpiesing

• Re: [spec-reviews] TV-Specific Web Subsetting (#105) (Wednesday, 16 March)

Julian Aubourg

• Re: [webcomponents] Rename custom tag (#434) (Monday, 14 March)
• Re: [webcomponents] Rename custom tag (#434) (Monday, 14 March)
• Re: [webcomponents] Rename custom tag (#434) (Monday, 14 March)

Jungkee Song

• Re: [slightlyoff/ServiceWorker] should update() during top level script evaluation be ignored? (#800) (Thursday, 31 March)
• Re: [slightlyoff/ServiceWorker] should update() during top level script evaluation be ignored? (#800) (Thursday, 31 March)
• Re: [slightlyoff/ServiceWorker] should update() during top level script evaluation be ignored? (#800) (Thursday, 31 March)
• Re: [ServiceWorker] should update() during top level script evaluation be ignored? (#800) (Friday, 25 March)
• Re: [ServiceWorker] Race in Schedule Job algorithm handling of equivalent job promises (#853) (Friday, 25 March)
• Re: [ServiceWorker] Race in Schedule Job algorithm handling of equivalent job promises (#853) (Friday, 25 March)
• Re: [ServiceWorker] Race in Schedule Job algorithm handling of equivalent job promises (#853) (Friday, 25 March)
• Re: [ServiceWorker] Race in Schedule Job algorithm handling of equivalent job promises (#853) (Thursday, 24 March)
• Re: [ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851) (Wednesday, 23 March)
• Re: [ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851) (Wednesday, 23 March)
• Re: [ServiceWorker] Install algorithm step 14 should clear waiting worker before updating state to redundant (#851) (Tuesday, 22 March)
• Re: [ServiceWorker] Update step 4 fails to fulfill job promise (#852) (Tuesday, 22 March)
• Re: [ServiceWorker] Update step 4 fails to fulfill job promise (#852) (Tuesday, 22 March)
• Re: [ServiceWorker] FetchEvent.respondWith does something weird with the body of a response (#850) (Friday, 18 March)
• Re: [ServiceWorker] What is the "Doom Installing Worker" algorithm supposed to be doing? (#847) (Thursday, 17 March)
• Re: [ServiceWorker] FetchEvent.respondWith does something weird with the body of a response (#850) (Thursday, 17 March)
• Re: [ServiceWorker] What is the "Doom Installing Worker" algorithm supposed to be doing? (#847) (Thursday, 17 March)
• [WebPlatformWG] Add jungkees to SW F2F attendees/agenda (#18) (Wednesday, 16 March)
• Re: [ServiceWorker] What is the "Doom Installing Worker" algorithm supposed to be doing? (#847) (Wednesday, 16 March)
• Re: [ServiceWorker] Fetch API respondWith's implicit RETURN (#844) (Friday, 11 March)
• Re: [ServiceWorker] Cache transactions & fixing `addAll` (#823) (Friday, 11 March)
• Re: [ServiceWorker] spec should be more explicit about accessing internal body on opaque Responses (#710) (Friday, 11 March)
• Re: [ServiceWorker] spec should be more explicit about accessing internal body on opaque Responses (#710) (Thursday, 10 March)
• Re: [ServiceWorker] spec should be more explicit about accessing internal body on opaque Responses (#710) (Thursday, 10 March)
• Re: [ServiceWorker] spec should be more explicit about accessing internal body on opaque Responses (#710) (Thursday, 10 March)
• Re: [ServiceWorker] spec should be more explicit about accessing internal body on opaque Responses (#710) (Wednesday, 9 March)
• Re: [ServiceWorker] Add worker modules (6d9500e) (Wednesday, 2 March)
• Re: [ServiceWorker] Support module service workers, and update for ES6 (#831) (Wednesday, 2 March)
• Re: [ServiceWorker] Support module service workers, and update for ES6 (#831) (Wednesday, 2 March)
• Re: [ServiceWorker] Add worker modules (9111303) (Wednesday, 2 March)
• Re: [ServiceWorker] Add worker modules (9111303) (Wednesday, 2 March)
• Re: [ServiceWorker] Add worker modules (9111303) (Wednesday, 2 March)

Justin Fagnani

• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)
• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)
• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Monday, 7 March)

Justin Rogers

• Re: [dom] Make Attr a Node again (#102) (Tuesday, 15 March)
• Re: [dom] Make Attr a Node again (#102) (Tuesday, 15 March)
• Re: [dom] Make Attr a Node again (#102) (Tuesday, 15 March)
• Re: [dom] Make Attr a Node again (#102) (Monday, 14 March)
• Re: [dom] Make Attr a Node again (#102) (Monday, 14 March)
• Re: [dom] Make Attr a Node again (#102) (Monday, 14 March)
• Re: [dom] Make Attr a Node again (#102) (Monday, 14 March)

Keith Yeung

• [fetch] Tight coupling between JS engine and browser engine (#263) (Thursday, 24 March)
• [xhr] Unclear algorithm used in step 4 of text response (#62) (Thursday, 17 March)

Kenji Baheux

• [spec-reviews] IntersectionObserver (#104) (Friday, 4 March)

Kenneth Rohde Christiansen

• Re: [w3c/manifest] Feat (splashscreens): Marked splashscreens as at risk (#439) (Thursday, 31 March)
• Re: [w3c/manifest] Add description field to Manifest (#435) (Thursday, 31 March)
• Re: [w3c/manifest] Add description field to Manifest (#435) (Thursday, 31 March)
• Re: [w3c/manifest] Feat (splashscreens): remove splash screen from spec (closes #9) (#440) (Thursday, 31 March)
• Re: [w3c/manifest] Privacy (#441) (Thursday, 31 March)
• Re: [w3c/manifest] Privacy (#441) (Thursday, 31 March)
• Re: [w3c/manifest] Privacy (#441) (Thursday, 31 March)
• Re: [w3c/manifest] Privacy (#441) (Thursday, 31 March)
• Re: [w3c/manifest] Privacy (#441) (Thursday, 31 March)
• Re: [w3c/manifest] Support window preferred/initial sizes (#436) (Wednesday, 30 March)
• Re: [w3c/manifest] Support window preferred/initial sizes (#436) (Wednesday, 30 March)
• Re: [w3c/manifest] Support window preferred/initial sizes (#436) (Tuesday, 29 March)
• Re: [w3c/manifest] Support window preferred/initial sizes (#436) (Tuesday, 29 March)
• Re: [w3c/manifest] Support window preferred/initial sizes (#436) (Tuesday, 29 March)
• [w3c/manifest] Support window preferred/initial sizes (#436) (Tuesday, 29 March)
• Re: [w3c/manifest] Add description field to Manifest (#435) (Tuesday, 29 March)
• Re: [w3c/manifest] Add description field to Manifest (#435) (Tuesday, 29 March)
• Re: [manifest] Ability to define platform-specific icon/splash style (#361) (Thursday, 24 March)
• Re: [manifest] Ability to define platform-specific icon/splash style (#361) (Thursday, 24 March)
• Re: [manifest] Allow developers to detect when the user has added the site to their home screen (or equivalent) (#417) (Wednesday, 23 March)
• Re: [manifest] Maintain list of sites that have a manifest (#404) (Tuesday, 22 March)
• Re: [manifest] Feat (dir member): Add dir member (closes #334) (#433) (Tuesday, 22 March)
• Re: [manifest] Feat (dir member): Add dir member (closes #334) (#433) (Tuesday, 22 March)
• Re: [manifest] Feat (l18n): define expected means of doing l18n (closes #323) (#434) (Tuesday, 22 March)
• Re: [manifest] Feat (l18n): define expected means of doing l18n (closes #323) (#434) (Tuesday, 22 March)
• Re: [manifest] Feat (l18n): define expected means of doing l18n (closes #323) (#434) (Tuesday, 22 March)
• Re: [manifest] Fix (references): correct messed up references (closes #431) (#432) (Friday, 18 March)
• Re: [manifest] 6.2: Fix member name to splash_screens (#430) (Tuesday, 15 March)
• Re: [manifest] Chaals patch 1 (#416) (Friday, 4 March)
• Re: [manifest] Abstract: clarifies new reader ambiguity (#423) (Friday, 4 March)
• Re: [manifest] 6.1: Shortens manifest cache time in example (#427) (Friday, 4 March)
• Re: [manifest] 1.2 Link Example: Aligns Example 1 with Example 2 (#425) (Friday, 4 March)
• Re: [manifest] 6.1 Grammar fix: "being return" to "being retuned" (#426) (Friday, 4 March)

Kevin Jackson

• Re: [webcomponents] Shadow DOM and comment nodes (#411) (Monday, 7 March)
• [webcomponents] Shadow DOM and comment nodes (#411) (Wednesday, 2 March)
• [webcomponents] Clarify shadow DOM algorithms (#410) (Wednesday, 2 March)

Kit Cambridge

• Re: [push-api] Expose options (#187) (Friday, 4 March)

KOLANICH

• Re: [permissions] Need information about whether a permission is persistent or temporary (#63) (Wednesday, 2 March)

Kornel

• Re: [slightlyoff/ServiceWorker] Allow caches to opt-in to granular cleanup (#863) (Thursday, 31 March)
• Re: [manifest] Manifest format should support some way of including a splash screen (#9) (Friday, 25 March)
• Re: [manifest] Manifest format should support some way of including a splash screen (#9) (Friday, 25 March)
• Re: [manifest] Manifest format should support some way of including a splash screen (#9) (Thursday, 24 March)
• Re: [manifest] Ability to define platform-specific icon/splash style (#361) (Thursday, 24 March)

Levi Weintraub

• Re: [w3c/webcomponents] Shadow dom: use css containment features by default (#355) (Monday, 28 March)

Lewis Phạm

• Re: [slightlyoff/ServiceWorker] `caches.match` search order (#862) (Thursday, 31 March)
• Re: [slightlyoff/ServiceWorker] `caches.match` search order (#862) (Thursday, 31 March)
• [slightlyoff/ServiceWorker] `caches.match` search order (#862) (Thursday, 31 March)

Louis Ryan

• Re: [fetch] Support full-duplex HTTP streaming (#229) (Monday, 14 March)
• Re: [fetch] Support full-duplex HTTP streaming (#229) (Monday, 14 March)
• Re: [fetch] Support full-duplex HTTP streaming (#229) (Wednesday, 2 March)
• Re: [fetch] Support full-duplex HTTP streaming (#229) (Wednesday, 2 March)
• Re: [fetch] Support full-duplex HTTP streaming (#229) (Wednesday, 2 March)
• [fetch] Support full-duplex HTTP streaming (#229) (Wednesday, 2 March)

malibuzios

• Re: [IndexedDB] Consider adding a completion event or callback to the IDBDatabase.close() operation (#72) (Tuesday, 22 March)
• Re: [IndexedDB] Rewindable cursors (#55) (Tuesday, 22 March)
• Re: [IndexedDB] Consider adding a completion event or callback to the IDBDatabase.close() operation (#72) (Tuesday, 22 March)
• Re: [IndexedDB] Consider adding a completion event or callback to the IDBDatabase.close() operation (#72) (Monday, 21 March)
• Re: [IndexedDB] Consider adding a completion event or callback to the IDBDatabase.close() operation (#72) (Monday, 21 March)
• Re: [IndexedDB] Consider adding a completion event or callback to the IDBDatabase.close() operation (#72) (Monday, 21 March)
• Re: [IndexedDB] Consider adding a completion event or callback to the IDBDatabase.close() operation (#72) (Monday, 21 March)
• Re: [IndexedDB] Consider adding some signaling method to notify on the completion of an IDBDatabase.close() operation (#72) (Sunday, 20 March)
• [IndexedDB] Consider adding some signaling method to notify on the completion of an IDBDatabase.close() operation (#72) (Sunday, 20 March)
• [IndexedDB] Consider adding some way to retrieve secondary keys when using IDBIndex.getAllKeys (#71) (Saturday, 19 March)

Marco

• Re: [manifest] Maintain list of sites that have a manifest (#404) (Tuesday, 22 March)

Marcos Caceres

• Re: [w3c/manifest] Feat (splashscreens): remove splash screen from spec (closes #9) (#440) (Thursday, 31 March)
• Re: [w3c/manifest] Privacy (#441) (Thursday, 31 March)
• Re: [w3c/manifest] Feat (splashscreens): Marked splashscreens as at risk (#439) (Thursday, 31 March)
• Re: [w3c/manifest] Deep linking - need proper use cases and requirements analysis (#363) (Thursday, 31 March)
• Re: [w3ctag/spec-reviews] ARIA (#107) (Thursday, 31 March)
• Re: [w3c/manifest] Privacy Review: how to handle navigation to a fullscreen'd application? (#402) (Thursday, 31 March)
• Re: [w3c/manifest] Ability to define platform-specific icon/splash style (#361) (Thursday, 31 March)
• [w3c/manifest] Privacy (#441) (Thursday, 31 March)
• Re: [w3c/manifest] Deep linking - need proper use cases and requirements analysis (#363) (Thursday, 31 March)
• Re: [w3c/manifest] Add integrity to image objects (#411) (Thursday, 31 March)
• Re: [w3c/manifest] Add integrity to image objects (#411) (Thursday, 31 March)
• Re: [w3c/manifest] Deep linking - need proper use cases and requirements analysis (#363) (Thursday, 31 March)
• Re: [w3c/manifest] A means to control how long a splash screen should remain on screen. (#372) (Thursday, 31 March)
• Re: [w3c/manifest] A means to control how long a splash screen should remain on screen. (#372) (Thursday, 31 March)
• Re: [w3c/manifest] Add description field to Manifest (#435) (Thursday, 31 March)
• Re: [w3c/manifest] Feat (splashscreens): remove splash screen from spec (closes #9) (#440) (Thursday, 31 March)
• [w3c/manifest] Feat (splashscreens): remove splash screen from spec (closes #9) (#440) (Thursday, 31 March)
• [w3c/manifest] Feat (splashscreens): Marked splashscreens as at risk (#439) (Thursday, 31 March)
• Re: [w3c/manifest] Fix (introduction): example math was wrong (closes #437) (e53263a) (Thursday, 31 March)
• [w3c/manifest] Fix (introduction): example math was wrong (closes #437) (#438) (Thursday, 31 March)
• Re: [w3c/manifest] Poorly coded example on w3c (#437) (Thursday, 31 March)
• Re: [w3c/manifest] Poorly coded example on w3c (#437) (Thursday, 31 March)
• Re: [w3c/manifest] Poorly coded example on w3c (#437) (Thursday, 31 March)
• Re: [manifest] Manifest format should support some way of including a splash screen (#9) (Friday, 25 March)
• Re: [manifest] Manifest format should support some way of including a splash screen (#9) (Friday, 25 March)
• Re: [manifest] Ability to define platform-specific icon/splash style (#361) (Thursday, 24 March)
• Re: [manifest] Manifest format should support some way of including a splash screen (#9) (Thursday, 24 March)
• Re: [permissions] Run Tidy and fix ReSpec errors. (#69) (Thursday, 24 March)
• Re: [permissions] Run Tidy and fix ReSpec errors. (#69) (Thursday, 24 March)
• Re: [permissions] Run Tidy and fix ReSpec errors. (#69) (Thursday, 24 March)
• Re: [manifest] Allow developers to detect when the user has added the site to their home screen (or equivalent) (#417) (Thursday, 24 March)
• Re: [manifest] Allow developers to detect when the user has added the site to their home screen (or equivalent) (#417) (Thursday, 24 March)
• Re: [manifest] Allow developers to detect when the user has added the site to their home screen (or equivalent) (#417) (Thursday, 24 March)
• Re: [manifest] Is prefer_related_applications too simplistic? (#365) (Thursday, 24 March)
• Re: [manifest] Add note about i18n (#323) (Thursday, 24 March)
• Re: [manifest] Feat (l18n): define expected means of doing l18n (closes #323) (#434) (Thursday, 24 March)
• Re: [manifest] Feat (l18n): define expected means of doing l18n (closes #323) (#434) (Thursday, 24 March)
• Re: [permissions] Run Tidy and fix ReSpec errors. (#69) (Thursday, 24 March)
• Re: [manifest] Allow developers to detect when the user has added the site to their home screen (or equivalent) (#417) (Wednesday, 23 March)
• Re: [manifest] Allow developers to detect when the user has added the site to their home screen (or equivalent) (#417) (Wednesday, 23 March)
• Re: [manifest] Allow developers to detect when the user has added the site to their home screen (or equivalent) (#417) (Wednesday, 23 March)
• Re: [manifest] Feat (l18n): define expected means of doing l18n (closes #323) (#434) (Wednesday, 23 March)
• Re: [manifest] Is prefer_related_applications too simplistic? (#365) (Wednesday, 23 March)
• Re: [manifest] Feat (l18n): define expected means of doing l18n (closes #323) (#434) (Wednesday, 23 March)
• Re: [manifest] Feat (l18n): define expected means of doing l18n (closes #323) (#434) (Wednesday, 23 March)
• Re: [manifest] Feat (l18n): define expected means of doing l18n (closes #323) (#434) (Wednesday, 23 March)
• Re: [manifest] Feat (l18n): define expected means of doing l18n (closes #323) (#434) (Wednesday, 23 March)
• Re: [manifest] Integration with service workers (#161) (Wednesday, 23 March)
• Re: [manifest] i18n: No direction metadata for 'name'; [I18N-ISSUE-416] (#334) (Tuesday, 22 March)
• Re: [manifest] Feat (dir member): Add dir member (closes #334) (#433) (Tuesday, 22 March)
• Re: [manifest] Feat (dir member): Add dir member (closes #334) (#433) (Tuesday, 22 March)
• Re: [manifest] Feat (dir member): Add dir member (closes #334) (#433) (Tuesday, 22 March)
• Re: [manifest] Maintain list of sites that have a manifest (#404) (Tuesday, 22 March)
• Re: [manifest] Ability to define platform-specific icon/splash style (#361) (Tuesday, 22 March)
• Re: [manifest] i18n: No localization model; [I18N-ISSUE-412] (#338) (Tuesday, 22 March)
• Re: [manifest] i18n: No localization model; [I18N-ISSUE-412] (#338) (Tuesday, 22 March)
• Re: [manifest] Triage privacy issues (#348) (Tuesday, 22 March)
• Re: [manifest] Triage privacy issues (#348) (Tuesday, 22 March)
• Re: [manifest] Integration with service workers (#161) (Tuesday, 22 March)
• Re: [manifest] Add note about i18n (#323) (Tuesday, 22 March)
• Re: [manifest] Add background color for splash screen. (#390) (Tuesday, 22 March)
• Re: [manifest] Add background color for splash screen. (#390) (Tuesday, 22 March)
• Re: [manifest] Allow developers to detect when the user has added the site to their home screen (or equivalent) (#417) (Tuesday, 22 March)
• Re: [manifest] Privacy Review: how to handle navigation to a fullscreen'd application? (#402) (Tuesday, 22 March)
• Re: [manifest] Add support for 9-Patch Images for splash screen (#373) (Tuesday, 22 March)
• Re: [manifest] Add support for 9-Patch Images for splash screen (#373) (Tuesday, 22 March)
• Re: [manifest] Add integrity to image objects (#411) (Tuesday, 22 March)
• Re: [manifest] Additional context for the Abstract (#392) (Tuesday, 22 March)
• Re: [manifest] Additional context for the Abstract (#392) (Tuesday, 22 March)
• [manifest] Feat (l18n): define expected means of doing l18n (closes #323) (#434) (Tuesday, 22 March)
• Re: [manifest] Feat (dir member): Add dir member (closes #334) (#433) (Tuesday, 22 March)
• Re: [manifest] Feat (dir member): Add dir member (closes #334) (#433) (Tuesday, 22 March)
• [manifest] Feat (dir member): Add dir member (closes #334) (#433) (Tuesday, 22 March)
• Re: [manifest] Maintain list of sites that have a manifest (#404) (Tuesday, 22 March)
• Re: [manifest] Maintain list of sites that have a manifest (#404) (Tuesday, 22 March)
• Re: [manifest] Manifest "sizes" fallback logic (#409) (Tuesday, 22 March)
• Re: [manifest] Are "hosted apps" in scope? (#340) (Tuesday, 22 March)
• Re: [manifest] Are "hosted apps" in scope? (#340) (Tuesday, 22 March)
• [manifest] Fix (references): correct messed up references (closes #431) (#432) (Friday, 18 March)
• Re: [webidl] Add a PermissionDeniedError (#99) (Thursday, 17 March)
• Re: [permissions] Add 'background-sync' permission (#60) (Wednesday, 16 March)
• Re: [permissions] Add pointerlock to the permissions enum? (#67) (Wednesday, 16 March)
• [permissions] Add pointerlock to the permissions enum? (#67) (Monday, 14 March)
• Re: [manifest] Don't publish if it's a pull request (#429) (Saturday, 12 March)
• Re: [url] URLSearchParams: calling .set() and .append() should return itself (#90) (Saturday, 12 March)
• Re: [url] URLSearchParams: calling .set() and .append() should return itself (#90) (Saturday, 12 March)
• Re: [directory-upload] It isn't clear whether Directory.path should include the name of the directory itself (#10) (Friday, 11 March)
• Re: [manifest] Handleing capabilities with Manifoldjs (#412) (Friday, 11 March)
• Re: [manifest] Handleing capabilities with Manifoldjs (#412) (Friday, 11 March)
• Re: [manifest] Remove reference to RFC5988. (#428) (Thursday, 10 March)
• Re: [manifest] Remove reference to RFC5988. (#428) (Thursday, 10 March)
• Re: [manifest] Is RFC5988 supported by implementers? (#424) (Thursday, 10 March)
• Re: [manifest] Is RFC5988 supported by implementers? (#424) (Thursday, 10 March)
• Re: [manifest] Chaals patch 1 (#416) (Sunday, 6 March)
• Re: [manifest] Chaals patch 1 (#416) (Friday, 4 March)

Marijn Kruisselbrink

• Re: [whatwg/fetch] Change how CORS filtered response filters the headers. (#265) (Wednesday, 30 March)
• Re: [whatwg/fetch] Change how CORS filtered response filters the headers. (#265) (Wednesday, 30 March)
• Re: [whatwg/fetch] Change how CORS filtered response filters the headers. (#265) (Tuesday, 29 March)
• Re: [whatwg/fetch] Change how CORS filtered response filters the headers. (#265) (Tuesday, 29 March)
• Re: [whatwg/fetch] Change how CORS filtered response filters the headers. (#265) (Tuesday, 29 March)
• Re: [whatwg/fetch] Change how CORS filtered response filters the headers. (#265) (Tuesday, 29 March)
• Re: [whatwg/fetch] Change how CORS filtered response filters the headers. (#265) (Tuesday, 29 March)
• [whatwg/fetch] Change how CORS filtered response filters the headers. (#265) (Monday, 28 March)
• Re: [FileAPI] Bikeshed the spec (#29) (Friday, 25 March)
• Re: [FileAPI] Bikeshedding the spec (#5) (Friday, 25 March)
• Re: [ServiceWorker] Define some way for foreign fetch to decide on opaqueness of responses (#841) (Thursday, 17 March)
• Re: [ServiceWorker] Define some way for foreign fetch to decide on opaqueness of responses (#841) (Wednesday, 16 March)
• Re: [ServiceWorker] Spec uses incorrect settings object when fetching a module worker (#849) (Wednesday, 16 March)
• Re: [ServiceWorker] What is the "Doom Installing Worker" algorithm supposed to be doing? (#847) (Wednesday, 16 March)
• [ServiceWorker] FetchEvent.respondWith does something weird with the body of a response (#850) (Tuesday, 15 March)
• [ServiceWorker] Spec uses incorrect settings object when fetching a module worker (#849) (Tuesday, 15 March)
• Re: [ServiceWorker] What is the "Doom Installing Worker" algorithm supposed to be doing? (#847) (Tuesday, 15 March)
• Re: [ServiceWorker] What is the "Doom Installing Worker" algorithm supposed to be doing? (#847) (Tuesday, 15 March)
• Re: [ServiceWorker] Support modifying cookies on an intercepted fetch (#837) (Friday, 4 March)
• Re: [ServiceWorker] Please deploy dfn.js or something similar (#489) (Tuesday, 1 March)

Mark Nottingham

• Re: [w3ctag/spec-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76) (Thursday, 31 March)
• Re: [fetch] PATCH verb (#50) (Wednesday, 23 March)
• Re: [fetch] Handling of empty bodies (#246) (Tuesday, 15 March)
• Re: [fetch] error types too vague for TLS certificate error (#205) (Monday, 14 March)
• Re: [spec-reviews] Privacy Mode (#101) (Wednesday, 9 March)
• Re: [fetch] Support full-duplex HTTP streaming (#229) (Friday, 4 March)
• Re: [fetch] Support full-duplex HTTP streaming (#229) (Thursday, 3 March)
• Re: [fetch] Support full-duplex HTTP streaming (#229) (Thursday, 3 March)
• Re: [fetch] Support full-duplex HTTP streaming (#229) (Thursday, 3 March)
• Re: [fetch] Support full-duplex HTTP streaming (#229) (Wednesday, 2 March)
• Re: [fetch] Proposal: Support GET bodies (#83) (Wednesday, 2 March)

Mark Rogers

• Re: [url] URL.pathname getter for file URLs produces odd result on Windows (#103) (Tuesday, 22 March)
• [url] URL.pathname getter for file URLs produces odd result on Windows (#103) (Monday, 21 March)

Markus Kobler

• Re: [ServiceWorker] DOMParser within ServiceWorkers (#846) (Friday, 18 March)
• Re: [ServiceWorker] DOMParser within ServiceWorkers (#846) (Wednesday, 16 March)
• [ServiceWorker] DOMParser within ServiceWorkers (#846) (Tuesday, 15 March)

Martin Thomson

• Re: [w3c/permissions] request/revoke (#46) (Tuesday, 29 March)
• Re: [permissions] request/revoke (#46) (Friday, 25 March)
• Re: [push-api] Expose options (#187) (Tuesday, 22 March)
• Re: [push-api] Expose options (#187) (Tuesday, 22 March)
• [push-api] Expose options (#187) (Friday, 4 March)

Masayuki Nakano

• Re: [uievents] Clarify expected DomKey for Ctrl+Alt+c on Android with default layout (#77) (Tuesday, 15 March)
• Re: [uievents] Request example for DomKey when Ctrl and CapsLock are both down (#70) (Tuesday, 1 March)

Mathias Bynens

• Re: [dom] High resolution timing for events (#23) (Monday, 14 March)

Matt Falkenhagen

• Re: [slightlyoff/ServiceWorker] should update() during top level script evaluation be ignored? (#800) (Thursday, 31 March)
• Re: [ServiceWorker] why does Register algorithm step 5.3.1 check for an active worker? (#856) (Monday, 28 March)
• Re: [ServiceWorker] if service-worker-allowed header changes should active worker be potentially unregistered? (#857) (Monday, 28 March)
• Re: [ServiceWorker] why does Register algorithm step 5.3.1 check for an active worker? (#856) (Monday, 28 March)
• Re: [ServiceWorker] What is the "Doom Installing Worker" algorithm supposed to be doing? (#847) (Wednesday, 16 March)
• [WebPlatformWG] Add falken to attendees (#17) (Wednesday, 16 March)
• Re: [ServiceWorker] What is the "Doom Installing Worker" algorithm supposed to be doing? (#847) (Wednesday, 16 March)

Melvyn Sopacua

• Re: [whatwg/url] Good defaults on URL() (#71) (Thursday, 31 March)
• [whatwg/url] Give optional argument to constructor a sane default (#108) (Thursday, 31 March)

Michael van Ouwerkerk

• Re: [push-api] Expose options (#187) (Tuesday, 22 March)
• Re: [push-api] Expose options (#187) (Monday, 21 March)

Michael[tm] Smith

• Re: [w3ctag/spec-reviews] Payments Drafts Review (#109) (Wednesday, 30 March)
• Re: [w3ctag/spec-reviews] Payments Drafts Review (#109) (Tuesday, 29 March)
• Re: [w3ctag/spec-reviews] Payments Drafts Review (#109) (Tuesday, 29 March)
• Re: [w3ctag/spec-reviews] Payments Drafts Review (#109) (Tuesday, 29 March)
• Re: [spec-reviews] Payments Drafts Review (#109) (Sunday, 27 March)
• Re: [xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Sunday, 20 March)
• Re: [webcomponents] Add authoring guidance for writing custom element constructors (#409) (Thursday, 3 March)
• Re: [webcomponents] Add authoring guidance for writing custom element constructors (#409) (Thursday, 3 March)

Michiel Bijl

• [clipboard-apis] How is focus managed? (#26) (Friday, 11 March)
• Re: [clipboard-apis] Add intro to 4. APIs from other specifications (#19) (Friday, 4 March)
• Re: [clipboard-apis] Be explicit about before* events (#24) (Thursday, 3 March)
• [clipboard-apis] Be explicit about before* events (#24) (Thursday, 3 March)
• [clipboard-apis] Add SVG reference to 3.2 Graphics with built-in semantics (#23) (Thursday, 3 March)
• [clipboard-apis] Expand explanation of UI state logic (#22) (Thursday, 3 March)
• [clipboard-apis] List of input types (#21) (Thursday, 3 March)
• [clipboard-apis] Definition of editing host (#20) (Thursday, 3 March)
• [clipboard-apis] Add intro to 4. APIs from other specifications (#19) (Thursday, 3 March)

Mike West

• Re: [w3ctag/spec-reviews] First Party Cookies (#114) (Thursday, 31 March)
• Re: [fetch] Block 'image/*' resources loaded as script. (#261) (Thursday, 24 March)
• Re: [fetch] Block 'image/*' resources loaded as script. (#261) (Thursday, 24 March)
• [fetch] Block 'image/*' resources loaded as script. (#261) (Wednesday, 23 March)
• Re: [webidl] Add a [SecureContext] operator attribute (#65) (Tuesday, 22 March)
• Re: [webidl] Add a [SecureContext] operator attribute (#65) (Tuesday, 22 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Friday, 11 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Friday, 11 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Friday, 11 March)
• Re: [fetch] Give user entered data: URI documents the HTTPS state 'modern' (#243) (Thursday, 10 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Thursday, 10 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Thursday, 10 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Thursday, 10 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Thursday, 10 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Thursday, 10 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Thursday, 10 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Thursday, 10 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Thursday, 10 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Wednesday, 9 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Wednesday, 9 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Wednesday, 9 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Wednesday, 9 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Wednesday, 9 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Wednesday, 9 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Wednesday, 9 March)
• Re: [fetch] Integrating support for PasswordCredential objects. (#237) (Wednesday, 9 March)
• [fetch] Integrating support for PasswordCredential objects. (#237) (Wednesday, 9 March)
• Re: [fetch] Define the WebSocket client handshake in terms of Fetch (#236) (Tuesday, 8 March)

Milan Raj

• Re: [webcomponents] ES5 consideration for custom elements (#423) (Tuesday, 22 March)
• Re: [webcomponents] ES5 consideration for custom elements (#423) (Tuesday, 22 March)
• Re: [webcomponents] ES5 consideration for custom elements (#423) (Tuesday, 22 March)
• Re: [webcomponents] ES5 consideration for custom elements (#423) (Tuesday, 22 March)

Monica Dinculescu

• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Wednesday, 2 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (bugzilla: 22056) (#239) (Tuesday, 1 March)

Mounir Lamouri

• Re: [w3c/manifest] Feat (splashscreens): Marked splashscreens as at risk (#439) (Thursday, 31 March)
• Re: [w3c/manifest] Feat (splashscreens): Marked splashscreens as at risk (#439) (Thursday, 31 March)
• Re: [permissions] Make Permissions.request() only take a single descriptor. (#72) (Thursday, 24 March)
• Re: [permissions] Run Tidy and fix ReSpec errors. (#69) (Thursday, 24 March)
• Re: [permissions] Define the 'get a permission storage identifier' algorithm. (#71) (Thursday, 24 March)
• Re: [permissions] Name the query, request, and revoke a permission algorithms. (#70) (Thursday, 24 March)
• Re: [permissions] Let each permission refine its algorithms and store data. (#66) (Wednesday, 23 March)
• Re: [permissions] Need a procedure reference for "request permission" (#62) (Wednesday, 23 March)
• Re: [manifest] Is prefer_related_applications too simplistic? (#365) (Wednesday, 23 March)
• Re: [manifest] Allow developers to detect when the user has added the site to their home screen (or equivalent) (#417) (Wednesday, 23 March)
• Re: [manifest] Feat (l18n): define expected means of doing l18n (closes #323) (#434) (Tuesday, 22 March)
• Re: [manifest] Privacy Review: how to handle navigation to a fullscreen'd application? (#402) (Tuesday, 22 March)
• Re: [manifest] Add integrity to image objects (#411) (Tuesday, 22 March)
• Re: [webidl] Need an error for "User refused permission" (#95) (Monday, 21 March)
• Re: [manifest] Editorial: some messed-up normative references (#431) (Friday, 18 March)
• Re: [manifest] Fix (references): correct messed up references (closes #431) (#432) (Friday, 18 March)
• Re: [fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) (Thursday, 17 March)
• Re: [fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) (Thursday, 17 March)
• Re: [permissions] Add 'background-sync' permission (#60) (Wednesday, 16 March)
• Re: [permissions] Add background-sync permission. (#61) (Wednesday, 16 March)
• Re: [permissions] Add getUserMedia permissions (#10) (Wednesday, 16 March)
• Re: [permissions] Add getUserMedia permissions (#10) (Wednesday, 16 March)
• [fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) (Tuesday, 15 March)
• Re: [permissions] Add pointerlock to the permissions enum? (#67) (Tuesday, 15 March)
• Re: [permissions] Re-entering agreed fixes to Media permissions (#68) (Tuesday, 15 March)
• Re: [permissions] Re-entering agreed fixes to Media permissions (#68) (Tuesday, 15 March)
• Re: [manifest] Is RFC5988 supported by implementers? (#424) (Saturday, 12 March)
• Re: [manifest] Remove reference to RFC5988. (#428) (Saturday, 12 March)
• Re: [manifest] Is RFC5988 supported by implementers? (#424) (Thursday, 10 March)
• Re: [manifest] Remove reference to RFC5988. (#428) (Saturday, 5 March)
• [manifest] Remove reference to RFC5988. (#428) (Saturday, 5 March)

Ms2ger

• Re: [webidl] Need an error for "User refused permission" (#95) (Saturday, 19 March)
• Re: [encoding] Consider removing TextEncoder support for UTF-16 (#18) (Thursday, 17 March)
• Re: [encoding] Fix #18: remove UTF-16 support from TextEncoder (#36) (Wednesday, 16 March)
• [fetch] WebSocket nits (#238) (Wednesday, 9 March)
• [FileAPI] Use `optional` for the Blob constructor (#33) (Wednesday, 2 March)

Nicholas Doty

• Re: [permissions] request/revoke (#46) (Friday, 25 March)

Nick Doty

• Re: [permissions] request/revoke (#46) (Friday, 25 March)
• Re: [permissions] request/revoke (#46) (Thursday, 24 March)
• Re: [manifest] Triage privacy issues (#348) (Tuesday, 22 March)

ojan

• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)

Olivier Lalonde

• Re: [fetch] Set content-length header of FormData requests? (#239) (Wednesday, 9 March)
• Re: [fetch] Set content-length header of FormData requests? (#239) (Wednesday, 9 March)
• [fetch] Set content-length header of FormData requests? (#239) (Wednesday, 9 March)

Owen Campbell-Moore

• [w3c/WebPlatformWG] Add Owen Campbell-Moore to remote attendees (#25) (Thursday, 31 March)
• [w3c/manifest] Add description field to Manifest (#435) (Monday, 28 March)
• Re: [ServiceWorker] Support modifying cookies on an intercepted fetch (#837) (Saturday, 5 March)
• Re: [ServiceWorker] Support modifying cookies on an intercepted fetch (#837) (Saturday, 5 March)
• Re: [ServiceWorker] Support modifying cookies on an intercepted fetch (#837) (Friday, 4 March)

Patrick H. Lauke

• Re: [touch-events] Spec should be explicit on whether the order of elements in TouchLists is relevant (#13) (Tuesday, 15 March)
• Re: [touch-events] Reformat code (#2) (Tuesday, 15 March)
• Re: [touch-events] Add Patrick Lauke to acknowledgements (2662687) (Monday, 7 March)
• Re: [touch-events] explicitly define what happens with Touch Events during scrolling, pinch-zoom, etc? (#60) (Sunday, 6 March)
• Re: [touch-events] explicitly define what happens with Touch Events during scrolling? (#60) (Sunday, 6 March)
• [touch-events] explicitly define what happens with Touch Events during scrolling? (#60) (Sunday, 6 March)

Paul Kinlan

• Re: [w3c/manifest] Support window preferred/initial sizes (#436) (Tuesday, 29 March)
• Re: [manifest] Manifest format should support some way of including a splash screen (#9) (Friday, 25 March)
• Re: [manifest] Maintain list of sites that have a manifest (#404) (Tuesday, 22 March)

Peter Beverloo

• Re: [push-api] Broadcast, Multi-Cast, or Topic messages via the Push API (#188) (Friday, 18 March)
• Re: [push-api] Broadcast, Multi-Cast, or Topic messages via the Push API (#188) (Friday, 18 March)
• Re: [push-api] Broadcast, Multi-Cast, or Topic messages via the Push API (#188) (Thursday, 17 March)
• Re: [push-api] Expose options (#187) (Wednesday, 16 March)
• Re: [push-api] Expose options (#187) (Wednesday, 16 March)
• Re: [push-api] Expose options (#187) (Wednesday, 16 March)
• Re: [push-api] Expose options (#187) (Wednesday, 16 March)
• Re: [push-api] Expose options (#187) (Wednesday, 16 March)
• Re: [push-api] Expose options (#187) (Wednesday, 16 March)
• Re: [push-api] Broadcast, Multi-Cast, or Topic messages via the Push API (#188) (Wednesday, 16 March)
• Re: [webidl] Need an error for "User refused permission" (#95) (Saturday, 5 March)

Peter Linss

• Re: [w3ctag/spec-reviews] CSS font-display (#71) (Thursday, 31 March)

Philip Jägenstedt

• Re: [xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Thursday, 24 March)
• Re: [xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Wednesday, 23 March)
• Re: [xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Tuesday, 22 March)
• Re: [webidl] Please rename things that are legacy so it's clear they are (#100) (Monday, 21 March)
• Re: [xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Monday, 21 March)
• Re: [xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Monday, 21 March)
• Re: [xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Saturday, 19 March)
• Re: [xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Thursday, 17 March)
• Re: [fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) (Thursday, 17 March)
• Re: [fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) (Thursday, 17 March)
• Re: [fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) (Thursday, 17 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Thursday, 17 March)
• Re: [fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) (Wednesday, 16 March)
• Re: [dom] Make Attr a Node again (#102) (Wednesday, 16 March)
• Re: [fullscreen] Allow fullscreen to be triggered by an orientation change event (#34) (Wednesday, 16 March)
• Re: [dom] Make Attr a Node again (#102) (Tuesday, 15 March)
• Re: [dom] Make Attr a Node again (#102) (Tuesday, 15 March)
• Re: [dom] Make Attr a Node again (#102) (Tuesday, 15 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Monday, 14 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Monday, 14 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Monday, 14 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Monday, 14 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Monday, 14 March)
• Re: [clipboard-apis] The ClipboardEvent constructor is strange (#10) (Friday, 11 March)
• Re: [clipboard-apis] The ClipboardEvent constructor is strange (#10) (Friday, 11 March)
• Re: [clipboard-apis] The ClipboardEvent constructor is strange (#10) (Friday, 11 March)
• Re: [clipboard-apis] event.clipboardData to be nullable, fixes #10 (07b6e98) (Friday, 11 March)
• Re: [webcomponents] Shadow DOM and the Fullscreen API (#180) (Thursday, 10 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Thursday, 10 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Thursday, 10 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Thursday, 10 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Thursday, 10 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Thursday, 10 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Thursday, 10 March)
• Re: [webcomponents] Shadow DOM and the Fullscreen API (#180) (Thursday, 10 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Thursday, 10 March)
• [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Wednesday, 9 March)
• Re: [webcomponents] Use FrozenArray<T> in WebIDL (#361) (Wednesday, 9 March)
• Re: [webcomponents] Use FrozenArray<T> in WebIDL (#361) (Wednesday, 9 March)
• Re: [clipboard-apis] The ClipboardEvent constructor is strange (#10) (Wednesday, 9 March)
• Re: [dom] The NodeFilter callback interface doesn't make sense (#186) (Tuesday, 8 March)
• [webidl] Object.getPrototypeOf(NodeFilter) should be Function.prototype, not Object.prototype (#96) (Tuesday, 8 March)
• Re: [dom] The NodeFilter callback interface doesn't make sense (#186) (Tuesday, 8 March)
• Re: [dom] The NodeFilter callback interface doesn't make sense (#186) (Tuesday, 8 March)
• Re: [dom] The NodeFilter callback interface doesn't make sense (#186) (Tuesday, 8 March)
• Re: [dom] The NodeFilter callback interface doesn't make sense (#186) (Tuesday, 8 March)
• [dom] The NodeFilter callback interface doesn't make sense (#186) (Tuesday, 8 March)
• Re: [dom] Make Attr a Node again (#102) (Tuesday, 8 March)
• Re: [dom] Make Attr a Node again (#102) (Tuesday, 8 March)
• Re: [uievents] Specify MouseEvent.which (#35) (Monday, 7 March)
• Re: [uievents] CompositionEvent constructor arguments name are atypical (#42) (Monday, 7 March)
• Re: [fullscreen] Compute sticky position? (#21) (Monday, 7 March)
• Re: [uievents] CompositionEvent constructor arguments name are atypical (#42) (Monday, 7 March)
• Re: [uievents] "Introduced in this specification" in IDL not helpful (#46) (Monday, 7 March)
• Re: [fullscreen] Fix #28: display:contents needs to compute to block in the top layer (8a662d2) (Saturday, 5 March)
• Re: [fullscreen] Fullscreen on non-HTML elements? (#22) (Saturday, 5 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Thursday, 3 March)
• Re: [selection-api] Make some arguments optional (#30) (Tuesday, 1 March)
• [selection-api] Make offset and allowPartialContainment arguments optional (#66) (Tuesday, 1 March)

Philippe Le Hegaret

• [manifest] Don't publish if it's a pull request (#429) (Friday, 11 March)
• Re: [uievents] The `resize` event isn't a UIEvent (#76) (Friday, 11 March)

ppppess

• Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808) (Monday, 7 March)
• Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808) (Monday, 7 March)
• Re: [ServiceWorker] What is FetchEvent.clientId for navigation requests (#808) (Saturday, 5 March)

raymeskhoury

• Re: [w3c/permissions] Define a PermissionStorage type for each permission to store data with. (#73) (Tuesday, 29 March)
• Re: [w3c/permissions] Define a PermissionStorage type for each permission to store data with. (#73) (Tuesday, 29 March)
• Re: [w3c/permissions] Define a PermissionStorage type for each permission to store data with. (#73) (Tuesday, 29 March)
• Re: [w3c/permissions] Define a PermissionStorage type for each permission to store data with. (#73) (Tuesday, 29 March)
• Re: [w3c/permissions] Define a PermissionStorage type for each permission to store data with. (#73) (Tuesday, 29 March)
• Re: [permissions] Let each permission refine its algorithms and store data. (#66) (Monday, 14 March)

Reilly Grant

• [spec-reviews] WebUSB (#108) (Monday, 21 March)

Richard Barnes

• Re: [webcomponents] Consider exposing Shadom DOM and Custom Elements only in secure contexts (#449) (Tuesday, 22 March)
• Re: [webcomponents] Consider exposing Shadom DOM and Custom Elements only in secure contexts (#449) (Tuesday, 22 March)
• Re: [webidl] Add a [SecureContext] operator attribute (#65) (Tuesday, 22 March)

Richard Maher

• Re: [push-api] Broadcast, Multi-Cast, or Topic messages via the Push API (#188) (Friday, 18 March)
• Re: [push-api] Broadcast, Multi-Cast, or Topic messages via the Push API (#188) (Thursday, 17 March)
• [push-api] Broadcast, Multi-Cast, or Topic messages via the Push API (#188) (Wednesday, 16 March)
• [ServiceWorker] HTML5's Offline-first Council of Trent (#845) (Monday, 14 March)
• Re: [ServiceWorker] Fetch API respondWith's implicit RETURN (#844) (Sunday, 13 March)
• Re: [ServiceWorker] Fetch API respondWith's implicit RETURN (#844) (Sunday, 13 March)
• Re: [ServiceWorker] Fetch API respondWith's implicit RETURN (#844) (Sunday, 13 March)
• Re: [ServiceWorker] Fetch API respondWith's implicit RETURN (#844) (Sunday, 13 March)
• Re: [ServiceWorker] Fetch API respondWith's implicit RETURN (#844) (Saturday, 12 March)
• Re: [ServiceWorker] Fetch API respondWith's implicit RETURN (#844) (Friday, 11 March)
• Re: [ServiceWorker] Fetch API respondWith's implicit RETURN (#844) (Friday, 11 March)
• Re: [ServiceWorker] Fetch API respondWith's implicit RETURN (#844) (Friday, 11 March)
• Re: [ServiceWorker] Fetch API respondWith's implicit RETURN (#844) (Friday, 11 March)
• Re: [ServiceWorker] Fetch API respondWith's implicit RETURN (#844) (Friday, 11 March)
• Re: [ServiceWorker] Fetch API respondWith's implicit RETURN (#844) (Friday, 11 March)
• [ServiceWorker] Fetch API respondWith's implicit RETURN (#844) (Friday, 11 March)
• Re: [ServiceWorker] setTimeout/setInterval are unreliable in ServiceWorkers (#838) (Wednesday, 2 March)
• Re: [ServiceWorker] setTimeout/setInterval are unreliable in ServiceWorkers (#838) (Tuesday, 1 March)

Rick Byers

• Re: [touch-events] Changed license, changed WG info to CG, used CG stylesheet (#61) (Friday, 18 March)
• Re: [touch-events] Changed license, changed WG info to CG, used CG stylesheet (#61) (Friday, 18 March)
• Re: [uievents] Gamepad-specific DOM keys / location? (#79) (Friday, 18 March)
• [uievents] Should key codes / location exist for gamepads? (#79) (Friday, 18 March)
• Re: [touch-events] Need tests for ontouch*, the GlobalEventHandlers (#44) (Tuesday, 8 March)
• Re: [touch-events] Need tests for ontouch*, the GlobalEventHandlers (#44) (Tuesday, 8 March)
• Re: [touch-events] Add tests for TouchEvent and Touch constructors (#27) (Tuesday, 8 March)
• Re: [touch-events] Add tests for TouchEvent and Touch constructors (#27) (Tuesday, 8 March)

Rob Dodson

• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)
• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)
• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)

Rob Dolin (MSFT)

• Re: [manifest] Maintain list of sites that have a manifest (#404) (Thursday, 24 March)
• [manifest] 6.2: Fix member name to splash_screens (#430) (Monday, 14 March)
• Re: [manifest] Is RFC5988 supported by implementers? (#424) (Tuesday, 8 March)
• [manifest] 6.1: Shortens manifest cache time in example (#427) (Friday, 4 March)
• [manifest] 6.1 Grammar fix: "being return" to "being retuned" (#426) (Friday, 4 March)
• [manifest] 1.2 Link Example: Aligns Example 1 with Example 2 (#425) (Friday, 4 March)
• [manifest] Is RFC5988 supported by implementers? (#424) (Friday, 4 March)
• [manifest] Abstract: clarifies new reader ambiguity (#423) (Friday, 4 March)

Robert DeLuca

• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Monday, 7 March)

roryhewitt

• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Thursday, 24 March)
• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Thursday, 24 March)
• Re: [fetch] RFC: a mechanism to bypass CORS preflight (#210) (Thursday, 24 March)
• [fetch] Provide more information in the spec on how withCredentials and Access-Control-Allow-Credentials interact (#264) (Thursday, 24 March)
• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Thursday, 24 March)
• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Thursday, 24 March)
• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Wednesday, 23 March)
• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Wednesday, 23 March)
• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Wednesday, 23 March)
• Re: [fetch] Add new Access-Control-Suppress-Headers CORS response header (#253) (Wednesday, 23 March)
• Re: [fetch] Add new Access-Control-Suppress-Headers CORS response header (#253) (Tuesday, 22 March)
• Re: [fetch] Add new Access-Control-Suppress-Headers CORS response header (#253) (Tuesday, 22 March)
• Re: [fetch] Add new Access-Control-Suppress-Headers CORS response header (#253) (Tuesday, 22 March)
• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Tuesday, 22 March)
• Re: [fetch] Add new Access-Control-Suppress-Headers CORS response header (#253) (Tuesday, 22 March)
• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Tuesday, 22 March)
• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Tuesday, 22 March)
• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Tuesday, 22 March)
• Re: [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Monday, 21 March)
• Re: [fetch] Add new Access-Control-Suppress-Headers CORS response header (#253) (Friday, 18 March)
• [fetch] Add new Access-Control-Suppress-Headers CORS response header (#253) (Friday, 18 March)
• [fetch] Update Access-Control-Expose-Headers CORS response header to allow * (allow-all) (#252) (Friday, 18 March)
• [fetch] Update Access-Control-Allow-Headers CORS response header to allow * (allow-all) (#251) (Friday, 18 March)

Rune Lillesveen

• Re: [webcomponents] Define the behavior of '::slotted' (the former name is '::content'). (#331) (Monday, 7 March)
• Re: [webcomponents] Define the behavior of '::slotted' (the former name is '::content'). (#331) (Monday, 7 March)

Russell Bicknell

• Re: [w3c/webcomponents] [Shadow] activeElement behavior seems to break encapsulation (#358) (Tuesday, 29 March)
• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)
• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)

Ryosuke Niwa

• Re: [w3c/webcomponents] Rename getAssignedNodes()? (#451) (Thursday, 31 March)
• Re: [w3c/webcomponents] node.isConnected (#81) (Thursday, 31 March)
• Re: [w3c/webcomponents] [Shadow] activeElement behavior seems to break encapsulation (#358) (Thursday, 31 March)
• Re: [w3c/webcomponents] node.isConnected (#81) (Wednesday, 30 March)
• Re: [w3c/webcomponents] Need "slotchange" event (#288) (Wednesday, 30 March)
• Re: [w3c/webcomponents] define() could use [[GetPrototypeOf]]? (#473) (Wednesday, 30 March)
• Re: [w3c/webcomponents] Need "slotchange" event (#288) (Wednesday, 30 March)
• Re: [w3c/webcomponents] Need "slotchange" event (#288) (Wednesday, 30 March)
• Re: [w3c/webcomponents] Need "slotchange" event (#288) (Tuesday, 29 March)
• Re: [w3c/webcomponents] Editorial: create an element step 3.4 (#459) (Tuesday, 29 March)
• Re: [w3c/webcomponents] Need "slotchange" event (#288) (Tuesday, 29 March)
• Re: [w3c/webcomponents] Need "slotchange" event (#288) (Tuesday, 29 March)
• Re: [w3c/webcomponents] Need "slotchange" event (#288) (Tuesday, 29 March)
• Re: [w3c/webcomponents] defineElement should not cache lifecycle callbacks and prototype of a custom element class (#417) (Tuesday, 29 March)
• Re: [w3c/webcomponents] Parse <slot> like <template> (#59) (Tuesday, 29 March)
• Re: [w3c/webcomponents] Need "slotchange" event (#288) (Tuesday, 29 March)
• Re: [w3c/webcomponents] Shadow dom: use css containment features by default (#355) (Tuesday, 29 March)
• Re: [webcomponents] [Shadow] activeElement behavior seems to break encapsulation (#358) (Monday, 28 March)
• Re: [webcomponents] [Shadow] activeElement behavior seems to break encapsulation (#358) (Monday, 28 March)
• Re: [webcomponents] Slots in a flat tree (#308) (Monday, 28 March)
• Re: [webcomponents] Slots in a flat tree (#308) (Monday, 28 March)
• Re: [webcomponents] [Shadow] activeElement behavior seems to break encapsulation (#358) (Monday, 28 March)
• Re: [webcomponents] [Shadow] activeElement behavior seems to break encapsulation (#358) (Saturday, 26 March)
• Re: [webcomponents] [Shadow] activeElement behavior seems to break encapsulation (#358) (Saturday, 26 March)
• Re: [webcomponents] Composition Algorithm shouldn't unwrap slots (#308) (Thursday, 24 March)
• Re: [webcomponents] Composition Algorithm shouldn't unwrap slots (#308) (Thursday, 24 March)
• Re: [webcomponents] Extend the slotting algorithm so that a slot can select an element which doesn't have slot attribute. (#343) (Wednesday, 23 March)
• Re: [webcomponents] ES5 consideration for custom elements (#423) (Wednesday, 23 March)
• Re: [webcomponents] ES5 consideration for custom elements (#423) (Wednesday, 23 March)
• Re: [webcomponents] ES5 consideration for custom elements (#423) (Tuesday, 22 March)
• Re: [webcomponents] Consider exposing Shadom DOM and Custom Elements only in secure contexts (#449) (Tuesday, 22 March)
• Re: [webcomponents] Parse <slot> like <template> (#59) (Tuesday, 22 March)
• Re: [webcomponents] Rename getAssignedNodes()? (#451) (Tuesday, 22 March)
• Re: [webcomponents] Extend the slotting algorithm so that a slot can select an element which doesn't have slot attribute. (#343) (Tuesday, 22 March)
• Re: [webcomponents] Consider exposing Shadom DOM and Custom Elements only in secure contexts (#449) (Tuesday, 22 March)
• Re: [webcomponents] ES5 consideration for custom elements (#423) (Tuesday, 22 March)
• Re: [webcomponents] Upgrades need to run attributeChangedCallbacks and connectedCallback (#450) (Tuesday, 22 March)
• Re: [webcomponents] Consider exposing Shadom DOM and Custom Elements only in secure contexts (#449) (Monday, 21 March)
• Re: [webcomponents] Expose ShadowRoot object's encapsulation mode (#275) (Friday, 18 March)
• Re: [webcomponents] scoped and relatedTargetScoped attributes are useless in Event, so remove then from Event interface (#442) (Friday, 18 March)
• Re: [webcomponents] Permit retrieval of registered classes from window.customElements (#445) (Thursday, 17 March)
• Re: [webcomponents] Fix typo in '2.1.1 Creating a custom tag' (#446) (Thursday, 17 March)
• Re: [selection-api] setBaseAndExtent() and setPositon() should be marked as "deprecated" (#67) (Wednesday, 16 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Wednesday, 16 March)
• Re: [selection-api] setBaseAndExtent() and setPositon() should be marked as "deprecated" (#67) (Wednesday, 16 March)
• Re: [selection-api] Define the visually equivalency. (#6) (Wednesday, 16 March)
• Re: [selection-api] We need to expose line direction coordinate as a property (#59) (Wednesday, 16 March)
• Re: [selection-api] Need an API to get the current caret rects (#58) (Wednesday, 16 March)
• Re: [selection-api] Need to be able to tell if the caret is displayed at the beginning or the end of the line (#32) (Wednesday, 16 March)
• Re: [webcomponents] [Shadow]: Add support for external stylesheets using link rel="stylesheet" (bugzilla: 22539) (#82) (Wednesday, 16 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Wednesday, 16 March)
• Re: [webcomponents] Rename custom tag (#434) (Monday, 14 March)
• Re: [webcomponents] Rename custom tag (#434) (Monday, 14 March)
• Re: [webcomponents] Rename custom tag (#434) (Monday, 14 March)
• Re: [webcomponents] Rename custom tag (#434) (Monday, 14 March)
• Re: [webcomponents] Rename custom tag (#434) (Monday, 14 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Monday, 14 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Monday, 14 March)
• Re: [webcomponents] Rename custom tag (#434) (Monday, 14 March)
• Re: [webcomponents] Need "slotting changed" event (#288) (Monday, 14 March)
• Re: [webcomponents] Rename custom tag (#434) (Monday, 14 March)
• Re: [webcomponents] Rename custom tag (#434) (Monday, 14 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Sunday, 13 March)
• Re: [webcomponents] Parse <slot> like <template> (#59) (Sunday, 13 March)
• Re: [webcomponents] Should shadow host have `display: block` by default? (#426) (Sunday, 13 March)
• Re: [webcomponents] document.registerElement should take a template as an argument (bugzilla: 28546) (#135) (Saturday, 12 March)
• Re: [webcomponents] Move defineElement elsewhere? (#431) (Friday, 11 March)
• Re: [webcomponents] Should relatedTargetScoped flag be set on mousedown/mouseup events? (#433) (Friday, 11 March)
• Re: [webcomponents] Should relatedTargetScoped flag be set on mousedown/mouseup events? (#433) (Friday, 11 March)
• [webcomponents] Should relatedTargetScoped flag be set on mousedown/mouseup events? (#433) (Friday, 11 March)
• Re: [webcomponents] deepPath's definition is ambiguous when the event path contains a non-Node EventTarget (#432) (Friday, 11 March)
• Re: [webcomponents] deepPath's definition is ambiguous when the event path contains a non-Node EventTarget (#432) (Friday, 11 March)
• Re: [webcomponents] deepPath's definition is ambiguous when the event path contains a non-Node EventTarget (#432) (Friday, 11 March)
• [webcomponents] deepPath's definition is ambiguous when the event path contains a non-Node EventTarget (#432) (Friday, 11 March)
• Re: [webcomponents] Add conformance requirements for custom element constructors (00ed64f) (Friday, 11 March)
• Re: [webcomponents] :unresolved vs :not(:upgraded) (#418) (Thursday, 10 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Thursday, 10 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Thursday, 10 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Thursday, 10 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Thursday, 10 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Thursday, 10 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Thursday, 10 March)
• Re: [webcomponents] defined promise (#427) (Thursday, 10 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Thursday, 10 March)
• Re: [webcomponents] Parse <slot> like <template> (#59) (Wednesday, 9 March)
• Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428) (Wednesday, 9 March)
• Re: [webcomponents] Figure out how form owner should work in shadow DOM (#196) (Wednesday, 9 March)
• Re: [webcomponents] Define the behavior for sync element creation when a custom element constructor does various bad things (#412) (Wednesday, 9 March)
• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)
• Re: [webcomponents] Should shadow host have `display: block` by default? (#426) (Tuesday, 8 March)
• [webcomponents] Should shadow host have `display: block` by default? (#426) (Tuesday, 8 March)
• Re: [webcomponents] Define the behavior when a custom element constructor returns an element with a parent node. (#412) (Tuesday, 8 March)
• Re: [webcomponents] Define the behavior when a custom element constructor returns an element with a parent node. (#412) (Tuesday, 8 March)
• Re: [webcomponents] :unresolved vs :not(:upgraded) (#418) (Tuesday, 8 March)
• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Tuesday, 8 March)
• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)
• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)
• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)
• Re: [webcomponents] Shadow DOM and comment nodes (#411) (Tuesday, 8 March)
• Re: [webcomponents] Shadow DOM and comment nodes (#411) (Tuesday, 8 March)
• Re: [webcomponents] Shadow DOM and comment nodes (#411) (Tuesday, 8 March)
• Re: [webcomponents] Define the behavior when a custom element constructor returns an element with a parent node. (#412) (Tuesday, 8 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Tuesday, 8 March)
• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)
• Re: [webcomponents] :unresolved vs :not(:upgraded) (#418) (Tuesday, 8 March)
• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Tuesday, 8 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Tuesday, 8 March)
• Re: [webcomponents] "Creating an element" needs to be more precise, for upgrades (#424) (Tuesday, 8 March)
• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Tuesday, 8 March)
• Re: [webcomponents] Should :unresolved apply to elements that failed to upgrade? (#422) (Tuesday, 8 March)
• Re: [webcomponents] Should :unresolved apply to elements that failed to upgrade? (#422) (Tuesday, 8 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Monday, 7 March)
• Re: [webcomponents] Should :unresolved apply to elements that failed to upgrade? (#422) (Monday, 7 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Monday, 7 March)
• Re: [webcomponents] defineElement should not cache lifecycle callbacks and prototype of a custom element class (#417) (Monday, 7 March)
• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (#224) (Monday, 7 March)
• Re: [webcomponents] Define the behavior of '::slotted' (the former name is '::content'). (#331) (Monday, 7 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Monday, 7 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Monday, 7 March)
• Re: [webcomponents] The algorithm "invoke callbacks" must halt as soon as one of callbacks throw an exception (#421) (Monday, 7 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Monday, 7 March)
• Re: [webcomponents] [Shadow]: Node should expose their scope so that shared state can be scoped to components. (bugzilla: 22080) (#80) (Monday, 7 March)
• Re: [webcomponents] Replace attached/detached callbacks with insertedIntoDocument/removedFromDocument (#362) (Monday, 7 March)
• Re: [webcomponents] Replace attached/detached callbacks with insertedIntoDocument/removedFromDocument (#362) (Monday, 7 March)
• [webcomponents] ES5 consideration for custom elements (#423) (Monday, 7 March)
• Re: [webcomponents] The algorithm "invoke callbacks" must halt as soon as one of callbacks throw an exception (#421) (Monday, 7 March)
• [webcomponents] Should :unresolved apply to elements that failed to upgrade? (#422) (Monday, 7 March)
• [webcomponents] The algorithm "invoke callbacks" must halt as soon as one of callbacks throw an exception (#421) (Monday, 7 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Monday, 7 March)
• Re: [webcomponents] Custom elements' upgrade order is ambiguous in the case of a detached node (#420) (Monday, 7 March)
• [webcomponents] Custom elements' upgrade order is ambiguous in the case of a detached node (#420) (Monday, 7 March)
• Re: [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Monday, 7 March)
• [webcomponents] Custom elements disconnected from a document should not be upgraded (#419) (Monday, 7 March)
• Re: [webcomponents] :unresolved vs :not(:upgraded) (#418) (Monday, 7 March)
• Re: [webcomponents] :unresolved vs :not(:upgraded) (#418) (Monday, 7 March)
• [webcomponents] :unresolved vs :not(:upgraded) (#418) (Monday, 7 March)
• Re: [webcomponents] Replace attached/detached callbacks with insertedIntoDocument/removedFromDocument (#362) (Sunday, 6 March)
• Re: [webcomponents] Rename the first argument of defineElement from type to localName (#416) (Saturday, 5 March)
• Re: [webcomponents] Replace attached/detached callbacks with insertedIntoDocument/removedFromDocument (#362) (Saturday, 5 March)
• [webcomponents] defineElement should not cache lifecycle callbacks and prototype of a custom element class (#417) (Saturday, 5 March)
• [webcomponents] Rename the first argument of defineElement from type to localName (#416) (Saturday, 5 March)
• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Friday, 4 March)
• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Friday, 4 March)
• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Thursday, 3 March)
• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Thursday, 3 March)
• Re: [webcomponents] Remove `Callback` suffix from custom elements callbacks (#414) (Thursday, 3 March)
• Re: [webcomponents] Remove `Callback` suffix from custom elements callbacks (#414) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Thursday, 3 March)
• Re: [webcomponents] Remove `Callback` suffix from custom elements callbacks (#414) (Thursday, 3 March)
• Re: [webcomponents] Replace attached/detached callbacks with insertedIntoDocument/removedFromDocument (#362) (Thursday, 3 March)
• Re: [webcomponents] Shadow DOM and comment nodes (#411) (Thursday, 3 March)
• Re: [webcomponents] Define the behavior when a custom element constructor returns an in-document element to parser (#412) (Thursday, 3 March)
• Re: [webcomponents] Replace attached/detached callbacks with insertedIntoDocument/removedFromDocument (#362) (Thursday, 3 March)
• Re: [webcomponents] Replace attached/detached callbacks with insertedIntoDocument/removedFromDocument (#362) (Thursday, 3 March)
• [webcomponents] Remove `Callback` suffix from custom elements callbacks (#414) (Thursday, 3 March)
• Re: [webcomponents] Change registries to be per document and never shared between documents (#369) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Thursday, 3 March)
• Re: [webcomponents] Shadow DOM and comment nodes (#411) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Thursday, 3 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Wednesday, 2 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Wednesday, 2 March)
• [webcomponents] Define the behavior when a custom element constructor returns an in-document element to parser (#412) (Wednesday, 2 March)
• Re: [webcomponents] Shadow DOM and comment nodes (#411) (Wednesday, 2 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Wednesday, 2 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Wednesday, 2 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Wednesday, 2 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Wednesday, 2 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Wednesday, 2 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Wednesday, 2 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Wednesday, 2 March)
• Re: [webcomponents] Travis build is always broken and seems completely useless (#407) (Wednesday, 2 March)
• Re: [webcomponents] Travis build is always broken and seems completely useless (#407) (Wednesday, 2 March)
• Re: [webcomponents] Travis build is always broken and seems completely useless (#407) (Wednesday, 2 March)
• Re: [webcomponents] Change createElement(localName, typeExtension) to createElement(localName, { is }) (#408) (Wednesday, 2 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Wednesday, 2 March)
• Re: [webcomponents] Should HTML parser instantiate custom elements inside a template element? (#406) (Wednesday, 2 March)
• Re: [webcomponents] Figure out terminology for Shadow DOM that everyone agrees on (#382) (Wednesday, 2 March)
• Re: [webcomponents] Figure out terminology for Shadow DOM that everyone agrees on (#382) (Wednesday, 2 March)
• [webcomponents] Should HTML parser instantiate custom elements inside a template element? (#406) (Wednesday, 2 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Wednesday, 2 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Wednesday, 2 March)
• Re: [webcomponents] Handle constructors that abuse return-override (4a09d96) (Wednesday, 2 March)
• Re: [webcomponents] Handle constructors that abuse return-override (4a09d96) (Wednesday, 2 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Wednesday, 2 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Wednesday, 2 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Wednesday, 2 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Wednesday, 2 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Wednesday, 2 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Wednesday, 2 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Wednesday, 2 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Tuesday, 1 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Tuesday, 1 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Tuesday, 1 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Tuesday, 1 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Tuesday, 1 March)
• Re: [webcomponents] Large custom element spec rewrite to implement some F2F decisions (#405) (Tuesday, 1 March)
• Re: [webcomponents] Rewrite Custom Element Construction Algorithm (#403) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239) (Tuesday, 1 March)
• Re: [webcomponents] When is the slotting algorithm run (#401) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (bugzilla: 22056) (#239) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (bugzilla: 22056) (#239) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (bugzilla: 22056) (#239) (Tuesday, 1 March)
• Re: [selection-api] Make some arguments optional (#30) (Tuesday, 1 March)
• Re: [selection-api] Make some arguments optional (#30) (Tuesday, 1 March)
• Re: [selection-api] Make offset and allowPartialContainment arguments optional (#66) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: Consider creating registries for HTML documents created through DOMImplementation in some cases (bugzilla: 23018) (#236) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: Consider creating registries for HTML documents created through DOMImplementation in some cases (bugzilla: 23018) (#236) (Tuesday, 1 March)
• Re: [webcomponents] [Meta]: Specify how custom elements work (bugzilla: 14968) (#132) (Tuesday, 1 March)
• Re: [webcomponents] Disallow extension of subclasses of HTMLElement and SVGElement/MathMLElement (#363) (Tuesday, 1 March)
• Re: [webcomponents] Disallow extension of subclasses of HTMLElement and SVGElement/MathMLElement (#363) (Tuesday, 1 March)
• Re: [webcomponents] Custom elements should use ES6 class constructor (bugzilla: 28541) (#139) (Tuesday, 1 March)
• Re: [webcomponents] Custom elements should use ES6 class constructor (bugzilla: 28541) (#139) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: Clarify in informative note that cloning/importing also enqueues created callback (bugzilla: 28092) (#144) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: ES6 section needs to be updated (bugzilla: 27769) (#164) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: ES6 section needs to be updated (bugzilla: 27769) (#164) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: Make "Parsing Custom Elements" section more explicit (bugzilla: 27768) (#165) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: Need adopted callback (bugzilla: 24577) (#210) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: Restrict custom elements to NCName (bugzilla: 20973) (#177) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: Need to define global/Realm handling for registerElement (bugzilla: 27260) (#185) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: make callbacks more explicit (bugzilla: 24579) (#186) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: Constructor/prototype linkage needs to actually be defined, since it's dynamic, not static (bugzilla: 27017) (#190) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: Constructor/prototype linkage needs to actually be defined, since it's dynamic, not static (bugzilla: 27017) (#190) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: Custom element constructor behavior makes no sense (bugzilla: 27016) (#189) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: Custom element constructor behavior makes no sense (bugzilla: 27016) (#189) (Tuesday, 1 March)
• Re: [webcomponents] [Custom] Should attachedCallback/detachedCallback callbacks be called when element is added to / removed from shadom dom which is attached to a in-document host? (bugzilla: 26943) (#191) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: Need adopted callback (bugzilla: 24577) (#210) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: What should be the name of the generated constructor returned by registerElement? (bugzilla: 25830) (#211) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: What should be the name of the generated constructor returned by registerElement? (bugzilla: 25830) (#211) (Tuesday, 1 March)
• Re: [webcomponents] [Custom Elements]: Custom elements should be display: block by default (bugzilla: 24876) (#224) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: Consider creating registries for HTML documents created through DOMImplementation in some cases (bugzilla: 23018) (#236) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (bugzilla: 22056) (#239) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (bugzilla: 22056) (#239) (Tuesday, 1 March)
• Re: [webcomponents] [Custom] attachedCallback and detechedCallback should be removed (#286) (Tuesday, 1 March)
• Re: [webcomponents] [Custom] attachedCallback and detechedCallback should be removed (#286) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: Consider adding inserted/removed callback (bugzilla: 24866) (#222) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: Consider adding inserted/removed callback (bugzilla: 24866) (#222) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: Rename document.registerElement to document.define or document.defineElement (bugzilla: 24087) (#140) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: A tag name should be associated with the constructor and not the prototype (bugzilla: 24020) (#214) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: Rename document.registerElement to document.define or document.defineElement (bugzilla: 24087) (#140) (Tuesday, 1 March)
• Re: [webcomponents] [Custom]: A tag name should be associated with the constructor and not the prototype (bugzilla: 24020) (#214) (Tuesday, 1 March)
• Re: [webcomponents] Rename registerElement and change API slightly (#365) (Tuesday, 1 March)
• Re: [webcomponents] Rewrite Custom Element Construction Algorithm (#403) (Tuesday, 1 March)
• [webcomponents] Rewrite Custom Element Construction Algorithm (#403) (Tuesday, 1 March)