public-webapps-github@w3.org from October 2017 by author

Abdón Rodríguez Davila

• Re: [w3c/webcomponents] Support for pseudo elements with ::slotted() selectors (#655) (Friday, 13 October)

achristensen07

• Re: [whatwg/url] percent-encode ' in queries of URLs with special schemes (#348) (Monday, 16 October)
• [whatwg/url] percent-encode ' in queries of URLs with special schemes (#348) (Monday, 16 October)

Adam Rice

• Re: [whatwg/streams] Add examples of using identity transforms to manipulate streams (#847) (Tuesday, 31 October)
• Re: [whatwg/streams] Add examples of using identity transforms to manipulate streams (#847) (Tuesday, 31 October)
• Re: [whatwg/streams] Add examples of using identity transforms to manipulate streams (#847) (Tuesday, 31 October)
• Re: [whatwg/streams] Add examples of using identity transforms to manipulate streams (#847) (Tuesday, 31 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Monday, 30 October)
• Re: [whatwg/streams] [Question] I created a project that explains the spec (#848) (Monday, 30 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Friday, 27 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Friday, 27 October)
• Re: [whatwg/streams] Add an example of a transform stream that replaces template tags (#846) (Friday, 27 October)
• Re: [whatwg/streams] Add an example of a transform stream that replaces template tags (#846) (Friday, 27 October)
• Re: [whatwg/streams] Add an example of a transform stream that replaces template tags (#846) (Friday, 27 October)
• Re: [whatwg/streams] Add an example of a transform stream that replaces template tags (#846) (Friday, 27 October)
• Re: [whatwg/streams] Add an example of a transform stream that replaces template tags (#846) (Friday, 27 October)
• Re: [whatwg/streams] Add an example of a transform stream that replaces template tags (#846) (Friday, 27 October)
• Re: [whatwg/streams] Add an example of a transform stream that replaces template tags (#846) (Friday, 27 October)
• Re: [whatwg/streams] Add examples of using identity transforms to manipulate streams (#847) (Friday, 27 October)
• [whatwg/streams] Add examples of using identity transforms to manipulate streams (#847) (Friday, 27 October)
• Re: [whatwg/streams] Initialise readableStrategy without using an object literal (#839) (Tuesday, 24 October)
• Re: [whatwg/streams] Initialise readableStrategy without using an object literal (#839) (Monday, 23 October)
• Re: [whatwg/streams] Initialise readableStrategy without using an object literal (#839) (Monday, 23 October)
• Re: [whatwg/streams] Add an example of a transform stream that replaces template tags (#846) (Monday, 23 October)
• Re: [whatwg/streams] Add an example of a transform stream that replaces template tags (#846) (Monday, 23 October)
• Re: [whatwg/streams] Add an example of a transform stream that replaces template tags (#846) (Monday, 23 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Monday, 23 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Monday, 23 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Monday, 23 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Monday, 23 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Monday, 23 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Monday, 23 October)
• Re: [whatwg/streams] Add an example of a transform stream that replaces template tags (#846) (Monday, 23 October)
• Re: [whatwg/streams] Add an example of a transform stream that replaces template tags (#846) (Monday, 23 October)
• Re: [whatwg/streams] Add SyncOneToOneTransformFunctionAdaptor example (#843) (Monday, 23 October)
• Re: [whatwg/streams] Add an example of a transform stream that replaces template tags (#846) (Monday, 23 October)
• Re: [whatwg/streams] Add an example of a transform stream that replaces template tags (#846) (Friday, 20 October)
• [whatwg/streams] Add an example of a transform stream that replaces template tags (#846) (Friday, 20 October)
• Re: [whatwg/streams] Is it bad that readableController.error() throws but writableController.error() no-ops in non-readable/writable states? (#821) (Wednesday, 18 October)
• Re: [whatwg/streams] Add a Random Values Generator Demonstration (#844) (Tuesday, 17 October)
• Re: [whatwg/streams] Add a Random Values Generator Demonstration (#844) (Tuesday, 17 October)
• Re: [whatwg/streams] Add a Random Values Generator Demonstration (#844) (Tuesday, 17 October)
• Re: [whatwg/streams] Add a Random Values Generator Demonstration (#844) (Tuesday, 17 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Tuesday, 17 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Tuesday, 17 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Tuesday, 17 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Tuesday, 17 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Tuesday, 17 October)
• Re: [whatwg/streams] Add SyncOneToOneTransformFunctionAdaptor example (#843) (Monday, 16 October)
• [whatwg/streams] Add SyncOneToOneTransformFunctionAdaptor example (#843) (Monday, 16 October)
• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Monday, 16 October)
• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Monday, 16 October)
• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Monday, 16 October)
• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Monday, 16 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Monday, 16 October)
• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Monday, 16 October)
• Re: [whatwg/streams] Meta: Use pr-preview to preview pull requests (#842) (Monday, 16 October)
• Re: [whatwg/streams] Meta: Use pr-preview to preview pull requests (#842) (Monday, 16 October)
• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Monday, 16 October)
• Re: [whatwg/streams] Meta: Use pr-preview to preview pull requests (#842) (Monday, 16 October)
• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Monday, 16 October)
• [whatwg/streams] Meta: Use pr-preview to preview pull requests (#842) (Monday, 16 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Monday, 16 October)
• Re: [whatwg/streams] Initialise readableStrategy without using an object literal (#839) (Monday, 16 October)
• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Monday, 16 October)
• Re: [whatwg/streams] Initialise readableStrategy without using an object literal (#839) (Friday, 13 October)
• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Friday, 13 October)
• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Friday, 13 October)
• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Friday, 13 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Friday, 13 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Friday, 13 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Friday, 13 October)
• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Friday, 13 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Friday, 13 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Friday, 13 October)
• [whatwg/streams] Meta: Make local-watch.js more robust (#841) (Thursday, 12 October)
• Re: [whatwg/streams] WIP: Standard text for TransformStream (#811) (Thursday, 12 October)
• [whatwg/streams] Add "controller" local to TransformStream constructor (#840) (Thursday, 12 October)
• Re: [whatwg/streams] Add "controller" local to TransformStream constructor (#840) (Thursday, 12 October)
• [whatwg/streams] Initialise readableStrategy without using an object literal (#839) (Thursday, 12 October)
• Re: [whatwg/streams] Remove inaccurate note about ReadableStreamDefaultControllerEnqueue (#829) (Wednesday, 11 October)
• Re: [whatwg/streams] Remove inaccurate note about ReadableStreamDefaultControllerEnqueue (#829) (Wednesday, 11 October)
• [whatwg/streams] Add a local variable to TransformStreamDefaultControllerTerminate (#838) (Wednesday, 11 October)
• [whatwg/streams] Fix brand check exception message from terminate() method (#837) (Wednesday, 11 October)
• Re: [whatwg/streams] Move TransformStreamDefaultControllerTerminate down (#835) (Wednesday, 11 October)
• [whatwg/streams] [META] Integrate with pr-preview (#836) (Wednesday, 11 October)
• [whatwg/streams] Move TransformStreamDefaultControllerTerminate down (#835) (Tuesday, 10 October)
• [whatwg/streams] Remove assert() descriptions (#834) (Tuesday, 10 October)
• Re: [whatwg/streams] Some assert()s have no description (#807) (Tuesday, 10 October)
• Re: [whatwg/streams] Switch from "assert" to "better-assert" in reference implementation (#830) (Tuesday, 10 October)
• Re: [whatwg/streams] Switch from "assert" to "better-assert" in reference implementation (#830) (Tuesday, 10 October)
• Re: [whatwg/streams] Use "debug" package for logging (#831) (Tuesday, 10 October)
• Re: [whatwg/streams] Use "debug" package for logging (#831) (Tuesday, 10 October)
• Re: [whatwg/streams] Use "debug" package for logging (#831) (Tuesday, 10 October)
• Re: [whatwg/streams] Remove legacy test infrastructure and abstract-ops tests (#832) (Tuesday, 10 October)
• Re: [whatwg/streams] Use "debug" package for logging (#831) (Tuesday, 10 October)
• Re: [whatwg/streams] Use "debug" package for logging (#831) (Tuesday, 10 October)
• Re: [whatwg/streams] Use "debug" package for logging (#831) (Tuesday, 10 October)
• Re: [whatwg/streams] Use "debug" package for logging (#831) (Tuesday, 10 October)
• Re: [whatwg/streams] Use "debug" package for logging (#831) (Tuesday, 10 October)
• [whatwg/streams] Use "debug" package for logging (#831) (Friday, 6 October)
• Re: [whatwg/streams] Add an extension point for byte transform streams (#820) (Friday, 6 October)
• [whatwg/streams] Switch from "assert" to "better-assert" in reference implementation (#830) (Friday, 6 October)
• [whatwg/streams] Remove inaccurate note about ReadableStreamDefaultControllerEnqueue (#829) (Friday, 6 October)
• Re: [whatwg/streams] WIP: Standard text for TransformStream (#811) (Friday, 6 October)
• [whatwg/streams] Add a local variable to TransformStreamDefaultSink abort() (#828) (Friday, 6 October)
• Re: [whatwg/streams] WIP: Standard text for TransformStream (#811) (Thursday, 5 October)
• [whatwg/streams] Test terminate() and error() inside flush() (#827) (Wednesday, 4 October)
• [whatwg/streams] Make error() and terminate() do nothing when stream is errored (#826) (Wednesday, 4 October)
• [whatwg/streams] Note on ReadableStreamDefaultControllerEnqueue is inaccurate (#824) (Wednesday, 4 October)
• Re: [whatwg/streams] Add an extension point for byte transform streams (#820) (Tuesday, 3 October)
• [whatwg/streams] Remove TransformStreamDefaultSinkDefaultTransform (#823) (Tuesday, 3 October)
• Re: [whatwg/streams] TransformStream: use throw instead of Promise.reject() in promise handlers (#804) (Tuesday, 3 October)
• Re: [whatwg/streams] throw instead of returning Promise.reject() from handlers (#819) (Tuesday, 3 October)
• Re: [whatwg/streams] What should the behaviour of controller.close() be? (#774) (Tuesday, 3 October)
• Re: [whatwg/streams] Add TransformStreamDefaultController terminate() method (#818) (Tuesday, 3 October)
• Re: [whatwg/streams] Add TransformStreamDefaultController terminate() method (#818) (Tuesday, 3 October)
• Re: [whatwg/streams] Add TransformStreamDefaultController terminate() method (#818) (Tuesday, 3 October)
• Re: [whatwg/streams] Add TransformStreamDefaultController terminate() method (#818) (Tuesday, 3 October)
• [whatwg/streams] Stop controller.error() and controller.terminate() throwing in unexpected states (#822) (Tuesday, 3 October)
• Re: [whatwg/streams] TransformStream: Verify behaviour of abort() during write() (#817) (Tuesday, 3 October)
• Re: [whatwg/streams] Is it bad that readableController.error() throws but writableController.error() no-ops in non-readable/writable states? (#821) (Tuesday, 3 October)
• Re: [whatwg/streams] throw instead of returning Promise.reject() from handlers (#819) (Tuesday, 3 October)
• Re: [whatwg/streams] TransformStream: Verify behaviour of abort() during write() (#817) (Tuesday, 3 October)
• Re: [whatwg/streams] TransformStream: Verify behaviour of abort() during write() (#817) (Tuesday, 3 October)
• Re: [whatwg/streams] WIP: Standard text for TransformStream (#811) (Monday, 2 October)
• [whatwg/streams] Add an extension point for byte transform streams (#820) (Monday, 2 October)
• [whatwg/streams] throw instead of returning Promise.reject() from handlers (#819) (Monday, 2 October)
• [whatwg/streams] Add TransformStreamDefaultController terminate() method (#818) (Monday, 2 October)
• [whatwg/streams] TransformStream: Verify behaviour of abort() during write() (#817) (Monday, 2 October)
• [whatwg/streams] Remove the check of the resolved value of _backpressurePromise (#816) (Monday, 2 October)
• [whatwg/streams] Verify that transformer start() is called as a method (#815) (Monday, 2 October)

Addison Phillips

• Re: [w3ctag/design-reviews] Serialization of natural language in data formats such as JSON [I18N] (#178) (Tuesday, 31 October)

Alex Russell

• Re: [w3ctag/design-reviews] saveData attribute in Network Information API (#204) (Tuesday, 31 October)
• Re: [w3ctag/design-reviews] Intersection Observer review (#197) (Tuesday, 31 October)
• Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141) (Tuesday, 17 October)
• Re: [w3ctag/design-reviews] Review request for Device Memory API (#190) (Tuesday, 17 October)
• [w3ctag/design-reviews] `Accept-CH` header is weird (#206) (Tuesday, 17 October)
• Re: [w3ctag/design-reviews] Review request for Device Memory API (#190) (Tuesday, 17 October)
• Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141) (Tuesday, 10 October)

Alexander Shalamov

• Re: [w3c/screen-orientation] Add [Exposed=Window] extended attribute to ScreenOrientation interface (#107) (Tuesday, 31 October)
• [w3c/screen-orientation] Add [Exposed=Window] extended attribute to ScreenOrientation interface (#107) (Tuesday, 31 October)

aliams

• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Friday, 20 October)

Andrea Giammarchi

• Re: [w3c/webcomponents] Custom Element - untrackable upgrade (#671) (Tuesday, 10 October)
• Re: [w3c/webcomponents] Custom Element - untrackable upgrade (#671) (Tuesday, 10 October)
• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Tuesday, 3 October)
• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Monday, 2 October)
• Re: [w3c/webcomponents] Custom Element - untrackable upgrade (#671) (Monday, 2 October)

Andrew Betts

• Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206) (Saturday, 28 October)
• Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206) (Wednesday, 18 October)

Andrew Sutherland

• Re: [whatwg/storage] Rename boxes to bins (#52) (Wednesday, 25 October)
• Re: [w3c/ServiceWorker] Mixed feelings about ServiceWorker for module loader (#1203) (Sunday, 15 October)

Anne van Kesteren

• Re: [whatwg/url] Meta: use the common deploy.sh (#351) (Tuesday, 31 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Tuesday, 31 October)
• Re: [whatwg/fetch] Document CORS safelist exceptions (#621) (Tuesday, 31 October)
• Re: [whatwg/fetch] Document CORS safelist exceptions (#621) (Tuesday, 31 October)
• Re: [whatwg/fetch] Document CORS safelist exceptions (#621) (Tuesday, 31 October)
• Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Tuesday, 31 October)
• Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Tuesday, 31 October)
• Re: [whatwg/fetch] Expose Content-Length header in CORS requests (#622) (Tuesday, 31 October)
• Re: [w3c/FileAPI] Async createObjectURL (#84) (Tuesday, 31 October)
• Re: [whatwg/dom] Add window.event for web compatibility. (e7cdac7) (Monday, 30 October)
• Re: [whatwg/url] Should URLSearchParams stringify be called in URL constructor? (#350) (Monday, 30 October)
• Re: [whatwg/dom] Add window.event for web compatibility. (e7cdac7) (Monday, 30 October)
• Re: [w3c/FileAPI] Async createObjectURL (#84) (Sunday, 29 October)
• Re: [whatwg/dom] Should we really support modifying an already dispatched event via initEvent()? (#523) (Sunday, 29 October)
• Re: [whatwg/fetch] Document CORS safelist exceptions (#621) (Friday, 27 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Thursday, 26 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Thursday, 26 October)
• Re: [w3c/FileAPI] Async createObjectURL (#84) (Thursday, 26 October)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Thursday, 26 October)
• Re: [whatwg/fetch] Add RequestInit members to Request domintro (#620) (Thursday, 26 October)
• Re: [whatwg/dom] Attributes not ready on element construction? (#522) (Wednesday, 25 October)
• Re: [whatwg/storage] Consider renaming boxes to bins or something (#51) (Wednesday, 25 October)
• Re: [whatwg/storage] Rename boxes to bins (#52) (Wednesday, 25 October)
• Re: [whatwg/storage] Rename boxes to bins (#52) (Wednesday, 25 October)
• Re: [whatwg/storage] Consider renaming boxes to bins or something (#51) (Wednesday, 25 October)
• [whatwg/storage] Rename boxes to bins (#52) (Wednesday, 25 October)
• Re: [whatwg/fetch] Address Domenic's Request domintro nits (#619) (Wednesday, 25 October)
• Re: [w3ctag/design-reviews] WebRTC Stats review (#148) (Wednesday, 25 October)
• Re: [whatwg/fetch] Address Domenic's Request domintro nits (#619) (Wednesday, 25 October)
• Re: [w3c/FileAPI] Async createObjectURL (#84) (Wednesday, 25 October)
• Re: [heycam/webidl] Add a frozen record type? (#469) (Wednesday, 25 October)
• Re: [whatwg/dom] Attributes not ready on element construction? (#522) (Wednesday, 25 October)
• Re: [w3c/FileAPI] Async createObjectURL (#84) (Tuesday, 24 October)
• Re: [w3c/webstorage] Async alternative? (#7) (Tuesday, 24 October)
• Re: [w3c/webstorage] Async alternative? (#7) (Tuesday, 24 October)
• Re: [heycam/webidl] Exposing an interface "on all globals" (#468) (Tuesday, 24 October)
• Re: [w3c/FileAPI] Async createObjectURL (#84) (Tuesday, 24 October)
• Re: [heycam/webidl] Exposing an interface "on all globals" (#468) (Tuesday, 24 October)
• Re: [w3c/FileAPI] Async createObjectURL (#84) (Monday, 23 October)
• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Sunday, 22 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Sunday, 22 October)
• [w3ctag/design-reviews] Editorial: change salutation (#209) (Saturday, 21 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Saturday, 21 October)
• Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Saturday, 21 October)
• Re: [whatwg/storage] Consider renaming boxes to bins or something (#51) (Saturday, 21 October)
• Re: [whatwg/storage] Consider renaming boxes to bins or something (#51) (Friday, 20 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Friday, 20 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Friday, 20 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Friday, 20 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Friday, 20 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Friday, 20 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Friday, 20 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Friday, 20 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Thursday, 19 October)
• Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165) (Thursday, 19 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Thursday, 19 October)
• Re: [whatwg/url] percent-encode ' in queries of URLs with special schemes (#348) (Tuesday, 17 October)
• Re: [w3c/FileAPI] Async createObjectURL (#84) (Tuesday, 17 October)
• Re: [w3c/webcomponents] createElement needs [CEReactions] because it sets is="" (#570) (Tuesday, 17 October)
• Re: [whatwg/dom] Add [CEReactions] to createElement() (#506) (Tuesday, 17 October)
• Re: [whatwg/fetch] [WIP] Request domintro box (#617) (Monday, 16 October)
• Re: [whatwg/fetch] [WIP] Request domintro box (#617) (Monday, 16 October)
• Re: [whatwg/fetch] [WIP] Request domintro box (#617) (Monday, 16 October)
• Re: [whatwg/fetch] [WIP] Request domintro box (#617) (Monday, 16 October)
• Re: [whatwg/fetch] Feed a Response to existing APIs (#49) (Monday, 16 October)
• Re: [whatwg/fetch] [WIP] Request domintro box (#617) (Monday, 16 October)
• Re: [whatwg/url] Percent-encode additional characters in "fragment state". (#347) (Monday, 16 October)
• Re: [whatwg/dom] Add [CEReactions] to createElement() (#506) (Monday, 16 October)
• Re: [whatwg/dom] MutationObserver attribute change record only gives us the `oldValue`, but not the `newValue`? (#521) (Monday, 16 October)
• Re: [whatwg/dom] MutationObserver attribute change record only gives us the `oldValue`, but not the `newValue`? (#521) (Monday, 16 October)
• Re: [whatwg/dom] MutationObserver attribute change record only gives us the `oldValue`, but not the `newValue`? (#521) (Monday, 16 October)
• Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165) (Monday, 16 October)
• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Monday, 16 October)
• Re: [w3c/webcomponents] Why does attributeChangedCallback fire when a new attribute value is the same? (#676) (Sunday, 15 October)
• Re: [whatwg/fetch] Doc: Definition of credentials unclear (#612) (Saturday, 14 October)
• Re: [whatwg/fetch] Clarify that credentials include HTTP auth (#616) (Saturday, 14 October)
• Re: [whatwg/xhr] externals.js?v=SV4wipYX62VSlFpHPU1b0oqTYYPkrgV1RT64uViudRk1:1 [Deprecation] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/. (#164) (Saturday, 14 October)
• Re: [whatwg/dom] MutationObserver: observing attribute changes fires even if the value didn't change. (#520) (Friday, 13 October)
• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Friday, 13 October)
• Re: [whatwg/xhr] Reference Fetch spec for “credentials” definition (#163) (Friday, 13 October)
• Re: [whatwg/xhr] Reference Fetch spec for “credentials” definition (#163) (Friday, 13 October)
• Re: [whatwg/fetch] Clarify that credentials include HTTP auth (#616) (Friday, 13 October)
• Re: [whatwg/fetch] Clarify that credentials include HTTP auth (#616) (Friday, 13 October)
• Re: [whatwg/fetch] Clarify that credentials include HTTP auth (#616) (Friday, 13 October)
• Re: [whatwg/fetch] Clarify that credentials include HTTP auth (#616) (Friday, 13 October)
• Re: [w3c/webcomponents] Why does attributeChangedCallback fire when a new attribute value is the same? (#676) (Friday, 13 October)
• Re: [w3c/webcomponents] Why does attributeChangedCallback fire when a new attribute value is the same? (#676) (Friday, 13 October)
• Re: [whatwg/dom] MutationObserver: observing attribute changes fires even if the value didn't change. (#520) (Friday, 13 October)
• Re: [whatwg/dom] MutationObserver: observing attribute changes fires even if the value didn't change. (#520) (Friday, 13 October)
• Re: [whatwg/dom] About `element` element (#519) (Friday, 13 October)
• Re: [whatwg/dom] About `element` element (#519) (Friday, 13 October)
• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Thursday, 12 October)
• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Thursday, 12 October)
• Re: [whatwg/dom] Use new DOMException style (#450) (Thursday, 12 October)
• Re: [whatwg/dom] Use new DOMException style (#450) (Thursday, 12 October)
• Re: [whatwg/fetch] Define data: URLs (#579) (Thursday, 12 October)
• Re: [whatwg/dom] Editorial: use "exception name" DOMException notation (#518) (Thursday, 12 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Thursday, 12 October)
• Re: [whatwg/dom] Editorial: use "exception name" DOMException notation (#518) (Thursday, 12 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Thursday, 12 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Thursday, 12 October)
• Re: [heycam/webidl] Mixin follow-up (#450) (Thursday, 12 October)
• Re: [heycam/webidl] Standardize around typography of IDL true/false/null (#457) (Wednesday, 11 October)
• Re: [heycam/webidl] Add a note on the difference of SyntaxError (#459) (Wednesday, 11 October)
• Re: [whatwg/fetch] Acknowledge Yehuda Katz (#615) (Wednesday, 11 October)
• Re: [whatwg/xhr] Meta: export FormData's concepts (#162) (Wednesday, 11 October)
• [whatwg/fetch] Acknowledge Yehuda Katz (#615) (Wednesday, 11 October)
• Re: [whatwg/xhr] Meta: export FormData's concepts (#162) (Wednesday, 11 October)
• [whatwg/xhr] Meta: export FormData's concepts (#162) (Wednesday, 11 October)
• Re: [heycam/webidl] Add mixins (#433) (Wednesday, 11 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Wednesday, 11 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Wednesday, 11 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Tuesday, 10 October)
• Re: [whatwg/encoding] Meta: TF-8 decode without BOM or fail is used at least once (#124) (Tuesday, 10 October)
• [whatwg/encoding] Give advice around specification hooks (#125) (Tuesday, 10 October)
• [whatwg/encoding] Meta: TF-8 decode without BOM or fail is used at least once (#124) (Tuesday, 10 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Tuesday, 10 October)
• Re: [whatwg/url] Consider percent-encoding more characters in "fragment state" (#344) (Tuesday, 10 October)
• Re: [whatwg/url] Define percent decoding of strings (#340) (Tuesday, 10 October)
• Re: [whatwg/url] Define percent decoding of strings (#340) (Tuesday, 10 October)
• Re: [whatwg/url] Define percent decoding of strings (#340) (Tuesday, 10 October)
• Re: [heycam/webidl] Consider renaming all legacy extended attributes (#350) (Tuesday, 10 October)
• Re: [whatwg/url] Consider percent-encoding more characters in "fragment state" (#344) (Tuesday, 10 October)
• Re: [whatwg/url] Consider percent-encoding more characters in "fragment state" (#344) (Tuesday, 10 October)
• Re: [whatwg/url] Consider percent-encoding more characters in "fragment state" (#344) (Tuesday, 10 October)
• Re: [whatwg/url] Percent-encode additional characters in "fragment state". (#347) (Tuesday, 10 October)
• Re: [whatwg/url] Consider percent-encoding more characters in "fragment state" (#344) (Tuesday, 10 October)
• Re: [whatwg/fetch] Wrong authors listed for WSP (#613) (Tuesday, 10 October)
• Re: [whatwg/fetch] Reference correct WebSocket protocol RFC (#614) (Tuesday, 10 October)
• Re: [whatwg/fetch] Wrong authors listed for WSP (#613) (Tuesday, 10 October)
• Re: [whatwg/url] Percent-encode additional characters in "fragment state". (#347) (Tuesday, 10 October)
• [whatwg/fetch] Reference correct WebSocket protocol RFC (#614) (Tuesday, 10 October)
• Re: [whatwg/fetch] Wrong authors listed for WSP (#613) (Tuesday, 10 October)
• [whatwg/streams] Editorial: address minor nits in the FAQ (#833) (Tuesday, 10 October)
• Re: [whatwg/url] Consider percent-encoding more characters in "fragment state" (#344) (Tuesday, 10 October)
• Re: [whatwg/url] Percent-encode additional characters in "fragment state". (#347) (Tuesday, 10 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Tuesday, 10 October)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Tuesday, 10 October)
• Re: [whatwg/xhr] final readystatechange (readyState === 3) (#161) (Monday, 9 October)
• Re: [whatwg/xhr] final readystatechange (readyState === 3) (#161) (Monday, 9 October)
• Re: [whatwg/xhr] final readystatechange (readyState === 3) (#161) (Monday, 9 October)
• Re: [whatwg/xhr] final readystatechange (readyState === 3) (#161) (Monday, 9 October)
• Re: [whatwg/xhr] final readystatechange (readyState === 3) (#161) (Monday, 9 October)
• Re: [whatwg/fetch] Doc: Definition of credentials unclear (#612) (Saturday, 7 October)
• Re: [whatwg/dom] Question about `attachShadow` to HTMLUnknownElement (#517) (Saturday, 7 October)
• Re: [whatwg/dom] Question about `attachShadow` to HTMLUnknownElement (#517) (Saturday, 7 October)
• Re: [whatwg/xhr] final readystatechange (readyState === 3) (#161) (Friday, 6 October)
• Re: [whatwg/xhr] final readystatechange (readyState === 3) (#161) (Friday, 6 October)
• Re: [whatwg/fetch] Regression: make Request constructor account for changes to fill (#484) (Friday, 6 October)
• Re: [whatwg/fetch] Regression: make Request constructor account for changes to fill (#484) (Friday, 6 October)
• Re: [whatwg/xhr] Use document encoding for URL parser (#159) (Friday, 6 October)
• Re: [whatwg/fetch] Regression: make Request constructor account for changes to fill (#484) (Friday, 6 October)
• Re: [whatwg/xhr] Synchronous XMLHttpRequest (#158) (Friday, 6 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Friday, 6 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Thursday, 5 October)
• [whatwg/xhr] Use "XML MIME type" (#160) (Thursday, 5 October)
• Re: [whatwg/fetch] Use Infra for JSON parsing (#610) (Thursday, 5 October)
• Re: [whatwg/xhr] Use Infra for JSON parsing (#153) (Thursday, 5 October)
• Re: [whatwg/xhr] Synchronous XMLHttpRequest (#158) (Thursday, 5 October)
• Re: [whatwg/xhr] Synchronous XMLHttpRequest (#158) (Thursday, 5 October)
• [whatwg/xhr] Use document encoding for URL parser (#159) (Thursday, 5 October)
• Re: [whatwg/dom] Event.target should return null after dispatch is complete, when stopped at ShadowRoot (#511) (Thursday, 5 October)
• Re: [whatwg/dom] Set event.target to null when dispatching finishes at ShadowRoot (#513) (Thursday, 5 October)
• Re: [whatwg/dom] Set event.target to null when dispatching finishes at ShadowRoot (#513) (Thursday, 5 October)
• Re: [whatwg/dom] Set event.target to null when dispatching finishes at ShadowRoot (#513) (Thursday, 5 October)
• Re: [whatwg/dom] Set event.target to null when dispatching finishes at ShadowRoot (#513) (Thursday, 5 October)
• Re: [whatwg/dom] Set event.target to null when dispatching finishes at ShadowRoot (#513) (Thursday, 5 October)
• Re: [whatwg/dom] Set event.target to null when dispatching finishes at ShadowRoot (#513) (Thursday, 5 October)
• Re: [whatwg/dom] Set event.target to null when dispatching finishes at ShadowRoot (#513) (Thursday, 5 October)
• Re: [heycam/webidl] Enumeration order of interface members (#432) (Thursday, 5 October)
• Re: [heycam/webidl] Dot notation for dictionary members is not spec'ed. (#453) (Wednesday, 4 October)
• Re: [heycam/webidl] Dot notation for dictionary members is not spec'ed. (#453) (Wednesday, 4 October)
• Re: [heycam/webidl] Dot notation for dictionary members is not spec'ed. (#453) (Wednesday, 4 October)
• Re: [heycam/webidl] Dot notation for dictionary members is not spec'ed. (#453) (Wednesday, 4 October)
• Re: [heycam/webidl] Dot notation for dictionary members is not spec'ed. (#453) (Wednesday, 4 October)
• Re: [whatwg/xhr] Should we be pinning Blob URIs on fetches? (#79) (Wednesday, 4 October)
• Re: [heycam/webidl] Dot notation for dictionary members is not spec'ed. (#453) (Tuesday, 3 October)
• [whatwg/xhr] Look at overrideMimeType() again (#157) (Tuesday, 3 October)
• Re: [heycam/webidl] Dot notation for dictionary members is not spec'ed. (#453) (Tuesday, 3 October)
• Re: [heycam/webidl] Dot notation for dictionary members is not spec'ed. (#453) (Tuesday, 3 October)
• Re: [heycam/webidl] Dot notation for Web IDL is not spec'ed. (#453) (Tuesday, 3 October)
• Re: [whatwg/xhr] does "remote address" in xhr response standard ? (#156) (Tuesday, 3 October)
• Re: [whatwg/xhr] does "remote address" in xhr response standard ? (#156) (Tuesday, 3 October)
• Re: [whatwg/xhr] I do not trust my P.C, it seems like someone else first read my gmail and I'm always kidding my PC. Maybe you can figure it out with Fri. gr Gino Schrijn (#155) (Monday, 2 October)
• Re: [whatwg/url] why are backslashes accepted for slashes? (#346) (Sunday, 1 October)
• Re: [whatwg/url] why are backslashes accepted for slashes? (#346) (Sunday, 1 October)

Anssi Kostiainen

• Re: [w3c/manifest] Fix validator errors and warnings (#625) (Thursday, 26 October)
• Re: [w3c/manifest] Fix validator errors and warnings (#625) (Thursday, 26 October)
• [w3c/manifest] Fix validator errors and warnings (#625) (Thursday, 26 October)
• Re: [w3c/manifest] Update implementation status (#624) (Thursday, 26 October)
• Re: [w3c/manifest] Update implementation status (#624) (Thursday, 26 October)
• [w3c/manifest] Update implementation status (#624) (Thursday, 26 October)
• [w3ctag/design-reviews] Sensor APIs (#207) (Friday, 20 October)
• [heycam/webidl] Fix ambiguity within the [SecureContext] section (#465) (Tuesday, 17 October)
• Re: [heycam/webidl] Dot notation for dictionary members is not spec'ed. (#453) (Wednesday, 4 October)
• [whatwg/streams] Use [[UpperCamelCase]] in internal slots (#825) (Wednesday, 4 October)
• Re: [heycam/webidl] Dot notation for dictionary members is not spec'ed. (#453) (Wednesday, 4 October)

Anthony Ramine

• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Friday, 20 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Thursday, 19 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Thursday, 19 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Thursday, 19 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Thursday, 19 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Thursday, 19 October)

Appie1958

• [whatwg/xhr] I do not trust my P.C, it seems like someone else first read my gmail and I'm always kidding my PC. Maybe you can figure it out with Fri. gr Gino Schrijn (#155) (Monday, 2 October)

Arthur Stolyar

• Re: [w3c/ServiceWorker] resurrected service workers don't fire an activate event which may break expectations (#1204) (Saturday, 7 October)
• Re: [w3c/ServiceWorker] resurrected service workers don't fire an activate event which may break expectations (#1204) (Friday, 6 October)

ashelyy88

• Re: [whatwg/fetch] Help removing this bd (#618) (Wednesday, 18 October)
• [whatwg/fetch] Help removing this bd (#618) (Wednesday, 18 October)

Ashley (Scirra)

• Re: [w3c/webcomponents] HTML Modules (#645) (Thursday, 5 October)

Azharuddin

• Re: [w3c/ServiceWorker] Consider mechanisms to bypass the service worker for things that we know won't be in it's cache (#1026) (Tuesday, 31 October)

Baocang Nie

• [whatwg/dom] About `element` element (#519) (Thursday, 12 October)
• Re: [whatwg/dom] Question about `attachShadow` to HTMLUnknownElement (#517) (Saturday, 7 October)
• Re: [whatwg/dom] Declarative Shadow DOM (#510) (Saturday, 7 October)
• [whatwg/dom] Allow attachShadow to HTMLUnknownElement (#517) (Saturday, 7 October)

beidson

• Re: [w3c/IndexedDB] API to enumerate databases (#31) (Tuesday, 24 October)

Ben Kelly

• Re: [w3c/ServiceWorker] Proposal: Allow addEventListener/removeEventListener for 'fetch' to called at anytime (#1195) (Tuesday, 31 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Tuesday, 31 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Monday, 30 October)
• Re: [w3c/ServiceWorker] reflect internal "parsed" state in ServiceWorkerState enum (#1162) (Monday, 30 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Monday, 30 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Friday, 27 October)
• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Friday, 27 October)
• Re: [w3c/ServiceWorker] Does changing updateViaCache mint a new ServiceWorkerRegistration or update them all? (#1189) (Friday, 27 October)
• Re: [w3c/ServiceWorker] Does changing updateViaCache mint a new ServiceWorkerRegistration or update them all? (#1189) (Friday, 27 October)
• Re: [whatwg/fetch] Use the URL from the response, if it has one (#146) (Thursday, 26 October)
• Re: [whatwg/fetch] Use the URL from the response, if it has one (#146) (Thursday, 26 October)
• Re: [w3c/ServiceWorker] Should we expose reserved clients? (#1216) (Thursday, 26 October)
• Re: [w3c/ServiceWorker] Should we expose reserved clients? (#1216) (Thursday, 26 October)
• Re: [w3c/ServiceWorker] Should we expose reserved clients? (#1216) (Thursday, 26 October)
• Re: [w3c/ServiceWorker] Navigating reserved clients (#1215) (Wednesday, 25 October)
• Re: [w3c/ServiceWorker] Navigating reserved clients (#1215) (Wednesday, 25 October)
• Re: [w3c/ServiceWorker] Remove foreign fetch (#1207) (Wednesday, 25 October)
• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Friday, 20 October)
• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Friday, 20 October)
• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Friday, 20 October)
• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Friday, 20 October)
• [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Friday, 20 October)
• Re: [w3c/ServiceWorker] async waitUntil() does not allow extension on final promise resolution? (#1039) (Friday, 20 October)
• Re: [w3c/ServiceWorker] Require JS content type for serviceworkers is not present in the spec (#1209) (Monday, 16 October)
• Re: [w3c/ServiceWorker] Require JS content type for serviceworkers is not present in the spec (#1209) (Monday, 16 October)
• Re: [w3c/ServiceWorker] Require JS content type for serviceworkers is not present in the spec (#1209) (Monday, 16 October)
• Re: [w3c/ServiceWorker] Require JS content type for serviceworkers is not present in the spec (#1209) (Monday, 16 October)
• Re: [w3c/ServiceWorker] Mixed feelings about ServiceWorker for module loader (#1203) (Thursday, 12 October)
• Re: [w3c/ServiceWorker] Mixed feelings about ServiceWorker for module loader (#1203) (Thursday, 12 October)
• Re: [w3c/ServiceWorker] resurrected service workers don't fire an activate event which may break expectations (#1204) (Thursday, 12 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Wednesday, 11 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Wednesday, 11 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Wednesday, 11 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Wednesday, 11 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Wednesday, 11 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Wednesday, 11 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Wednesday, 11 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Tuesday, 10 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Tuesday, 10 October)
• Re: [w3c/ServiceWorker] resurrected service workers don't fire an activate event which may break expectations (#1204) (Saturday, 7 October)
• [w3c/ServiceWorker] resurrected service workers don't fire an activate event which may break expectations (#1204) (Friday, 6 October)
• Re: [whatwg/fetch] Why does Fetch specify a max redirect count of 20? (#576) (Wednesday, 4 October)

bengreenstein

• [w3ctag/design-reviews] saveData attribute in Network Information API (#204) (Friday, 6 October)

Benjamin Gruenbaum

• [whatwg/fetch] Expose Content-Length header in CORS requests (#622) (Sunday, 29 October)

Benoit Girard

• Re: [w3c/ServiceWorker] Proposal: Allow addEventListener/removeEventListener for 'fetch' to called at anytime (#1195) (Tuesday, 3 October)

Bevis Tseng

• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Tuesday, 24 October)

Boris Zbarsky

• Re: [heycam/webidl] Exposing an interface "on all globals" (#468) (Friday, 27 October)
• Re: [heycam/webidl] Add a frozen record type? (#469) (Tuesday, 24 October)
• [whatwg/streams] Need to define the current Realm for pipeTo operations (#845) (Thursday, 19 October)
• [w3c/uievents] Activation behavior and click interaction is not specified (#164) (Thursday, 19 October)
• Re: [heycam/webidl] Fix #461 - clarify applicability of overload resolution (#462) (Monday, 16 October)
• Re: [heycam/webidl] Fix #461 - clarify applicability of overload resolution (#462) (Monday, 16 October)
• Re: [heycam/webidl] Missing argument handling (#461) (Monday, 16 October)
• Re: [heycam/webidl] Add mixins (#433) (Monday, 9 October)
• Re: [heycam/webidl] Enumeration order of interface members (#432) (Thursday, 5 October)
• Re: [heycam/webidl] Enumeration order of interface members (#432) (Thursday, 5 October)
• Re: [heycam/webidl] Enumeration order of interface members (#432) (Wednesday, 4 October)
• Re: [heycam/webidl] Enumeration order of interface members (#432) (Wednesday, 4 October)
• Re: [whatwg/url] Consider percent-encoding more characters in "fragment state" (#344) (Tuesday, 3 October)

Bradley Meck

• Re: [w3c/FileAPI] Async createObjectURL (#84) (Tuesday, 31 October)
• Re: [w3c/FileAPI] Async createObjectURL (#84) (Tuesday, 31 October)
• Re: [w3c/FileAPI] Async createObjectURL (#84) (Monday, 30 October)
• Re: [w3c/FileAPI] Async createObjectURL (#84) (Friday, 27 October)
• Re: [w3c/FileAPI] Async createObjectURL (#84) (Wednesday, 25 October)
• Re: [w3c/FileAPI] Async createObjectURL (#84) (Tuesday, 24 October)
• Re: [w3c/FileAPI] Async createObjectURL (#84) (Tuesday, 24 October)
• Re: [w3c/FileAPI] Async createObjectURL (#84) (Monday, 23 October)
• Re: [w3c/FileAPI] Async createObjectURL (#84) (Tuesday, 17 October)
• Re: [w3c/FileAPI] Async createObjectURL (#84) (Monday, 16 October)
• Re: [w3c/FileAPI] Async createObjectURL (#84) (Monday, 16 October)
• [w3c/FileAPI] Async createObjectURL (#84) (Monday, 16 October)

Brandon Jones

• Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141) (Thursday, 26 October)
• Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141) (Thursday, 19 October)

Brian Burg

• Re: [w3c/permissions] Introduce "Automation" section (#151) (Wednesday, 4 October)
• Re: [w3c/permissions] Introduce "Automation" section (#151) (Wednesday, 4 October)
• Re: [w3c/permissions] Introduce "Automation" section (#151) (Wednesday, 4 October)
• Re: [w3c/permissions] Introduce "Automation" section (#151) (Wednesday, 4 October)

C. Van Wiemeersch

• Re: [w3c/gamepad] Ask for tests for normative changes in CONTRIBUTING.md (#64) (Tuesday, 24 October)
• Re: [w3c/gamepad] Ask for tests for normative changes in CONTRIBUTING.md (#64) (Monday, 23 October)
• Re: [w3c/gamepad] Ask for tests for normative changes in CONTRIBUTING.md (#64) (Monday, 23 October)

chaals

• Re: [w3c/webcomponents] CfC: Move Shadow DOM standalone spec to NOTE (#670) (Friday, 6 October)
• Re: [w3c/webcomponents] CfC: Move Shadow DOM standalone spec to NOTE (#670) (Friday, 6 October)
• Re: [w3c/WebPlatformWG] TPAC agenda: Thu Nov 9 (WebPlat general) (#94) (Tuesday, 3 October)

Chad Killingsworth

• Re: [w3c/webcomponents] Support `>>>` combinator in static profile (#78) (Monday, 9 October)
• Re: [w3c/webcomponents] Support `>>>` combinator in static profile (#78) (Monday, 9 October)
• Re: [w3c/webcomponents] Support `>>>` combinator in static profile (#78) (Sunday, 8 October)
• Re: [w3c/webcomponents] Support `>>>` combinator in static profile (#78) (Sunday, 8 October)

Chris Dumez

• Re: [whatwg/dom] Should we really support modifying an already dispatched event via initEvent()? (#523) (Friday, 27 October)
• Re: [whatwg/dom] Should we really support modifying an already dispatched event via initEvent()? (#523) (Friday, 27 October)
• [whatwg/dom] Should we really support modifying an already dispatched event via initEvent()? (#523) (Friday, 27 October)
• Re: [whatwg/dom] Should we really support modifying an already dispatched event via initEvent()? (#523) (Friday, 27 October)
• Re: [whatwg/dom] DOMTokenList.remove() can add an attribute (#462) (Friday, 13 October)

Chris Rebert

• Re: [w3c/uievents-code] Bad grammar in Abstract (#17) (Thursday, 5 October)

cynthia

• Re: [w3c/workers] Should Shared Workers be removed? (#2) (Thursday, 19 October)
• Re: [w3c/workers] Should Shared Workers be removed? (#2) (Thursday, 19 October)
• Re: [w3ctag/design-reviews] Review request: Web Lifecycle for system initiated Discarding & Stopping (#205) (Tuesday, 17 October)

Cyril Auburtin

• Re: [whatwg/dom] Element.prototype.once for event listeners (#524) (Saturday, 28 October)
• Re: [whatwg/dom] Element.prototype.once for event listeners (#524) (Saturday, 28 October)
• [whatwg/dom] Element.prototype.once for event listeners (#524) (Saturday, 28 October)

Daniel Appelquist

• Re: [w3ctag/design-reviews] WebUSB (#108) (Tuesday, 31 October)
• Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141) (Tuesday, 10 October)

Daniel Baulig

• Re: [whatwg/fetch] Handling Partial Content / 206 (#144) (Monday, 30 October)

Daniel Cheng

• Re: [w3c/clipboard-apis] Support for reading custom MIME types from the clipboard (#46) (Monday, 23 October)

Daniel Ehrenberg

• Re: [heycam/webidl] Exposing an interface "on all globals" (#468) (Friday, 27 October)
• Re: [heycam/webidl] Add a frozen record type? (#469) (Tuesday, 24 October)
• Re: [heycam/webidl] Add a frozen record type? (#469) (Tuesday, 24 October)
• [heycam/webidl] Add a frozen record type? (#469) (Tuesday, 24 October)
• Re: [heycam/webidl] Exposing an interface "on all globals" (#468) (Tuesday, 24 October)
• [heycam/webidl] Exposing an interface "on all globals" (#468) (Monday, 23 October)

Daniel Huigens

• [w3c/ServiceWorker] Feature request: Make updatefound an ExtendableEvent (#1208) (Monday, 16 October)

Daniel Murphy

• Re: [w3ctag/design-reviews] Review request for IndexedDB Observers (#189) (Tuesday, 17 October)
• Re: [whatwg/xhr] Should we be pinning Blob URIs on fetches? (#79) (Tuesday, 3 October)

Daniel Stenberg

• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Thursday, 19 October)
• Re: [whatwg/url] why are backslashes accepted for slashes? (#346) (Sunday, 1 October)

Danyao Wang

• Re: [whatwg/dom] Should we really support modifying an already dispatched event via initEvent()? (#523) (Friday, 27 October)

darinadler

• Re: [whatwg/dom] Should we really support modifying an already dispatched event via initEvent()? (#523) (Sunday, 29 October)

Dave Methvin

• Re: [whatwg/dom] Add window.event for web compatibility. (e7cdac7) (Friday, 27 October)

Dave Tapuska

• Re: [w3c/touch-events] Add getModifierState definition to TouchEvent. This matches the text (#91) (Monday, 23 October)
• [w3c/touch-events] Add getModifierState definition to TouchEvent. This matches the text (#91) (Monday, 23 October)
• Re: [w3c/touch-events] should TouchEvent define getModifierState (#41) (Monday, 23 October)
• Re: [w3c/touch-events] Add a default passive algorithm definition for Window, Document and HTMLElement. (#75) (Monday, 23 October)

David Benjamin

• Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165) (Friday, 20 October)

dfabulich

• Re: [w3c/ServiceWorker] Provide a way to skipWaiting when the last tab refreshes (#993) (Monday, 23 October)
• Re: [w3c/ServiceWorker] Provide a way to skipWaiting when the last tab refreshes (#993) (Monday, 23 October)
• Re: [whatwg/dom] Declarative Shadow DOM (#510) (Sunday, 1 October)

Domenic Denicola

• Re: [whatwg/streams] Standard text for TransformStream (#811) (Tuesday, 31 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Tuesday, 31 October)
• Re: [whatwg/streams] Meta: use the common deploy.sh (with POST_BUILD_STEP) (#849) (Tuesday, 31 October)
• Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Tuesday, 31 October)
• Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Tuesday, 31 October)
• Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Tuesday, 31 October)
• Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Tuesday, 31 October)
• Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Tuesday, 31 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Monday, 30 October)
• Re: [whatwg/dom] Should we really support modifying an already dispatched event via initEvent()? (#523) (Friday, 27 October)
• Re: [whatwg/streams] Add examples of using identity transforms to manipulate streams (#847) (Friday, 27 October)
• Re: [whatwg/fetch] Add RequestInit members to Request domintro (#620) (Thursday, 26 October)
• Re: [w3c/ServiceWorker] The classic script's source text isn't defined in HTML any more (#1212) (Thursday, 26 October)
• Re: [w3c/ServiceWorker] The classic script's source text isn't defined in HTML any more (#1212) (Wednesday, 25 October)
• Re: [whatwg/fetch] Address Domenic's Request domintro nits (#619) (Wednesday, 25 October)
• Re: [whatwg/dom] Attributes not ready on element construction? (#522) (Tuesday, 24 October)
• Re: [whatwg/dom] Attributes not ready on element construction? (#522) (Tuesday, 24 October)
• Re: [heycam/webidl] Add a frozen record type? (#469) (Tuesday, 24 October)
• Re: [heycam/webidl] Exposing an interface "on all globals" (#468) (Tuesday, 24 October)
• Re: [whatwg/streams] Initialise readableStrategy without using an object literal (#839) (Monday, 23 October)
• Re: [heycam/webidl] Exposing an interface "on all globals" (#468) (Monday, 23 October)
• Re: [whatwg/streams] Add an example of a transform stream that replaces template tags (#846) (Monday, 23 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Monday, 23 October)
• Re: [whatwg/streams] Add an example of a transform stream that replaces template tags (#846) (Monday, 23 October)
• Re: [whatwg/streams] Add an example of a transform stream that replaces template tags (#846) (Monday, 23 October)
• Re: [whatwg/streams] Add an example of a transform stream that replaces template tags (#846) (Friday, 20 October)
• Re: [whatwg/streams] Add SyncOneToOneTransformFunctionAdaptor example (#843) (Friday, 20 October)
• Re: [whatwg/streams] Add SyncOneToOneTransformFunctionAdaptor example (#843) (Friday, 20 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Friday, 20 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Friday, 20 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Friday, 20 October)
• Re: [whatwg/streams] Initialise readableStrategy without using an object literal (#839) (Friday, 20 October)
• [w3ctag/design-reviews] import.meta.url, and import.meta generally (#208) (Friday, 20 October)
• Re: [whatwg/storage] Consider renaming boxes to bins or something (#51) (Friday, 20 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Friday, 20 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Friday, 20 October)
• Re: [whatwg/fetch] Help removing this bd (#618) (Wednesday, 18 October)
• [heycam/webidl] Make creation of all initial objects/properties/methods/etc. imperative (#467) (Tuesday, 17 October)
• Re: [heycam/webidl] [SecureContext] restrictions on interface vs. interface member are confusing (#153) (Tuesday, 17 October)
• [heycam/webidl] ECMAScript global environment -> realm, as appropriate (#466) (Tuesday, 17 October)
• Re: [heycam/webidl] The [SecureContext] text is unclear on exposure for interfaces (#119) (Tuesday, 17 October)
• Re: [heycam/webidl] [Exposed] doesn't seem to work well with partial interfaces (#154) (Tuesday, 17 October)
• Re: [heycam/webidl] Fix and clarify exposed dfn (#464) (Tuesday, 17 October)
• Re: [heycam/webidl] Add post-processor (#460) (Tuesday, 17 October)
• Re: [w3ctag/design-reviews] HTML General Review (#174) (Tuesday, 17 October)
• Re: [whatwg/fetch] [WIP] Request domintro box (#617) (Monday, 16 October)
• Re: [whatwg/dom] Add [CEReactions] to createElement() (#506) (Monday, 16 October)
• Re: [w3c/webcomponents] Which standard defines :defined (#665) (Friday, 13 October)
• Re: [w3c/webcomponents] 'attributeChangedCallback' not working with a data attribute on Firefox or Edge (#637) (Friday, 13 October)
• Re: [w3c/webcomponents] 'attributeChangedCallback' not working with a data attribute on Firefox or Edge (#637) (Friday, 13 October)
• Re: [w3c/webcomponents] Constructor arguments in custom elements (#605) (Friday, 13 October)
• Re: [w3c/webcomponents] Constructor arguments in custom elements (#605) (Friday, 13 October)
• Re: [whatwg/dom] Add [CEReactions] to createElement() (#506) (Friday, 13 October)
• Re: [whatwg/dom] Add [CEReactions] to createElement() (#506) (Friday, 13 October)
• Re: [whatwg/streams] Initialise readableStrategy without using an object literal (#839) (Friday, 13 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Friday, 13 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Thursday, 12 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Thursday, 12 October)
• Re: [whatwg/streams] Initialise readableStrategy without using an object literal (#839) (Thursday, 12 October)
• Re: [whatwg/streams] Meta: Make local-watch.js more robust (#841) (Thursday, 12 October)
• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Thursday, 12 October)
• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Thursday, 12 October)
• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Thursday, 12 October)
• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Thursday, 12 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Thursday, 12 October)
• Re: [whatwg/streams] Remove inaccurate note about ReadableStreamDefaultControllerEnqueue (#829) (Wednesday, 11 October)
• Re: [whatwg/streams] Note on ReadableStreamDefaultControllerEnqueue is inaccurate (#824) (Wednesday, 11 October)
• Re: [whatwg/streams] Add a local variable to TransformStreamDefaultControllerTerminate (#838) (Wednesday, 11 October)
• Re: [whatwg/streams] Fix brand check exception message from terminate() method (#837) (Wednesday, 11 October)
• Re: [heycam/webidl] Add mixins (#433) (Wednesday, 11 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Wednesday, 11 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Wednesday, 11 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Wednesday, 11 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Wednesday, 11 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Wednesday, 11 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Warn readers that V1 is missing features compared to the nightly (#1205) (Wednesday, 11 October)
• Re: [heycam/webidl] Check grammar is LL(1) as part of Travis builds (#458) (Wednesday, 11 October)
• Re: [whatwg/url] Percent-encode additional characters in "fragment state". (#347) (Tuesday, 10 October)
• Re: [whatwg/streams] Move TransformStreamDefaultControllerTerminate down (#835) (Tuesday, 10 October)
• Re: [whatwg/streams] Use some logging framework (#499) (Tuesday, 10 October)
• Re: [whatwg/streams] Use "debug" package for logging (#831) (Tuesday, 10 October)
• Re: [whatwg/streams] Remove assert() descriptions (#834) (Tuesday, 10 October)
• Re: [whatwg/streams] Editorial: address minor nits in the FAQ (#833) (Tuesday, 10 October)
• Re: [whatwg/streams] Editorial: address minor nits in the FAQ (#833) (Tuesday, 10 October)
• Re: [whatwg/streams] Remove legacy test infrastructure and abstract-ops tests (#832) (Tuesday, 10 October)
• Re: [whatwg/streams] Remove legacy test infrastructure and abstract-ops tests (#832) (Tuesday, 10 October)
• Re: [whatwg/streams] Remove legacy test infrastructure and abstract-ops tests (#832) (Tuesday, 10 October)
• Re: [whatwg/streams] Remove legacy test infrastructure and abstract-ops tests (#832) (Tuesday, 10 October)
• Re: [heycam/webidl] Add mixins (#433) (Friday, 6 October)
• [whatwg/streams] Remove legacy test infrastructure and abstract-ops tests (#832) (Friday, 6 October)
• Re: [whatwg/streams] Use "debug" package for logging (#831) (Friday, 6 October)
• Re: [whatwg/streams] Switch from "assert" to "better-assert" in reference implementation (#830) (Friday, 6 October)
• Re: [whatwg/streams] Remove inaccurate note about ReadableStreamDefaultControllerEnqueue (#829) (Friday, 6 October)
• Re: [whatwg/streams] Add a local variable to TransformStreamDefaultSink abort() (#828) (Friday, 6 October)
• Re: [whatwg/streams] Test terminate() and error() inside flush() (#827) (Friday, 6 October)
• Re: [whatwg/streams] Stop controller.error() and controller.terminate() throwing in unexpected states (#822) (Friday, 6 October)
• Re: [whatwg/streams] Make error() and terminate() do nothing when stream is errored (#826) (Friday, 6 October)
• Re: [whatwg/streams] Make error() and terminate() do nothing when stream is errored (#826) (Friday, 6 October)
• Re: [whatwg/streams] Remove TransformStreamDefaultSinkDefaultTransform (#823) (Friday, 6 October)
• Re: [whatwg/streams] Remove TransformStreamDefaultSinkDefaultTransform (#823) (Friday, 6 October)
• Re: [whatwg/streams] Remove TransformStreamDefaultSinkDefaultTransform (#823) (Friday, 6 October)
• Re: [whatwg/streams] Add an extension point for byte transform streams (#820) (Friday, 6 October)
• Re: [whatwg/streams] Add an extension point for byte transform streams (#820) (Friday, 6 October)
• Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Thursday, 5 October)
• Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Thursday, 5 October)
• Re: [heycam/webidl] [WIP] Add mixins (#433) (Tuesday, 3 October)
• Re: [heycam/webidl] Editorial: fix spelling mistakes (#454) (Tuesday, 3 October)
• Re: [heycam/webidl] [WIP] Add mixins (#433) (Tuesday, 3 October)
• Re: [heycam/webidl] Dot notation for dictionary members is not spec'ed. (#453) (Tuesday, 3 October)
• Re: [whatwg/streams] Add TransformStreamDefaultController terminate() method (#818) (Monday, 2 October)
• [whatwg/streams] Is it bad that readableController.error() throws but writableController.error() no-ops in non-readable/writable states? (#821) (Monday, 2 October)
• Re: [whatwg/streams] throw instead of returning Promise.reject() from handlers (#819) (Monday, 2 October)
• Re: [whatwg/streams] TransformStream: Verify behaviour of abort() during write() (#817) (Monday, 2 October)
• Re: [whatwg/streams] Remove the check of the resolved value of _backpressurePromise (#816) (Monday, 2 October)
• Re: [whatwg/streams] Verify that transformer start() is called as a method (#815) (Monday, 2 October)
• Re: [whatwg/streams] Verify that transformer start() is called as a method (#815) (Monday, 2 October)
• Re: [whatwg/streams] Add an extension point for byte transform streams (#820) (Monday, 2 October)
• Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Monday, 2 October)
• Re: [whatwg/url] why are backslashes accepted for slashes? (#346) (Sunday, 1 October)
• Re: [whatwg/xhr] chrome-extension://agddmammmnpdglmincfngjfnehmopoln/js/content_script.js (#154) (Sunday, 1 October)

Dominic Farolino

• [whatwg/fetch] Add RequestInit members to Request domintro (#620) (Thursday, 26 October)
• Re: [whatwg/fetch] Address Domenic's Request domintro nits (#619) (Wednesday, 25 October)
• Re: [whatwg/fetch] Address Domenic's Request domintro nits (#619) (Wednesday, 25 October)
• Re: [whatwg/fetch] Address Domenic's Request domintro nits (#619) (Wednesday, 25 October)
• [whatwg/fetch] Address Domenic's Request domintro nits (#619) (Saturday, 21 October)
• Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365) (Friday, 20 October)
• Re: [w3c/touch-events] Add a default passive algorithm definition for Window, Document and HTMLElement. (#75) (Friday, 20 October)
• Re: [w3c/touch-events] Add a default passive algorithm definition for Window, Document and HTMLElement. (#75) (Friday, 20 October)
• Re: [whatwg/fetch] [WIP] Request domintro box (#617) (Monday, 16 October)
• Re: [whatwg/fetch] [WIP] Request domintro box (#617) (Monday, 16 October)
• Re: [whatwg/fetch] [WIP] Request domintro box (#617) (Monday, 16 October)
• Re: [whatwg/fetch] [WIP] Request domintro box (#617) (Monday, 16 October)
• Re: [whatwg/fetch] Add domintro explanations for web developers (#543) (Monday, 16 October)
• [whatwg/fetch] [WIP] Request domintro box (#617) (Monday, 16 October)

Dominique Hazael-Massieux

• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Monday, 16 October)

Dr. Ken Lunde

• Re: [whatwg/encoding] If gb18030 is revised, consider aligning the Encoding Standard (#27) (Sunday, 15 October)

drwez

• Re: [w3c/uievents] Add specification for AltGraph key & modifier behaviour (#147) (Tuesday, 10 October)

Duarte Cunha Leão

• Re: [w3c/webcomponents] HTML Modules (#645) (Thursday, 5 October)

effulgentsia

• Re: [w3c/webcomponents] Custom attribute names conflicting with built-in attribute names (#654) (Wednesday, 25 October)

EiraGe

• Re: [w3c/uievents] MouseEvent.screenX/Y coordinate space id not clear (#150) (Wednesday, 4 October)

Emily Stark

• Re: [whatwg/fetch] Document CORS safelist exceptions (#621) (Friday, 27 October)
• Re: [whatwg/fetch] Document CORS safelist exceptions (#621) (Friday, 27 October)
• Re: [whatwg/fetch] Document CORS safelist exceptions (#621) (Thursday, 26 October)
• [whatwg/fetch] Document CORS safelist exceptions (#621) (Thursday, 26 October)

eranroz

• Re: [w3c/editing] INPUT/TEXTAREA should support subset of execCommand (#160) (Friday, 20 October)

fantasai

• Re: [whatwg/storage] Consider renaming boxes to bins or something (#51) (Monday, 23 October)
• Re: [whatwg/storage] Consider renaming boxes to bins or something (#51) (Thursday, 19 October)
• [whatwg/storage] Consider renaming boxes to bins or something (#51) (Thursday, 19 October)

Fuqiao Xue

• [w3c/IndexedDB] Mark the Revision History and the Acknowledgements sections as non-normative (#220) (Saturday, 21 October)
• [w3c/IndexedDB] Validate HTML (#219) (Thursday, 19 October)
• Re: [w3c/IndexedDB] Implementation report (#213) (Thursday, 12 October)
• Re: [w3c/IndexedDB] Implementation report (#213) (Wednesday, 11 October)
• Re: [w3c/IndexedDB] Implementation report (#213) (Wednesday, 11 October)
• Re: [w3c/IndexedDB] Fix several issue URLs (#218) (Monday, 9 October)
• [w3c/IndexedDB] Fix several issue URLs (#218) (Monday, 9 October)

Gary Kacmarcik

• Re: [w3c/clipboard-apis] Ask for tests for normative changes in CONTRIBUTING.md (#56) (Wednesday, 18 October)
• Re: [w3c/uievents] Ask for tests for normative changes in CONTRIBUTING.md (#163) (Wednesday, 18 October)
• Re: [w3c/uievents] Add webidl code snippet for input and beforeinput events (#162) (Tuesday, 17 October)
• Re: [w3c/clipboard-apis] User gesture requirement for Clipboard API access (#52) (Tuesday, 17 October)
• Re: [w3c/clipboard-apis] Clipboard Permission (#51) (Tuesday, 17 October)
• Re: [w3c/clipboard-apis] Make sure examples and tests know that ClipboardEvent constructor is useless (#27) (Monday, 16 October)
• Re: [w3c/clipboard-apis] Make sure examples and tests know that ClipboardEvent constructor is useless (#27) (Monday, 16 October)
• Re: [w3c/clipboard-apis] Create an easier to use API (#12) (Monday, 16 October)
• Re: [w3c/clipboard-apis] Create an easier to use API (#12) (Monday, 16 October)
• Re: [w3c/clipboard-apis] Where would one get a DataTransfer to hand to the ClipboardEvent constructor? (#33) (Monday, 16 October)
• Re: [w3c/clipboard-apis] Where would one get a DataTransfer to hand to the ClipboardEvent constructor? (#33) (Monday, 16 October)
• Re: [w3c/clipboard-apis] Aling 'set clipboard event target' spec. to current implementation 'out there' (#40) (Monday, 16 October)
• Re: [w3c/clipboard-apis] Data store's mode should be readonly when firing a paste event (#45) (Monday, 16 October)
• Re: [w3c/permissions] A more modest request() (#158) (Wednesday, 11 October)
• Re: [w3c/clipboard-apis] User gesture requirement for Clipboard API access (#52) (Wednesday, 11 October)
• Re: [w3c/WebPlatformWG] TPAC agenda: Tue Nov 7 (Editing TF) (#93) (Monday, 9 October)
• Re: [w3c/uievents-code] Ed: Include more international keyboard examples (#11) (Thursday, 5 October)
• Re: [w3c/uievents-code] Bad grammar in Abstract (#17) (Thursday, 5 October)
• Re: [w3c/uievents-code] Bad grammar in Abstract (#17) (Thursday, 5 October)
• Re: [w3c/uievents-code] Bad grammar in Abstract (#17) (Thursday, 5 October)
• Re: [w3c/uievents-code] Bad grammar in Abstract (#17) (Thursday, 5 October)
• Re: [w3c/uievents-code] Bikeshed syntax problem in section 3 (#18) (Thursday, 5 October)
• Re: [w3c/uievents-code] Bikeshed syntax problem in section 3 (#18) (Thursday, 5 October)
• Re: [w3c/uievents-code] Implementation report (#19) (Thursday, 5 October)
• Re: [w3c/uievents-code] Implementation report (#19) (Thursday, 5 October)
• Re: [w3c/uievents-code] Need an implementation report (#20) (Thursday, 5 October)
• Re: [w3c/uievents-code] Need an implementation report (#20) (Thursday, 5 October)
• Re: [w3c/clipboard-apis] Clipboard Permission (#51) (Thursday, 5 October)
• Re: [w3c/uievents-key] Implementation report (#45) (Wednesday, 4 October)

Geoffrey Sneddon

• Re: [w3c/permissions] Introduce "Automation" section (#151) (Monday, 30 October)

gked

• Re: [w3c/clipboard-apis] User gesture requirement for Clipboard API access (#52) (Wednesday, 11 October)
• Re: [w3c/clipboard-apis] Pull request for Issue #40 (#42) (Tuesday, 10 October)
• [w3c/uievents] Add webidl code snippet for input and beforeinput events (#162) (Tuesday, 10 October)

Gordon P. Hemsley

• Re: [whatwg/url] "the substring from pointer in input" (#349) (Sunday, 29 October)
• [whatwg/url] "the substring from pointer in input" (#349) (Sunday, 29 October)

Guillaume Lakano

• Re: [w3c/IndexedDB] API to enumerate databases (#31) (Tuesday, 24 October)
• Re: [w3c/IndexedDB] API to enumerate databases (#31) (Tuesday, 24 October)
• Re: [w3c/IndexedDB] API to enumerate databases (#31) (Tuesday, 24 October)
• Re: [w3c/IndexedDB] API to enumerate databases (#31) (Tuesday, 24 October)

Hannan Ali

• Re: [whatwg/streams] Add a Random Values Generator Demonstration (#844) (Tuesday, 17 October)
• [whatwg/streams] Add a Random Values Generator Demonstration (#844) (Tuesday, 17 October)

Harald Alvestrand

• Re: [w3ctag/design-reviews] WebRTC Stats review (#148) (Wednesday, 25 October)

Hayato Ito

• Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Tuesday, 31 October)
• Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Tuesday, 31 October)
• Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Tuesday, 31 October)
• Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Tuesday, 31 October)
• Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Tuesday, 31 October)
• Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Tuesday, 31 October)
• Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Tuesday, 31 October)
• Re: [whatwg/dom] Add window.event for web compatibility. (e7cdac7) (Monday, 30 October)
• Re: [whatwg/dom] Should we really support modifying an already dispatched event via initEvent()? (#523) (Monday, 30 October)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Friday, 27 October)
• Re: [whatwg/dom] Add window.event for web compatibility. (e7cdac7) (Friday, 27 October)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Thursday, 26 October)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Thursday, 26 October)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Wednesday, 25 October)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Wednesday, 25 October)
• Re: [w3c/webcomponents] Detecting finally-distributed nodes. (#675) (Tuesday, 17 October)
• Re: [w3c/webcomponents] Detecting finally-distributed nodes. (#675) (Monday, 16 October)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Wednesday, 11 October)
• Re: [whatwg/dom] Set event.target to null when dispatching finishes at ShadowRoot (#513) (Friday, 6 October)

Hiroki Nakagawa

• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Wednesday, 11 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Tuesday, 10 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Tuesday, 10 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Friday, 6 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Thursday, 5 October)

Ian Kilpatrick

• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Friday, 27 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Friday, 27 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Wednesday, 25 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Wednesday, 25 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Wednesday, 11 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Wednesday, 11 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Wednesday, 11 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Wednesday, 11 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Wednesday, 11 October)

Ilya Grigorik

• Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206) (Tuesday, 31 October)
• Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206) (Sunday, 29 October)
• Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206) (Saturday, 28 October)
• Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206) (Friday, 27 October)

Irakli Gozalishvili

• Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Wednesday, 25 October)
• Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Wednesday, 25 October)
• Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Wednesday, 25 October)

Isiah Meadows

• [w3c/IndexedDB] Should it be clarified that `IDBDatabase.close()` is idempotent? (#222) (Tuesday, 24 October)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Thursday, 12 October)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Thursday, 12 October)

Ivan Nikulin

• Re: [whatwg/dom] Declarative Shadow DOM (#510) (Monday, 2 October)

Jake Archibald

• Re: [w3c/ServiceWorker] Should we expose reserved clients? (#1216) (Thursday, 26 October)
• Re: [w3c/ServiceWorker] Should we expose reserved clients? (#1216) (Thursday, 26 October)
• Re: [w3c/ServiceWorker] Should we expose reserved clients? (#1216) (Thursday, 26 October)
• Re: [w3c/ServiceWorker] Navigating reserved clients (#1215) (Thursday, 26 October)
• Re: [w3c/ServiceWorker] Should we expose reserved clients? (#1216) (Thursday, 26 October)
• [w3c/ServiceWorker] Should we expose reserved clients? (#1216) (Thursday, 26 October)
• Re: [w3c/ServiceWorker] Navigating reserved clients (#1215) (Wednesday, 25 October)
• Re: [w3c/ServiceWorker] Navigating reserved clients (#1215) (Wednesday, 25 October)
• [w3c/ServiceWorker] Navigating reserved clients (#1215) (Wednesday, 25 October)
• Re: [w3c/ServiceWorker] Remove foreign fetch (#1207) (Wednesday, 25 October)
• Re: [w3c/ServiceWorker] Remove foreign fetch (#1207) (Wednesday, 25 October)
• Re: [w3c/ServiceWorker] Remove foreign fetch (#1207) (Friday, 13 October)
• Re: [w3c/ServiceWorker] Remove foreign fetch (#1207) (Friday, 13 October)
• Re: [w3c/ServiceWorker] Remove foreign fetch (#1207) (Friday, 13 October)
• Re: [w3c/ServiceWorker] Remove foreign fetch (#1207) (Friday, 13 October)
• [w3c/ServiceWorker] Remove foreign fetch (#1207) (Friday, 13 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Friday, 13 October)
• Re: [w3c/ServiceWorker] Mixed feelings about ServiceWorker for module loader (#1203) (Thursday, 12 October)
• Re: [w3c/ServiceWorker] Mixed feelings about ServiceWorker for module loader (#1203) (Thursday, 12 October)
• Re: [w3c/ServiceWorker] resurrected service workers don't fire an activate event which may break expectations (#1204) (Thursday, 12 October)
• Re: [w3c/ServiceWorker] resurrected service workers don't fire an activate event which may break expectations (#1204) (Thursday, 12 October)
• Re: [w3c/ServiceWorker] Warn readers that V1 is missing features compared to the nightly (#1205) (Thursday, 12 October)
• Re: [w3c/ServiceWorker] Warn readers that V1 is missing features compared to the nightly (#1205) (Thursday, 12 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Thursday, 12 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Thursday, 12 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Thursday, 12 October)
• Re: [whatwg/fetch] FetchObserver (for a single fetch) (#607) (Thursday, 12 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Wednesday, 11 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Wednesday, 11 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Wednesday, 11 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Warn readers that V1 is missing features compared to the nightly (#1205) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Warn readers that V1 is missing features compared to the nightly (#1205) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Handing fetch termination (#1178) (Wednesday, 11 October)
• [w3c/ServiceWorker] Create F2F agenda - 7 November 2017 (#1206) (Wednesday, 11 October)
• [w3c/ServiceWorker] Warn readers that V1 is missing features compared to the nightly (#1205) (Wednesday, 11 October)
• Re: [whatwg/fetch] FetchObserver (for a single fetch) (#607) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] reflect WG change [depends on another PR] (#1202) (Tuesday, 10 October)
• Re: [w3c/ServiceWorker] reflect WG change [depends on another PR] (#1202) (Tuesday, 10 October)
• Re: [w3c/ServiceWorker] reflect WG change [depends on another PR] (#1202) (Tuesday, 10 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Tuesday, 10 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Tuesday, 10 October)
• Re: [w3c/ServiceWorker] Proposal: Allow addEventListener/removeEventListener for 'fetch' to called at anytime (#1195) (Tuesday, 3 October)
• Re: [whatwg/fetch] History behind the decision to make fetch return a Promise (#611) (Monday, 2 October)

jan-ivar

• Re: [w3c/permissions] Allowing permission for non-fully-active documents is weird and should be disallowed (#162) (Friday, 6 October)
• [w3c/permissions] Allowing permission for non-fully-active documents is weird and should be disallowed (#162) (Friday, 6 October)
• Re: [w3c/permissions] "Requesting more permission" algorithms are tightly coupled to prompts (#153) (Friday, 6 October)
• Re: [w3c/permissions] A more modest request() (#158) (Monday, 2 October)

Janne Koschinski

• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Friday, 20 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Friday, 20 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Friday, 20 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Friday, 20 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Friday, 20 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Friday, 20 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Friday, 20 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Friday, 20 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Friday, 20 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Friday, 20 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Friday, 20 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Friday, 20 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Friday, 20 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Thursday, 19 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Thursday, 19 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Thursday, 19 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Thursday, 19 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Thursday, 19 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Thursday, 19 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Thursday, 19 October)

Jason Strimpel

• Re: [w3c/webcomponents] light dom availability (#673) (Tuesday, 3 October)
• Re: [w3c/webcomponents] light dom availability (#673) (Tuesday, 3 October)
• Re: [w3c/webcomponents] light dom availability (#673) (Monday, 2 October)
• Re: [w3c/webcomponents] light dom availability (#673) (Monday, 2 October)
• Re: [w3c/webcomponents] light dom availability (#673) (Monday, 2 October)
• [w3c/webcomponents] light dom availability (#673) (Monday, 2 October)

Jasper St. Pierre

• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Thursday, 19 October)

Jeffrey Yasskin

• Re: [w3c/permissions] Granting permission to non-fully-active documents is weird and should be disallowed (#162) (Sunday, 8 October)

jgraham

• Re: [whatwg/storage] Rename boxes to bins (#52) (Wednesday, 25 October)

jianli-chromium

• Re: [whatwg/dom] Declarative Shadow DOM (#510) (Thursday, 5 October)

Jimmy Thomsen

• Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Thursday, 26 October)

Joe Pea

• Re: [w3c/webcomponents] A new attribute similar to is="", but would allow multiple behaviors to be attached to a given element. (#662) (Friday, 27 October)
• Re: [w3c/webcomponents] A new attribute similar to is="", but would allow multiple behaviors to be attached to a given element. (#662) (Friday, 27 October)
• Re: [whatwg/dom] Attributes not ready on element construction? (#522) (Wednesday, 25 October)
• Re: [whatwg/dom] Attributes not ready on element construction? (#522) (Tuesday, 24 October)
• Re: [whatwg/dom] Attributes not ready on element construction? (#522) (Tuesday, 24 October)
• Re: [whatwg/dom] Attributes not ready on element construction? (#522) (Tuesday, 24 October)
• [whatwg/dom] Attributes not ready on element construction? (#522) (Tuesday, 24 October)
• Re: [w3c/webcomponents] Detecting finally-distributed nodes. (#675) (Monday, 16 October)
• [whatwg/dom] MutationObserver attribute change record only gives us the `oldValue`, but not the `newValue`? (#521) (Sunday, 15 October)
• Re: [w3c/webcomponents] Why does attributeChangedCallback fire when a new attribute value is the same? (#676) (Friday, 13 October)
• Re: [whatwg/dom] MutationObserver: observing attribute changes fires even if the value didn't change. (#520) (Friday, 13 October)
• Re: [whatwg/dom] MutationObserver: observing attribute changes fires even if the value didn't change. (#520) (Friday, 13 October)
• [w3c/webcomponents] Why does attributeChangedCallback fire when a new attribute value is the same? (#676) (Friday, 13 October)
• [whatwg/dom] MutationObserver: observing attribute changes fires even if the value didn't change. (#520) (Friday, 13 October)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Tuesday, 10 October)
• Re: [w3c/webcomponents] How to avoid memory leaks when detecting custom elements? (#674) (Tuesday, 10 October)
• Re: [w3c/webcomponents] Custom Element - untrackable upgrade (#671) (Tuesday, 10 October)
• Re: [w3c/webcomponents] Custom Element - untrackable upgrade (#671) (Tuesday, 10 October)
• Re: [w3c/webcomponents] Custom Element - untrackable upgrade (#671) (Tuesday, 10 October)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Tuesday, 10 October)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Tuesday, 10 October)
• Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447) (Tuesday, 10 October)
• Re: [w3c/webcomponents] How to avoid memory leaks when detecting custom elements? (#674) (Tuesday, 10 October)
• Re: [w3c/webcomponents] How to avoid memory leaks when detecting custom elements? (#674) (Tuesday, 10 October)
• Re: [w3c/webcomponents] How to avoid memory leaks when detecting custom elements? (#674) (Tuesday, 10 October)
• Re: [w3c/webcomponents] How to avoid memory leaks when detecting custom elements? (#674) (Tuesday, 10 October)
• [w3c/webcomponents] Detecting finally-distributed nodes. (#675) (Tuesday, 10 October)
• Re: [w3c/webcomponents] How to avoid memory leaks when detecting custom elements? (#674) (Monday, 9 October)
• Re: [w3c/webcomponents] Custom Element definition ordering can cause difficult-to-find bugs. (#668) (Monday, 9 October)
• Re: [w3c/webcomponents] Custom Element definition ordering can cause difficult-to-find bugs. (#668) (Monday, 9 October)
• Re: [w3c/webcomponents] Custom Element definition ordering can cause difficult-to-find bugs. (#668) (Sunday, 8 October)
• Re: [w3c/webcomponents] Custom Element definition ordering can cause difficult-to-find bugs. (#668) (Sunday, 8 October)
• Re: [w3c/webcomponents] Custom Element definition ordering can cause difficult-to-find bugs. (#668) (Sunday, 8 October)
• Re: [w3c/webcomponents] Consider adding a childrenChangedCallback or something (#619) (Sunday, 8 October)
• Re: [w3c/webcomponents] Consider adding a childrenChangedCallback or something (#619) (Sunday, 8 October)
• Re: [w3c/webcomponents] Consider adding a childrenChangedCallback or something (#619) (Sunday, 8 October)
• Re: [w3c/webcomponents] Custom Element definition ordering can cause difficult-to-find bugs. (#668) (Sunday, 8 October)
• Re: [w3c/webcomponents] Custom Element definition ordering can cause difficult-to-find bugs. (#668) (Sunday, 8 October)
• Re: [w3c/webcomponents] Custom Element definition ordering can cause difficult-to-find bugs. (#668) (Sunday, 8 October)
• Re: [w3c/webcomponents] Custom Element definition ordering can cause difficult-to-find bugs. (#668) (Sunday, 8 October)
• Re: [w3c/webcomponents] Custom Element definition ordering can cause difficult-to-find bugs. (#668) (Sunday, 8 October)
• Re: [w3c/webcomponents] Custom Element definition ordering can cause difficult-to-find bugs. (#668) (Sunday, 8 October)
• Re: [w3c/webcomponents] Custom Element definition ordering can cause difficult-to-find bugs. (#668) (Sunday, 8 October)
• Re: [w3c/webcomponents] Custom Element definition ordering can cause difficult-to-find bugs. (#668) (Sunday, 8 October)
• [w3c/webcomponents] How to avoid memory leaks when detecting custom elements? (#674) (Sunday, 8 October)
• Re: [w3c/webcomponents] Custom Element definition ordering can cause difficult-to-find bugs. (#668) (Sunday, 8 October)
• Re: [w3c/webcomponents] Custom Element - untrackable upgrade (#671) (Sunday, 8 October)
• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Tuesday, 3 October)
• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Tuesday, 3 October)
• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Sunday, 1 October)

Johannes Wilm

• Re: [w3ctag/design-reviews] Request for TAG review of Input events level 2 (#173) (Tuesday, 31 October)
• Re: [w3c/WebPlatformWG] TPAC agenda: Tue Nov 7 (Editing TF) (#93) (Saturday, 28 October)
• Re: [w3c/WebPlatformWG] TPAC agenda: Tue Nov 7 (Editing TF) (#93) (Thursday, 26 October)
• Re: [w3c/editing] make need of execCommand to hide table controls go away on FF (#171) (Sunday, 8 October)
• [w3c/editing] make need of execCommand to hide table controls go away on FF (#171) (Sunday, 8 October)

John M. Harris, Jr.

• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Thursday, 19 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Thursday, 19 October)

Jonathon Kereliuk

• Re: [w3c/permissions] Introduce "Automation" section (#151) (Monday, 16 October)

Joseph Pecoraro

• [w3c/ServiceWorker] Typo: "is dispatched a set of" (#1214) (Monday, 23 October)

Joshua Bell

• Re: [w3c/IndexedDB] boolean should be a valid key (#76) (Tuesday, 31 October)
• Re: [whatwg/dom] Element.prototype.once for event listeners (#524) (Saturday, 28 October)
• [w3c/IndexedDB] Provide finer control over open request edge cases (#223) (Thursday, 26 October)
• Re: [w3c/IndexedDB] Should it be clarified that `IDBDatabase.close()` is idempotent? (#222) (Tuesday, 24 October)
• Re: [w3c/IndexedDB] Mark the Revision History and the Acknowledgements sections as non-normative (#220) (Sunday, 22 October)
• Re: [whatwg/storage] Consider renaming boxes to bins or something (#51) (Friday, 20 October)
• Re: [w3c/IndexedDB] Validate HTML (#219) (Thursday, 19 October)
• Re: [w3c/IndexedDB] Validate HTML (#219) (Thursday, 19 October)
• Re: [w3c/IndexedDB] Implementation report (#213) (Tuesday, 17 October)
• Re: [w3c/IndexedDB] Implementation report (#213) (Wednesday, 11 October)
• Re: [w3c/IndexedDB] Implementation report (#213) (Wednesday, 11 October)
• Re: [w3c/IndexedDB] Fix several issue URLs (#218) (Monday, 9 October)
• Re: [w3c/IndexedDB] Fix several issue URLs (#218) (Monday, 9 October)

juj

• Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141) (Saturday, 21 October)

Julian Reschke

• Re: [whatwg/url] Consider percent-encoding more characters in "fragment state" (#344) (Tuesday, 10 October)
• Re: [whatwg/url] Consider percent-encoding more characters in "fragment state" (#344) (Tuesday, 10 October)
• Re: [whatwg/url] Consider percent-encoding more characters in "fragment state" (#344) (Tuesday, 10 October)
• Re: [whatwg/url] Consider percent-encoding more characters in "fragment state" (#344) (Tuesday, 10 October)

Jun

• Re: [w3c/ServiceWorker] Require JS content type for serviceworkers is not present in the spec (#1209) (Monday, 16 October)
• Re: [w3c/ServiceWorker] Require JS content type for serviceworkers is not present in the spec (#1209) (Monday, 16 October)
• [w3c/ServiceWorker] Require JS content type for serviceworkers is not present in the spec (#1209) (Monday, 16 October)

Jungkee Song

• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Friday, 27 October)
• Re: [w3c/ServiceWorker] Navigating reserved clients (#1215) (Thursday, 26 October)
• Re: [w3c/ServiceWorker] Navigating reserved clients (#1215) (Thursday, 26 October)
• Re: [w3c/ServiceWorker] Navigating reserved clients (#1215) (Thursday, 26 October)
• Re: [w3c/ServiceWorker] The classic script's source text isn't defined in HTML any more (#1212) (Thursday, 26 October)
• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Tuesday, 24 October)
• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Monday, 23 October)
• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Monday, 23 October)
• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Monday, 23 October)
• [w3c/ServiceWorker] The classic script's source text isn't defined in HTML any more (#1212) (Friday, 20 October)
• Re: [w3c/ServiceWorker] Block 206s entering the cache (via put & addAll) (#937) (Tuesday, 17 October)
• Re: [w3c/ServiceWorker] Block partial responses entering the cache (#1210) (Tuesday, 17 October)
• [w3c/ServiceWorker] Block partial responses entering the cache (#1210) (Tuesday, 17 October)
• Re: [w3c/ServiceWorker] Remove foreign fetch (#1207) (Monday, 16 October)
• Re: [w3c/ServiceWorker] Handing fetch termination (#1178) (Monday, 16 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Friday, 13 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Friday, 13 October)
• Re: [w3c/ServiceWorker] addAll should resolve when the cache is fully & successfully written (#884) (Friday, 13 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Friday, 13 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Friday, 13 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Friday, 13 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Friday, 13 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Friday, 13 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Friday, 13 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Friday, 13 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Friday, 13 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Friday, 13 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Friday, 13 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Friday, 13 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Thursday, 12 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Thursday, 12 October)
• Re: [w3c/ServiceWorker] Warn readers that V1 is missing features compared to the nightly (#1205) (Thursday, 12 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Thursday, 12 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Warn readers that V1 is missing features compared to the nightly (#1205) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Warn readers that V1 is missing features compared to the nightly (#1205) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] reflect WG change [depends on another PR] (#1202) (Tuesday, 10 October)

jungshik

• Re: [whatwg/encoding] If gb18030 is revised, consider aligning the Encoding Standard (#27) (Monday, 16 October)
• Re: [whatwg/encoding] If gb18030 is revised, consider aligning the Encoding Standard (#27) (Friday, 13 October)

Justin Novosad

• Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141) (Thursday, 19 October)

KaiChen

• Re: [whatwg/xhr] does "remote address" in xhr response standard ? (#156) (Wednesday, 4 October)
• [whatwg/xhr] does "remote address" in xhr response standard ? (#156) (Tuesday, 3 October)

Kelvin Yong

• Re: [w3c/WebPlatformWG] TPAC agenda: Thu Nov 9 (WebPlat general) (#94) (Monday, 23 October)

Kenneth Rohde Christiansen

• Re: [w3c/manifest] Create a test suite for the specification (#623) (Thursday, 19 October)
• Re: [w3c/manifest] Richer splash screen backgrounds (#589) (Wednesday, 18 October)
• Re: [w3c/manifest] Added missing space. (#616) (Wednesday, 18 October)
• Re: [w3c/manifest] Create a test suite for the specification (#623) (Wednesday, 18 October)
• [w3c/manifest] Create a test suite for the specification (#623) (Wednesday, 18 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Friday, 13 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Friday, 13 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 10 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 10 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 10 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 10 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 10 October)
• [w3c/manifest] IDL: Make name required (#622) (Tuesday, 10 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 10 October)
• Re: [heycam/webidl] Dot notation for dictionary members is not spec'ed. (#453) (Tuesday, 3 October)
• [w3c/manifest] Use Infra spec for iterations (#621) (Tuesday, 3 October)
• Re: [heycam/webidl] Dot notation for dictionary members is not spec'ed. (#453) (Tuesday, 3 October)
• Re: [heycam/webidl] Dot notation for Web IDL is not spec'ed. (#453) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• [heycam/webidl] Dot notation for Web IDL is not spec'ed. (#453) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Remove Trim() logic on string members (#620) (Tuesday, 3 October)
• Re: [w3c/manifest] Remove Trim() logic on string members (#620) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Monday, 2 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Monday, 2 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Monday, 2 October)

Kenton Varda

• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Saturday, 21 October)
• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Saturday, 14 October)
• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Thursday, 12 October)
• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Thursday, 12 October)

klk-

• Re: [w3c/FileAPI] Add method to read file into user given Uint8Array (#83) (Thursday, 12 October)

Krzysztof Kotowicz

• Re: [w3ctag/design-reviews] Trusted Types (#198) (Thursday, 12 October)

L. David Baron

• Re: [w3ctag/design-reviews] Serialization of natural language in data formats such as JSON [I18N] (#178) (Tuesday, 31 October)
• Re: [w3ctag/design-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76) (Tuesday, 31 October)
• Re: [w3ctag/design-reviews] Review request for WebVR (#185) (Tuesday, 24 October)

Lucy Linder

• Re: [w3c/manifest] Hope for external `start_url`s (#276) (Saturday, 28 October)

Léonie Watson

• Re: [w3c/IndexedDB] CFC: Move IndexedDB 2.0 to PR (#221) (Tuesday, 31 October)
• Re: [w3c/IndexedDB] CFC: Move IndexedDB 2.0 to PR (#221) (Tuesday, 31 October)
• [w3c/uievents-key] Time to CR? (#46) (Thursday, 26 October)
• [w3c/uievents-code] Time to exit CR? (#21) (Thursday, 26 October)
• [w3c/uievents] Time to CR? (#168) (Thursday, 26 October)
• Re: [w3c/push-api] Wide review tracker (#265) (Thursday, 26 October)
• [w3c/FileAPI] Update the WD (#86) (Monday, 23 October)
• [w3c/IndexedDB] CFC: Move IndexedDB 2.0 to PR (#221) (Monday, 23 October)
• Re: [w3ctag/design-reviews] Intersection Observer review (#197) (Thursday, 19 October)
• Re: [w3c/WebPlatformWG] TPAC agenda: Tue Nov 7 (Editing TF) (#93) (Monday, 9 October)
• Re: [w3c/WebPlatformWG] TPAC agenda: Thu Nov 9 (WebPlat general) (#94) (Friday, 6 October)
• Re: [w3c/WebPlatformWG] TPAC agenda: Thu Nov 9 (WebPlat general) (#94) (Tuesday, 3 October)

Majid Valipour

• Re: [w3ctag/design-reviews] Request review for Scroll Boundary Behavior (#193) (Monday, 23 October)
• Re: [w3ctag/design-reviews] Request review for Scroll Boundary Behavior (#193) (Monday, 16 October)

Marcos Cáceres

• Re: [w3c/screen-orientation] Add [Exposed] to all interfaces (#106) (Tuesday, 31 October)
• Re: [w3c/screen-orientation] Add [Exposed=Window] extended attribute to ScreenOrientation interface (#107) (Tuesday, 31 October)
• Re: [w3c/screen-orientation] Add [Exposed=Window] extended attribute to ScreenOrientation interface (#107) (Tuesday, 31 October)
• Re: [w3c/screen-orientation] Add [Exposed=Window] extended attribute to ScreenOrientation interface (#107) (Tuesday, 31 October)
• Re: [w3c/permissions] Introduce "Automation" section (#151) (Tuesday, 31 October)
• Re: [w3c/manifest] Hope for external `start_url`s (#276) (Monday, 30 October)
• Re: [w3c/manifest] Fix validator errors and warnings (#625) (Thursday, 26 October)
• Re: [w3c/manifest] Update implementation status (#624) (Thursday, 26 October)
• Re: [w3c/manifest] Update implementation status (#624) (Thursday, 26 October)
• Re: [w3c/manifest] Added missing space. (#616) (Friday, 20 October)
• Re: [w3c/manifest] Added missing space. (#616) (Friday, 20 October)
• Re: [w3c/manifest] Create a test suite for the specification (#623) (Friday, 20 October)
• Re: [w3c/manifest] Create a test suite for the specification (#623) (Friday, 20 October)
• Re: [w3c/manifest] Create a test suite for the specification (#623) (Thursday, 19 October)
• Re: [w3c/manifest] Create a test suite for the specification (#623) (Thursday, 19 October)
• Re: [w3c/manifest] Create a test suite for the specification (#623) (Thursday, 19 October)
• Re: [w3c/manifest] Create a test suite for the specification (#623) (Thursday, 19 October)
• Re: [w3c/manifest] Richer splash screen backgrounds (#589) (Thursday, 19 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Friday, 13 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Friday, 13 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Friday, 13 October)
• Re: [heycam/webidl] Dot notation for dictionary members is not spec'ed. (#453) (Wednesday, 4 October)
• Re: [w3c/manifest] Remove Trim() logic on string members (#620) (Wednesday, 4 October)
• Re: [heycam/webidl] Dot notation for dictionary members is not spec'ed. (#453) (Wednesday, 4 October)
• Re: [heycam/webidl] Dot notation for dictionary members is not spec'ed. (#453) (Tuesday, 3 October)
• Re: [heycam/webidl] Dot notation for dictionary members is not spec'ed. (#453) (Tuesday, 3 October)
• Re: [w3c/manifest] Remove Trim() logic on string members (#620) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add an icon "purpose" for displaying on the theme color (#617) (Tuesday, 3 October)
• Re: [w3c/manifest] Add an icon "purpose" for displaying on the theme color (#617) (Tuesday, 3 October)
• Re: [w3c/manifest] Remove Trim() logic on string members (#620) (Tuesday, 3 October)
• Re: [w3c/manifest] Remove Trim() logic on string members (#620) (Tuesday, 3 October)
• Re: [w3c/manifest] Remove Trim() logic on string members (#620) (Tuesday, 3 October)
• Re: [w3c/manifest] Remove Trim() logic on string members (#620) (Tuesday, 3 October)
• Re: [w3c/permissions] Add ClipboardPermissionDescriptor (#155) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Remove Trim() logic on string members (#620) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Monday, 2 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Monday, 2 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Monday, 2 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Monday, 2 October)
• [w3c/manifest] Parse JSON from bytes (#619) (Monday, 2 October)

Marijn Kruisselbrink

• Re: [w3c/FileAPI] Update the WD (#86) (Tuesday, 24 October)
• Re: [w3c/FileAPI] Fixed metadata. Updated Editors. For #86 (#87) (Tuesday, 24 October)
• Re: [w3c/FileAPI] Fixed metadata. Updated Editors. For #86 (#87) (Tuesday, 24 October)
• Re: [w3c/FileAPI] Ask for tests for normative changes in CONTRIBUTING.md (#85) (Wednesday, 18 October)
• Re: [w3c/FileAPI] Async createObjectURL (#84) (Monday, 16 October)
• Re: [w3c/ServiceWorker] Remove foreign fetch (#1207) (Friday, 13 October)
• Re: [w3c/ServiceWorker] Mixed feelings about ServiceWorker for module loader (#1203) (Thursday, 12 October)

Mark Kennedy

• Re: [whatwg/dom] MutationObserver: observing attribute changes fires even if the value didn't change. (#520) (Saturday, 14 October)
• Re: [whatwg/dom] MutationObserver: observing attribute changes fires even if the value didn't change. (#520) (Friday, 13 October)
• Re: [w3c/webcomponents] How to avoid memory leaks when detecting custom elements? (#674) (Tuesday, 10 October)

Mark Nottingham

• Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206) (Sunday, 29 October)
• Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206) (Sunday, 29 October)
• Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206) (Thursday, 19 October)
• Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165) (Thursday, 19 October)

Martijn Thé

• Re: [w3c/webstorage] Async alternative? (#7) (Tuesday, 24 October)
• [w3c/webstorage] Async alternative? (#7) (Tuesday, 24 October)

Martin Thomson

• Re: [w3c/push-api] Wide review tracker (#265) (Thursday, 26 October)
• Re: [w3c/push-api] Clarify requirements for push endpoint determinism and predictability (#274) (Thursday, 26 October)
• Re: [w3c/push-api] Security review of Push API W3C Working Draft 23 June 2017 (#273) (Thursday, 26 October)

Masayuki Nakano

• Re: [w3c/uievents] Fire keydown/keyup during composition (#75) (Thursday, 19 October)

Matt Brubeck

• Re: [w3c/touch-events] Update the editor's draft link (#89) (Tuesday, 3 October)
• Re: [w3c/touch-events] Update the editor's draft link (#89) (Tuesday, 3 October)

Matt Falkenhagen

• Re: [w3c/ServiceWorker] Does changing updateViaCache mint a new ServiceWorkerRegistration or update them all? (#1189) (Friday, 27 October)
• Re: [w3c/ServiceWorker] Does changing updateViaCache mint a new ServiceWorkerRegistration or update them all? (#1189) (Friday, 27 October)
• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Friday, 20 October)
• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Friday, 20 October)

Matt Giuca

• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Wednesday, 4 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Wednesday, 4 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Wednesday, 4 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Wednesday, 4 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Wednesday, 4 October)
• Re: [w3c/manifest] Remove Trim() logic on string members (#620) (Wednesday, 4 October)
• Re: [w3c/manifest] Add an icon "purpose" for displaying on the theme color (#617) (Tuesday, 3 October)
• Re: [w3c/manifest] Remove Trim() logic on string members (#620) (Tuesday, 3 October)
• Re: [w3c/manifest] Remove Trim() logic on string members (#620) (Tuesday, 3 October)
• Re: [w3c/manifest] Remove Trim() logic on string members (#620) (Tuesday, 3 October)
• Re: [w3c/manifest] Remove Trim() logic on string members (#620) (Tuesday, 3 October)
• [w3c/manifest] Remove Trim() logic on string members (#620) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)

Matthew Dean

• Re: [w3c/webcomponents] Please revisit HTML Imports (#677) (Friday, 20 October)
• Re: [w3c/webcomponents] Please revisit HTML Imports (#677) (Thursday, 19 October)
• Re: [w3c/webcomponents] Please revisit HTML Imports (#677) (Thursday, 19 October)
• [w3c/webcomponents] Please revisit HTML Imports (#677) (Thursday, 19 October)

Matthew Phillips

• Re: [w3c/webcomponents] Please revisit HTML Imports (#677) (Thursday, 19 October)
• Re: [w3c/webcomponents] Please revisit HTML Imports (#677) (Thursday, 19 October)

Matthew Ryan

• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Thursday, 12 October)
• Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640) (Thursday, 12 October)

Mattia Astorino

• Re: [w3c/webcomponents] Support `>>>` combinator in static profile (#78) (Sunday, 8 October)
• Re: [w3c/webcomponents] Support `>>>` combinator in static profile (#78) (Monday, 2 October)

Michael[tm] Smith

• Re: [whatwg/encoding] Meta: use the common deploy.sh (#121) (Tuesday, 31 October)
• Re: [whatwg/encoding] Meta: use the common deploy.sh (#121) (Tuesday, 31 October)
• Re: [whatwg/encoding] Meta: use the common deploy.sh (#121) (Tuesday, 31 October)
• Re: [whatwg/fetch] Doc: Definition of credentials unclear (#612) (Saturday, 14 October)
• Re: [whatwg/fetch] Clarify that credentials include HTTP auth (#616) (Saturday, 14 October)
• [whatwg/xhr] Reference Fetch spec for “credentials” definition (#163) (Friday, 13 October)
• Re: [whatwg/fetch] Clarify that credentials include HTTP auth (#616) (Friday, 13 October)
• Re: [whatwg/fetch] Clarify that credentials include HTTP auth (#616) (Friday, 13 October)
• [whatwg/fetch] Clarify that credentials include HTTP auth (#616) (Friday, 13 October)
• Re: [whatwg/fetch] Doc: Definition of credentials unclear (#612) (Sunday, 8 October)

mik25

• Re: [whatwg/fetch] Block requests for suspected dangling markup. (#519) (Sunday, 1 October)
• Re: [whatwg/fetch] Block requests for suspected dangling markup. (#519) (Sunday, 1 October)

Mike Collins

• Re: [whatwg/dom] Attributes not ready on element construction? (#522) (Tuesday, 24 October)
• Re: [whatwg/dom] MutationObserver: observing attribute changes fires even if the value didn't change. (#520) (Saturday, 14 October)

Mike North

• Re: [w3c/IndexedDB] API to enumerate databases (#31) (Tuesday, 24 October)

Mike Taylor

• Re: [whatwg/dom] Add window.event for web compatibility. (e7cdac7) (Monday, 30 October)
• Re: [whatwg/dom] Add window.event, event.srcElement, event.returnValue as a legacy compat requirements (#407) (Thursday, 26 October)
• Re: [whatwg/dom] Add window.event, event.srcElement, event.returnValue as a legacy compat requirements (#407) (Thursday, 26 October)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Thursday, 26 October)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Tuesday, 24 October)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Tuesday, 24 October)

Mike West

• [w3c/workers] `SharedWorker` secure context integration. (#6) (Wednesday, 18 October)
• Re: [whatwg/url] Percent-encode additional characters in "fragment state". (#347) (Tuesday, 10 October)
• Re: [whatwg/fetch] Adds "audioworklet" and "paintworklet" as destinations. (#527) (Tuesday, 10 October)
• Re: [whatwg/url] Percent-encode additional characters in "fragment state". (#347) (Tuesday, 10 October)
• Re: [whatwg/url] Percent-encode additional characters in "fragment state". (#347) (Tuesday, 10 October)
• Re: [whatwg/url] Percent-encode additional characters in "fragment state". (#347) (Tuesday, 10 October)
• Re: [whatwg/url] Percent-encode additional characters in "fragment state". (#347) (Tuesday, 10 October)
• Re: [whatwg/url] Consider percent-encoding more characters in "fragment state" (#344) (Monday, 9 October)
• Re: [whatwg/url] Percent-encode additional characters in "fragment state". (#347) (Monday, 9 October)
• [whatwg/url] Percent-encode additional characters in "fragment state". (#347) (Monday, 9 October)
• Re: [w3c/WebPlatformWG] TPAC agenda: Thu Nov 9 (WebPlat general) (#94) (Tuesday, 3 October)
• Re: [w3c/WebPlatformWG] TPAC agenda: Thu Nov 9 (WebPlat general) (#94) (Monday, 2 October)

Morgan Conrad

• Re: [w3c/ServiceWorker] Allow Caching of POST requests (#977) (Tuesday, 31 October)

Mounir Lamouri

• Re: [w3ctag/design-reviews] Request Review: Gesture Delegation (#199) (Thursday, 12 October)

Mustaq Ahmed

• Re: [w3c/touch-events] Specify what browsers do on non-touch devices (#64) (Thursday, 19 October)

Nathan Schloss

• Re: [w3c/ServiceWorker] resurrected service workers don't fire an activate event which may break expectations (#1204) (Friday, 6 October)

Nolan Lawson

• Re: [w3c/IndexedDB] boolean should be a valid key (#76) (Tuesday, 31 October)
• Re: [w3c/IndexedDB] Encrypted storage (#191) (Tuesday, 31 October)
• Re: [w3c/IndexedDB] Add caniuse panels (#159) (Friday, 27 October)

Nux

• Re: [w3c/editing] INPUT/TEXTAREA should support subset of execCommand (#160) (Monday, 9 October)

Pacerier

• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Wednesday, 18 October)
• Re: [w3c/ServiceWorker] Responding to cross-origin requests using a worker? (#130) (Sunday, 15 October)

Patrick Dark

• [w3c/uievents] Editorial: Grammatical Errors in mouseleave and mouseout Sections (#167) (Monday, 23 October)
• [w3c/uievents] Editorial: Inconsistent Choice of “Descendant”/“Descendent” (#166) (Monday, 23 October)
• [w3c/uievents] Specification Should Link to Its Own Definition of Cancelable (#165) (Saturday, 21 October)

Patrick H. Lauke

• Re: [w3c/touch-events] Add getModifierState definition to TouchEvent. This matches the text (#91) (Monday, 23 October)
• Re: [w3c/touch-events] Add getModifierState definition to TouchEvent. This matches the text (#91) (Monday, 23 October)
• Re: [w3c/touch-events] Ask for tests for normative changes in README (#90) (Monday, 23 October)
• Re: [w3c/touch-events] createTouch has all the params as required, should probably have them optional (#58) (Monday, 23 October)
• Re: [w3c/touch-events] Initialize touchList in Chrome (#78) (Monday, 23 October)
• Re: [w3c/touch-events] should TouchEvent define getModifierState (#41) (Monday, 23 October)
• Re: [w3c/touch-events] Re-add tests for extentions APIs (#21) (Monday, 23 October)
• Re: [w3c/touch-events] Initialize touchList in Chrome (#78) (Monday, 23 October)
• Re: [w3c/touch-events] Ask for tests for normative changes in README (#90) (Monday, 23 October)
• Re: [w3c/touch-events] Ask for tests for normative changes in README (#90) (Monday, 23 October)

Patrick McManus

• Re: [whatwg/url] Consider percent-encoding more characters in "fragment state" (#344) (Tuesday, 3 October)

Pedram Emrouznejad

• Re: [w3c/webcomponents] Disconnected Events (#678) (Tuesday, 31 October)
• [w3c/webcomponents] Disconnected Events (#678) (Tuesday, 31 October)
• Re: [w3c/webcomponents] Support `>>>` combinator in static profile (#78) (Tuesday, 3 October)

peria

• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Wednesday, 25 October)

Philip Jägenstedt

• Re: [whatwg/streams] Meta: use the common deploy.sh (with POST_BUILD_STEP) (#849) (Tuesday, 31 October)
• Re: [whatwg/streams] Meta: use the common deploy.sh (with POST_BUILD_STEP) (#849) (Tuesday, 31 October)
• Re: [whatwg/streams] Meta: use the common deploy.sh (with POST_BUILD_STEP) (#849) (Tuesday, 31 October)
• [whatwg/streams] Meta: use the common deploy.sh (with POST_BUILD_STEP) (#849) (Tuesday, 31 October)
• Re: [whatwg/url] Meta: use the common deploy.sh (#351) (Tuesday, 31 October)
• Re: [whatwg/url] Meta: use the common deploy.sh (#351) (Tuesday, 31 October)
• Re: [whatwg/url] Meta: use the common deploy.sh (#351) (Tuesday, 31 October)
• [whatwg/url] Meta: use the common deploy.sh (#351) (Tuesday, 31 October)
• Re: [whatwg/encoding] Meta: use the common deploy.sh (#121) (Tuesday, 31 October)
• Re: [whatwg/encoding] Meta: use the common deploy.sh (#121) (Monday, 30 October)
• Re: [whatwg/encoding] Meta: use the common deploy.sh (#121) (Monday, 30 October)
• Re: [w3c/touch-events] Ask for tests for normative changes in README (#90) (Monday, 23 October)
• Re: [w3c/touch-events] createTouch has all the params as required, should probably have them optional (#58) (Monday, 23 October)
• Re: [w3c/DOM-Parsing] Ask for tests for normative changes in CONTRIBUTING.md (#32) (Monday, 23 October)
• Re: [w3c/touch-events] Ask for tests for normative changes in README (#90) (Monday, 23 October)
• [w3c/touch-events] Ask for tests for normative changes in README (#90) (Thursday, 19 October)
• Re: [w3c/ServiceWorker] Meta: mention type:untestable and type:missing-coverage wpt labels (#1211) (Thursday, 19 October)
• [w3c/ServiceWorker] Meta: mention type:untestable and type:missing-coverage wpt labels (#1211) (Thursday, 19 October)
• [w3c/FileAPI] Ask for tests for normative changes in CONTRIBUTING.md (#85) (Wednesday, 18 October)
• [w3c/DOM-Parsing] Ask for tests for normative changes in CONTRIBUTING.md (#32) (Wednesday, 18 October)
• [w3c/clipboard-apis] Ask for tests for normative changes in CONTRIBUTING.md (#56) (Wednesday, 18 October)
• [w3c/uievents] Ask for tests for normative changes in CONTRIBUTING.md (#163) (Wednesday, 18 October)
• Re: [w3c/clipboard-apis] Where would one get a DataTransfer to hand to the ClipboardEvent constructor? (#33) (Tuesday, 17 October)
• Re: [whatwg/fetch] Define data: URLs (#579) (Wednesday, 11 October)
• Re: [w3c/permissions] Introduce "Automation" section (#151) (Wednesday, 4 October)
• [w3c/touch-events] Update the editor's draft link (#89) (Tuesday, 3 October)

Philippe Le Hegaret

• Re: [w3c/FileAPI] Update the WD (#86) (Thursday, 26 October)
• Re: [w3c/FileAPI] Update the WD (#86) (Thursday, 26 October)
• Re: [w3c/FileAPI] Update the WD (#86) (Wednesday, 25 October)
• Re: [w3c/FileAPI] Fixed metadata. Updated Editors. For #86 (#87) (Tuesday, 24 October)
• Re: [w3c/FileAPI] Fixed metadata. Updated Editors. For #86 (#87) (Tuesday, 24 October)
• [w3c/FileAPI] Fixed metadata. Updated Editors. For #86 (#87) (Tuesday, 24 October)

PhistucK

• Re: [w3c/webcomponents] Support `>>>` combinator in static profile (#78) (Tuesday, 3 October)

Piotr Swigon

• Re: [w3c/manifest] Richer splash screen backgrounds (#589) (Wednesday, 18 October)

r12a

• Re: [w3c/uievents-code] Ed: Include more international keyboard examples (#11) (Friday, 6 October)
• Re: [whatwg/encoding] gb18030 encoding/decoding support (#57) (Wednesday, 4 October)

Raphael Kubo da Costa

• Re: [w3c/gamepad] Ask for tests for normative changes in CONTRIBUTING.md (#64) (Friday, 27 October)
• Re: [w3c/gamepad] Ask for tests for normative changes in CONTRIBUTING.md (#64) (Tuesday, 24 October)
• Re: [w3c/gamepad] Ask for tests for normative changes in CONTRIBUTING.md (#64) (Tuesday, 24 October)
• Re: [w3c/gamepad] Ask for tests for normative changes in CONTRIBUTING.md (#64) (Monday, 23 October)
• Re: [w3c/gamepad] Ask for tests for normative changes in CONTRIBUTING.md (#64) (Monday, 23 October)
• [w3c/gamepad] Ask for tests for normative changes in CONTRIBUTING.md (#64) (Monday, 23 October)
• Re: [whatwg/fetch] Regression: make Request constructor account for changes to fill (#484) (Friday, 6 October)
• Re: [whatwg/fetch] Regression: make Request constructor account for changes to fill (#484) (Friday, 6 October)

raymeskhoury

• Re: [w3c/permissions] Granting permission to non-fully-active documents is weird and should be disallowed (#162) (Tuesday, 10 October)
• Re: [w3c/permissions] Add support for permissions that have an associated Feature Policy (#163) (Tuesday, 10 October)
• Re: [w3c/permissions] Add support for permissions that have an associated Feature Policy (#163) (Tuesday, 10 October)
• [w3c/permissions] Add support for permissions that have an associated Feature Policy (#163) (Tuesday, 10 October)
• Re: [w3c/permissions] Add ClipboardPermissionDescriptor (#155) (Thursday, 5 October)
• Re: [w3c/clipboard-apis] Clipboard Permission (#51) (Wednesday, 4 October)
• Re: [w3c/permissions] A more modest request() (#158) (Tuesday, 3 October)

Richard Gibson

• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Saturday, 21 October)
• Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118) (Friday, 20 October)

Rick Byers

• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Thursday, 26 October)
• Re: [w3c/uievents] Add text around dispatching mouseenter/leave/out/over when an element (#155) (Tuesday, 24 October)

Rimas Misevičius

• Re: [whatwg/url] Consider percent-encoding more characters in "fragment state" (#344) (Tuesday, 10 October)

Rob Buis

• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Friday, 13 October)

Rob Dodson

• Re: [w3c/webcomponents] Custom attribute names conflicting with built-in attribute names (#654) (Wednesday, 25 October)
• Re: [w3c/webcomponents] Consider adding a childrenChangedCallback or something (#619) (Monday, 9 October)
• Re: [w3c/webcomponents] Support `>>>` combinator in static profile (#78) (Sunday, 8 October)
• Re: [w3c/webcomponents] light dom availability (#673) (Thursday, 5 October)
• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Sunday, 1 October)
• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Sunday, 1 October)

Robert B Colton

• [w3c/editing] Draggable elements with clipboard actions clarification (#170) (Friday, 6 October)

rolivo

• Re: [whatwg/fetch] FetchObserver (for a single fetch) (#607) (Tuesday, 10 October)

roryhewitt

• [whatwg/fetch] Doc: Definition of credentials unclear (#612) (Friday, 6 October)

RUffass

• [whatwg/xhr] externals.js?v=SV4wipYX62VSlFpHPU1b0oqTYYPkrgV1RT64uViudRk1:1 [Deprecation] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/. (#164) (Saturday, 14 October)

Ryosuke Niwa

• Re: [w3c/webcomponents] Disconnected Events (#678) (Tuesday, 31 October)
• Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Tuesday, 31 October)
• Re: [w3c/webcomponents] Disconnected Events (#678) (Tuesday, 31 October)
• Re: [w3c/clipboard-apis] Support for reading custom MIME types from the clipboard (#46) (Monday, 23 October)
• Re: [w3c/webcomponents] Please revisit HTML Imports (#677) (Thursday, 19 October)
• Re: [w3c/webcomponents] Support `>>>` combinator in static profile (#78) (Wednesday, 18 October)
• [w3c/clipboard-apis] Clipboard API mixies representations of an item with distinct items. (#55) (Tuesday, 17 October)
• Re: [w3c/webcomponents] Custom Element - untrackable upgrade (#671) (Tuesday, 10 October)
• Re: [w3c/webcomponents] How to avoid memory leaks when detecting custom elements? (#674) (Tuesday, 10 October)
• Re: [w3c/webcomponents] How to avoid memory leaks when detecting custom elements? (#674) (Tuesday, 10 October)
• Re: [w3c/webcomponents] How to avoid memory leaks when detecting custom elements? (#674) (Monday, 9 October)
• Re: [w3c/webcomponents] Custom Element definition ordering can cause difficult-to-find bugs. (#668) (Monday, 9 October)
• Re: [w3c/webcomponents] Support `>>>` combinator in static profile (#78) (Monday, 9 October)
• Re: [w3c/webcomponents] Support `>>>` combinator in static profile (#78) (Monday, 9 October)
• Re: [w3c/webcomponents] Support `>>>` combinator in static profile (#78) (Sunday, 8 October)
• Re: [w3c/webcomponents] Support `>>>` combinator in static profile (#78) (Sunday, 8 October)
• Re: [w3c/webcomponents] Support `>>>` combinator in static profile (#78) (Sunday, 8 October)
• Re: [w3c/webcomponents] Custom Element definition ordering can cause difficult-to-find bugs. (#668) (Sunday, 8 October)
• Re: [w3c/webcomponents] Custom Element definition ordering can cause difficult-to-find bugs. (#668) (Sunday, 8 October)
• Re: [w3c/webcomponents] Custom Element definition ordering can cause difficult-to-find bugs. (#668) (Sunday, 8 October)
• Re: [w3c/webcomponents] How to avoid memory leaks when detecting custom elements? (#674) (Sunday, 8 October)
• Re: [w3c/webcomponents] How to avoid memory leaks when detecting custom elements? (#674) (Sunday, 8 October)
• Re: [w3c/webcomponents] Support `>>>` combinator in static profile (#78) (Saturday, 7 October)
• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Tuesday, 3 October)
• Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) (Tuesday, 3 October)
• Re: [w3c/webcomponents] light dom availability (#673) (Tuesday, 3 October)
• Re: [whatwg/dom] Declarative Shadow DOM (#510) (Monday, 2 October)

Salvador de la Puente González

• Re: [w3c/manifest] Add an icon "purpose" for displaying on the theme color (#617) (Tuesday, 10 October)

Sam Saccone

• Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Monday, 2 October)

Scott Graham

• Re: [w3c/gamepad] Ask for tests for normative changes in CONTRIBUTING.md (#64) (Friday, 27 October)
• Re: [w3c/gamepad] Ask for tests for normative changes in CONTRIBUTING.md (#64) (Friday, 27 October)

Sean D

• Re: [w3c/webcomponents] Why do we really need hyphens? (#658) (Wednesday, 11 October)

Shiino Yuki

• Re: [whatwg/dom] Add window.event for web compatibility. (e7cdac7) (Monday, 30 October)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Wednesday, 25 October)

sleevi

• Re: [whatwg/fetch] Why does Fetch specify a max redirect count of 20? (#576) (Wednesday, 11 October)

smaug----

• [whatwg/dom] "node's tree" seems to be an undefined concept (#526) (Tuesday, 31 October)
• Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Tuesday, 31 October)
• Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Tuesday, 31 October)
• Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Tuesday, 31 October)
• Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Tuesday, 31 October)
• Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Monday, 30 October)
• Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Monday, 30 October)
• [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525) (Monday, 30 October)
• Re: [whatwg/dom] Should we really support modifying an already dispatched event via initEvent()? (#523) (Sunday, 29 October)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Wednesday, 25 October)
• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Monday, 23 October)
• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Monday, 23 October)
• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Saturday, 21 October)
• Re: [w3c/ServiceWorker] async waitUntil microtask issue (#1213) (Friday, 20 October)
• Re: [whatwg/dom] MutationObserver: observing attribute changes fires even if the value didn't change. (#520) (Friday, 13 October)

spanicker

• [w3ctag/design-reviews] Review request: Web Lifecycle for system initiated Discarding & Stopping (#205) (Friday, 13 October)

stefan hakansson

• Re: [whatwg/fetch] Wrong authors listed for WSP (#613) (Tuesday, 10 October)
• [whatwg/fetch] Wrong authors listed for WSP (#613) (Tuesday, 10 October)

Tab Atkins Jr.

• Re: [whatwg/streams] Add an example of a transform stream that replaces template tags (#846) (Tuesday, 24 October)
• Re: [whatwg/streams] Add an example of a transform stream that replaces template tags (#846) (Tuesday, 24 October)
• Re: [w3c/webcomponents] Support `>>>` combinator in static profile (#78) (Wednesday, 18 October)
• Re: [w3c/webcomponents] Which standard defines :defined (#665) (Friday, 13 October)
• Re: [w3c/webcomponents] Support `>>>` combinator in static profile (#78) (Saturday, 7 October)
• Re: [heycam/webidl] Status of this document section mistakenly links to public-webapps@ (#455) (Friday, 6 October)
• Re: [heycam/webidl] Status of this document section mistakenly links to public-webapps@ (#455) (Friday, 6 October)

Takayoshi Kochi

• Re: [w3c/webcomponents] Please revisit HTML Imports (#677) (Friday, 20 October)
• Re: [w3c/webcomponents] Please revisit HTML Imports (#677) (Friday, 20 October)
• Re: [heycam/webidl] Add a note on the difference of SyntaxError (#459) (Thursday, 12 October)
• Re: [heycam/webidl] Add a note on the difference of SyntaxError (#459) (Wednesday, 11 October)
• Re: [heycam/webidl] Add a note on the difference of SyntaxError (#459) (Wednesday, 11 October)
• [heycam/webidl] Add a note on the difference of SyntaxError (#459) (Wednesday, 11 October)
• Re: [whatwg/dom] Set event.target to null when dispatching finishes at ShadowRoot (#513) (Thursday, 5 October)
• Re: [whatwg/dom] Set event.target to null when dispatching finishes at ShadowRoot (#513) (Thursday, 5 October)
• Re: [whatwg/dom] Set event.target to null when dispatching finishes at ShadowRoot (#513) (Thursday, 5 October)
• Re: [whatwg/dom] Set event.target to null when dispatching finishes at ShadowRoot (#513) (Thursday, 5 October)
• Re: [whatwg/dom] Set event.target to null when dispatching finishes at ShadowRoot (#513) (Thursday, 5 October)
• Re: [whatwg/dom] Set event.target to null when dispatching finishes at ShadowRoot (#513) (Thursday, 5 October)
• Re: [whatwg/dom] Set event.target to null when dispatching finishes at ShadowRoot (#513) (Thursday, 5 October)
• Re: [whatwg/dom] Set event.target to null when dispatching finishes at ShadowRoot (#513) (Thursday, 5 October)
• Re: [whatwg/dom] Event.target should return null after dispatch is complete, when stopped at ShadowRoot (#511) (Thursday, 5 October)
• Re: [w3c/webcomponents] Support `>>>` combinator in static profile (#78) (Tuesday, 3 October)

Takeshi Yoshino

• Re: [whatwg/streams] Standard text for TransformStream (#811) (Tuesday, 17 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Tuesday, 17 October)
• Re: [whatwg/streams] Standard text for TransformStream (#811) (Tuesday, 17 October)
• Re: [whatwg/streams] Add "controller" local to TransformStream constructor (#840) (Thursday, 12 October)
• Re: [whatwg/fetch] Reference correct WebSocket protocol RFC (#614) (Tuesday, 10 October)

Tantek Çelik

• Re: [w3ctag/design-reviews] HTML General Review (#174) (Tuesday, 17 October)
• Re: [w3ctag/design-reviews] Request review for Scroll Boundary Behavior (#193) (Tuesday, 17 October)
• Re: [w3ctag/design-reviews] ads.txt (#201) (Tuesday, 17 October)
• Re: [w3ctag/design-reviews] ads.txt (#201) (Tuesday, 17 October)

Tejas Kumar

• Re: [whatwg/streams] [Question] I created a project that explains the spec (#848) (Tuesday, 31 October)
• Re: [whatwg/streams] [Question] I created a project that explains the spec (#848) (Monday, 30 October)
• [whatwg/streams] I created a project that explains the spec (#848) (Saturday, 28 October)
• Re: [whatwg/streams] new ReadableStream({type: 'bytes'}, new CountQueuingStrategy({highWaterMark: 5})) is weird (#729) (Saturday, 28 October)

Thomas Wisniewski

• [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165) (Monday, 16 October)

Tim Ruffles

• Re: [heycam/webidl] Editorial: ack Tim Ruffles (#463) (Tuesday, 17 October)
• Re: [heycam/webidl] Missing argument handling (#461) (Monday, 16 October)
• [heycam/webidl] Fix #461 - clarify applicability of overload resolution (#462) (Monday, 16 October)
• [heycam/webidl] Missing argument handling (#461) (Monday, 16 October)

Timo Tijhof

• [w3c/ServiceWorker] Mixed feelings about ServiceWorker for module loader (#1203) (Thursday, 5 October)

Timothy Gu

• Re: [whatwg/url] Should URLSearchParams stringify be called in URL constructor? (#350) (Monday, 30 October)
• Re: [heycam/webidl] Standardize around typography of IDL true/false/null (#457) (Tuesday, 17 October)
• Re: [whatwg/url] percent-encode ' in queries of URLs with special schemes (#348) (Monday, 16 October)
• Re: [whatwg/url] percent-encode ' in queries of URLs with special schemes (#348) (Monday, 16 October)
• Re: [heycam/webidl] Missing argument handling (#461) (Monday, 16 October)
• Re: [heycam/webidl] Add post-processor (#460) (Sunday, 15 October)
• Re: [heycam/webidl] Add post-processor (#460) (Sunday, 15 October)
• Re: [whatwg/url] Percent-encode additional characters in "fragment state". (#347) (Monday, 9 October)
• [heycam/webidl] Standardize around typography of IDL true/false/null (#457) (Saturday, 7 October)
• Re: [heycam/webidl] More ECMAScript biblio cleanup (#451) (Thursday, 5 October)
• Re: [heycam/webidl] Enumeration order of interface members (#432) (Wednesday, 4 October)
• Re: [heycam/webidl] Enumeration order of interface members (#432) (Wednesday, 4 October)
• Re: [heycam/webidl] More ECMAScript biblio cleanup (#451) (Monday, 2 October)
• [heycam/webidl] More ECMAScript biblio cleanup (#451) (Monday, 2 October)

Tobie Langel

• Re: [heycam/webidl] Exposing an interface "on all globals" (#468) (Friday, 27 October)
• Re: [heycam/webidl] Exposing an interface "on all globals" (#468) (Tuesday, 24 October)
• Re: [heycam/webidl] Exposing an interface "on all globals" (#468) (Tuesday, 24 October)
• Re: [heycam/webidl] Exposing an interface "on all globals" (#468) (Tuesday, 24 October)
• Re: [heycam/webidl] [SecureContext] restrictions on interface vs. interface member are confusing (#153) (Friday, 20 October)
• Re: [heycam/webidl] [SecureContext] restrictions on interface vs. interface member are confusing (#153) (Tuesday, 17 October)
• Re: [heycam/webidl] Status of this document section mistakenly links to public-webapps@ (#455) (Tuesday, 17 October)
• Re: [heycam/webidl] Fix SOTD (#456) (Tuesday, 17 October)
• Re: [heycam/webidl] Add post-processor (#460) (Tuesday, 17 October)
• Re: [heycam/webidl] Fix and clarify exposed dfn (#464) (Tuesday, 17 October)
• Re: [heycam/webidl] Add post-processor (#460) (Tuesday, 17 October)
• Re: [heycam/webidl] Standardize around typography of IDL true/false/null (#457) (Tuesday, 17 October)
• Re: [heycam/webidl] Standardize around typography of IDL true/false/null (#457) (Tuesday, 17 October)
• Re: [heycam/webidl] Standardize around typography of IDL true/false/null (#457) (Tuesday, 17 October)
• [heycam/webidl] Fix and clarify exposed dfn (#464) (Tuesday, 17 October)
• Re: [heycam/webidl] Editorial: ack Tim Ruffles (#463) (Monday, 16 October)
• [heycam/webidl] Editorial: ack Tim Ruffles (#463) (Monday, 16 October)
• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Monday, 16 October)
• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Monday, 16 October)
• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Monday, 16 October)
• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Monday, 16 October)
• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Monday, 16 October)
• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Monday, 16 October)
• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Monday, 16 October)
• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Monday, 16 October)
• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Monday, 16 October)
• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Monday, 16 October)
• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Monday, 16 October)
• Re: [heycam/webidl] Add post-processor (#460) (Sunday, 15 October)
• Re: [heycam/webidl] Add post-processor (#460) (Sunday, 15 October)
• [heycam/webidl] Add post-processor (#460) (Sunday, 15 October)
• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Friday, 13 October)
• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Thursday, 12 October)
• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Thursday, 12 October)
• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Thursday, 12 October)
• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Thursday, 12 October)
• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Thursday, 12 October)
• Re: [whatwg/streams] [META] Integrate with pr-preview (#836) (Thursday, 12 October)
• Re: [heycam/webidl] Mixin follow-up (#450) (Thursday, 12 October)
• Re: [whatwg/dom] Editorial: use "exception name" DOMException notation (#518) (Thursday, 12 October)
• Re: [whatwg/dom] Editorial: use "exception name" DOMException notation (#518) (Thursday, 12 October)
• Re: [whatwg/dom] Editorial: use "exception name" DOMException notation (#518) (Thursday, 12 October)
• Re: [heycam/webidl] Add a note on the difference of SyntaxError (#459) (Thursday, 12 October)
• Re: [heycam/webidl] Add a note on the difference of SyntaxError (#459) (Thursday, 12 October)
• Re: [heycam/webidl] Add a note on the difference of SyntaxError (#459) (Thursday, 12 October)
• [whatwg/dom] Editorial: use "exception name" DOMException notation (#518) (Thursday, 12 October)
• Re: [heycam/webidl] Add a note on the difference of SyntaxError (#459) (Thursday, 12 October)
• Re: [heycam/webidl] Add a note on the difference of SyntaxError (#459) (Thursday, 12 October)
• Re: [heycam/webidl] Add a note on the difference of SyntaxError (#459) (Thursday, 12 October)
• Re: [heycam/webidl] The spec's wording for where to place operations is broken and confusing (#164) (Wednesday, 11 October)
• Re: [heycam/webidl] What is the expected interaction of [SecureContext] with mixins? (#118) (Wednesday, 11 October)
• Re: [heycam/webidl] Designing mixins (#363) (Wednesday, 11 October)
• Re: [heycam/webidl] Add mixins (#433) (Wednesday, 11 October)
• Re: [heycam/webidl] Should mixins be able to add overloads? (#261) (Wednesday, 11 October)
• Re: [heycam/webidl] Add mixins (#433) (Wednesday, 11 October)
• Re: [heycam/webidl] Add mixins (#433) (Wednesday, 11 October)
• Re: [heycam/webidl] Add mixins (#433) (Wednesday, 11 October)
• Re: [heycam/webidl] Add mixins (#433) (Wednesday, 11 October)
• Re: [heycam/webidl] Add mixins (#433) (Wednesday, 11 October)
• Re: [heycam/webidl] Add a note on the difference of SyntaxError (#459) (Wednesday, 11 October)
• Re: [heycam/webidl] Standardize around typography of IDL true/false/null (#457) (Wednesday, 11 October)
• Re: [heycam/webidl] Add mixins (#433) (Wednesday, 11 October)
• Re: [heycam/webidl] Add mixins (#433) (Wednesday, 11 October)
• Re: [heycam/webidl] Add mixins (#433) (Wednesday, 11 October)
• Re: [heycam/webidl] Check grammar is LL(1) as part of Travis builds (#458) (Wednesday, 11 October)
• Re: [heycam/webidl] Check grammar is LL(1) as part of Travis builds (#458) (Wednesday, 11 October)
• Re: [heycam/webidl] Check grammar is LL(1) as part of Travis builds (#458) (Wednesday, 11 October)
• Re: [heycam/webidl] Check grammar is LL(1) as part of Travis builds (#458) (Tuesday, 10 October)
• Re: [heycam/webidl] Add mixins (#433) (Tuesday, 10 October)
• [heycam/webidl] Check grammar is LL(1) as part of Travis builds (#458) (Tuesday, 10 October)
• Re: [heycam/webidl] Add mixins (#433) (Monday, 9 October)
• Re: [heycam/webidl] Add mixins (#433) (Monday, 9 October)
• Re: [heycam/webidl] Add mixins (#433) (Monday, 9 October)
• Re: [heycam/webidl] Add mixins (#433) (Monday, 9 October)
• Re: [heycam/webidl] Add mixins (#433) (Monday, 9 October)
• Re: [heycam/webidl] Add mixins (#433) (Monday, 9 October)
• Re: [heycam/webidl] Add mixins (#433) (Monday, 9 October)
• [heycam/webidl] Fix SOTD (#456) (Friday, 6 October)
• Re: [heycam/webidl] Status of this document section mistakenly links to public-webapps@ (#455) (Friday, 6 October)
• [heycam/webidl] Status of this document section mistakenly links to public-webapps@ (#455) (Friday, 6 October)
• Re: [heycam/webidl] Enumeration order of interface members (#432) (Thursday, 5 October)
• Re: [heycam/webidl] Update Document conventions section with ES6 notation details (#452) (Thursday, 5 October)
• Re: [heycam/webidl] More ECMAScript biblio cleanup (#451) (Thursday, 5 October)
• Re: [heycam/webidl] More ECMAScript biblio cleanup (#451) (Thursday, 5 October)
• Re: [heycam/webidl] Enumeration order of interface members (#432) (Wednesday, 4 October)
• Re: [heycam/webidl] Enumeration order of interface members (#432) (Wednesday, 4 October)
• Re: [heycam/webidl] Enumeration order of interface members (#432) (Wednesday, 4 October)
• Re: [heycam/webidl] Enumeration order of interface members (#432) (Wednesday, 4 October)
• Re: [heycam/webidl] Add mixins (#433) (Wednesday, 4 October)
• Re: [heycam/webidl] Add mixins (#433) (Wednesday, 4 October)
• Re: [heycam/webidl] Add mixins (#433) (Wednesday, 4 October)
• Re: [heycam/webidl] Add mixins (#433) (Wednesday, 4 October)
• Re: [heycam/webidl] Add mixins (#433) (Wednesday, 4 October)
• Re: [heycam/webidl] Dot notation for dictionary members is not spec'ed. (#453) (Wednesday, 4 October)
• Re: [heycam/webidl] Dot notation for dictionary members is not spec'ed. (#453) (Wednesday, 4 October)
• Re: [heycam/webidl] Dot notation for dictionary members is not spec'ed. (#453) (Wednesday, 4 October)
• Re: [heycam/webidl] Add mixins (#433) (Tuesday, 3 October)
• Re: [heycam/webidl] [WIP] Add mixins (#433) (Tuesday, 3 October)
• Re: [heycam/webidl] [WIP] Add mixins (#433) (Tuesday, 3 October)
• Re: [heycam/webidl] Editorial: fix spelling mistakes (#454) (Tuesday, 3 October)
• Re: [heycam/webidl] [WIP] Add mixins (#433) (Tuesday, 3 October)
• [heycam/webidl] Editorial: fix spelling mistakes (#454) (Tuesday, 3 October)
• Re: [heycam/webidl] [WIP] Add mixins (#433) (Tuesday, 3 October)
• Re: [heycam/webidl] [WIP] Add mixins (#433) (Tuesday, 3 October)
• Re: [heycam/webidl] [WIP] Add mixins (#433) (Tuesday, 3 October)
• Re: [heycam/webidl] [WIP] Add mixins (#433) (Tuesday, 3 October)
• Re: [heycam/webidl] Dot notation for dictionary members is not spec'ed. (#453) (Tuesday, 3 October)
• Re: [heycam/webidl] [WIP] Add mixins (#433) (Tuesday, 3 October)
• Re: [heycam/webidl] [WIP] Add mixins (#433) (Tuesday, 3 October)
• Re: [heycam/webidl] [WIP] Add mixins (#433) (Tuesday, 3 October)
• Re: [heycam/webidl] [WIP] Add mixins (#433) (Tuesday, 3 October)
• Re: [heycam/webidl] [WIP] Add mixins (#433) (Tuesday, 3 October)
• Re: [heycam/webidl] Dot notation for dictionary members is not spec'ed. (#453) (Tuesday, 3 October)
• Re: [heycam/webidl] Dot notation for Web IDL is not spec'ed. (#453) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Tuesday, 3 October)
• Re: [heycam/webidl] [WIP] Add mixins (#433) (Monday, 2 October)
• Re: [heycam/webidl] [WIP] Add mixins (#433) (Monday, 2 October)
• Re: [heycam/webidl] [WIP] Add mixins (#433) (Monday, 2 October)
• Re: [heycam/webidl] [WIP] Add mixins (#433) (Monday, 2 October)
• Re: [heycam/webidl] [WIP] Add mixins (#433) (Monday, 2 October)
• Re: [heycam/webidl] [WIP] Add mixins (#433) (Monday, 2 October)
• Re: [heycam/webidl] [WIP] Add mixins (#433) (Monday, 2 October)
• Re: [heycam/webidl] [WIP] Add mixins (#433) (Monday, 2 October)
• Re: [heycam/webidl] More ECMAScript biblio cleanup (#451) (Monday, 2 October)
• Re: [heycam/webidl] More ECMAScript biblio cleanup (#451) (Monday, 2 October)
• [heycam/webidl] Update Document conventions section with ES6 notation details (#452) (Monday, 2 October)
• Re: [heycam/webidl] [WIP] Add mixins (#433) (Monday, 2 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Monday, 2 October)
• Re: [w3c/manifest] Add IDL section and define IDL for all the members (#613) (Monday, 2 October)
• Re: [heycam/webidl] More ECMAScript biblio cleanup (#451) (Monday, 2 October)
• [heycam/webidl] Mixin follow-up (#450) (Sunday, 1 October)
• Re: [heycam/webidl] [WIP] Add mixins (#433) (Sunday, 1 October)
• Re: [heycam/webidl] [WIP] Add mixins (#433) (Sunday, 1 October)
• Re: [heycam/webidl] [WIP] Add mixins (#433) (Sunday, 1 October)
• Re: [heycam/webidl] [WIP] Add mixins (#433) (Sunday, 1 October)
• Re: [heycam/webidl] [WIP] Add mixins (#433) (Sunday, 1 October)
• Re: [heycam/webidl] [WIP] Add mixins (#433) (Sunday, 1 October)

Tomek Wytrębowicz

• Re: [whatwg/dom] Declarative Shadow DOM (#510) (Tuesday, 24 October)
• Re: [whatwg/dom] Declarative Shadow DOM (#510) (Monday, 23 October)
• Re: [w3c/webcomponents] How to avoid memory leaks when detecting custom elements? (#674) (Saturday, 21 October)

Toni-Jan Keith Monserrat

• Re: [whatwg/dom] Declarative Shadow DOM (#510) (Tuesday, 31 October)
• Re: [whatwg/dom] Declarative Shadow DOM (#510) (Tuesday, 31 October)
• Re: [whatwg/dom] Declarative Shadow DOM (#510) (Monday, 2 October)

Travis Leithead

• Re: [w3ctag/design-reviews] Request for TAG review of Input events level 2 (#173) (Tuesday, 31 October)
• Re: [w3ctag/design-reviews] Review request for IndexedDB Observers (#189) (Tuesday, 31 October)
• Re: [w3ctag/design-reviews] Review request for IndexedDB Observers (#189) (Tuesday, 31 October)
• [w3ctag/design-reviews] Consider general storage observer that works for cookies (#210) (Tuesday, 31 October)
• Re: [w3ctag/design-reviews] Review request for IndexedDB Observers (#189) (Tuesday, 17 October)
• Re: [w3c/DOM-Parsing] Add [Exposed] to all interfaces (#31) (Wednesday, 11 October)
• Re: [heycam/webidl] Add mixins (#433) (Wednesday, 11 October)

Trey Shugart

• Re: [whatwg/dom] Declarative Shadow DOM (#510) (Tuesday, 31 October)
• Re: [w3c/webcomponents] Disconnected Events (#678) (Tuesday, 31 October)
• Re: [whatwg/dom] Declarative Shadow DOM (#510) (Monday, 30 October)
• Re: [whatwg/dom] Declarative Shadow DOM (#510) (Monday, 30 October)
• Re: [whatwg/dom] Declarative Shadow DOM (#510) (Monday, 23 October)

triple-underscore

• Re: [whatwg/dom] Some tweaks for traverse algo and others (#87) (Monday, 2 October)

Valentin Gosu

• Re: [whatwg/url] percent-encode ' in queries of URLs with special schemes (#348) (Tuesday, 17 October)
• Re: [whatwg/url] Consider percent-encoding more characters in "fragment state" (#344) (Tuesday, 10 October)

vans163

• [w3c/pointerlock] Raw movement data, not pixel location clamped (#28) (Tuesday, 24 October)
• Re: [w3c/pointerlock] Pointer Clip (#27) (Tuesday, 24 October)

vaykar

• Re: [whatwg/xhr] vaykar (#166) (Monday, 16 October)
• Re: [whatwg/xhr] vaykar (#166) (Monday, 16 October)
• Re: [whatwg/xhr] vaykar (#166) (Monday, 16 October)
• [whatwg/xhr] vaykar (#166) (Monday, 16 October)

Victor Costan

• Re: [w3c/IndexedDB] API to enumerate databases (#31) (Tuesday, 24 October)
• Re: [w3c/IndexedDB] API to enumerate databases (#31) (Tuesday, 24 October)
• Re: [w3c/IndexedDB] Implementation report (#213) (Wednesday, 11 October)

Viktor

• Re: [whatwg/xhr] final readystatechange (readyState === 3) (#161) (Monday, 9 October)
• Re: [whatwg/xhr] final readystatechange (readyState === 3) (#161) (Monday, 9 October)
• Re: [whatwg/xhr] final readystatechange (readyState === 3) (#161) (Monday, 9 October)
• Re: [whatwg/xhr] final readystatechange (readyState === 3) (#161) (Monday, 9 October)
• Re: [whatwg/xhr] final readystatechange (readyState === 3) (#161) (Friday, 6 October)
• Re: [whatwg/xhr] final readystatechange (readyState === 3) (#161) (Friday, 6 October)
• Re: [whatwg/xhr] final readystatechange (readyState === 3) (#161) (Friday, 6 October)
• Re: [whatwg/xhr] final readystatechange (readyState === 3) (#161) (Friday, 6 October)
• [whatwg/xhr] final readystatechange (readyState === 3) (#161) (Friday, 6 October)

Vincent Scheib

• Re: [w3c/uievents] MouseEvent.screenX/Y coordinate space id not clear (#150) (Tuesday, 3 October)
• Re: [w3c/pointerlock] movementX/Y when zoom in/out (#23) (Tuesday, 3 October)

Vladan Djeric

• Re: [w3c/ServiceWorker] Proposal: Allow addEventListener/removeEventListener for 'fetch' to called at anytime (#1195) (Thursday, 5 October)
• Re: [w3c/ServiceWorker] Proposal: Allow addEventListener/removeEventListener for 'fetch' to called at anytime (#1195) (Thursday, 5 October)

Walle Cyril

• Re: [w3c/ServiceWorker] Mixed feelings about ServiceWorker for module loader (#1203) (Monday, 23 October)

Wanming Lin

• Re: [w3c/manifest] Create a test suite for the specification (#623) (Friday, 20 October)

Wenbo Zhu

• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Thursday, 12 October)

Wired Earp

• Re: [w3c/webcomponents] Custom Element definition ordering can cause difficult-to-find bugs. (#668) (Sunday, 8 October)
• Re: [w3c/webcomponents] Custom Element definition ordering can cause difficult-to-find bugs. (#668) (Sunday, 8 October)

Xiaoqian Wu

• Re: [w3c/IndexedDB] Implementation report (#213) (Wednesday, 18 October)
• [w3c/workers] CSP: "CSP List" is missing. (#5) (Monday, 9 October)

Yehuda Katz

• Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Wednesday, 25 October)
• Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Wednesday, 25 October)
• Re: [whatwg/dom] Proposal: DOMChangeList (#270) (Wednesday, 25 October)

Yoichi Osato

• Re: [w3c/WebPlatformWG] TPAC agenda: Tue Nov 7 (Editing TF) (#93) (Monday, 30 October)
• Re: [w3c/WebPlatformWG] TPAC agenda: Tue Nov 7 (Editing TF) (#93) (Thursday, 26 October)
• Re: [w3c/selection-api] Support multi range selection (#41) (Thursday, 26 October)
• Re: [w3c/WebPlatformWG] TPAC agenda: Tue Nov 7 (Editing TF) (#93) (Wednesday, 25 October)

Yutaka Hirano

• Re: [whatwg/url] Should URLSearchParams stringify be called in URL constructor? (#350) (Monday, 30 October)
• [whatwg/url] Should URLSearchParams stringify be called in URL constructor? (#350) (Monday, 30 October)
• Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165) (Friday, 20 October)

Yves Lafon

• Re: [w3c/ServiceWorker] Warn readers that V1 is missing features compared to the nightly (#1205) (Thursday, 12 October)
• Re: [w3c/ServiceWorker] Warn readers that V1 is missing features compared to the nightly (#1205) (Wednesday, 11 October)
• Re: [w3c/ServiceWorker] reflect WG change [depends on another PR] (#1202) (Tuesday, 10 October)
• Re: [w3c/ServiceWorker] reflect WG change [depends on another PR] (#1202) (Tuesday, 10 October)
• [w3c/ServiceWorker] reflect WG change [depends on another PR] (#1202) (Wednesday, 4 October)

Z3TA

• Re: [whatwg/xhr] Synchronous XMLHttpRequest (#158) (Friday, 6 October)
• Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Thursday, 5 October)
• Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20) (Thursday, 5 October)
• [whatwg/xhr] Synchronous XMLHttpRequest (#158) (Thursday, 5 October)

Zazck

• Re: [w3c/IndexedDB] Encrypted storage (#191) (Sunday, 29 October)

zdzinks

• [whatwg/xhr] chrome-extension://agddmammmnpdglmincfngjfnehmopoln/js/content_script.js (#154) (Sunday, 1 October)

zhaoz

• Re: [w3c/webcomponents] Support `>>>` combinator in static profile (#78) (Tuesday, 10 October)

Last message date: Tuesday, 31 October 2017 23:47:28 UTC