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

=JeffH

• [w3c/WebPlatformWG] added my name to "hope to attend" list (#67) (Monday, 12 September)

Adam Rice

• Re: [w3c/ServiceWorker] Block 206s entering the cache (via put & addAll) (#937) (Thursday, 29 September)
• Re: [whatwg/encoding] Add support for whatwg streams (9224c4c) (Tuesday, 27 September)
• Re: [whatwg/encoding] Add support for whatwg streams (9224c4c) (Monday, 26 September)
• Re: [whatwg/encoding] Add support for whatwg streams (9224c4c) (Monday, 26 September)
• Re: [whatwg/streams] TransformStream: return promise from transformer.start() (cad1cc1) (Wednesday, 21 September)
• Re: [whatwg/streams] Update TransformStream API & misc. fixups (#519) (Tuesday, 20 September)
• Re: [whatwg/streams] Pass controller to transformer methods in TransformStream (#518) (Tuesday, 20 September)
• [whatwg/streams] Pass controller to transformer methods in TransformStream (#518) (Friday, 16 September)
• Re: [whatwg/streams] Factor out WritableStreamDefaultWriterRelease (#513) (Thursday, 1 September)

Ade Bateman

• Re: [w3c/uievents] Figure out what to do with focusin/focusout (#88) (Wednesday, 7 September)

Adrian Hope-Bailie

• Re: [w3c/manifest] Integration with service workers (#161) (Wednesday, 14 September)
• Re: [w3c/manifest] Integration with service workers (#161) (Tuesday, 13 September)
• Re: [w3c/manifest] Integration with service workers (#161) (Monday, 12 September)
• Re: [w3c/manifest] Integration with service workers (#161) (Monday, 12 September)
• Re: [w3c/manifest] Integration with service workers (#161) (Monday, 12 September)
• Re: [w3c/manifest] Integration with service workers (#161) (Monday, 12 September)
• Re: [w3c/manifest] Integration with service workers (#161) (Monday, 12 September)
• Re: [w3c/manifest] Integration with service workers (#161) (Monday, 12 September)
• Re: [w3c/manifest] Integration with service workers (#161) (Friday, 9 September)

Alex Danilo

• Re: [w3c/WebPlatformWG] CFC: Collect CFC responses on Github (#80) (Friday, 30 September)
• [w3c/WebPlatformWG] Add alex tpac (#79) (Thursday, 22 September)

Alex Russell

• [w3ctag/spec-reviews] A spec style/structure checklist? (#136) (Wednesday, 21 September)
• Re: [w3c/ServiceWorker] Inconsistencies due to when clients are created (#870) (Friday, 2 September)

Alexander Surkov

• Re: [w3c/webcomponents] Should ARIA 2.0 have a role corresponding to every HTML element? (#552) (Thursday, 8 September)
• Re: [w3c/webcomponents] Extensibility: How should we best support accessible Custom widgets and interactivity with ARIA? (#553) (Wednesday, 7 September)

aliams

• Re: [w3c/ServiceWorker] spec exactly how to order non-window Client objects (#887) (Wednesday, 28 September)

Alice

• Re: [WICG/modality] tiny typo fix (#27) (Monday, 26 September)
• Re: [WICG/modality] Add a simple example, remove the detailed docs. (#26) (Friday, 23 September)
• Re: [WICG/modality] Add a simple example, remove the detailed docs. (#26) (Friday, 23 September)

alisorri

• Re: [w3c/IndexedDB] IndexedDB refresh (#93) (Monday, 26 September)
• [w3c/IndexedDB] IndexedDB refresh (#93) (Sunday, 25 September)

Andrea Giammarchi

• Re: [w3c/webcomponents] [idea] Make use of `observedAttributes` optional (#565) (Wednesday, 21 September)
• Re: [w3c/webcomponents] [idea] Make use of `observedAttributes` optional (#565) (Wednesday, 21 September)
• Re: [w3c/webcomponents] [idea] Make use of `observedAttributes` optional (#565) (Tuesday, 20 September)
• Re: [w3c/webcomponents] [idea] Make use of `observedAttributes` optional (#565) (Tuesday, 20 September)
• Re: [w3c/webcomponents] [idea] Make use of `observedAttributes` optional (#565) (Tuesday, 20 September)
• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Wednesday, 14 September)
• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Wednesday, 14 September)
• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Wednesday, 14 September)
• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Wednesday, 14 September)
• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Wednesday, 14 September)
• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Wednesday, 14 September)
• Re: [w3c/webcomponents] Better custom event support for custom elements would be great (#546) (Wednesday, 14 September)

Andrew Sutherland

• Re: [w3c/ServiceWorker] Provide a simple synchronous k-v storage for ServiceWorker? (#981) (Saturday, 24 September)
• Re: [w3c/ServiceWorker] Allow Caching of POST requests (#977) (Wednesday, 14 September)
• Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920) (Wednesday, 14 September)
• Re: [w3c/ServiceWorker] Using BroadcastChannel to wake up a service worker (#975) (Friday, 9 September)
• Re: [w3c/ServiceWorker] Using BroadcastChannel to wake up a service worker (#975) (Friday, 9 September)

Andrés

• Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304) (Monday, 26 September)
• Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304) (Monday, 26 September)

Andy Earnshaw

• Re: [w3c/webcomponents] missing guidance on implementing an 'refresh' option. (#562) (Wednesday, 7 September)

Anne van Kesteren

• Re: [w3c/webcomponents] Shadow DOM and the Fullscreen API (#180) (Friday, 30 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Friday, 30 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Friday, 30 September)
• Re: [whatwg/fullscreen] Allow element in Shadow DOM to become fullscreen (#42) (Friday, 30 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Friday, 30 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Friday, 30 September)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Friday, 30 September)
• [whatwg/fetch] Reinvestigate redirects to data URLs (#393) (Friday, 30 September)
• Re: [whatwg/fetch] Handling of data URLs (#111) (Friday, 30 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Friday, 30 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Friday, 30 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Friday, 30 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Friday, 30 September)
• Re: [whatwg/fetch] Handling of data URLs (#111) (Friday, 30 September)
• Re: [whatwg/fetch] (WIP) allow Request to outlive environment settings object (#388) (Friday, 30 September)
• Re: [whatwg/storage] Use more generic example to demonstrate estimate() (#37) (Friday, 30 September)
• Re: [whatwg/storage] Use more generic example to demonstrate estimate() (#37) (Friday, 30 September)
• Re: [whatwg/storage] Use more generic example to demonstrate estimate() (#37) (Friday, 30 September)
• Re: [w3c/webcomponents] The get-the-parent algorithm shouldn't return null until we reach the root of the current tree (#577) (Friday, 30 September)
• Re: [heycam/webidl] Specify open dictionaries. (#180) (Friday, 30 September)
• Re: [w3c/webcomponents] The get-the-parent algorithm shouldn't return null until we reach the root of the current tree (#577) (Friday, 30 September)
• [heycam/webidl] Remove "initializing objects from iterables" (#181) (Friday, 30 September)
• Re: [whatwg/fetch] Clarification of Body package data algorithm with bytes, FormData and multipart/form-data MIME type (#392) (Friday, 30 September)
• Re: [w3c/webcomponents] The get-the-parent algorithm shouldn't return null until we reach the root of the current tree (#577) (Friday, 30 September)
• Re: [heycam/webidl] Specify open dictionaries. (#180) (Friday, 30 September)
• Re: [heycam/webidl] Specify open dictionaries. (#180) (Friday, 30 September)
• Re: [w3c/pointerlock] pointerlockchange is cancelable, breaking the processing model (#9) (Friday, 30 September)
• Re: [w3c/webcomponents] The get-the-parent algorithm shouldn't return null until we reach the root of the current tree (#577) (Thursday, 29 September)
• Re: [w3c/ServiceWorker] Foreign fetch vs non-credentialed requests (#878) (Thursday, 29 September)
• Re: [w3c/ServiceWorker] Foreign fetch vs non-credentialed requests (#878) (Thursday, 29 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Thursday, 29 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Thursday, 29 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Thursday, 29 September)
• Re: [w3c/ServiceWorker] registerForeignFetch({ origins, scope }) optional (#982) (Thursday, 29 September)
• Re: [w3c/ServiceWorker] registerForeignFetch({ origins, scope }) optional (#982) (Thursday, 29 September)
• Re: [whatwg/storage] Use more generic example to demonstrate estimate() (#37) (Thursday, 29 September)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Thursday, 29 September)
• Re: [w3c/webcomponents] Synthetic click activation steps should state whether the event is composed or not (#578) (Thursday, 29 September)
• Re: [w3c/webcomponents] The get-the-parent algorithm shouldn't return null until we reach the root of the current tree (#577) (Thursday, 29 September)
• Re: [whatwg/dom] Clarify that new Document creates a document of type "html", not "xml" (#308) (Thursday, 29 September)
• Re: [whatwg/dom] Clarify that new Document creates a document of type "html", not "xml" (#308) (Thursday, 29 September)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Wednesday, 28 September)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Wednesday, 28 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Wednesday, 28 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Wednesday, 28 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Wednesday, 28 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Wednesday, 28 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Wednesday, 28 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Wednesday, 28 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Wednesday, 28 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Wednesday, 28 September)
• Re: [whatwg/xhr] The spec needs to reflect legacy behavior for firing multiple LOADING readystatechanges. (#92) (Wednesday, 28 September)
• Re: [whatwg/xhr] The spec needs to reflect legacy behavior for firing multiple LOADING readystatechanges. (#92) (Wednesday, 28 September)
• Re: [w3c/webcomponents] Synthetic click activation steps should state whether the event is composed or not (#578) (Wednesday, 28 September)
• Re: [w3c/pointerlock] pointerlockchange is cancelable, breaking the processing model (#9) (Wednesday, 28 September)
• Re: [w3c/webcomponents] The get-the-parent algorithm shouldn't return null until we reach the root of the current tree (#577) (Wednesday, 28 September)
• Re: [heycam/webidl] Numeric type reform strawperson (#33) (Tuesday, 27 September)
• Re: [w3c/ServiceWorker] Using BroadcastChannel to wake up a service worker (#975) (Tuesday, 27 September)
• Re: [w3c/FileAPI] Streams is hot, FileReader.readAs____ is not (#40) (Tuesday, 27 September)
• [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Tuesday, 27 September)
• Re: [whatwg/fullscreen] Move the element type check out of the ready check (#57) (Tuesday, 27 September)
• Re: [whatwg/fullscreen] Move the element type check out of the ready check (#57) (Tuesday, 27 September)
• Re: [whatwg/fullscreen] Move the element type check out of the ready check (#57) (Tuesday, 27 September)
• Re: [whatwg/fetch] Make Request constructor more forgiving (#377) (Tuesday, 27 September)
• Re: [whatwg/fetch] Make Request constructor more forgiving (#377) (Tuesday, 27 September)
• [whatwg/fetch] Figure out if request header mutation is possible (#391) (Tuesday, 27 September)
• Re: [w3c/FileAPI] Streams is hot, FileReader.readAs____ is not (#40) (Tuesday, 27 September)
• Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304) (Tuesday, 27 September)
• Re: [whatwg/fetch] OpenEndedDictionary clarification (#164) (Tuesday, 27 September)
• [whatwg/encoding] Add Streams support (#72) (Tuesday, 27 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Monday, 26 September)
• Re: [whatwg/fullscreen] Should browser UI be able to activate fullscreen even if iframe is missing allowfullscreen (#56) (Monday, 26 September)
• Re: [w3c/ServiceWorker] Using BroadcastChannel to wake up a service worker (#975) (Monday, 26 September)
• Re: [w3c/pointerlock] pointerlockchange is cancelable, breaking the processing model (#9) (Monday, 26 September)
• Re: [whatwg/dom] Consider adding Promise-based API for listerning event (#333) (Monday, 26 September)
• Re: [heycam/webidl] Does a non-nullable and non-required dictionary member of interface type make sense? (#176) (Saturday, 24 September)
• Re: [w3c/ServiceWorker] Provide a simple synchronous k-v storage for ServiceWorker? (#981) (Saturday, 24 September)
• Re: [whatwg/dom] Symbols should be allowed as Event types. (#331) (Friday, 23 September)
• Re: [whatwg/dom] Why is the second parameter to MutationObserver.observe() optional? (#332) (Friday, 23 September)
• Re: [whatwg/dom] Why is the second parameter to MutationObserver.observe() optional? (#332) (Friday, 23 September)
• Re: [heycam/webidl] Namespace is a misnomer, should we fix it? (#177) (Wednesday, 21 September)
• Re: [w3c/webcomponents] slotchange event should not bubble (#571) (Wednesday, 21 September)
• Re: [whatwg/dom] Will there be a special nodeType for shadow root? (#330) (Wednesday, 21 September)
• Re: [heycam/webidl] Does a non-nullable and non-required dictionary member of interface type make sense? (#176) (Wednesday, 21 September)
• Re: [whatwg/streams] create a document from a stream (#520) (Tuesday, 20 September)
• Re: [heycam/webidl] Does a non-nullable and non-required dictionary member of interface type make sense? (#176) (Tuesday, 20 September)
• Re: [whatwg/streams] create a document from a stream (#520) (Tuesday, 20 September)
• Re: [whatwg/streams] create a document from a stream (#520) (Tuesday, 20 September)
• Re: [w3c/webcomponents] slotchange event should not bubble (#571) (Tuesday, 20 September)
• Re: [whatwg/fetch] (WIP) allow Request to outlive environment settings object (#388) (Tuesday, 20 September)
• Re: [w3c/DOM-Parsing] HTML Entities & Serialization output (code versus rendered) (#20) (Tuesday, 20 September)
• Re: [w3c/ServiceWorker] html no longer defines "referrer source" (#834) (Tuesday, 20 September)
• Re: [heycam/webidl] Does a non-nullable and non-required dictionary member of interface type make sense? (#176) (Tuesday, 20 September)
• Re: [whatwg/fetch] upload progress return response.json()? (#389) (Saturday, 17 September)
• Re: [whatwg/fetch] upload progress return response.json()? (#389) (Friday, 16 September)
• Re: [whatwg/fullscreen] To fullscreen/unfullscreen, do not take document as an argument (#55) (Friday, 16 September)
• Re: [whatwg/fullscreen] To fullscreen/unfullscreen, do not take document as an argument (#55) (Friday, 16 September)
• Re: [whatwg/fullscreen] To fullscreen/unfullscreen, do not take document as an argument (#55) (Friday, 16 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Friday, 16 September)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Friday, 16 September)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Friday, 16 September)
• Re: [whatwg/encoding] Add UTF-7 to replacement encoding list? (#68) (Friday, 16 September)
• Re: [whatwg/encoding] Add UTF-7 to replacement encoding list? (#68) (Friday, 16 September)
• Re: [whatwg/xhr] What with dat code? He not work :( (#91) (Friday, 16 September)
• Re: [whatwg/xhr] What with dat code? He not work :( (#91) (Friday, 16 September)
• Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Thursday, 15 September)
• Re: [whatwg/fetch] Treat data URLs as same-origin, except for workers (#387) (Thursday, 15 September)
• Re: [whatwg/fetch] Same-origin data-URL flag only for fetch and XHR? (#381) (Thursday, 15 September)
• Re: [whatwg/dom] Define how script-created click events are special during dispatch (#325) (Thursday, 15 September)
• Re: [whatwg/dom] Define how script-created click events are special during dispatch (#325) (Thursday, 15 September)
• Re: [whatwg/xhr] Fiddle with progress events (#90) (Thursday, 15 September)
• Re: [whatwg/xhr] Kill the progress event when readyState is 4 (#72) (Thursday, 15 September)
• Re: [whatwg/fetch] Treat data URLs as same-origin, except for workers (#387) (Thursday, 15 September)
• Re: [whatwg/xhr] Kill the progress event when readyState is 4 (#72) (Thursday, 15 September)
• Re: [whatwg/fetch] Treat data URLs as same-origin, except for workers (#387) (Thursday, 15 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Thursday, 15 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Thursday, 15 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Thursday, 15 September)
• Re: [whatwg/xhr] Fiddle with progress events (#90) (Thursday, 15 September)
• Re: [whatwg/xhr] Kill the progress event when readyState is 4 (#72) (Thursday, 15 September)
• Re: [whatwg/fullscreen] Editorial: shorten the top layer add/remove IDs (#51) (Thursday, 15 September)
• Re: [whatwg/fullscreen] Editorial: shorten the top layer add/remove IDs (#51) (Thursday, 15 September)
• Re: [whatwg/fullscreen] Editorial: shorten the top layer add/remove IDs (#51) (Thursday, 15 September)
• Re: [whatwg/fetch] Make Request constructor more forgiving (#377) (Thursday, 15 September)
• Re: [whatwg/fetch] Treat data URLs as same-origin, except for workers (#387) (Thursday, 15 September)
• [whatwg/xhr] Fiddle with progress events (#90) (Thursday, 15 September)
• Re: [whatwg/xhr] Kill the progress event when readyState is 4 (#72) (Thursday, 15 September)
• Re: [whatwg/xhr] Kill the progress event when readyState is 4 (#72) (Thursday, 15 September)
• Re: [whatwg/dom] Define a document's origin instead of linking to HTML's generic "origin" definition. (#313) (Thursday, 15 September)
• Re: [whatwg/dom] Make Element's slot attributes Unscopable (#328) (Thursday, 15 September)
• Re: [whatwg/dom] Make Element's slot attributes Unscopable (#329) (Thursday, 15 September)
• Re: [whatwg/fullscreen] Remove redundant recursive step of fullscreen element ready check (#52) (Thursday, 15 September)
• Re: [whatwg/fullscreen] Editorial: shorten the top layer add/remove IDs (#51) (Thursday, 15 September)
• Re: [whatwg/dom] Make Element's slot attributes Unscopable (#329) (Thursday, 15 September)
• Re: [whatwg/dom] Make Element's slot attributes Unscopable (#329) (Thursday, 15 September)
• Re: [whatwg/dom] Make Element's slot attributes Unscopable (#329) (Thursday, 15 September)
• Re: [whatwg/dom] Make Element's slot attributes Unscopable (#329) (Thursday, 15 September)
• Re: [whatwg/fetch] Same-origin data-URL flag only for fetch and XHR? (#381) (Thursday, 15 September)
• Re: [whatwg/fetch] Same-origin data-URL flag only for fetch and XHR? (#381) (Thursday, 15 September)
• Re: [whatwg/fetch] Treat data URLs as same-origin, except for workers (#387) (Wednesday, 14 September)
• Re: [whatwg/fetch] Same-origin data-URL flag only for fetch and XHR? (#381) (Wednesday, 14 September)
• Re: [whatwg/fetch] Treat data URLs as same-origin, except for workers (#387) (Wednesday, 14 September)
• [whatwg/fetch] Treat data URLs as same-origin, except for workers (#387) (Wednesday, 14 September)
• Re: [whatwg/fetch] Add request's reserved client (#383) (Wednesday, 14 September)
• Re: [whatwg/fetch] There's no reason to make fetch of about:blank same-origin for loads other than navigations and `<object>` (#384) (Wednesday, 14 September)
• Re: [whatwg/fetch] Main fetch should not make all about-scheme things same-origin (#385) (Wednesday, 14 September)
• Re: [whatwg/fetch] There's no reason to make fetch of about:blank same-origin for loads other than navigations and `<object>` (#384) (Wednesday, 14 September)
• Re: [whatwg/fetch] Add request's reserved client (#383) (Wednesday, 14 September)
• Re: [whatwg/fetch] There's no reason to make fetch of about:blank same-origin for loads other than navigations and `<object>` (#384) (Wednesday, 14 September)
• Re: [whatwg/fetch] Add request's reserved client (#383) (Wednesday, 14 September)
• Re: [whatwg/fullscreen] Convert to Bikeshed (#49) (Wednesday, 14 September)
• Re: [whatwg/fullscreen] Convert to Bikeshed (#49) (Wednesday, 14 September)
• Re: [whatwg/fullscreen] Convert to Bikeshed (#49) (Wednesday, 14 September)
• Re: [whatwg/fullscreen] Convert to Bikeshed (#49) (Wednesday, 14 September)
• Re: [whatwg/fetch] Same-origin data-URL flag only for fetch and XHR? (#381) (Wednesday, 14 September)
• Re: [whatwg/dom] Shadow: Make Event.composedPath() use closed-shadow-hidden when currentTarget is window (#327) (Wednesday, 14 September)
• Re: [whatwg/dom] event.composedPath() should not return every items in path if event.currentTarget is window (#326) (Wednesday, 14 September)
• Re: [whatwg/dom] Shadow: Make Event.composedPath() use closed-shadow-hidden when currentTarget is window (#327) (Wednesday, 14 September)
• Re: [whatwg/dom] Shadow: Make Event.composedPath() use closed-shadow-hidden when currentTarget is window (#327) (Wednesday, 14 September)
• Re: [whatwg/dom] Shadow: Make Event.composedPath() use closed-shadow-hidden when currentTarget is window (#327) (Wednesday, 14 September)
• Re: [whatwg/fetch] Add request's reserved client (#383) (Tuesday, 13 September)
• Re: [whatwg/fetch] Add request's reserved client (#383) (Tuesday, 13 September)
• Re: [whatwg/fetch] Add request's reserved client (#383) (Tuesday, 13 September)
• Re: [whatwg/fullscreen] Convert to Bikeshed (#49) (Tuesday, 13 September)
• Re: [whatwg/fullscreen] Convert to Bikeshed (#49) (Tuesday, 13 September)
• Re: [whatwg/fullscreen] Convert to Bikeshed (#49) (Tuesday, 13 September)
• Re: [whatwg/fullscreen] Prepare for conversion to Bikeshed (#48) (Tuesday, 13 September)
• Re: [whatwg/fullscreen] Prepare for conversion to Bikeshed (#48) (Tuesday, 13 September)
• Re: [whatwg/fullscreen] Prepare for conversion to Bikeshed (#48) (Tuesday, 13 September)
• Re: [whatwg/dom] Shadow: Make Event.composedPath() use closed-shadow-hidden when currentTarget is window (#327) (Tuesday, 13 September)
• Re: [whatwg/dom] Shadow: Make Event.composedPath() use closed-shadow-hidden when currentTarget is window (#327) (Tuesday, 13 September)
• Re: [whatwg/dom] Shadow: Make Event.composedPath() use closed-shadow-hidden when currentTarget is window (#327) (Tuesday, 13 September)
• Re: [whatwg/dom] Shadow: Make Event.composedPath() use closed-shadow-hidden when currentTarget is window (#327) (Tuesday, 13 September)
• Re: [whatwg/dom] Shadow: Make Event.composedPath() use closed-shadow-hidden when currentTarget is window (#327) (Tuesday, 13 September)
• Re: [whatwg/dom] Shadow: Make Event.composedPath() use closed-shadow-hidden when currentTarget is window (#327) (Tuesday, 13 September)
• Re: [whatwg/dom] Shadow: Make Event.composedPath() use closed-shadow-hidden when currentTarget is window (#327) (Tuesday, 13 September)
• Re: [whatwg/dom] Shadow: Make Event.composedPath() use closed-shadow-hidden when currentTarget is window (#327) (Tuesday, 13 September)
• Re: [whatwg/dom] window.composedPath() should not return every items in path (#326) (Tuesday, 13 September)
• Re: [w3c/webcomponents] Is <slot> a replaced element or not? (#564) (Monday, 12 September)
• Re: [whatwg/encoding] Remove the last 14 characters PUA of GB18030-2005 (#27) (Saturday, 10 September)
• Re: [heycam/webidl] Contributing to webidl just got a lot harder (#171) (Friday, 9 September)
• Re: [w3c/ServiceWorker] Using BroadcastChannel to wake up a service worker (#975) (Friday, 9 September)
• Re: [heycam/webidl] Contributing to webidl just got a lot harder (#171) (Friday, 9 September)
• Re: [heycam/webidl] Convert idl- prefixed anchors to Bikeshed notation. (#170) (Friday, 9 September)
• Re: [whatwg/xhr] Please fix this issue (#89) (Friday, 9 September)
• Re: [whatwg/xhr] Please fix this issue (#89) (Friday, 9 September)
• Re: [w3c/ServiceWorker] Using BroadcastChannel to wake up a service worker (#975) (Friday, 9 September)
• Re: [w3c/ServiceWorker] Using BroadcastChannel to wake up a service worker (#975) (Friday, 9 September)
• Re: [w3c/ServiceWorker] Inconsistencies due to when clients are created (#870) (Thursday, 8 September)
• Re: [whatwg/fetch] Same-origin data-URL flag only for fetch and XHR? (#381) (Thursday, 8 September)
• Re: [whatwg/fetch] Same-origin data-URL flag only for fetch and XHR? (#381) (Thursday, 8 September)
• Re: [whatwg/fetch] Listing headers safe only for certain values is a bad idea (#313) (Thursday, 8 September)
• Re: [whatwg/fetch] CORS-safelisted request headers should be restricted according to RFC 7231 (#382) (Wednesday, 7 September)
• Re: [whatwg/fetch] Same-origin data-URL flag only for fetch and XHR? (#381) (Wednesday, 7 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Wednesday, 7 September)
• Re: [whatwg/fetch] Same-origin data-URL flag only for fetch and XHR? (#381) (Wednesday, 7 September)
• Re: [w3c/ServiceWorker] CacheStorage has an associated global object? (#964) (Wednesday, 7 September)
• Re: [whatwg/encoding] Remove the last 14 characters PUA of GB18030-2005 (#27) (Wednesday, 7 September)
• Re: [whatwg/fetch] Same-origin data-URL flag only for fetch and XHR? (#381) (Wednesday, 7 September)
• Re: [w3c/ServiceWorker] CacheStorage has an associated global object? (#964) (Wednesday, 7 September)
• Re: [whatwg/fetch] CORS-safelisted request headers should be restricted according to RFC 7231 (#382) (Wednesday, 7 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Wednesday, 7 September)
• Re: [whatwg/dom] Clarify that new Document creates a document of type "html", not "xml" (#308) (Tuesday, 6 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Tuesday, 6 September)
• Re: [whatwg/fetch] Same-origin data-URL flag only for fetch and XHR? (#381) (Tuesday, 6 September)
• Re: [whatwg/encoding] Remove the last 14 characters PUA of GB18030-2005 (#27) (Tuesday, 6 September)
• Re: [w3c/webcomponents] missing guidance on implementing an 'refresh' option. (#562) (Tuesday, 6 September)
• Re: [w3c/ServiceWorker] CacheStorage has an associated global object? (#964) (Tuesday, 6 September)
• Re: [whatwg/encoding] Remove the last 14 characters PUA of GB18030-2005 (#27) (Tuesday, 6 September)
• Re: [w3c/webcomponents] missing guidance on implementing an 'refresh' option. (#562) (Tuesday, 6 September)
• Re: [whatwg/fetch] Prevent modifying headers on Responses (#24) (Tuesday, 6 September)
• Re: [whatwg/dom] Clarify that new Document creates a document of type "html", not "xml" (#308) (Tuesday, 6 September)
• Re: [whatwg/encoding] Remove the last 14 characters PUA of GB18030-2005 (#27) (Tuesday, 6 September)
• Re: [w3c/permissions] refactor(media devices): use "allowed to use" (#122) (Saturday, 3 September)
• Re: [whatwg/dom] Define how script-created click events are special during dispatch (#325) (Friday, 2 September)
• Re: [w3c/webcomponents] [Shadow]: rename <content> to <slot> (bugzilla: 28561) (#92) (Friday, 2 September)
• Re: [whatwg/url] Editorial: Update spelling of HTML terms to en-US (#147) (Friday, 2 September)
• Re: [whatwg/fetch] Allow custom headers on no-cors requests (#380) (Friday, 2 September)
• Re: [whatwg/fetch] Allow custom headers on no-cors requests (#380) (Friday, 2 September)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Friday, 2 September)
• Re: [whatwg/dom] Drop support for SVGZoomEvent in createEvent (#323) (Thursday, 1 September)
• Re: [whatwg/dom] Drop support for SVGZoomEvent in createEvent (#323) (Thursday, 1 September)
• Re: [whatwg/dom] Drop support for SVGZoomEvent in createEvent (#323) (Thursday, 1 September)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Thursday, 1 September)
• Re: [whatwg/xhr] Fix an obsolete ReadableStream operation name (#87) (Thursday, 1 September)
• Re: [whatwg/xhr] Fix ReadableStream abstract operations markup (#85) (Thursday, 1 September)
• Re: [whatwg/xhr] Fix an obsolete ReadableStream operation name (#87) (Thursday, 1 September)
• Re: [whatwg/dom] CDATASection misses (#300) (Thursday, 1 September)
• Re: [whatwg/dom] CDATASection misses (#300) (Thursday, 1 September)
• Re: [whatwg/dom] " public-scrip-coord@w3.org" (#322) (Thursday, 1 September)
• Re: [whatwg/dom] " public-scrip-coord@w3.org" (#322) (Thursday, 1 September)
• Re: [whatwg/dom] CDATASection nodes don't like to be normalized away (#310) (Thursday, 1 September)
• Re: [whatwg/dom] CDATASection nodes don't like to be normalized away (#310) (Thursday, 1 September)
• Re: [heycam/webidl] Add [[PlatformBrand]] internal slot to all platform objects (#97) (Thursday, 1 September)

Anssi Kostiainen

• [w3c/manifest] Combine Origin Policy mechanism with the Web App Manifest? (#500) (Wednesday, 21 September)

aphillips

• Re: [whatwg/encoding] Remove the last 14 characters PUA of GB18030-2005 (#27) (Tuesday, 6 September)

ArkadiuszMichalski

• Re: [whatwg/dom] Clarify that DOMTokenList's .replace() must preserve the original order (#324) (Thursday, 1 September)

Arthur Stolyar

• Re: [w3c/ServiceWorker] Allow Caching of POST requests (#977) (Wednesday, 14 September)

Aryeh Gregor

• Re: [whatwg/dom] Clarify that DOMTokenList's .replace() must preserve the original order (#324) (Thursday, 1 September)
• [whatwg/dom] Clarify that DOMTokenList's .replace() must preserve the original order (#324) (Thursday, 1 September)
• Re: [whatwg/dom] Drop support for SVGZoomEvent in createEvent (#323) (Thursday, 1 September)
• Re: [whatwg/dom] Drop support for SVGZoomEvent in createEvent (#323) (Thursday, 1 September)

Ashley (Scirra)

• Re: [w3c/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Monday, 5 September)

bashi

• [heycam/webidl] Fix typo (#161) (#162) (Thursday, 8 September)
• [heycam/webidl] Typo in converting sequence (#161) (Thursday, 8 September)

Bede Overend

• [w3c/webcomponents] Expected behaviour of contentEditable, slot and distributed nodes (#579) (Wednesday, 28 September)

Ben

• Re: [w3c/manifest] (Re-)Add Optional Splash Screens (#501) (Friday, 23 September)

Ben Buchanan (200ok)

• Re: [w3c/manifest] Support a way to update explicitly (#446) (Thursday, 15 September)

Ben Francis

• Re: [w3c/manifest] (Re-)Add Optional Splash Screens (#501) (Friday, 23 September)
• Re: [w3c/manifest] Integration with service workers (#161) (Tuesday, 20 September)
• Re: [w3c/manifest] Add optional Transition Screen member (#478) (Friday, 16 September)
• Re: [w3c/manifest] Allow for multiple scopes (#449) (Tuesday, 13 September)
• Re: [w3c/manifest] Allow for multiple scopes (#449) (Tuesday, 13 September)

Ben Gummer

• [w3c/webcomponents] How should autofill work for inputs generated inside shadow roots (#572) (Wednesday, 21 September)

Ben Kelly

• Re: [w3c/ServiceWorker] Provide a simple synchronous k-v storage for ServiceWorker? (#981) (Monday, 26 September)
• Re: [whatwg/fetch] (WIP) allow Request to outlive environment settings object (#388) (Friday, 23 September)
• Re: [w3c/ServiceWorker] postMessage keeps service workers alive indefinitely (#980) (Wednesday, 21 September)
• Re: [w3c/ServiceWorker] Allow Caching of POST requests (#977) (Tuesday, 20 September)
• Re: [w3c/ServiceWorker] Allow Caching of POST requests (#977) (Wednesday, 14 September)
• Re: [w3c/ServiceWorker] is it possible to stop browser to refetch scripts and reevaluate them if they haven't changed? (#978) (Wednesday, 14 September)
• Re: [whatwg/fetch] Can an internal response be another filtered response? (#386) (Wednesday, 14 September)
• Re: [w3c/ServiceWorker] Communicate with Native Apps (#960) (Tuesday, 13 September)
• Re: [w3c/ServiceWorker] Using BroadcastChannel to wake up a service worker (#975) (Friday, 9 September)
• Re: [w3c/ServiceWorker] allow service worker produced resources to be marked as "cachable" (#962) (Friday, 9 September)
• Re: [w3c/ServiceWorker] Using BroadcastChannel to wake up a service worker (#975) (Friday, 9 September)
• Re: [w3c/ServiceWorker] Reloading page causes one extra client on client list (#972) (Tuesday, 6 September)

Benjamin C. Wiley Sittler

• Re: [w3c/ServiceWorker] Provide a simple synchronous k-v storage for ServiceWorker? (#981) (Sunday, 25 September)

Bevis Tseng

• Re: [w3c/IndexedDB] Abort behavior for renames of newly created stores/indexes, for #89 (#90) (Thursday, 8 September)
• Re: [w3c/IndexedDB] Specify interaction between transaction abort and index/object store renames (#89) (Thursday, 8 September)
• Re: [w3c/IndexedDB] Specify interaction between transaction abort and index/object store renames (#89) (Thursday, 8 September)

Birdie377

• [whatwg/xhr] Please fix this issue (#89) (Thursday, 8 September)

Boris Zbarsky

• Re: [heycam/webidl] Specify open dictionaries. (#180) (Friday, 30 September)
• Re: [heycam/webidl] Specify open dictionaries. (#180) (Friday, 30 September)
• Re: [heycam/webidl] Specify open dictionaries. (#180) (Friday, 30 September)
• Re: [heycam/webidl] Remove "initializing objects from iterables" (#181) (Friday, 30 September)
• Re: [w3c/IndexedDB] Remove IDBEnvironment in favor of partial interface (#95) (Thursday, 29 September)
• [w3c/IndexedDB] IDBEnvironment IDL is not valid (#94) (Wednesday, 28 September)
• Re: [whatwg/dom] Figure out what to do with XMLDocument (#278) (Wednesday, 28 September)
• Re: [heycam/webidl] ES [[Get]] now takes a Receiver (#178) (Thursday, 22 September)
• Re: [heycam/webidl] ES [[Get]] now takes a Receiver (#178) (Thursday, 22 September)
• Re: [heycam/webidl] Add a forgotten closing parenthesis. (#179) (Thursday, 22 September)
• Re: [heycam/webidl] Named properties visibility algorithm leads to ES invariant violation (#152) (Tuesday, 20 September)
• Re: [heycam/webidl] Does a non-nullable and non-required dictionary member of interface type make sense? (#176) (Tuesday, 20 September)
• Re: [heycam/webidl] Namespace is a misnomer, should we fix it? (#177) (Monday, 19 September)
• Re: [whatwg/dom] Clarify that new Document creates a document of type "html", not "xml" (#308) (Friday, 16 September)
• Re: [whatwg/dom] Clarify that new Document creates a document of type "html", not "xml" (#308) (Friday, 16 September)
• Re: [whatwg/dom] Clarify that new Document creates a document of type "html", not "xml" (#308) (Friday, 16 September)
• Re: [whatwg/fetch] Same-origin data-URL flag only for fetch and XHR? (#381) (Tuesday, 13 September)
• [whatwg/fetch] Main fetch should not make all about-scheme things same-origin (#385) (Tuesday, 13 September)
• [whatwg/fetch] There's no reason to make fetch of about:blank same-origin for loads other than navigations and `<object>` (#384) (Tuesday, 13 September)
• Re: [heycam/webidl] Named properties visibility algorithm leads to ES invariant violation (#152) (Monday, 12 September)
• Re: [heycam/webidl] Named properties visibility algorithm leads to ES invariant violation (#152) (Monday, 12 September)
• [heycam/webidl] Various named property stuff seems confused in the face of symbols (#175) (Friday, 9 September)
• Re: [heycam/webidl] Contributing to webidl just got a lot harder (#171) (Friday, 9 September)
• Re: [heycam/webidl] Change the named property visibility algorithm so that existing own props always make corresponding named props invisible. (#174) (Friday, 9 September)
• Re: [heycam/webidl] Change the named property visibility algorithm so that existing own props always make corresponding named props invisible. (#174) (Friday, 9 September)
• Re: [heycam/webidl] Change the named property visibility algorithm so that existing own props always make corresponding named props invisible. (#174) (Friday, 9 September)
• [heycam/webidl] Change the named property visibility algorithm so that existing own props always make corresponding named props invisible. (#174) (Friday, 9 September)
• Re: [heycam/webidl] Contributing to webidl just got a lot harder (#171) (Friday, 9 September)
• Re: [heycam/webidl] Contributing to webidl just got a lot harder (#171) (Friday, 9 September)
• Re: [heycam/webidl] Contributing to webidl just got a lot harder (#171) (Friday, 9 September)
• Re: [heycam/webidl] Contributing to webidl just got a lot harder (#171) (Friday, 9 September)
• Re: [heycam/webidl] Contributing to webidl just got a lot harder (#171) (Friday, 9 September)
• Re: [heycam/webidl] Contributing to webidl just got a lot harder (#171) (Friday, 9 September)
• Re: [heycam/webidl] Contributing to webidl just got a lot harder (#171) (Friday, 9 September)
• [heycam/webidl] Contributing to webidl just got a lot harder (#171) (Friday, 9 September)
• Re: [heycam/webidl] Move conventions and conformance to appendices (#167) (Friday, 9 September)
• Re: [heycam/webidl] Move conventions and conformance to appendices (#167) (Friday, 9 September)
• Re: [heycam/webidl] Remove the "Changes" section (#166) (Thursday, 8 September)
• Re: [heycam/webidl] Consolidate issue tracking links in the header under "Feedback" (#169) (Thursday, 8 September)
• Re: [heycam/webidl] Consolidate issue tracking links in the header under "Feedback" (#169) (Thursday, 8 September)
• Re: [heycam/webidl] Should specify that all JS functions created by IDL are "built-in functions" (#106) (Thursday, 8 September)
• Re: [heycam/webidl] Update method creation for operations (#155) (Thursday, 8 September)
• Re: [heycam/webidl] Fix typo (#161) (#162) (Thursday, 8 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Wednesday, 7 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Wednesday, 7 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Wednesday, 7 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Tuesday, 6 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Tuesday, 6 September)
• Re: [heycam/webidl] Update method creation for operations (#155) (Friday, 2 September)
• Re: [heycam/webidl] Update method creation for operations (#155) (Friday, 2 September)
• Re: [heycam/webidl] Update method creation for operations (#155) (Friday, 2 September)

bORm

• Re: [whatwg/fetch] upload progress return response.json()? (#389) (Saturday, 17 September)
• Re: [whatwg/fetch] upload progress return response.json()? (#389) (Friday, 16 September)
• [whatwg/fetch] upload progress return response.json()? (#389) (Friday, 16 September)
• Re: [whatwg/fetch] upload progress? (#21) (Friday, 16 September)

Bradley Ayers

• Re: [w3c/webcomponents] Is there a way to retrieve the localName from a custom element constructor? (#566) (Monday, 19 September)
• Re: [w3c/webcomponents] Is there a way to retrieve the localName from a custom element constructor? (#566) (Monday, 19 September)

Brandon Jones

• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Friday, 16 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Friday, 16 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Friday, 16 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Thursday, 15 September)
• Re: [w3c/gamepad] Added GamepadPose (#25) (Wednesday, 14 September)
• Re: [w3c/gamepad] Added GamepadPose (#25) (Wednesday, 14 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Wednesday, 14 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Wednesday, 14 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Tuesday, 13 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Tuesday, 13 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Monday, 12 September)
• [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Sunday, 11 September)

Brennan Frydl

• [whatwg/fetch] Gretchen, stop trying to make fetch happen! (#394) (Friday, 30 September)

Cameron McCormack

• Re: [heycam/webidl] Remove the "Changes" section (#166) (Friday, 9 September)
• Re: [heycam/webidl] Remove the "Changes" section (#166) (Friday, 9 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Wednesday, 7 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Wednesday, 7 September)

chaals

• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Tuesday, 27 September)
• [w3c/XMLHttpRequest] Publish as a Note - abandoned work item? (#2) (Tuesday, 27 September)
• Re: [w3c/WebPlatformWG] Different ways to run a CFC? (#38) (Tuesday, 27 September)
• Re: [w3c/WebPlatformWG] Update TPAC Editing meeting agenda (#77) (Thursday, 22 September)
• Re: [w3c/WebPlatformWG] Update 16-09-22TPAC-3.md (#76) (Thursday, 22 September)

chenqiang1986

• Re: [w3ctag/spec-reviews] Disable Local Playback During Audio Sharing (#137) (Tuesday, 27 September)
• Re: [w3ctag/spec-reviews] Disable Local Playback During Audio Sharing (#137) (Tuesday, 27 September)
• [w3ctag/spec-reviews] Disable Local Playback During Audio Sharing (#137) (Tuesday, 27 September)

Chong Zhang

• [w3c/WebPlatformWG] Update TPAC Editing meeting agenda (#77) (Thursday, 22 September)
• Re: [w3c/editing] Feedback on beforeinput (spec and the current implementation in Chrome Canary) (#149) (Wednesday, 21 September)
• [w3c/WebPlatformWG] Add Chong Zhang to attendees (#74) (Sunday, 18 September)

Chris Dumez

• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Wednesday, 28 September)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Wednesday, 28 September)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Wednesday, 28 September)
• [whatwg/dom] Why is the second parameter to MutationObserver.observe() optional? (#332) (Thursday, 22 September)
• Re: [whatwg/dom] Clarify that new Document creates a document of type "html", not "xml" (#308) (Friday, 16 September)
• Re: [whatwg/dom] Clarify that new Document creates a document of type "html", not "xml" (#308) (Friday, 16 September)
• Re: [heycam/webidl] Named properties visibility algorithm leads to ES invariant violation (#152) (Monday, 12 September)
• Re: [heycam/webidl] Remove the RegExp type (#148) (Thursday, 8 September)

Chris Lord

• Re: [w3c/manifest] Add optional Transition Screen member (#478) (Thursday, 22 September)

Chris Rebert

• Re: [w3c/uievents] Converge with CSSOM-View (#24) (Monday, 12 September)

chris van wiemeersch

• Re: [w3c/gamepad] Support Buffered Haptic Effects (#39) (Wednesday, 28 September)
• Re: [w3c/gamepad] Support Buffered Haptic Effects (#39) (Tuesday, 27 September)
• Re: [w3c/gamepad] Determine how Multi-touch surfaces should be handled. (#27) (Saturday, 24 September)
• Re: [w3c/gamepad] spec `gamepadbuttondown` and `gamepadbuttonup` events (issue #4) (#15) (Sunday, 18 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Friday, 16 September)
• Re: [w3c/gamepad] Support trackpad inputs (#34) (Thursday, 15 September)
• Re: [w3c/gamepad] Added GamepadPose (#25) (Wednesday, 14 September)
• Re: [w3c/gamepad] Consider using Bikeshed for spec formatting (#33) (Tuesday, 13 September)
• [w3c/gamepad] Consider using Bikeshed for spec formatting (#33) (Tuesday, 13 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Tuesday, 13 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Tuesday, 13 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Tuesday, 13 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Tuesday, 13 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Tuesday, 13 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Tuesday, 13 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Tuesday, 13 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Tuesday, 13 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Tuesday, 13 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Tuesday, 13 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Tuesday, 13 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Tuesday, 13 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Tuesday, 13 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Tuesday, 13 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Tuesday, 13 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Tuesday, 13 September)

Chris Wilson

• [w3c/WebPlatformWG] Added cwilso. (#78) (Thursday, 22 September)

cynthia

• Re: [w3c/WebPlatformWG] Add Nolan to attendees (#75) (Wednesday, 21 September)

Cyril Auburtin

• Re: [w3c/selection-api] user-select: none and selectionchange event (#74) (Monday, 12 September)
• [w3c/selection-api] user-select: none and selectionchange event (#74) (Monday, 12 September)

Cătălin Mariș

• Re: [w3c/manifest] [Appendix] Add crawl opt-out (closes #498) (#499) (Friday, 16 September)
• Re: [w3c/manifest] Describe how developers can block web crawlers (#498) (Saturday, 10 September)

Daniel Glazman

• Re: [w3c/pointerlock] pointerlockchange is cancelable, breaking the processing model (#9) (Wednesday, 28 September)
• [w3c/pointerlock] pointerlockchange is cancelable, breaking the processing model (#9) (Thursday, 22 September)

Daniel Herr

• [w3c/ServiceWorker] registerForeignFetch({ origins, scope }) optional (#982) (Tuesday, 27 September)

davaajav-shino

• [w3c/webcomponents] CustomElements: upgrade runs connectedCallback on an element with a throwing constructor (#563) (Wednesday, 7 September)

Dave Tapuska

• Re: [whatwg/dom] Consider adding Promise-based API for listerning event (#333) (Tuesday, 27 September)
• Re: [w3c/selection-api] Selection events for text controls (#53) (Tuesday, 20 September)
• Re: [w3c/uievents] Figure out what to do with focusin/focusout (#88) (Tuesday, 20 September)
• Re: [w3c/editing] July 29th F2F Agenda Item - Set Virtual Keyboard Enter Key Text (#142) (Friday, 16 September)
• Re: [w3c/uievents] Figure out what to do with focusin/focusout (#88) (Wednesday, 7 September)

David Baron

• Re: [w3ctag/spec-reviews] Disable Local Playback During Audio Sharing (#137) (Tuesday, 27 September)

David Singer

• Re: [w3ctag/spec-reviews] A spec style/structure checklist? (#136) (Monday, 26 September)
• Re: [w3ctag/spec-reviews] A spec style/structure checklist? (#136) (Thursday, 22 September)

Devdatta Akhawe

• Re: [w3c/ServiceWorker] Allow Caching of POST requests (#977) (Wednesday, 14 September)
• [w3c/ServiceWorker] Allow Caching of POST requests (#977) (Tuesday, 13 September)

Dima Voytenko

• Re: [whatwg/dom] Will there be a special nodeType for shadow root? (#330) (Wednesday, 21 September)
• Re: [whatwg/dom] Will there be a special nodeType for shadow root? (#330) (Wednesday, 21 September)
• [whatwg/dom] Will there be a special nodeType for shadow root? (#330) (Tuesday, 20 September)

Domenic Denicola

• Re: [heycam/webidl] Specify open dictionaries. (#180) (Friday, 30 September)
• Re: [heycam/webidl] Specify open dictionaries. (#180) (Friday, 30 September)
• Re: [whatwg/fetch] (WIP) allow Request to outlive environment settings object (#388) (Thursday, 29 September)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Wednesday, 28 September)
• Re: [w3c/FileAPI] Streams is hot, FileReader.readAs____ is not (#40) (Tuesday, 27 September)
• Re: [whatwg/streams] fix ReadableStream spec inconsistencies (#521) (Sunday, 25 September)
• Re: [whatwg/streams] fix ReadableStream spec inconsistencies (#521) (Sunday, 25 September)
• Re: [w3c/webcomponents] [Custom]: Callback for cloneNode/importNode (bugzilla: 24570) (#176) (Thursday, 22 September)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Thursday, 22 September)
• Re: [w3c/webcomponents] [Custom]: Callback for cloneNode/importNode (bugzilla: 24570) (#176) (Thursday, 22 September)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Thursday, 22 September)
• Re: [w3c/webcomponents] Status codes for HTML Imports (#568) (Wednesday, 21 September)
• Re: [w3c/ServiceWorker] html no longer defines "referrer source" (#834) (Tuesday, 20 September)
• Re: [whatwg/streams] create a document from a stream (#520) (Tuesday, 20 September)
• Re: [whatwg/streams] create a document from a stream (#520) (Tuesday, 20 September)
• Re: [whatwg/fetch] (WIP) allow Request to outlive environment settings object (#388) (Tuesday, 20 September)
• Re: [heycam/webidl] Does a non-nullable and non-required dictionary member of interface type make sense? (#176) (Tuesday, 20 September)
• Re: [heycam/webidl] Does a non-nullable and non-required dictionary member of interface type make sense? (#176) (Tuesday, 20 September)
• Re: [w3c/webcomponents] [Custom]: Need callback for form submit data (bugzilla: 24603) (#187) (Monday, 19 September)
• Re: [w3c/webcomponents] Make createElement report an exception instead of propagating an exception (#569) (Monday, 19 September)
• [w3c/webcomponents] createElement needs [CEReactions] because it sets is="" (#570) (Monday, 19 September)
• Re: [w3c/webcomponents] Should parser extensibility be a design goal? (#113) (Monday, 19 September)
• Re: [w3c/webcomponents] Should parser extensibility be a design goal? (#113) (Monday, 19 September)
• Re: [w3c/webcomponents] Status codes for HTML Imports (#568) (Sunday, 18 September)
• Re: [w3c/webcomponents] Better custom event support for custom elements would be great (#546) (Sunday, 18 September)
• Re: [w3c/webcomponents] Is there a way to retrieve the localName from a custom element constructor? (#566) (Friday, 16 September)
• Re: [whatwg/dom] Clarify that new Document creates a document of type "html", not "xml" (#308) (Friday, 16 September)
• Re: [whatwg/dom] Clarify that new Document creates a document of type "html", not "xml" (#308) (Friday, 16 September)
• Re: [w3c/webcomponents] HTML element constructors need to Get(newTarget, "Prototype") (#560) (Thursday, 15 September)
• Re: [w3c/webcomponents] CustomElements: upgrade runs connectedCallback on an element with a throwing constructor (#563) (Thursday, 15 September)
• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Wednesday, 14 September)
• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Wednesday, 14 September)
• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Wednesday, 14 September)
• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Wednesday, 14 September)
• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Wednesday, 14 September)
• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Wednesday, 14 September)
• Re: [w3c/webcomponents] [idea] Make use of `observedAttributes` optional (#565) (Wednesday, 14 September)
• Re: [w3c/webcomponents] [idea] Make use of `observedAttributes` optional (#565) (Wednesday, 14 September)
• Re: [w3c/webcomponents] Is there a way to retrieve the localName from a custom element constructor? (#566) (Wednesday, 14 September)
• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Wednesday, 14 September)
• Re: [whatwg/fetch] Treat data URLs as same-origin, except for workers (#387) (Wednesday, 14 September)
• Re: [w3c/webcomponents] [idea] Make use of `observedAttributes` optional (#565) (Wednesday, 14 September)
• Re: [whatwg/xhr] Kill the progress event when readyState is 4 (#72) (Monday, 12 September)
• Re: [whatwg/streams] getReader behaviour with empty mode (#517) (Friday, 9 September)
• Re: [whatwg/streams] Factor out WritableStreamDefaultWriterRelease (#513) (Friday, 9 September)
• Re: [heycam/webidl] Various named property stuff seems confused in the face of symbols (#175) (Friday, 9 September)
• Re: [heycam/webidl] Convert idl- prefixed anchors to Bikeshed notation. (#170) (Friday, 9 September)
• Re: [heycam/webidl] Various "terms defined by this specification" are miscapitalized (#172) (Friday, 9 September)
• Re: [heycam/webidl] Change the named property visibility algorithm so that existing own props always make corresponding named props invisible. (#174) (Friday, 9 September)
• Re: [heycam/webidl] Change the named property visibility algorithm so that existing own props always make corresponding named props invisible. (#174) (Friday, 9 September)
• Re: [heycam/webidl] Change the named property visibility algorithm so that existing own props always make corresponding named props invisible. (#174) (Friday, 9 September)
• Re: [heycam/webidl] Contributing to webidl just got a lot harder (#171) (Friday, 9 September)
• Re: [heycam/webidl] Contributing to webidl just got a lot harder (#171) (Friday, 9 September)
• [heycam/webidl] Various "terms defined by this specification" are miscapitalized (#172) (Friday, 9 September)
• Re: [heycam/webidl] Contributing to webidl just got a lot harder (#171) (Friday, 9 September)
• Re: [w3c/webcomponents] CustomElements: upgrade runs connectedCallback on an element with a throwing constructor (#563) (Thursday, 8 September)
• Re: [heycam/webidl] Consolidate issue tracking links in the header under "Feedback" (#169) (Thursday, 8 September)
• Re: [heycam/webidl] Consolidate issue tracking links in the header under "Feedback" (#169) (Thursday, 8 September)
• [heycam/webidl] Consolidate issue tracking links in the header under "Feedback" (#169) (Thursday, 8 September)
• [heycam/webidl] "descriptor" CSS class collides with CSS styling (#168) (Thursday, 8 September)
• [heycam/webidl] Move conventions and conformance to appendices (#167) (Thursday, 8 September)
• [heycam/webidl] Remove the "Changes" section (#166) (Thursday, 8 September)
• [heycam/webidl] Cleanup trailing whitespace (#165) (Thursday, 8 September)
• Re: [heycam/webidl] Update method creation for operations (#155) (Thursday, 8 September)
• [heycam/webidl] The spec's wording for where to place operations is broken and confusing (#164) (Thursday, 8 September)
• Re: [w3c/webcomponents] CustomElements: upgrade runs connectedCallback on an element with a throwing constructor (#563) (Thursday, 8 September)
• Re: [w3c/webcomponents] missing guidance on implementing an 'refresh' option. (#562) (Thursday, 8 September)
• Re: [w3c/webcomponents] missing guidance on implementing an 'refresh' option. (#562) (Thursday, 8 September)
• Re: [whatwg/streams] First draft at a pipeTo "algorithm" (#512) (Wednesday, 7 September)
• Re: [whatwg/streams] First draft at a pipeTo "algorithm" (#512) (Wednesday, 7 September)
• Re: [whatwg/streams] First draft at a pipeTo "algorithm" (#512) (Wednesday, 7 September)
• Re: [heycam/webidl] Update to latest Bikeshed (#160) (Wednesday, 7 September)
• Re: [whatwg/streams] First draft at a pipeTo "algorithm" (#512) (Wednesday, 7 September)
• Re: [whatwg/streams] getReader behaviour with empty mode (#517) (Wednesday, 7 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Tuesday, 6 September)
• Re: [w3c/webcomponents] A custom element should be marked as "failed" if a constructor returns a wrong object (#561) (Tuesday, 6 September)
• Re: [whatwg/streams] Add a proof of concept of optimized pipe (#511) (Tuesday, 6 September)
• Re: [whatwg/streams] Add a proof of concept of optimized pipe (#511) (Tuesday, 6 September)
• Re: [w3c/ServiceWorker] Parse URLs relative to the relevant settings object, not entry (#963) (Tuesday, 6 September)
• Re: [heycam/webidl] Update method creation for operations (#155) (Tuesday, 6 September)
• Re: [w3c/webcomponents] missing guidance on implementing an 'refresh' option. (#562) (Tuesday, 6 September)
• Re: [w3c/ServiceWorker] Parse URLs relative to the relevant settings object, not entry (#963) (Tuesday, 6 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Monday, 5 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Monday, 5 September)
• Re: [whatwg/xhr] Wrong state after abort() (#88) (Saturday, 3 September)
• Re: [whatwg/streams] Question: what is the difference of pipeThrough and pipeTo? (#515) (Friday, 2 September)
• Re: [whatwg/streams] Question: what is the difference of pipeThrough and pipeTo? (#515) (Friday, 2 September)
• Re: [whatwg/streams] Question: what is the difference of pipeThrough and pipeTo? (#515) (Friday, 2 September)
• Re: [whatwg/streams] Question: what is the difference of pipeThrough and pipeTo? (#515) (Friday, 2 September)
• Re: [whatwg/dom] Define how script-created click events are special during dispatch (#325) (Friday, 2 September)
• Re: [w3c/webcomponents] [Shadow]: rename <content> to <slot> (bugzilla: 28561) (#92) (Friday, 2 September)
• Re: [whatwg/streams] lint glob should exclude Emacs backup files (#514) (Thursday, 1 September)
• Re: [whatwg/streams] Factor out WritableStreamDefaultWriterRelease (#513) (Thursday, 1 September)
• Re: [w3c/webcomponents] HTML element constructors need to Get(newTarget, "Prototype") (#560) (Thursday, 1 September)

Dominic Cooney

• Re: [w3c/webcomponents] [Custom]: Callback for cloneNode/importNode (bugzilla: 24570) (#176) (Thursday, 22 September)
• Re: [w3c/webcomponents] [Custom]: Callback for cloneNode/importNode (bugzilla: 24570) (#176) (Thursday, 22 September)
• Re: [w3c/webcomponents] [Custom]: Callback for cloneNode/importNode (bugzilla: 24570) (#176) (Thursday, 22 September)
• Re: [w3c/webcomponents] [Custom]: Callback for cloneNode/importNode (bugzilla: 24570) (#176) (Thursday, 22 September)
• Re: [w3c/webcomponents] [Custom]: Callback for cloneNode/importNode (bugzilla: 24570) (#176) (Thursday, 22 September)
• [w3c/WebPlatformWG] TPAC 2016/Monday proposed agenda items (#68) (Monday, 12 September)
• Re: [w3c/webcomponents] CustomElements: upgrade runs connectedCallback on an element with a throwing constructor (#563) (Thursday, 8 September)
• Re: [heycam/webidl] Add [[PlatformBrand]] internal slot to all platform objects (#97) (Thursday, 1 September)
• Re: [w3c/webcomponents] HTML element constructors need to Get(newTarget, "Prototype") (#560) (Thursday, 1 September)

Dominique Hazael-Massieux

• Re: [w3ctag/url] Mark spec as obsolete (#6) (Friday, 30 September)
• Re: [w3ctag/url] Mark spec as obsolete (#6) (Tuesday, 27 September)
• [w3ctag/url] Mark spec as obsolete (#6) (Monday, 26 September)

Dr. Ken Lunde

• Re: [whatwg/encoding] Remove the last 14 characters PUA of GB18030-2005 (#27) (Tuesday, 6 September)

Duan Yao

• Re: [whatwg/fullscreen] Allow fullscreen on initial load of a page (#36) (Tuesday, 20 September)
• Re: [whatwg/fullscreen] Allow fullscreen on initial load of a page (#36) (Monday, 19 September)
• Re: [whatwg/fullscreen] Allow fullscreen on initial load of a page (#36) (Monday, 19 September)
• Re: [whatwg/fullscreen] Allow fullscreen on initial load of a page (#36) (Thursday, 15 September)

EduardoRFS

• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 10 September)

Eero Häkkinen

• Re: [whatwg/fetch] Clarification of Body package data algorithm with bytes, FormData and multipart/form-data MIME type (#392) (Thursday, 29 September)
• [whatwg/fetch] Clarification of Body package data algorithm with bytes, FormData and multipart/form-data MIME type (#392) (Thursday, 29 September)

Florian Bösch

• Re: [w3c/gamepad] Should fire events instead of using passive model (#4) (Monday, 19 September)

Gary Kacmarcik

• Re: [whatwg/dom] Define how script-created click events are special during dispatch (#325) (Thursday, 15 September)

gked

• [w3c/WebPlatformWG] Update 16-09-22TPAC-3.md (#76) (Wednesday, 21 September)
• [w3c/WebPlatformWG] Update 16-09-22TPAC-3.md (#70) (Tuesday, 13 September)

Haoqun Jiang

• Re: [w3c/webcomponents] Is <slot> a replaced element or not? (#564) (Tuesday, 13 September)
• [w3c/webcomponents] Is <slot> a replaced element or not? (#564) (Monday, 12 September)

Harald Alvestrand

• Re: [w3ctag/spec-reviews] Disable Local Playback During Audio Sharing (#137) (Tuesday, 27 September)
• Re: [w3c/permissions] refactor(media devices): use "allowed to use" (#122) (Tuesday, 13 September)
• Re: [w3c/permissions] Drop .request() (#83) (Friday, 2 September)
• Re: [w3c/permissions] Drop .request() (#83) (Friday, 2 September)
• Re: [w3c/permissions] Drop .request() (#83) (Friday, 2 September)
• Re: [w3c/permissions] Drop .request() (#83) (Thursday, 1 September)

Hayato Ito

• Re: [w3c/webcomponents] Upstream Shadow DOM spec to DOM/HTML Standard (#377) (Friday, 30 September)
• Re: [w3c/webcomponents] The get-the-parent algorithm shouldn't return null until we reach the root of the current tree (#577) (Friday, 30 September)
• Re: [w3c/webcomponents] slotchange event should not bubble (#571) (Thursday, 22 September)
• Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78) (Wednesday, 21 September)
• Re: [w3c/webcomponents] slotchange event should not bubble (#571) (Wednesday, 21 September)
• Re: [w3c/webcomponents] slotchange event should not bubble (#571) (Wednesday, 21 September)
• Re: [w3c/webcomponents] slotchange event should not bubble (#571) (Wednesday, 21 September)
• Re: [w3c/webcomponents] slotchange event should not bubble (#571) (Tuesday, 20 September)
• Re: [w3c/webcomponents] slotchange event should not bubble (#571) (Tuesday, 20 September)
• Re: [w3c/webcomponents] slotchange event should not bubble (#571) (Tuesday, 20 September)
• Re: [w3c/webcomponents] slotchange event should not bubble (#571) (Tuesday, 20 September)
• Re: [whatwg/dom] Make Element's slot attributes Unscopable (#329) (Thursday, 15 September)
• [whatwg/dom] Make Element's slot attributes Unscopable (#329) (Thursday, 15 September)
• [whatwg/dom] Make Element's slot attributes Unscopable (#328) (Thursday, 15 September)
• Re: [w3c/webcomponents] Is <slot> a replaced element or not? (#564) (Wednesday, 14 September)
• Re: [whatwg/dom] Shadow: Make Event.composedPath() use closed-shadow-hidden when currentTarget is window (#327) (Wednesday, 14 September)
• Re: [whatwg/dom] Shadow: Make Event.composedPath() use closed-shadow-hidden when currentTarget is window (#327) (Tuesday, 13 September)
• Re: [whatwg/dom] Shadow: Make Event.composedPath() use closed-shadow-hidden when currentTarget is window (#327) (Tuesday, 13 September)
• Re: [whatwg/dom] Shadow: Make Event.composedPath() use closed-shadow-hidden when currentTarget is window (#327) (Tuesday, 13 September)
• Re: [whatwg/dom] Shadow: Make Event.composedPath() use closed-shadow-hidden when currentTarget is window (#327) (Tuesday, 13 September)
• Re: [whatwg/dom] Shadow: Make Event.composedPath() use closed-shadow-hidden when currentTarget is window (#327) (Tuesday, 13 September)
• Re: [whatwg/dom] Shadow: Make Event.composedPath() use closed-shadow-hidden when currentTarget is window (#327) (Tuesday, 13 September)
• Re: [whatwg/dom] event.composedPath() should not return every items in path if event.currentTarget is window (#326) (Tuesday, 13 September)
• Re: [whatwg/dom] window.composedPath() should not return every items in path (#326) (Tuesday, 13 September)
• [whatwg/dom] Shadow: Make window.composedPath() use closed-shadow-hidden (#327) (Tuesday, 13 September)
• [whatwg/dom] window.composedPath() should not return every items in path (#326) (Tuesday, 13 September)
• Re: [w3c/webcomponents] Is <slot> a replaced element or not? (#564) (Tuesday, 13 September)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Friday, 2 September)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Friday, 2 September)
• Re: [w3c/touch-events] Add TouchEvent's retargeting steps (#73) (Friday, 2 September)
• Re: [w3c/touch-events] Add TouchEvent's retargeting steps (#73) (Friday, 2 September)
• Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300) (Friday, 2 September)
• Re: [w3c/webcomponents] Events whose composed flag should be true (#513) (Friday, 2 September)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Thursday, 1 September)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Thursday, 1 September)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Thursday, 1 September)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Thursday, 1 September)
• Re: [w3c/webcomponents] Fix #556, make focus navigation work when shadow host's tabindex is -1 (#557) (Thursday, 1 September)

Hugh Isaacs II

• [w3c/gamepad] Support gamepad speakers/headsets (#36) (Friday, 16 September)

Ilya Grigorik

• Re: [whatwg/fetch] (WIP) allow Request to outlive environment settings object (#388) (Friday, 30 September)
• Re: [whatwg/fetch] (WIP) allow Request to outlive environment settings object (#388) (Friday, 30 September)
• Re: [whatwg/fetch] (WIP) allow Request to outlive environment settings object (#388) (Friday, 30 September)
• Re: [whatwg/fetch] (WIP) allow Request to outlive environment settings object (#388) (Friday, 30 September)
• Re: [whatwg/fetch] (WIP) allow Request to outlive environment settings object (#388) (Friday, 30 September)
• Re: [whatwg/fetch] (WIP) allow Request to outlive environment settings object (#388) (Thursday, 29 September)
• Re: [whatwg/fetch] (WIP) allow Request to outlive environment settings object (#388) (Thursday, 29 September)
• Re: [whatwg/fetch] (WIP) allow Request to outlive environment settings object (#388) (Thursday, 29 September)
• Re: [whatwg/fetch] (WIP) allow Request to outlive environment settings object (#388) (Thursday, 22 September)
• Re: [whatwg/fetch] (WIP) allow Request to outlive environment settings object (#388) (Tuesday, 20 September)
• [whatwg/fetch] (WIP) allow Request to outlive environment settings object (#388) (Friday, 16 September)

Ingvar Stepanyan

• Re: [whatwg/fetch] Allow custom headers on no-cors requests (#380) (Friday, 2 September)
• Re: [whatwg/fetch] Allow custom headers on no-cors requests (#380) (Friday, 2 September)
• [whatwg/fetch] Allow custom headers on no-cors requests (#380) (Thursday, 1 September)

isonmad

• [whatwg/streams] ReadableStreamDefaultControllerEnqueue throws (#522) (Friday, 30 September)
• Re: [whatwg/streams] Update TransformStream API & misc. fixups (#519) (Friday, 23 September)
• [whatwg/streams] fix ReadableStream spec inconsistencies (#521) (Thursday, 22 September)
• Re: [whatwg/streams] Update TransformStream API & misc. fixups (#519) (Thursday, 22 September)
• Re: [whatwg/streams] Update TransformStream API & misc. fixups (#519) (Thursday, 22 September)
• Re: [whatwg/streams] Update TransformStream API & misc. fixups (#519) (Wednesday, 21 September)
• Re: [whatwg/streams] Update TransformStream API & misc. fixups (#519) (Tuesday, 20 September)
• Re: [whatwg/streams] Update TransformStream API & misc. fixups (#519) (Tuesday, 20 September)
• Re: [whatwg/streams] Update TransformStream API & misc. fixups (#519) (Tuesday, 20 September)
• Re: [whatwg/streams] piping issue (#509) (Saturday, 17 September)
• Re: [whatwg/streams] Update TransformStream API & misc. fixups (#519) (Saturday, 17 September)
• Re: [whatwg/streams] Update TransformStream API & misc. fixups (#519) (Saturday, 17 September)
• Re: [whatwg/streams] Update TransformStream API & misc. fixups (#519) (Saturday, 17 September)
• Re: [whatwg/streams] Update TransformStream API & misc. fixups (#519) (Saturday, 17 September)
• [whatwg/streams] Update TransformStream API & misc. fixups (#519) (Friday, 16 September)
• Re: [whatwg/streams] Pass controller to transformer methods in TransformStream (#518) (Friday, 16 September)

jabcreations

• [w3c/DOM-Parsing] HTML Entities & Serialization output (code versus rendered) (#20) (Monday, 19 September)

Jake Archibald

• Re: [w3c/ServiceWorker] Foreign fetch vs non-credentialed requests (#878) (Thursday, 29 September)
• Re: [w3c/ServiceWorker] Foreign fetch vs non-credentialed requests (#878) (Thursday, 29 September)
• Re: [w3c/ServiceWorker] registerForeignFetch({ origins, scope }) optional (#982) (Thursday, 29 September)
• Re: [w3c/ServiceWorker] registerForeignFetch({ origins, scope }) optional (#982) (Thursday, 29 September)
• Re: [w3c/ServiceWorker] registerForeignFetch({ origins, scope }) optional (#982) (Thursday, 29 September)
• Re: [whatwg/encoding] Add support for whatwg streams (9224c4c) (Monday, 26 September)
• Re: [w3c/ServiceWorker] Provide a simple synchronous k-v storage for ServiceWorker? (#981) (Sunday, 25 September)
• Re: [w3c/ServiceWorker] Provide a simple synchronous k-v storage for ServiceWorker? (#981) (Sunday, 25 September)
• Re: [w3c/ServiceWorker] Provide a simple synchronous k-v storage for ServiceWorker? (#981) (Sunday, 25 September)
• Re: [w3c/ServiceWorker] postMessage keeps service workers alive indefinitely (#980) (Thursday, 22 September)
• Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920) (Wednesday, 21 September)
• Re: [w3c/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756) (Tuesday, 20 September)
• Re: [w3c/ServiceWorker] spec behavior when ServiceWorkerContainer parent client is dead (#777) (Tuesday, 20 September)
• Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920) (Tuesday, 20 September)
• Re: [w3c/ServiceWorker] Add option to ignore case for cache querying (#956) (Tuesday, 20 September)
• Re: [w3c/ServiceWorker] Add option to ignore case for cache querying (#956) (Tuesday, 20 September)
• Re: [w3c/ServiceWorker] Create F2F agenda - 20 September 2016 (#974) (Tuesday, 20 September)
• Re: [w3c/ServiceWorker] Receivers of ranged responses must ensure all ranges come from the same underlying resource (#703) (Tuesday, 20 September)
• Re: [w3c/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Tuesday, 20 September)
• Re: [w3c/ServiceWorker] spec exactly how to order non-window Client objects (#887) (Tuesday, 20 September)
• Re: [w3c/ServiceWorker] Inconsistencies due to when clients are created (#870) (Tuesday, 20 September)
• Re: [w3c/ServiceWorker] should FetchEvent.request.cache reflect non-fetch browser cache controls? (#875) (Tuesday, 20 September)
• Re: [w3c/ServiceWorker] Drop isReload (#873) (Tuesday, 20 September)
• Re: [w3c/manifest] Integration with service workers (#161) (Friday, 16 September)
• Re: [w3c/ServiceWorker] Allow Caching of POST requests (#977) (Friday, 16 September)
• Re: [w3c/manifest] Integration with service workers (#161) (Friday, 16 September)
• Re: [w3c/manifest] Add optional Transition Screen member (#478) (Friday, 16 September)
• Re: [w3c/ServiceWorker] Allow Caching of POST requests (#977) (Wednesday, 14 September)
• Re: [w3c/ServiceWorker] Allow Caching of POST requests (#977) (Wednesday, 14 September)
• Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920) (Wednesday, 14 September)
• Re: [w3c/ServiceWorker] is it possible to stop browser to refetch scripts and reevaluate them if they haven't changed? (#978) (Wednesday, 14 September)
• Re: [w3c/ServiceWorker] is it possible to stop browser to refetch scripts and reevaluate them if they haven't changed? (#978) (Wednesday, 14 September)
• Re: [w3c/ServiceWorker] Make cache example easier to understand (#976) (Wednesday, 14 September)
• Re: [w3c/ServiceWorker] Serve subfolder to gh-pages (#966) (Tuesday, 13 September)
• Re: [w3c/ServiceWorker] Serve subfolder to gh-pages (#966) (Tuesday, 13 September)
• Re: [w3c/manifest] Integration with service workers (#161) (Tuesday, 13 September)
• Re: [w3c/ServiceWorker] Serve subfolder to gh-pages (#966) (Tuesday, 13 September)
• Re: [w3c/ServiceWorker] Serve subfolder to gh-pages (#966) (Tuesday, 13 September)
• Re: [w3c/ServiceWorker] Serve subfolder to gh-pages (#966) (Tuesday, 13 September)
• Re: [w3c/ServiceWorker] Communicate with Native Apps (#960) (Tuesday, 13 September)
• Re: [w3c/ServiceWorker] Handle the quota exceeded error globally (#971) (Tuesday, 13 September)
• Re: [w3c/manifest] Integration with service workers (#161) (Tuesday, 13 September)
• Re: [w3c/manifest] Integration with service workers (#161) (Monday, 12 September)
• Re: [w3c/manifest] Integration with service workers (#161) (Monday, 12 September)
• Re: [w3c/manifest] Integration with service workers (#161) (Monday, 12 September)
• Re: [w3c/manifest] Integration with service workers (#161) (Monday, 12 September)
• Re: [w3c/manifest] Integration with service workers (#161) (Monday, 12 September)
• Re: [w3c/ServiceWorker] Using BroadcastChannel to wake up a service worker (#975) (Friday, 9 September)
• Re: [w3c/ServiceWorker] Reloading page causes one extra client on client list (#972) (Friday, 9 September)
• Re: [w3c/ServiceWorker] Reloading page causes one extra client on client list (#972) (Friday, 9 September)
• Re: [w3c/ServiceWorker] Using BroadcastChannel to wake up a service worker (#975) (Friday, 9 September)
• Re: [w3c/ServiceWorker] allow service worker produced resources to be marked as "cachable" (#962) (Friday, 9 September)
• Re: [w3c/ServiceWorker] Eliminating SW startup latency for common case (#920) (Friday, 9 September)
• Re: [w3c/ServiceWorker] Eliminating SW startup latency for common case (#920) (Friday, 9 September)
• Re: [w3c/ServiceWorker] Create F2F agenda - 20 September 2016 (#974) (Thursday, 8 September)
• [w3c/ServiceWorker] Create F2F agenda - 20 September 2016 (#974) (Thursday, 8 September)
• Re: [w3c/ServiceWorker] Eliminating SW startup latency for common case (#920) (Thursday, 8 September)
• Re: [w3c/ServiceWorker] Inconsistencies due to when clients are created (#870) (Thursday, 8 September)
• Re: [w3c/ServiceWorker] Inconsistencies due to when clients are created (#870) (Thursday, 8 September)
• Re: [w3c/ServiceWorker] Inconsistencies due to when clients are created (#870) (Thursday, 8 September)
• Re: [w3c/ServiceWorker] Inconsistencies due to when clients are created (#870) (Thursday, 8 September)
• Re: [w3c/ServiceWorker] Inconsistencies due to when clients are created (#870) (Thursday, 8 September)
• Re: [w3c/ServiceWorker] Inconsistencies due to when clients are created (#870) (Thursday, 8 September)
• Re: [w3c/ServiceWorker] Inconsistencies due to when clients are created (#870) (Thursday, 8 September)

James Craig

• Re: [w3c/webcomponents] Should ARIA 2.0 have a role corresponding to every HTML element? (#552) (Monday, 19 September)
• Re: [w3c/webcomponents] Should ARIA 2.0 have a role corresponding to every HTML element? (#552) (Monday, 19 September)

Jan Miksovsky

• Re: [w3c/webcomponents] [idea] Make use of `observedAttributes` optional (#565) (Wednesday, 14 September)
• Re: [w3c/webcomponents] [idea] Make use of `observedAttributes` optional (#565) (Wednesday, 14 September)

jan-ivar

• [w3c/permissions] Allow UA option to call getUserMedia in non-secure origin (#129) (Saturday, 17 September)
• [w3c/permissions] Incorrectly says "camera", "microphone" aren't allowed in non-secure contexts. (#128) (Friday, 16 September)
• Re: [w3c/permissions] fix(request): clarify how requests affect state (#127) (Friday, 9 September)
• Re: [w3c/permissions] Drop .request() (#83) (Friday, 2 September)
• Re: [w3c/permissions] Drop .request() (#83) (Friday, 2 September)
• Re: [w3c/permissions] Drop .request() (#83) (Thursday, 1 September)

jasan-s

• [w3c/ServiceWorker] is it possible to stop browser to refetch scripts and reevaluate them if they haven't changed? (#978) (Wednesday, 14 September)

Jeff Burtoft

• Re: [w3c/manifest] Allow for multiple scopes (#449) (Monday, 12 September)

Jeffrey Yasskin

• Re: [heycam/webidl] Specify open dictionaries. (#180) (Friday, 30 September)
• Re: [heycam/webidl] Specify open dictionaries. (#180) (Friday, 30 September)
• Re: [heycam/webidl] Specify open dictionaries. (#180) (Friday, 30 September)
• Re: [heycam/webidl] Specify open dictionaries. (#180) (Friday, 30 September)
• Re: [heycam/webidl] Specify open dictionaries. (#180) (Friday, 30 September)
• Re: [heycam/webidl] Specify open dictionaries. (#180) (Friday, 30 September)
• [heycam/webidl] Specify open dictionaries. (#180) (Friday, 30 September)
• [heycam/webidl] Add a forgotten closing parenthesis. (#179) (Thursday, 22 September)
• [heycam/webidl] ES [[Get]] now takes a Receiver (#178) (Thursday, 22 September)
• Re: [w3c/permissions] Passing base dictionary wont work. (#59) (Wednesday, 21 September)
• Re: [w3c/permissions] Pass objects instead of PermissionDescriptors to the Permissions interface. (#125) (Wednesday, 21 September)
• Re: [w3c/permissions] Allow UA option to call getUserMedia in non-secure origin (#129) (Saturday, 17 September)
• Re: [w3c/permissions] Incorrectly says "camera", "microphone" aren't allowed in non-secure contexts. (#128) (Saturday, 17 September)
• Re: [w3c/permissions] Incorrectly says "camera", "microphone" aren't allowed in non-secure contexts. (#128) (Friday, 16 September)
• Re: [w3c/permissions] Move to using Echidna (#24) (Tuesday, 13 September)
• Re: [w3c/permissions] Move to using Echidna (#24) (Tuesday, 13 September)
• Re: [w3c/permissions] Move to using Echidna (#24) (Tuesday, 13 September)
• Re: [w3c/permissions] Use HTML's new "allowed to use" algorithm (#121) (Tuesday, 13 September)
• Re: [w3c/permissions] refactor(media devices): use "allowed to use" (#122) (Tuesday, 13 September)
• Re: [w3c/permissions] Drop .request() (#83) (Tuesday, 13 September)
• Re: [w3c/permissions] Move to using Echidna (#24) (Monday, 12 September)
• Re: [w3c/permissions] Move to using Echidna (#24) (Monday, 12 September)
• Re: [w3c/permissions] fix(request): clarify how requests affect state (#127) (Friday, 9 September)
• Re: [w3c/permissions] fix(request): clarify how requests affect state (#127) (Friday, 9 September)
• [w3c/permissions] fix(request): clarify how requests affect state (#127) (Thursday, 8 September)
• Re: [w3c/permissions] refactor(media devices): use "allowed to use" (#122) (Thursday, 8 September)
• Re: [w3c/permissions] refactor(permission state): pass the settings object explicitly (#114) (Thursday, 8 September)
• Re: [w3c/permissions] refactor(permission state): pass the settings object explicitly (#114) (Thursday, 8 September)
• Re: [w3c/permissions] feat(state): delegate to features for constraints (#117) (Tuesday, 6 September)
• Re: [w3c/permissions] refactor(media devices): use "allowed to use" (#122) (Tuesday, 6 September)
• Re: [w3c/permissions] refactor(media devices): use "allowed to use" (#122) (Saturday, 3 September)
• Re: [w3c/permissions] feat(state): delegate to features for constraints (#117) (Friday, 2 September)
• Re: [w3c/permissions] Drop .request() (#83) (Friday, 2 September)
• Re: [w3c/permissions] Drop .request() (#83) (Friday, 2 September)
• Re: [w3c/permissions] Drop .request() (#83) (Thursday, 1 September)
• Re: [w3c/permissions] Drop .request() (#83) (Thursday, 1 September)
• Re: [w3c/permissions] Drop .request() (#83) (Thursday, 1 September)

Jimmy Karl Roland Wärting

• Re: [w3c/FileAPI] Streams is hot, FileReader.readAs____ is not (#40) (Tuesday, 27 September)
• Re: [w3c/FileAPI] Remove FileList (Migrate to | typedef FileList FrozenArray<File>; | (#19) (Saturday, 17 September)
• Re: [whatwg/fetch] Setting strategy to control ReadableStream's internal buffer (#257) (Friday, 9 September)
• Re: [w3c/FileAPI] Streams is hot, FileReader.readAs____ is not (#40) (Thursday, 8 September)
• Re: [whatwg/streams] Add URL.createObjectURL(stream) support (#480) (Sunday, 4 September)
• Re: [whatwg/streams] Question: what is the difference of pipeThrough and pipeTo? (#515) (Friday, 2 September)
• Re: [whatwg/streams] Question: what is the difference of pipeThrough and pipeTo? (#515) (Friday, 2 September)
• Re: [whatwg/streams] Question: what is the difference of pipeThrough and pipeTo? (#515) (Friday, 2 September)
• Re: [whatwg/streams] Question: what is the difference of pipeThrough and pipeTo? (#515) (Friday, 2 September)
• Re: [whatwg/streams] Question: what is the difference of pipeThrough and pipeTo? (#515) (Friday, 2 September)
• [whatwg/streams] Question: what is the difference of pipeThrough and pipeTo? (#515) (Friday, 2 September)
• Re: [w3c/permissions] Drop .request() (#83) (Friday, 2 September)

Joel Richard

• Re: [w3c/webcomponents] [Shadow] Slotting indirect children (#574) (Wednesday, 28 September)
• Re: [w3c/webcomponents] [Shadow] Slotting indirect children (#574) (Wednesday, 28 September)
• Re: [w3c/webcomponents] [Shadow] Slotting indirect children (#574) (Friday, 23 September)
• [w3c/webcomponents] [Shadow] Slotting indirect children (#574) (Friday, 23 September)

Johannes Wilm

• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Tuesday, 27 September)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Tuesday, 27 September)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Tuesday, 27 September)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Tuesday, 27 September)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Tuesday, 27 September)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Tuesday, 27 September)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Monday, 26 September)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Monday, 26 September)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Monday, 26 September)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Monday, 26 September)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Monday, 26 September)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Monday, 26 September)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Saturday, 24 September)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Saturday, 24 September)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Saturday, 24 September)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Saturday, 24 September)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Saturday, 24 September)
• [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Saturday, 24 September)
• Re: [w3c/editing] Feedback on beforeinput (spec and the current implementation in Chrome Canary) (#149) (Wednesday, 21 September)
• [w3c/WebPlatformWG] spell fix (#73) (Friday, 16 September)
• Re: [w3c/WebPlatformWG] spell fix (#73) (Friday, 16 September)
• Re: [w3c/WebPlatformWG] stylistic changes (#72) (Wednesday, 14 September)
• [w3c/WebPlatformWG] stylistic changes (#72) (Wednesday, 14 September)
• Re: [w3c/WebPlatformWG] added agenda proposal (#71) (Wednesday, 14 September)
• [w3c/WebPlatformWG] added agenda proposal (#71) (Wednesday, 14 September)
• Re: [w3c/editing] Change default paragraph separator from <p> to <div> (#146) (Thursday, 1 September)
• Re: [w3c/editing] Change default paragraph separator from <p> to <div> (#146) (Thursday, 1 September)

John Wilander

• Re: [whatwg/fetch] Listing headers safe only for certain values is a bad idea (#313) (Friday, 9 September)
• Re: [whatwg/fetch] Listing headers safe only for certain values is a bad idea (#313) (Wednesday, 7 September)
• Re: [whatwg/fetch] CORS-safelisted request headers should be restricted according to RFC 7231 (#382) (Wednesday, 7 September)
• [whatwg/fetch] CORS-safelisted request headers should be restricted according to RFC 7231 (#382) (Tuesday, 6 September)

Jonas Sicking

• Re: [whatwg/fetch] Listing headers safe only for certain values is a bad idea (#313) (Friday, 9 September)
• Re: [whatwg/fetch] Listing headers safe only for certain values is a bad idea (#313) (Friday, 9 September)
• Re: [whatwg/fetch] Listing headers safe only for certain values is a bad idea (#313) (Thursday, 8 September)

Joseph Orbegoso Pea

• Re: [w3c/webcomponents] [Shadow] Slotting indirect children (#574) (Wednesday, 28 September)
• Re: [w3c/webcomponents] [Shadow] Slotting indirect children (#574) (Tuesday, 27 September)
• [w3c/webcomponents] [Idea] Distant ShadowDOM. (#576) (Tuesday, 27 September)
• Re: [w3c/webcomponents] [idea] Make use of `observedAttributes` optional (#565) (Wednesday, 21 September)
• Re: [w3c/webcomponents] [idea] Make use of `observedAttributes` optional (#565) (Wednesday, 21 September)
• Re: [w3c/webcomponents] [idea] Make use of `observedAttributes` optional (#565) (Wednesday, 21 September)
• Re: [w3c/webcomponents] [idea] Make use of `observedAttributes` optional (#565) (Wednesday, 21 September)
• Re: [w3c/webcomponents] Better custom event support for custom elements would be great (#546) (Sunday, 18 September)
• Re: [w3c/webcomponents] Better custom event support for custom elements would be great (#546) (Saturday, 17 September)
• Re: [w3c/webcomponents] Better custom event support for custom elements would be great (#546) (Saturday, 17 September)
• Re: [w3c/webcomponents] [idea] Make use of `observedAttributes` optional (#565) (Wednesday, 14 September)
• [w3c/webcomponents] [idea] Static observedAttributes property being optional. (#565) (Tuesday, 13 September)
• Re: [w3c/webcomponents] Better custom event support for custom elements would be great (#546) (Tuesday, 13 September)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 10 September)
• Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550) (Thursday, 1 September)

Josh Triplett

• Re: [w3c/ServiceWorker] Foreign fetch vs non-credentialed requests (#878) (Thursday, 29 September)

Joshua Bell

• Re: [w3c/IndexedDB] Introduce a more general query mechanism beyond keys/ranges (#45) (Friday, 30 September)
• Re: [w3c/IndexedDB] IDBEnvironment IDL is not valid (#94) (Thursday, 29 September)
• Re: [w3c/IndexedDB] IDBEnvironment IDL is not valid (#94) (Thursday, 29 September)
• Re: [w3c/IndexedDB] Remove IDBEnvironment in favor of partial interface (#95) (Thursday, 29 September)
• Re: [w3c/IndexedDB] Support full text indexes (#44) (Wednesday, 28 September)
• Re: [w3c/IndexedDB] Allow expressions in addition to keyPaths when creating indexes (#33) (Wednesday, 28 September)
• Re: [w3c/IndexedDB] IDBEnvironment IDL is not valid (#94) (Wednesday, 28 September)
• [w3c/IndexedDB] Remove IDBEnvironment in favor of partial interface (#95) (Wednesday, 28 September)
• Re: [whatwg/encoding] Add Streams support (#72) (Tuesday, 27 September)
• Re: [w3c/FileAPI] Streams is hot, FileReader.readAs____ is not (#40) (Tuesday, 27 September)
• Re: [w3c/FileAPI] Streams is hot, FileReader.readAs____ is not (#40) (Monday, 26 September)
• Re: [w3c/IndexedDB] IndexedDB refresh (#93) (Monday, 26 September)
• Re: [w3c/IndexedDB] IndexedDB refresh (#93) (Monday, 26 September)
• Re: [w3c/IndexedDB] deleteDatabase error case should never happen (#74) (Friday, 23 September)
• Re: [w3c/IndexedDB] Validate exception ordering against implementations (#11) (Friday, 23 September)
• Re: [w3c/IndexedDB] Validate exception ordering against implementations (#11) (Friday, 23 September)
• Re: [w3c/IndexedDB] Gather developer feedback on new spec additions (#65) (Friday, 23 September)
• Re: [w3c/IndexedDB] Async LocalStorage (transactionless key-value API over IDB) (#91) (Thursday, 22 September)
• Re: [w3c/IndexedDB] Introduce a more general query mechanism beyond keys/ranges (#45) (Thursday, 22 September)
• Re: [w3c/IndexedDB] Introduce a more general query mechanism beyond keys/ranges (#45) (Thursday, 22 September)
• Re: [w3c/IndexedDB] Introduce a more general query mechanism beyond keys/ranges (#45) (Thursday, 22 September)
• Re: [whatwg/encoding] gb18030 encoding/decoding support (#57) (Friday, 16 September)
• Re: [w3c/IndexedDB] Specify interaction between transaction abort and index/object store renames (#89) (Thursday, 8 September)
• Re: [w3c/IndexedDB] Abort behavior for renames of newly created stores/indexes, for #89 (#90) (Thursday, 8 September)
• [w3c/IndexedDB] Abort behavior for renames of newly created stores/indexes, for #89 (#90) (Wednesday, 7 September)
• Re: [w3c/IndexedDB] Specify interaction between transaction abort and index/object store renames (#89) (Wednesday, 7 September)
• Re: [w3c/IndexedDB] Return number of records deleted (#32) (Tuesday, 6 September)
• [w3c/WebPlatformWG] Update Indexed DB, Directory Upload (etc) discussions (#66) (Tuesday, 6 September)
• Re: [w3c/IndexedDB] Error events from open/deleteDatabase requests - cancelable? bubbles? (#86) (Saturday, 3 September)
• Re: [w3c/IndexedDB] IDBDatabase createObjectStore() - check keypath syntax before name constraint (#88) (Thursday, 1 September)
• [w3c/IndexedDB] IDBDatabase createObjectStore() - check keypath syntax before name constraint (#88) (Thursday, 1 September)

Jungkee Song

• Re: [w3c/ServiceWorker] postMessage keeps service workers alive indefinitely (#980) (Wednesday, 21 September)
• Re: [w3c/ServiceWorker] Does accessing ExtendableEvent's extend lifetime promises race? (#931) (Wednesday, 21 September)
• Re: [w3c/ServiceWorker] should FetchEvent.request.cache reflect non-fetch browser cache controls? (#875) (Tuesday, 20 September)
• Re: [w3c/ServiceWorker] ExtendableMessageEvent.source cannot be SameObject (#816) (Tuesday, 20 September)
• Re: [w3c/ServiceWorker] ExtendableMessageEvent.source cannot be SameObject (#816) (Tuesday, 20 September)
• Re: [w3c/ServiceWorker] Does accessing ExtendableEvent's extend lifetime promises race? (#931) (Tuesday, 20 September)
• Re: [w3c/ServiceWorker] html no longer defines "referrer source" (#834) (Monday, 19 September)
• Re: [w3c/ServiceWorker] should FetchEvent.request.cache reflect non-fetch browser cache controls? (#875) (Monday, 19 September)
• Re: [whatwg/fetch] Add request's reserved client (#383) (Wednesday, 14 September)
• Re: [whatwg/fetch] Add request's reserved client (#383) (Wednesday, 14 September)
• Re: [w3c/ServiceWorker] Serve subfolder to gh-pages (#966) (Tuesday, 13 September)
• Re: [whatwg/fetch] Add request's reserved client (#383) (Tuesday, 13 September)
• Re: [whatwg/fetch] Add request's reserved client (#383) (Tuesday, 13 September)
• Re: [whatwg/fetch] Add request's reserved client (#383) (Tuesday, 13 September)
• [whatwg/fetch] Add request's reserved client (#383) (Tuesday, 13 September)
• Re: [w3c/ServiceWorker] Inconsistencies due to when clients are created (#870) (Thursday, 8 September)
• Re: [w3c/ServiceWorker] Inconsistencies due to when clients are created (#870) (Thursday, 8 September)
• Re: [w3c/ServiceWorker] Inconsistencies due to when clients are created (#870) (Thursday, 8 September)
• Re: [w3c/ServiceWorker] Inconsistencies due to when clients are created (#870) (Thursday, 8 September)
• Re: [w3c/ServiceWorker] Inconsistencies due to when clients are created (#870) (Thursday, 8 September)
• Re: [w3c/ServiceWorker] Inconsistencies due to when clients are created (#870) (Thursday, 8 September)
• Re: [w3c/ServiceWorker] Inconsistencies due to when clients are created (#870) (Thursday, 8 September)
• Re: [w3c/ServiceWorker] Inconsistencies due to when clients are created (#870) (Thursday, 8 September)
• Re: [w3c/ServiceWorker] add redirect from /SW/ to /spec/s_w/ (#973) (Wednesday, 7 September)
• Re: [w3c/ServiceWorker] CacheStorage has an associated global object? (#964) (Wednesday, 7 September)
• Re: [w3c/ServiceWorker] CacheStorage has an associated global object? (#964) (Wednesday, 7 September)
• Re: [w3c/ServiceWorker] CacheStorage has an associated global object? (#964) (Wednesday, 7 September)
• Re: [w3c/ServiceWorker] CacheStorage has an associated global object? (#964) (Wednesday, 7 September)
• Re: [w3c/ServiceWorker] Reloading page causes one extra client on client list (#972) (Wednesday, 7 September)
• Re: [w3c/ServiceWorker] Parse URLs relative to the relevant settings object, not entry (#963) (Wednesday, 7 September)
• Re: [w3c/ServiceWorker] Parse URLs relative to the relevant settings object, not entry (#963) (Wednesday, 7 September)
• Re: [w3c/ServiceWorker] CacheStorage has an associated global object? (#964) (Tuesday, 6 September)
• Re: [w3c/ServiceWorker] Parse URLs relative to the relevant settings object, not entry (#963) (Tuesday, 6 September)
• Re: [w3c/ServiceWorker] Parse URLs relative to the relevant settings object, not entry (#963) (Tuesday, 6 September)
• Re: [w3c/ServiceWorker] Parse URLs relative to the relevant settings object, not entry (#963) (Tuesday, 6 September)
• Re: [w3c/ServiceWorker] Serve subfolder to gh-pages (#966) (Tuesday, 6 September)

jungshik

• Re: [whatwg/encoding] ISO 2022-jp encoding/decoding support (#60) (Thursday, 22 September)
• Re: [whatwg/encoding] EUK-kr encoding/decoding support (#62) (Sunday, 18 September)
• Re: [whatwg/encoding] EUK-kr encoding/decoding support (#62) (Friday, 16 September)
• Re: [whatwg/encoding] Add UTF-7 to replacement encoding list? (#68) (Friday, 16 September)
• Re: [whatwg/encoding] Add UTF-7 to replacement encoding list? (#68) (Friday, 16 September)
• Re: [whatwg/encoding] ISO 2022-jp encoding/decoding support (#60) (Friday, 16 September)
• Re: [whatwg/encoding] Add UTF-7 to replacement encoding list? (#68) (Friday, 16 September)
• Re: [whatwg/encoding] index-jis0208.txt should be JIS X 0208 and add another index file (#47) (Friday, 16 September)
• Re: [whatwg/encoding] gb18030 encoding/decoding support (#57) (Friday, 16 September)
• Re: [whatwg/encoding] GBK encoding/decoding support (#56) (Friday, 16 September)
• Re: [whatwg/encoding] Big5 encoding/decoding support (#58) (Friday, 16 September)
• Re: [whatwg/encoding] Shift-JIS encoding/decoding support (#61) (Friday, 16 September)
• Re: [whatwg/encoding] EUC-jp encoding/decoding support (#59) (Friday, 16 September)
• Re: [whatwg/encoding] EUK-kr encoding/decoding support (#62) (Friday, 16 September)
• Re: [whatwg/encoding] Remove the last 14 characters PUA of GB18030-2005 (#27) (Saturday, 10 September)

Kearwood Gilbert

• Re: [w3c/gamepad] Support Buffered Haptic Effects (#39) (Monday, 26 September)
• Re: [w3c/gamepad] Support Buffered Haptic Effects (#39) (Monday, 26 September)
• [w3c/gamepad] Support Buffered Haptic Effects (#39) (Monday, 26 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Monday, 19 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Friday, 16 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Thursday, 15 September)
• Re: [w3c/gamepad] Consider changing API to match SDL2's (#24) (Thursday, 15 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Thursday, 15 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Thursday, 15 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Thursday, 15 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Thursday, 15 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Thursday, 15 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Wednesday, 14 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Wednesday, 14 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Wednesday, 14 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Wednesday, 14 September)
• [w3c/gamepad] Support trackpad inputs (#34) (Wednesday, 14 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Tuesday, 13 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Tuesday, 13 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Tuesday, 13 September)

Keith Yeung

• [whatwg/fetch] Can an internal response be another filtered response? (#386) (Wednesday, 14 September)

Kenneth Rohde Christiansen

• Re: [w3c/manifest] Integration with service workers (#161) (Friday, 16 September)
• Re: [w3c/manifest] Support a way to update explicitly (#446) (Thursday, 15 September)
• Re: [w3c/manifest] Add optional Transition Screen member (#478) (Thursday, 15 September)
• Re: [w3c/manifest] [Appendix] Add crawl opt-out (closes #498) (#499) (Wednesday, 14 September)
• Re: [w3c/manifest] Integration with service workers (#161) (Tuesday, 13 September)
• Re: [w3c/manifest] Allow for multiple scopes (#449) (Monday, 12 September)
• Re: [w3c/manifest] Allow for multiple scopes (#449) (Monday, 12 September)
• Re: [w3c/manifest] fix: address @kenchris' feedback (dddeb97) (Monday, 12 September)
• Re: [w3c/manifest] Add optional Transition Screen member (#478) (Wednesday, 7 September)

Kiril Seksenov

• Re: [w3c/manifest] Add optional Transition Screen member (#478) (Wednesday, 14 September)
• Re: [w3c/manifest] Add optional Transition Screen member (#478) (Wednesday, 7 September)

Koji Ishii

• Re: [w3c/webcomponents] CustomElements: upgrade runs connectedCallback on an element with a throwing constructor (#563) (Wednesday, 7 September)
• Re: [w3c/webcomponents] A custom element should be marked as "failed" if a constructor returns a wrong object (#561) (Monday, 5 September)

Kris Borchers

• [w3c/WebPlatformWG] Add Kris Borchers to TPAC meetings (#65) (Monday, 5 September)

Lewis Phạm

• Re: [w3c/ServiceWorker] Handle the quota exceeded error globally (#971) (Tuesday, 13 September)
• Re: [w3c/ServiceWorker] Reloading page causes one extra client on client list (#972) (Wednesday, 7 September)
• Re: [w3c/ServiceWorker] Reloading page causes one extra client on client list (#972) (Tuesday, 6 September)
• [w3c/ServiceWorker] Reloading page causes one extra client on client list (#972) (Monday, 5 September)
• [w3c/ServiceWorker] Handle the quota exceeded error globally (#971) (Thursday, 1 September)

Lukasz Olejnik

• Re: [w3ctag/spec-reviews] Ambient Light Sensor API (#115) (Friday, 2 September)

Luke Childs

• [w3c/ServiceWorker] Make cache example easier to understand (#976) (Friday, 9 September)

Léonie Watson

• Re: [w3c/WebPlatformWG] Different ways to run a CFC? (#38) (Thursday, 29 September)
• [w3c/WebPlatformWG] CFC: Collect CFC responses on Github (#80) (Thursday, 29 September)
• Re: [w3c/WebPlatformWG] Add alex tpac (#79) (Thursday, 22 September)
• Re: [w3c/WebPlatformWG] Added cwilso. (#78) (Thursday, 22 September)
• Re: [w3c/WebPlatformWG] Add Tomek Wytrębowicz to session attendees (#69) (Monday, 12 September)
• Re: [w3c/WebPlatformWG] TPAC 2016/Monday proposed agenda items (#68) (Monday, 12 September)
• Re: [w3c/WebPlatformWG] TPAC 2016/Monday proposed agenda items (#68) (Monday, 12 September)
• Re: [w3c/WebPlatformWG] added my name to "hope to attend" list (#67) (Monday, 12 September)
• Re: [w3c/ServiceWorker] Create F2F agenda - 20 September 2016 (#974) (Thursday, 8 September)
• Re: [w3c/WebPlatformWG] Update Indexed DB, Directory Upload (etc) discussions (#66) (Tuesday, 6 September)
• Re: [w3c/WebPlatformWG] Add Kris Borchers to TPAC meetings (#65) (Tuesday, 6 September)

Marc G.

• Re: [whatwg/streams] create a document from a stream (#520) (Tuesday, 20 September)
• Re: [whatwg/streams] create a document from a stream (#520) (Tuesday, 20 September)
• Re: [whatwg/streams] create a document from a stream (#520) (Tuesday, 20 September)
• [whatwg/streams] create a document from a stream (#520) (Tuesday, 20 September)

Marcos Cáceres

• Re: [whatwg/storage] Use more generic example to demonstrate estimate() (#37) (Friday, 30 September)
• Re: [whatwg/storage] Use more generic example to demonstrate estimate() (#37) (Thursday, 29 September)
• Re: [w3ctag/spec-reviews] A spec style/structure checklist? (#136) (Wednesday, 28 September)
• Re: [w3ctag/spec-reviews] A spec style/structure checklist? (#136) (Tuesday, 27 September)
• Re: [w3ctag/spec-reviews] A spec style/structure checklist? (#136) (Monday, 26 September)
• Re: [w3c/manifest] Add optional Transition Screen member (#478) (Monday, 26 September)
• Re: [w3c/manifest] (Re-)Add Optional Splash Screens (#501) (Monday, 26 September)
• Re: [w3c/manifest] Add optional Transition Screen member (#478) (Thursday, 22 September)
• Re: [w3ctag/spec-reviews] A spec style/structure checklist? (#136) (Thursday, 22 September)
• Re: [w3c/manifest] Allow for multiple scopes (#449) (Wednesday, 21 September)
• Re: [w3c/ServiceWorker] Define procedure to convert options object of `sw.register()` to `Link` header (#979) (Wednesday, 21 September)
• Re: [w3c/ServiceWorker] Define procedure to convert options object of `sw.register()` to `Link` header (#979) (Wednesday, 21 September)
• Re: [w3c/manifest] Integration with service workers (#161) (Wednesday, 21 September)
• Re: [w3c/manifest] Integration with service workers (#161) (Tuesday, 20 September)
• Re: [w3c/manifest] Integration with service workers (#161) (Tuesday, 20 September)
• Re: [w3c/manifest] Integration with service workers (#161) (Friday, 16 September)
• Re: [w3c/manifest] Integration with service workers (#161) (Friday, 16 September)
• Re: [w3c/manifest] Add optional Transition Screen member (#478) (Friday, 16 September)
• Re: [w3c/manifest] Support a way to update explicitly (#446) (Friday, 16 September)
• Re: [w3c/manifest] Support a way to update explicitly (#446) (Friday, 16 September)
• Re: [w3c/manifest] Add optional Transition Screen member (#478) (Thursday, 15 September)
• Re: [w3c/manifest] [Appendix] Add crawl opt-out (closes #498) (#499) (Wednesday, 14 September)
• Re: [w3c/ServiceWorker] Communicate with Native Apps (#960) (Wednesday, 14 September)
• Re: [w3c/manifest] Integration with service workers (#161) (Wednesday, 14 September)
• Re: [w3c/manifest] Integration with service workers (#161) (Tuesday, 13 September)
• Re: [w3c/manifest] Integration with service workers (#161) (Tuesday, 13 September)
• Re: [w3c/permissions] refactor(media devices): use "allowed to use" (#122) (Tuesday, 13 September)
• Re: [w3c/manifest] Allow unique start_url for subdomains (#470) (Tuesday, 13 September)
• Re: [w3c/permissions] Move to using Echidna (#24) (Tuesday, 13 September)
• Re: [w3c/permissions] Consider removing Permissions.revoke(). (#46) (Tuesday, 13 September)
• Re: [w3c/manifest] WIP: purpose (#493) (Monday, 12 September)
• Re: [w3c/manifest] Adding the webapp's badge to the manifest (#480) (Monday, 12 September)
• Re: [w3c/manifest] WIP: purpose (#493) (Monday, 12 September)
• Re: [w3c/manifest] Describe how developers can block web crawlers (#498) (Monday, 12 September)
• Re: [w3c/manifest] Describe how developers can block web crawlers (#498) (Monday, 12 September)
• Re: [w3c/manifest] WIP: purpose (#493) (Monday, 12 September)
• Re: [w3c/manifest] WIP: purpose (#493) (Monday, 12 September)
• Re: [w3c/permissions] Drop .request() (#83) (Monday, 12 September)
• Re: [w3c/manifest] Integration with service workers (#161) (Monday, 12 September)
• Re: [w3c/manifest] WIP: purpose (#493) (Monday, 12 September)
• Re: [w3c/manifest] Add optional Transition Screen member (#478) (Friday, 9 September)
• Re: [whatwg/xhr] Please fix this issue (#89) (Friday, 9 September)
• Re: [heycam/webidl] Move conventions and conformance to appendices (#167) (Friday, 9 September)
• Re: [heycam/webidl] Move conventions and conformance to appendices (#167) (Friday, 9 September)
• Re: [heycam/webidl] Move conventions and conformance to appendices (#167) (Friday, 9 September)
• Re: [w3c/manifest] Describe how developers can block web crawlers (#498) (Friday, 9 September)
• Re: [heycam/webidl] Remove mention of OMG IDL (#144) (Thursday, 8 September)
• Re: [w3c/manifest] deprecate gh-pages in favor of echidna (#494) (Wednesday, 7 September)
• Re: [w3c/permissions] feat(state): delegate to features for constraints (#117) (Monday, 5 September)
• Re: [w3c/ServiceWorker] allow service worker produced resources to be marked as "cachable" (#962) (Monday, 5 September)
• Re: [w3c/manifest] WIP: purpose (#493) (Thursday, 1 September)
• [w3c/permissions] Make sure spec reflects issues (#126) (Thursday, 1 September)
• Re: [w3c/permissions] Move to using Echidna (#24) (Thursday, 1 September)
• Re: [w3c/permissions] feat(travis): autopublish with echidna (closes #24) (#99) (Thursday, 1 September)
• Re: [w3c/manifest] Ability to claim web app (#476) (Thursday, 1 September)
• Re: [w3c/manifest] doc(extensibility): e.g., of site verificaton (closes #476) (#497) (Thursday, 1 September)
• Re: [w3c/manifest] doc(extensibility): e.g., of site verificaton (closes #476) (#497) (Thursday, 1 September)
• Re: [w3c/manifest] Standalone description not accurate (#495) (Thursday, 1 September)
• Re: [w3c/manifest] fix(display modes): refine standalone (closes #495) (#496) (Thursday, 1 September)
• Re: [w3ctag/spec-reviews] Review Accessibility Object Model (#134) (Thursday, 1 September)

Marijn Kruisselbrink

• [w3c/ServiceWorker] Using BroadcastChannel to wake up a service worker (#975) (Thursday, 8 September)
• Re: [w3c/ServiceWorker] Create F2F agenda - 20 September 2016 (#974) (Thursday, 8 September)

Mark Nottingham

• Re: [w3ctag/spec-reviews] A spec style/structure checklist? (#136) (Wednesday, 21 September)
• Re: [whatwg/fetch] Prevent modifying headers on Responses (#24) (Wednesday, 7 September)
• Re: [whatwg/fetch] Preventing some CRLF header injection attacks (#375) (Wednesday, 7 September)

Martin Thomson

• Re: [w3c/permissions] fix(request): clarify how requests affect state (#127) (Friday, 9 September)
• Re: [w3c/permissions] Drop .request() (#83) (Friday, 9 September)
• Re: [w3c/permissions] Drop .request() (#83) (Thursday, 1 September)

Matt Falkenhagen

• Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920) (Monday, 26 September)
• Re: [w3c/ServiceWorker] postMessage keeps service workers alive indefinitely (#980) (Monday, 26 September)
• Re: [w3c/ServiceWorker] postMessage keeps service workers alive indefinitely (#980) (Wednesday, 21 September)
• [w3c/ServiceWorker] postMessage keeps service workers alive indefinitely (#980) (Wednesday, 21 September)
• Re: [whatwg/fetch] Allow "manual" redirect fetches with caveats (#66) (Friday, 16 September)
• Re: [w3c/ServiceWorker] Using BroadcastChannel to wake up a service worker (#975) (Friday, 9 September)

Matthew Phillips

• Re: [w3c/webcomponents] Better custom event support for custom elements would be great (#546) (Wednesday, 14 September)
• Re: [w3c/webcomponents] [idea] Make use of `observedAttributes` optional (#565) (Tuesday, 13 September)
• Re: [w3c/webcomponents] missing guidance on implementing an 'refresh' option. (#562) (Tuesday, 6 September)
• Re: [w3c/webcomponents] missing guidance on implementing an 'refresh' option. (#562) (Tuesday, 6 September)

Megan Lindsay

• Re: [w3ctag/spec-reviews] WebVR (#106) (Wednesday, 7 September)

micabe

• Re: [whatwg/fetch] Document usage for GET requests with URI parameters (#56) (Thursday, 29 September)

Michael Blix

• [w3c/gamepad] Add 'Actuator' (#38) (Tuesday, 20 September)

Michael[tm] Smith

• Re: [w3ctag/spec-reviews] A spec style/structure checklist? (#136) (Tuesday, 27 September)

Michiel Bijl

• Re: [w3c/XMLHttpRequest] Publish as a Note - abandoned work item? (#2) (Tuesday, 27 September)

Mike Taylor

• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Tuesday, 27 September)
• Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334) (Tuesday, 27 September)

Mike West

• Re: [whatwg/fetch] Treat data URLs as same-origin, except for workers (#387) (Thursday, 15 September)
• Re: [whatwg/fetch] Treat data URLs as same-origin, except for workers (#387) (Wednesday, 14 September)
• Re: [whatwg/xhr] Add a <dfn> for FormData's entry's type. (#63) (Thursday, 8 September)
• Re: [whatwg/xhr] Add a <dfn> for FormData's entry's type. (#63) (Thursday, 8 September)
• Re: [whatwg/fetch] Same-origin data-URL flag only for fetch and XHR? (#381) (Wednesday, 7 September)
• Re: [whatwg/fetch] Same-origin data-URL flag only for fetch and XHR? (#381) (Wednesday, 7 September)
• Re: [whatwg/fetch] Same-origin data-URL flag only for fetch and XHR? (#381) (Wednesday, 7 September)

Mingye Wang

• Re: [whatwg/encoding] Remove the last 14 characters PUA of GB18030-2005 (#27) (Tuesday, 6 September)
• Re: [whatwg/encoding] Remove the last 14 characters PUA of GB18030-2005 (#27) (Tuesday, 6 September)
• Re: [whatwg/encoding] Remove the last 14 characters PUA of GB18030-2005 (#27) (Tuesday, 6 September)
• Re: [whatwg/encoding] Remove the last 14 characters PUA of GB18030-2005 (#27) (Monday, 5 September)

Nathan

• Re: [w3c/webcomponents] [imports]: Respect the crossOrigin attribute (bugzilla: 25568) (#216) (Monday, 26 September)

Nathan Schloss

• Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920) (Wednesday, 14 September)
• Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920) (Wednesday, 14 September)
• Re: [w3c/ServiceWorker] Eliminating SW startup latency for common case (#920) (Thursday, 8 September)

Nitin Prabhakar

• Re: [w3c/webcomponents] [Shadow]: rename <content> to <slot> (bugzilla: 28561) (#92) (Friday, 2 September)
• Re: [w3c/webcomponents] [Shadow]: rename <content> to <slot> (bugzilla: 28561) (#92) (Friday, 2 September)

Nolan Lawson

• Re: [w3c/ServiceWorker] Using BroadcastChannel to wake up a service worker (#975) (Tuesday, 27 September)
• Re: [w3c/IndexedDB] deleteDatabase error case should never happen (#74) (Friday, 23 September)
• Re: [w3c/IndexedDB] Support N-dimensional queries on indexes (#40) (Thursday, 22 September)
• Re: [w3c/IndexedDB] Introduce a more general query mechanism beyond keys/ranges (#45) (Thursday, 22 September)
• Re: [w3c/IndexedDB] Support N-dimensional queries on indexes (#40) (Thursday, 22 September)
• Re: [w3c/IndexedDB] Async LocalStorage (transactionless key-value API over IDB) (#91) (Thursday, 22 September)
• [w3c/IndexedDB] "Join" queries on multiple object stores (#92) (Thursday, 22 September)
• [w3c/IndexedDB] Async LocalStorage (transactionless key-value API over IDB) (#91) (Thursday, 22 September)
• Re: [w3c/IndexedDB] Introduce a more general query mechanism beyond keys/ranges (#45) (Thursday, 22 September)
• Re: [w3c/IndexedDB] Support full text indexes (#44) (Thursday, 22 September)
• Re: [w3c/IndexedDB] Consider adding a completion event or callback to the IDBDatabase.close() operation (#72) (Thursday, 22 September)
• Re: [w3c/IndexedDB] boolean should be a valid key (#76) (Wednesday, 21 September)
• [w3c/WebPlatformWG] Add Nolan to attendees (#75) (Wednesday, 21 September)
• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Tuesday, 20 September)
• Re: [w3c/ServiceWorker] Allow Caching of POST requests (#977) (Tuesday, 20 September)
• Re: [w3c/ServiceWorker] Using BroadcastChannel to wake up a service worker (#975) (Tuesday, 20 September)
• Re: [w3c/manifest] Describe how developers can block web crawlers (#498) (Monday, 12 September)
• Re: [w3c/manifest] Describe how developers can block web crawlers (#498) (Monday, 12 September)
• Re: [w3c/manifest] Describe how developers can block web crawlers (#498) (Monday, 12 September)

patrick kettner

• Re: [w3c/manifest] Describe how developers can block web crawlers (#498) (Monday, 12 September)
• Re: [w3c/manifest] Describe how developers can block web crawlers (#498) (Monday, 12 September)
• Re: [w3c/manifest] Describe how developers can block web crawlers (#498) (Monday, 12 September)
• Re: [w3c/manifest] Describe how developers can block web crawlers (#498) (Monday, 12 September)
• Re: [w3c/manifest] Describe how developers can block web crawlers (#498) (Friday, 9 September)

Peter Müller

• [w3ctag/packaging-on-the-web] Nested packages (#33) (Thursday, 15 September)

Philip Jägenstedt

• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Friday, 30 September)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Friday, 30 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Friday, 30 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Friday, 30 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Friday, 30 September)
• Re: [whatwg/fullscreen] What should happen if an element is moved to another document right after requestFullscreen (#33) (Friday, 30 September)
• Re: [w3c/selection-api] Limit onselectionchange to Document until known to be needed elsewhere (#75) (Thursday, 29 September)
• Re: [w3c/selection-api] Limit onselectionchange to Document until known to be needed elsewhere (#75) (Thursday, 29 September)
• Re: [w3c/selection-api] Limit onselectionchange to Document until known to be needed elsewhere (#75) (Thursday, 29 September)
• Re: [w3c/selection-api] Limit onselectionchange to Document until known to be needed elsewhere (#75) (Thursday, 29 September)
• Re: [whatwg/fullscreen] What should happen if an element is moved to another document right after requestFullscreen (#33) (Thursday, 29 September)
• Re: [whatwg/fullscreen] Element moved into another document after requesting fullscreen should make the request fail (#59) (Thursday, 29 September)
• Re: [whatwg/fullscreen] Element moved into another document after requesting fullscreen should make the request fail (#59) (Thursday, 29 September)
• Re: [whatwg/fullscreen] Fullscreen request on invisible document should be denied (#58) (Thursday, 29 September)
• Re: [whatwg/dom] Clarify that new Document creates a document of type "html", not "xml" (#308) (Wednesday, 28 September)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Wednesday, 28 September)
• Re: [whatwg/dom] Clarify that new Document creates a document of type "html", not "xml" (#308) (Wednesday, 28 September)
• Re: [whatwg/dom] Clarify that new Document creates a document of type "html", not "xml" (#308) (Wednesday, 28 September)
• Re: [whatwg/dom] Figure out what to do with XMLDocument (#278) (Wednesday, 28 September)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Wednesday, 28 September)
• Re: [whatwg/fullscreen] Move the element type check out of the ready check (#57) (Tuesday, 27 September)
• Re: [whatwg/fullscreen] Move the element type check out of the ready check (#57) (Tuesday, 27 September)
• Re: [whatwg/fullscreen] Move the element type check out of the ready check (#57) (Tuesday, 27 September)
• [whatwg/fullscreen] Move the element type check out of the ready check (#57) (Tuesday, 27 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Monday, 26 September)
• Re: [heycam/webidl] Does a non-nullable and non-required dictionary member of interface type make sense? (#176) (Monday, 26 September)
• Re: [heycam/webidl] Does a non-nullable and non-required dictionary member of interface type make sense? (#176) (Friday, 23 September)
• Re: [heycam/webidl] Does a non-nullable and non-required dictionary member of interface type make sense? (#176) (Friday, 23 September)
• Re: [heycam/webidl] Does a non-nullable and non-required dictionary member of interface type make sense? (#176) (Friday, 23 September)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Thursday, 22 September)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Thursday, 22 September)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Thursday, 22 September)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Thursday, 22 September)
• Re: [whatwg/fullscreen] Should browser UI be able to activate fullscreen even if iframe is missing allowfullscreen (#56) (Wednesday, 21 September)
• Re: [heycam/webidl] Does a non-nullable and non-required dictionary member of interface type make sense? (#176) (Tuesday, 20 September)
• Re: [w3c/selection-api] Clarify the additions of this spec to GlobalEventHandlers (#54) (Tuesday, 20 September)
• Re: [whatwg/fullscreen] Should browser UI be able to activate fullscreen even if iframe is missing allowfullscreen (#56) (Tuesday, 20 September)
• [w3c/selection-api] Limit onselectionchange to Document until known to be needed elsewhere (#75) (Tuesday, 20 September)
• Re: [w3c/selection-api] Add a "Selection interface" section (#29) (Tuesday, 20 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Tuesday, 20 September)
• Re: [heycam/webidl] Does a non-nullable and non-required dictionary member of interface type make sense? (#176) (Tuesday, 20 September)
• Re: [heycam/webidl] Does a non-nullable and non-required dictionary member of interface type make sense? (#176) (Tuesday, 20 September)
• Re: [heycam/webidl] Does a non-nullable and non-required dictionary member of interface type make sense? (#176) (Tuesday, 20 September)
• Re: [heycam/webidl] Does a non-nullable and non-required dictionary member of interface type make sense? (#176) (Tuesday, 20 September)
• Re: [heycam/webidl] Does a non-nullable and non-required dictionary member of interface type make sense? (#176) (Tuesday, 20 September)
• [heycam/webidl] Does a non-nullable and non-required dictionary member of interface type make sense? (#176) (Monday, 19 September)
• Re: [whatwg/fullscreen] Allow fullscreen on initial load of a page (#36) (Monday, 19 September)
• Re: [w3c/touch-events] createTouch has all the params as required, should probably have them optional (#58) (Sunday, 18 September)
• Re: [whatwg/dom] Clarify that new Document creates a document of type "html", not "xml" (#308) (Sunday, 18 September)
• Re: [whatwg/dom] Clarify that new Document creates a document of type "html", not "xml" (#308) (Friday, 16 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Friday, 16 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Friday, 16 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Friday, 16 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Friday, 16 September)
• Re: [whatwg/fullscreen] To fullscreen/unfullscreen, do not take document as an argument (#55) (Friday, 16 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Thursday, 15 September)
• Re: [whatwg/fullscreen] Remove redundant recursive step of fullscreen element ready check (#52) (Thursday, 15 September)
• Re: [whatwg/fullscreen] Final recursive step of fullscreen element ready check is redundant (#50) (Thursday, 15 September)
• Re: [whatwg/fullscreen] Remove redundant recursive step of fullscreen element ready check (#52) (Thursday, 15 September)
• Re: [whatwg/fullscreen] Editorial: shorten the top layer add/remove IDs (#51) (Thursday, 15 September)
• Re: [whatwg/fullscreen] Editorial: shorten the top layer add/remove IDs (#51) (Thursday, 15 September)
• Re: [whatwg/fullscreen] Editorial: shorten the top layer add/remove IDs (#51) (Thursday, 15 September)
• Re: [whatwg/fullscreen] Editorial: shorten the top layer add/remove IDs (#51) (Thursday, 15 September)
• [w3c/gamepad] GamepadEvent constructor is missing the type argument (#35) (Thursday, 15 September)
• Re: [whatwg/fullscreen] Allow fullscreen on initial load of a page (#36) (Wednesday, 14 September)
• [whatwg/fullscreen] Remove redundant recursive step of fullscreen element ready check (#52) (Wednesday, 14 September)
• [whatwg/fullscreen] Editorial: shorten the top layer add/remove IDs (#51) (Wednesday, 14 September)
• Re: [whatwg/fullscreen] Convert to Bikeshed (#47) (Wednesday, 14 September)
• Re: [whatwg/fullscreen] Convert to Bikeshed (#49) (Wednesday, 14 September)
• Re: [whatwg/fullscreen] Convert to Bikeshed (#47) (Wednesday, 14 September)
• Re: [whatwg/fullscreen] Convert to Bikeshed (#49) (Wednesday, 14 September)
• Re: [whatwg/fullscreen] Convert to Bikeshed (#49) (Wednesday, 14 September)
• Re: [whatwg/fullscreen] Convert to Bikeshed (#49) (Wednesday, 14 September)
• Re: [whatwg/fullscreen] Convert to Bikeshed (#49) (Wednesday, 14 September)
• Re: [whatwg/fullscreen] Convert to Bikeshed (#49) (Wednesday, 14 September)
• Re: [whatwg/fullscreen] Convert to Bikeshed (#49) (Wednesday, 14 September)
• Re: [whatwg/fullscreen] Convert to Bikeshed (#49) (Wednesday, 14 September)
• Re: [whatwg/fullscreen] Convert to Bikeshed (#49) (Wednesday, 14 September)
• Re: [whatwg/fullscreen] Convert to Bikeshed (#49) (Wednesday, 14 September)
• [whatwg/fullscreen] Final recursive step of fullscreen element ready check is redundant (#50) (Tuesday, 13 September)
• Re: [whatwg/fullscreen] What should happen if an element is moved to another document right after requestFullscreen (#33) (Tuesday, 13 September)
• Re: [whatwg/fullscreen] Convert to Bikeshed (#49) (Tuesday, 13 September)
• Re: [whatwg/fullscreen] Convert to Bikeshed (#49) (Tuesday, 13 September)
• Re: [whatwg/fullscreen] Convert to Bikeshed (#49) (Tuesday, 13 September)
• Re: [whatwg/fullscreen] Convert to Bikeshed (#49) (Tuesday, 13 September)
• Re: [whatwg/fullscreen] Convert to Bikeshed (#49) (Tuesday, 13 September)
• Re: [whatwg/fullscreen] Convert to Bikeshed (#49) (Tuesday, 13 September)
• Re: [whatwg/fullscreen] Convert to Bikeshed (#49) (Tuesday, 13 September)
• [whatwg/fullscreen] Convert to Bikeshed (#49) (Tuesday, 13 September)
• Re: [whatwg/fullscreen] Prepare for conversion to Bikeshed (#48) (Tuesday, 13 September)
• Re: [whatwg/fullscreen] Prepare for conversion to Bikeshed (#48) (Tuesday, 13 September)
• [whatwg/fullscreen] Prepare for conversion to Bikeshed (#48) (Tuesday, 13 September)
• [whatwg/fullscreen] Convert to Bikeshed (#47) (Tuesday, 13 September)
• Re: [whatwg/dom] Clarify that new Document creates a document of type "html", not "xml" (#308) (Tuesday, 6 September)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Monday, 5 September)
• Re: [whatwg/dom] Clarify that new Document creates a document of type "html", not "xml" (#308) (Monday, 5 September)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Monday, 5 September)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Monday, 5 September)
• Re: [whatwg/dom] Define how script-created click events are special during dispatch (#325) (Monday, 5 September)
• Re: [w3c/permissions] refactor(media devices): use "allowed to use" (#122) (Monday, 5 September)
• [whatwg/dom] Define how script-created click events are special during dispatch (#325) (Friday, 2 September)
• Re: [whatwg/dom] Further Attr node fixes for compareDocumentPosition() (#312) (Friday, 2 September)
• Re: [whatwg/dom] CDATASection misses (#300) (Thursday, 1 September)
• Re: [whatwg/dom] Drop support for SVGZoomEvent in createEvent (#323) (Thursday, 1 September)
• [whatwg/dom] Drop support for SVGZoomEvent in createEvent (#323) (Thursday, 1 September)

Philippe Le Hegaret

• Re: [w3ctag/spec-reviews] A spec style/structure checklist? (#136) (Tuesday, 27 September)
• Re: [w3c/charter-html] HTML AAM should remain a joint deliverable (#133) (Thursday, 15 September)
• Re: [w3c/charter-html] HTML AAM should remain a joint deliverable (#133) (Thursday, 15 September)

PhistucK

• Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304) (Monday, 26 September)
• Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304) (Monday, 26 September)

Piotrek Koszuliński

• [w3c/editing] Feedback on beforeinput in Chrome Canary (#149) (Wednesday, 21 September)
• Re: [w3c/editing] When should UA synthesize heights of an element? (#70) (Monday, 5 September)
• Re: [w3c/editing] Change default paragraph separator from <p> to <div> (#146) (Monday, 5 September)
• Re: [w3c/editing] Change default paragraph separator from <p> to <div> (#146) (Thursday, 1 September)

Pulzar1989

• Re: [whatwg/xhr] What with dat code? He not work :( (#91) (Friday, 16 September)
• [whatwg/xhr] What with dat code? He not work :( (#91) (Friday, 16 September)

r12a

• Re: [whatwg/encoding] Please double-check the end of the EUDC range (#53) (Friday, 16 September)
• Re: [whatwg/encoding] EUK-kr encoding/decoding support (#62) (Friday, 16 September)
• Re: [whatwg/encoding] ISO 2022-jp encoding/decoding support (#60) (Friday, 16 September)
• Re: [whatwg/encoding] GBK encoding/decoding support (#56) (Thursday, 15 September)
• Re: [whatwg/encoding] gb18030 encoding/decoding support (#57) (Thursday, 15 September)
• Re: [whatwg/encoding] Big5 encoding/decoding support (#58) (Thursday, 15 September)
• Re: [whatwg/encoding] Big5 encoding/decoding support (#58) (Thursday, 15 September)
• Re: [whatwg/encoding] EUC-jp encoding/decoding support (#59) (Thursday, 15 September)
• Re: [whatwg/encoding] ISO 2022-jp encoding/decoding support (#60) (Thursday, 15 September)
• Re: [whatwg/encoding] Shift-JIS encoding/decoding support (#61) (Thursday, 15 September)
• Re: [whatwg/encoding] EUK-kr encoding/decoding support (#62) (Thursday, 15 September)

raymeskhoury

• Re: [w3c/permissions] refactor(media devices): use "allowed to use" (#122) (Tuesday, 6 September)

Raymond May Jr.

• Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304) (Monday, 26 September)
• Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304) (Monday, 26 September)

Rebeca Ruiz

• Re: [w3c/XMLHttpRequest] Publish as a Note - abandoned work item? (#2) (Tuesday, 27 September)

Rhys Evans

• Re: [whatwg/fetch] Prevent modifying headers on Responses (#24) (Wednesday, 7 September)
• Re: [whatwg/fetch] Prevent modifying headers on Responses (#24) (Tuesday, 6 September)

Richard Schwerdtfeger

• Re: [w3c/webcomponents] Should ARIA 2.0 have a role corresponding to every HTML element? (#552) (Wednesday, 7 September)

Rick Byers

• Re: [w3c/touch-events] Consider defaulting to use passive listener on window/document/document.body (#74) (Monday, 26 September)
• [w3c/uievents] Reduce scroll performance impact of `wheel` listeners (#109) (Monday, 26 September)
• Re: [whatwg/dom] High resolution timing for events (#23) (Friday, 23 September)
• [w3c/uievents] Consider integrating InputDeviceCapabilities (#108) (Friday, 23 September)
• Re: [whatwg/dom] Define how script-created click events are special during dispatch (#325) (Thursday, 15 September)
• Re: [w3c/uievents] Figure out what to do with focusin/focusout (#88) (Thursday, 8 September)
• Re: [whatwg/dom] Having getElementsByTagName match on localName is not "web"-compatible for IE and Firefox (#143) (Thursday, 8 September)
• [w3c/uievents] Can't suppress the default action of non-primary button clicks (#107) (Thursday, 8 September)
• Re: [w3c/touch-events] Add TouchEvent's retargeting steps (#73) (Friday, 2 September)
• Re: [w3c/touch-events] Add TouchEvent's retargeting steps (#73) (Friday, 2 September)
• Re: [w3c/touch-events] Add TouchEvent's retargeting steps (#73) (Friday, 2 September)
• Re: [w3c/touch-events] Add TouchEvent's retargeting steps (#73) (Friday, 2 September)

Rob Brackett

• Re: [w3c/webcomponents] [idea] Make use of `observedAttributes` optional (#565) (Thursday, 22 September)
• Re: [w3c/webcomponents] [idea] Make use of `observedAttributes` optional (#565) (Tuesday, 20 September)

Rob Dodson

• [WICG/modality] tiny typo fix (#27) (Monday, 26 September)

Rob Dolin (MSFT)

• Re: [w3c/manifest] (Re-)Add Optional Splash Screens (#501) (Wednesday, 21 September)
• Re: [w3c/manifest] (Re-)Add Optional Splash Screens (#501) (Wednesday, 21 September)
• Re: [w3c/manifest] Allow for multiple scopes (#449) (Wednesday, 21 September)
• [w3c/manifest] (Re-)Add Optional Splash Screens (#501) (Wednesday, 21 September)
• Re: [w3c/manifest] Integration with service workers (#161) (Tuesday, 20 September)
• Re: [w3c/manifest] Add optional Transition Screen member (#478) (Friday, 16 September)
• Re: [w3c/manifest] Add optional Transition Screen member (#478) (Friday, 16 September)
• Re: [w3c/manifest] Support a way to update explicitly (#446) (Thursday, 15 September)
• Re: [w3c/manifest] [Appendix] Add crawl opt-out (closes #498) (#499) (Wednesday, 14 September)
• [w3c/manifest] [Appendix] Add crawl opt-out (closes #498) (#499) (Tuesday, 13 September)
• Re: [w3c/manifest] Allow for multiple scopes (#449) (Tuesday, 13 September)
• Re: [w3c/manifest] Integration with service workers (#161) (Tuesday, 13 September)
• Re: [w3c/manifest] Describe how developers can block web crawlers (#498) (Friday, 9 September)
• [w3c/manifest] Describe how developers can block web crawlers (#498) (Friday, 9 September)
• Re: [w3c/manifest] Add optional Transition Screen member (#478) (Wednesday, 7 September)
• Re: [w3c/manifest] Allow for multiple scopes (#449) (Wednesday, 7 September)
• Re: [w3c/manifest] doc(extensibility): e.g., of site verificaton (closes #476) (#497) (Thursday, 1 September)

Romain

• Re: [whatwg/streams] getReader behaviour with empty mode (#517) (Wednesday, 7 September)
• [whatwg/streams] getReader behaviour with empty mode (#517) (Wednesday, 7 September)

roryhewitt

• Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Thursday, 15 September)

Russell Bicknell

• Re: [w3c/webcomponents] slotchange event should not bubble (#571) (Thursday, 22 September)
• [whatwg/dom] Symbols should be allowed as Event types. (#331) (Wednesday, 21 September)
• Re: [w3c/webcomponents] slotchange event should not bubble (#571) (Wednesday, 21 September)
• Re: [w3c/webcomponents] slotchange event should not bubble (#571) (Tuesday, 20 September)

Ryosuke Niwa

• Re: [w3c/webcomponents] The get-the-parent algorithm shouldn't return null until we reach the root of the current tree (#577) (Friday, 30 September)
• Re: [w3c/selection-api] Limit onselectionchange to Document until known to be needed elsewhere (#75) (Thursday, 29 September)
• Re: [w3c/selection-api] Limit onselectionchange to Document until known to be needed elsewhere (#75) (Thursday, 29 September)
• Re: [w3c/webcomponents] The get-the-parent algorithm shouldn't return null until we reach the root of the current tree (#577) (Thursday, 29 September)
• Re: [w3c/selection-api] Limit onselectionchange to Document until known to be needed elsewhere (#75) (Thursday, 29 September)
• Re: [w3c/selection-api] Selection events for text controls (#53) (Thursday, 29 September)
• Re: [w3c/webcomponents] The get-the-parent algorithm shouldn't return null until we reach the root of the current tree (#577) (Thursday, 29 September)
• [w3c/DOM-Parsing] innerHTML should be defined on ShadowRoot interface in addition to Element interface (#21) (Thursday, 29 September)
• Re: [w3c/webcomponents] Expected behaviour of contentEditable, slot and distributed nodes (#579) (Thursday, 29 September)
• Re: [whatwg/dom] Clarify that new Document creates a document of type "html", not "xml" (#308) (Wednesday, 28 September)
• Re: [w3c/webcomponents] The get-the-parent algorithm shouldn't return null until we reach the root of the current tree (#577) (Wednesday, 28 September)
• Re: [w3c/webcomponents] Synthetic click activation steps should state whether the event is composed or not (#578) (Wednesday, 28 September)
• Re: [w3c/webcomponents] Synthetic click activation steps should state whether the event is composed or not (#578) (Wednesday, 28 September)
• [w3c/webcomponents] Synthetic click activation steps should state whether the event is composed or not (#578) (Wednesday, 28 September)
• Re: [w3c/webcomponents] Synthetic click activation steps should state whether the event is composed or not (#578) (Wednesday, 28 September)
• Re: [w3c/webcomponents] The get-the-parent algorithm shouldn't return null until we reach the root of the current tree (#577) (Wednesday, 28 September)
• Re: [w3c/webcomponents] The get-the-parent algorithm shouldn't return null until we reach the root of the current tree (#577) (Wednesday, 28 September)
• [w3c/webcomponents] The get-the-parent algorithm shouldn't return null until we reach the root of the current tree (#577) (Wednesday, 28 September)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Wednesday, 28 September)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Tuesday, 27 September)
• Re: [w3c/webcomponents] [Idea] Distant ShadowDOM. (#576) (Tuesday, 27 September)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Tuesday, 27 September)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Tuesday, 27 September)
• Re: [w3c/webcomponents] [Idea] Distant ShadowDOM. (#576) (Tuesday, 27 September)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Monday, 26 September)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Monday, 26 September)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Monday, 26 September)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Saturday, 24 September)
• Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150) (Saturday, 24 September)
• Re: [w3c/webcomponents] [Shadow] Slotting indirect children (#574) (Friday, 23 September)
• Re: [w3c/webcomponents] [Shadow] Slotting indirect children (#574) (Friday, 23 September)
• Re: [w3c/webcomponents] [Custom]: Callback for cloneNode/importNode (bugzilla: 24570) (#176) (Thursday, 22 September)
• Re: [w3c/webcomponents] [Custom]: Callback for cloneNode/importNode (bugzilla: 24570) (#176) (Thursday, 22 September)
• Re: [w3c/webcomponents] [Custom]: Callback for cloneNode/importNode (bugzilla: 24570) (#176) (Thursday, 22 September)
• Re: [w3c/webcomponents] [idea] Make use of `observedAttributes` optional (#565) (Thursday, 22 September)
• Re: [w3c/selection-api] Event handlers missing (#60) (Tuesday, 20 September)
• Re: [w3c/selection-api] Event handlers missing (#60) (Tuesday, 20 September)
• Re: [w3c/selection-api] Clarify the additions of this spec to GlobalEventHandlers (#54) (Tuesday, 20 September)
• Re: [w3c/selection-api] Clarify the additions of this spec to GlobalEventHandlers (#54) (Tuesday, 20 September)
• Re: [w3c/selection-api] Add a "Selection interface" section (#29) (Tuesday, 20 September)
• Re: [w3c/selection-api] Add a "Selection interface" section (#29) (Tuesday, 20 September)
• Re: [w3c/webcomponents] [idea] Make use of `observedAttributes` optional (#565) (Tuesday, 20 September)
• Re: [w3c/webcomponents] slotchange event should not bubble (#571) (Tuesday, 20 September)
• Re: [w3c/webcomponents] slotchange event should not bubble (#571) (Tuesday, 20 September)
• Re: [w3c/webcomponents] [idea] Make use of `observedAttributes` optional (#565) (Tuesday, 20 September)
• Re: [w3c/selection-api] user-select: none and selectionchange event (#74) (Tuesday, 20 September)
• Re: [w3c/webcomponents] slotchange event should not bubble (#571) (Tuesday, 20 September)
• Re: [w3c/webcomponents] slotchange event should not bubble (#571) (Tuesday, 20 September)
• Re: [w3c/webcomponents] [idea] Make use of `observedAttributes` optional (#565) (Tuesday, 20 September)
• Re: [w3c/webcomponents] [Custom]: Need callback for form submit data (bugzilla: 24603) (#187) (Tuesday, 20 September)
• [w3c/webcomponents] Make createElement report an exception instead of propagating an exception (#569) (Monday, 19 September)
• Re: [w3c/webcomponents] Is there a way to retrieve the localName from a custom element constructor? (#566) (Friday, 16 September)
• Re: [w3c/webcomponents] Is there a way to retrieve the localName from a custom element constructor? (#566) (Friday, 16 September)
• Re: [w3c/webcomponents] Is <slot> a replaced element or not? (#564) (Monday, 12 September)
• Re: [w3c/selection-api] user-select: none and selectionchange event (#74) (Monday, 12 September)
• Re: [w3c/webcomponents] CustomElements: upgrade runs connectedCallback on an element with a throwing constructor (#563) (Wednesday, 7 September)
• Re: [w3c/webcomponents] A custom element should be marked as "failed" if a constructor returns a wrong object (#561) (Saturday, 3 September)
• [w3c/webcomponents] A custom element should be marked as "failed" if a constructor returns a wrong object (#561) (Saturday, 3 September)
• Re: [w3c/webcomponents] HTML element constructors need to Get(newTarget, "Prototype") (#560) (Thursday, 1 September)

Salvador de la Puente González

• Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920) (Wednesday, 21 September)
• Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920) (Wednesday, 21 September)
• Re: [w3c/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893) (Tuesday, 20 September)
• Re: [w3c/ServiceWorker] Allow Caching of POST requests (#977) (Thursday, 15 September)
• Re: [w3c/ServiceWorker] Eliminating SW startup latency for common case (#920) (Friday, 9 September)
• Re: [w3c/ServiceWorker] allow service worker produced resources to be marked as "cachable" (#962) (Friday, 9 September)
• Re: [w3c/ServiceWorker] Eliminating SW startup latency for common case (#920) (Friday, 9 September)

Sam Ruby

• Re: [w3ctag/url] Mark spec as obsolete (#6) (Monday, 26 September)

Sander Elias

• Re: [w3c/webcomponents] missing guidance on implementing an 'refresh' option. (#562) (Wednesday, 7 September)
• Re: [w3c/webcomponents] missing guidance on implementing an 'refresh' option. (#562) (Wednesday, 7 September)
• Re: [w3c/webcomponents] missing guidance on implementing an 'refresh' option. (#562) (Tuesday, 6 September)
• Re: [w3c/webcomponents] missing guidance on implementing an 'refresh' option. (#562) (Tuesday, 6 September)
• Re: [w3c/webcomponents] missing guidance on implementing an 'refresh' option. (#562) (Tuesday, 6 September)
• [w3c/webcomponents] missing guidance on implementing an 'refresh' option. (#562) (Tuesday, 6 September)

Scott Graham

• Re: [w3c/gamepad] Add 'Actuator' (#38) (Tuesday, 20 September)
• Re: [w3c/gamepad] Add 'Actuator' (#38) (Tuesday, 20 September)
• Re: [w3c/gamepad] Add 'Actuator' (#38) (Tuesday, 20 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Friday, 16 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Friday, 16 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Monday, 12 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Monday, 12 September)

shans

• Re: [WICG/modality] Add a simple example, remove the detailed docs. (#26) (Friday, 23 September)
• [WICG/modality] Add a simple example, remove the detailed docs. (#26) (Friday, 23 September)

Shiino Yuki

• Re: [heycam/webidl] Change the named property visibility algorithm so that existing own props always make corresponding named props invisible. (#174) (Monday, 12 September)

Simon Pieters

• Re: [whatwg/fetch] Same-origin data-URL flag only for fetch and XHR? (#381) (Thursday, 8 September)
• [whatwg/url] Editorial: Update spelling of HTML terms to en-US (#147) (Friday, 2 September)

smaug----

• Re: [w3c/webcomponents] The get-the-parent algorithm shouldn't return null until we reach the root of the current tree (#577) (Friday, 30 September)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Wednesday, 28 September)
• Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221) (Wednesday, 28 September)
• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Saturday, 24 September)
• Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) (Friday, 23 September)
• Re: [w3c/touch-events] Consider defaulting to use passive listener on window/document/document.body (#74) (Friday, 23 September)
• [w3c/touch-events] Consider defaulting to use passive listener on window/document/document.body (#74) (Friday, 23 September)
• Re: [whatwg/fullscreen] Should browser UI be able to activate fullscreen even if iframe is missing allowfullscreen (#56) (Tuesday, 20 September)
• Re: [whatwg/fullscreen] Should browser UI be able to activate fullscreen even if iframe is missing allowfullscreen (#56) (Tuesday, 20 September)
• [whatwg/fullscreen] Should browser UI be able to activate fullscreen even if iframe is missing allowfullscreen (#56) (Tuesday, 20 September)
• Re: [w3c/uievents] Figure out what to do with focusin/focusout (#88) (Tuesday, 20 September)
• Re: [whatwg/dom] Define how script-created click events are special during dispatch (#325) (Thursday, 15 September)
• Re: [w3c/webcomponents] <iframe> and the History API (#184) (Tuesday, 13 September)
• Re: [w3c/uievents] Figure out what to do with focusin/focusout (#88) (Wednesday, 7 September)
• Re: [w3c/uievents] Figure out what to do with focusin/focusout (#88) (Tuesday, 6 September)
• Re: [whatwg/dom] Drop support for SVGZoomEvent in createEvent (#323) (Thursday, 1 September)
• Re: [whatwg/dom] Drop support for SVGZoomEvent in createEvent (#323) (Thursday, 1 September)

Stefan

• Re: [w3c/ServiceWorker] Allow Caching of POST requests (#977) (Wednesday, 21 September)

stefan hakansson

• Re: [w3c/permissions] fix(request): clarify how requests affect state (#127) (Friday, 9 September)
• Re: [w3c/permissions] refactor(permission state): pass the settings object explicitly (#114) (Thursday, 8 September)

Steve Orvell

• [w3c/webcomponents] slotchange event should not bubble (#571) (Monday, 19 September)

stevefaulkner

• Re: [w3c/WebPlatformWG] TPAC 2016/Monday proposed agenda items (#68) (Monday, 12 September)

Stuart P. Bentley

• Re: [whatwg/storage] Use more generic example to demonstrate estimate() (#37) (Thursday, 29 September)
• [whatwg/storage] Use more generic example to demonstrate estimate() (#37) (Wednesday, 28 September)

sureshkm

• Re: [w3c/IndexedDB] Error events from open/deleteDatabase requests - cancelable? bubbles? (#86) (Saturday, 3 September)
• Re: [w3c/IndexedDB] Error events from open/deleteDatabase requests - cancelable? bubbles? (#86) (Friday, 2 September)

Surma

• [w3c/ServiceWorker] Define procedure to convert options object of `sw.register()` to `Link` header (#979) (Tuesday, 20 September)

Tab Atkins Jr.

• Re: [w3c/permissions] Move to using Echidna (#24) (Tuesday, 13 September)
• Re: [heycam/webidl] Contributing to webidl just got a lot harder (#171) (Friday, 9 September)
• Re: [heycam/webidl] Various "terms defined by this specification" are miscapitalized (#172) (Friday, 9 September)
• Re: [heycam/webidl] Contributing to webidl just got a lot harder (#171) (Friday, 9 September)
• Re: [heycam/webidl] Various "terms defined by this specification" are miscapitalized (#172) (Friday, 9 September)
• Re: [heycam/webidl] Contributing to webidl just got a lot harder (#171) (Friday, 9 September)
• Re: [whatwg/dom] Further Attr node fixes for compareDocumentPosition() (#312) (Thursday, 1 September)

Takayoshi Kochi

• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Friday, 30 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Friday, 30 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Friday, 30 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Friday, 30 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Friday, 30 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Thursday, 29 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Thursday, 29 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Thursday, 29 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Wednesday, 28 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Wednesday, 28 September)
• Re: [w3c/webcomponents] [imports]: Respect the crossOrigin attribute (bugzilla: 25568) (#216) (Tuesday, 27 September)
• Re: [w3c/webcomponents] How should autofill work for inputs generated inside shadow roots (#572) (Tuesday, 27 September)
• Re: [w3c/webcomponents] How should autofill work for inputs generated inside shadow roots (#572) (Monday, 26 September)
• Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78) (Wednesday, 21 September)
• Re: [w3c/webcomponents] Support /deep/ in static profile (bugzilla: 28591) (#78) (Wednesday, 21 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Tuesday, 20 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Tuesday, 20 September)
• Re: [whatwg/fullscreen] To fullscreen/unfullscreen, do not take document as an argument (#55) (Friday, 16 September)
• Re: [whatwg/fullscreen] To fullscreen/unfullscreen, do not take document as an argument (#55) (Friday, 16 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Friday, 16 September)
• [whatwg/fullscreen] To fullscreen/unfullscreen, do not take document as an argument (#55) (Friday, 16 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Friday, 16 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Friday, 16 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Friday, 16 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Friday, 16 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Friday, 16 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Thursday, 15 September)
• [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#54) (Thursday, 15 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#53) (Thursday, 15 September)
• Re: [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#53) (Thursday, 15 September)
• [whatwg/fullscreen] Update fullscreen spec to be Shadow DOM compliant (#53) (Thursday, 15 September)
• Re: [w3c/webcomponents] <iframe> and the History API (#184) (Wednesday, 14 September)
• Re: [w3c/webcomponents] <iframe> and the History API (#184) (Tuesday, 13 September)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Thursday, 1 September)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Thursday, 1 September)
• Re: [w3c/webcomponents] :focus behavior of delegatesFocus:true will be confusing for users (#554) (Thursday, 1 September)

Takeshi Yoshino

• Re: [whatwg/streams] Update TransformStream API & misc. fixups (#519) (Thursday, 29 September)
• Re: [whatwg/encoding] Add support for whatwg streams (9224c4c) (Tuesday, 27 September)
• Re: [whatwg/encoding] Add support for whatwg streams (9224c4c) (Monday, 26 September)
• Re: [whatwg/encoding] Add support for whatwg streams (9224c4c) (Monday, 26 September)
• Re: [whatwg/encoding] Add support for whatwg streams (9224c4c) (Monday, 26 September)
• Re: [whatwg/streams] Update TransformStream API & misc. fixups (#519) (Tuesday, 20 September)
• Re: [whatwg/streams] Factor out WritableStreamDefaultWriterRelease (#513) (Friday, 9 September)
• Re: [whatwg/streams] Factor out WritableStreamDefaultWriterRelease (#513) (Friday, 9 September)
• Re: [whatwg/fetch] Listing headers safe only for certain values is a bad idea (#313) (Friday, 9 September)
• Re: [whatwg/fetch] Listing headers safe only for certain values is a bad idea (#313) (Friday, 9 September)
• Re: [whatwg/fetch] Listing headers safe only for certain values is a bad idea (#313) (Friday, 9 September)
• Re: [whatwg/fetch] Listing headers safe only for certain values is a bad idea (#313) (Friday, 9 September)
• Re: [whatwg/fetch] Listing headers safe only for certain values is a bad idea (#313) (Thursday, 8 September)
• Re: [whatwg/fetch] Listing headers safe only for certain values is a bad idea (#313) (Thursday, 8 September)
• Re: [whatwg/fetch] Listing headers safe only for certain values is a bad idea (#313) (Thursday, 8 September)
• Re: [whatwg/fetch] Same-origin data-URL flag only for fetch and XHR? (#381) (Wednesday, 7 September)
• Re: [whatwg/streams] Add a proof of concept of optimized pipe (#511) (Wednesday, 7 September)
• [whatwg/streams] Document difference of lock between writable and readable (#516) (Tuesday, 6 September)
• Re: [whatwg/streams] Add a proof of concept of optimized pipe (#511) (Tuesday, 6 September)
• Re: [whatwg/streams] First draft at a pipeTo "algorithm" (#512) (Tuesday, 6 September)
• Re: [whatwg/streams] First draft at a pipeTo "algorithm" (#512) (Tuesday, 6 September)
• Re: [whatwg/streams] First draft at a pipeTo "algorithm" (#512) (Tuesday, 6 September)
• Re: [whatwg/streams] lint glob should exclude Emacs backup files (#514) (Friday, 2 September)

Ted Mielczarek

• Re: [w3c/gamepad] Support Buffered Haptic Effects (#39) (Tuesday, 27 September)
• Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32) (Tuesday, 20 September)
• Re: [w3c/gamepad] Consider using Bikeshed for spec formatting (#33) (Tuesday, 13 September)

Theo Zourzouvillys

• [w3c/webcomponents] integrity attribute in <link rel="import"/> (#575) (Monday, 26 September)

Thomas Pessato

• Re: [w3c/manifest] Allow unique start_url for subdomains (#470) (Monday, 12 September)

Tiago Oliveira

• Re: [whatwg/xhr] Wrong state after abort() (#88) (Saturday, 3 September)
• [whatwg/xhr] Wrong state after abort() (#88) (Saturday, 3 September)

tkodw

• Re: [w3c/gamepad] Support Buffered Haptic Effects (#39) (Thursday, 29 September)
• Re: [w3c/gamepad] Support Buffered Haptic Effects (#39) (Wednesday, 28 September)
• Re: [w3c/gamepad] Should fire events instead of using passive model (#4) (Tuesday, 20 September)
• Re: [w3c/gamepad] Should fire events instead of using passive model (#4) (Monday, 19 September)
• Re: [w3c/gamepad] Make gamepads accessible by web worker (#37) (Monday, 19 September)
• [w3c/gamepad] Make gamepads accessible by web worker (#37) (Friday, 16 September)

Tobie Langel

• Re: [heycam/webidl] Specify open dictionaries. (#180) (Friday, 30 September)
• Re: [heycam/webidl] Specify open dictionaries. (#180) (Friday, 30 September)
• Re: [heycam/webidl] Make defaults to API when Bikeshed isn’t installed locally. (#173) (Tuesday, 27 September)
• Re: [w3ctag/spec-reviews] A spec style/structure checklist? (#136) (Tuesday, 27 September)
• Re: [whatwg/fetch] OpenEndedDictionary clarification (#164) (Tuesday, 27 September)
• Re: [w3ctag/spec-reviews] A spec style/structure checklist? (#136) (Tuesday, 27 September)
• Re: [heycam/webidl] Add a forgotten closing parenthesis. (#179) (Monday, 26 September)
• Re: [heycam/webidl] Add a forgotten closing parenthesis. (#179) (Monday, 26 September)
• Re: [heycam/webidl] Namespace is a misnomer, should we fix it? (#177) (Thursday, 22 September)
• Re: [heycam/webidl] Namespace is a misnomer, should we fix it? (#177) (Wednesday, 21 September)
• [heycam/webidl] Namespace is a misnomer, should we fix it? (#177) (Monday, 19 September)
• Re: [heycam/webidl] Move conventions and conformance to appendices (#167) (Sunday, 11 September)
• Re: [heycam/webidl] Change the named property visibility algorithm so that existing own props always make corresponding named props invisible. (#174) (Sunday, 11 September)
• Re: [heycam/webidl] Named properties visibility algorithm leads to ES invariant violation (#152) (Sunday, 11 September)
• Re: [heycam/webidl] Change the named property visibility algorithm so that existing own props always make corresponding named props invisible. (#174) (Sunday, 11 September)
• Re: [heycam/webidl] Convert idl- prefixed anchors to Bikeshed notation. (#170) (Friday, 9 September)
• [heycam/webidl] Make defaults to API when Bikeshed isn’t installed locally. (#173) (Friday, 9 September)
• Re: [heycam/webidl] Contributing to webidl just got a lot harder (#171) (Friday, 9 September)
• Re: [heycam/webidl] Contributing to webidl just got a lot harder (#171) (Friday, 9 September)
• Re: [heycam/webidl] Contributing to webidl just got a lot harder (#171) (Friday, 9 September)
• Re: [heycam/webidl] Contributing to webidl just got a lot harder (#171) (Friday, 9 September)
• Re: [heycam/webidl] Contributing to webidl just got a lot harder (#171) (Friday, 9 September)
• Re: [heycam/webidl] Contributing to webidl just got a lot harder (#171) (Friday, 9 September)
• Re: [heycam/webidl] Contributing to webidl just got a lot harder (#171) (Friday, 9 September)
• Re: [heycam/webidl] Contributing to webidl just got a lot harder (#171) (Friday, 9 September)
• Re: [heycam/webidl] Cleanup trailing whitespace (#165) (Friday, 9 September)
• Re: [heycam/webidl] Cleanup trailing whitespace (#165) (Friday, 9 September)
• Re: [heycam/webidl] Convert idl- prefixed anchors to Bikeshed notation. (#170) (Friday, 9 September)
• [heycam/webidl] Convert idl- prefixed anchors to Bikeshed notation. (#170) (Thursday, 8 September)
• Re: [heycam/webidl] Remove the "Changes" section (#166) (Thursday, 8 September)
• Re: [heycam/webidl] Consolidate issue tracking links in the header under "Feedback" (#169) (Thursday, 8 September)
• Re: [heycam/webidl] Consolidate issue tracking links in the header under "Feedback" (#169) (Thursday, 8 September)
• Re: [heycam/webidl] Move conventions and conformance to appendices (#167) (Thursday, 8 September)
• Re: [heycam/webidl] Consolidate issue tracking links in the header under "Feedback" (#169) (Thursday, 8 September)
• Re: [heycam/webidl] Consolidate issue tracking links in the header under "Feedback" (#169) (Thursday, 8 September)
• Re: [heycam/webidl] More meaniful labels (#136) (Thursday, 8 September)
• Re: [heycam/webidl] docs(README): contributing section (closes #136) (#143) (Thursday, 8 September)
• Re: [heycam/webidl] Fix calls to the create a sequence from an iterable algorithm. (#163) (Thursday, 8 September)
• Re: [heycam/webidl] Typo in converting sequence (#161) (Thursday, 8 September)
• [heycam/webidl] Fix calls to the create a sequence from an iterable algorithm. (#163) (Thursday, 8 September)
• Re: [heycam/webidl] Update to latest Bikeshed (#160) (Wednesday, 7 September)
• [heycam/webidl] Update to latest Bikeshed (#160) (Wednesday, 7 September)
• Re: [heycam/webidl] "File a bug" header goes to bugzilla not github (#122) (Wednesday, 7 September)
• Re: [heycam/webidl] Remove final TYPEDARRAYS reference (#157) (Wednesday, 7 September)
• Re: [heycam/webidl] "File a bug" header goes to bugzilla not github (#122) (Wednesday, 7 September)
• Re: [heycam/webidl] Bikeshed Conversion (#147) (Wednesday, 7 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Wednesday, 7 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Wednesday, 7 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Wednesday, 7 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Wednesday, 7 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Wednesday, 7 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Wednesday, 7 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Wednesday, 7 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Tuesday, 6 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Tuesday, 6 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Tuesday, 6 September)
• [heycam/webidl] Add a contributing guide (#159) (Tuesday, 6 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Tuesday, 6 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Monday, 5 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Monday, 5 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Monday, 5 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Monday, 5 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Monday, 5 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Monday, 5 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Monday, 5 September)
• Re: [heycam/webidl] Remove final TYPEDARRAYS reference (#157) (Monday, 5 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Monday, 5 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Monday, 5 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Monday, 5 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Sunday, 4 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Sunday, 4 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Sunday, 4 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Sunday, 4 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Sunday, 4 September)
• Re: [heycam/webidl] Bikeshed conversion (#158) (Sunday, 4 September)
• Re: [heycam/webidl] Bikeshed Conversion (#147) (Sunday, 4 September)
• [heycam/webidl] Bikeshed conversion (#158) (Sunday, 4 September)
• Re: [w3c/permissions] Pass objects instead of PermissionDescriptors to the Permissions interface. (#125) (Thursday, 1 September)

Tomek Wytrębowicz

• [w3c/webcomponents] Use cases for HTML Imports (#573) (Friday, 23 September)
• Re: [w3c/webcomponents] Status codes for HTML Imports (#568) (Wednesday, 21 September)
• [w3c/webcomponents] Status codes for HTML Imports (#568) (Sunday, 18 September)
• Re: [w3c/webcomponents] [imports] HTML Includes (<import src='header.html'/> in <body>) (#280) (Sunday, 18 September)
• [w3c/WebPlatformWG] Add Tomek Wytrębowicz to session attendees (#69) (Monday, 12 September)

Tony Jin

• Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Friday, 16 September)
• Re: [whatwg/fetch] More wildcards in CORS when used without credentials (#298) (Thursday, 15 September)

Travis Leithead

• Re: [w3c/uievents] Figure out what to do with focusin/focusout (#88) (Friday, 16 September)
• Re: [w3ctag/spec-reviews] WebVR (#106) (Wednesday, 14 September)
• Re: [w3ctag/spec-reviews] Review of WakeLock API and suitability for overall platform requested by 31 August 2016 (#126) (Thursday, 1 September)

Trey Shugart

• Re: [w3c/webcomponents] How should autofill work for inputs generated inside shadow roots (#572) (Tuesday, 27 September)
• Re: [w3c/webcomponents] How should autofill work for inputs generated inside shadow roots (#572) (Tuesday, 27 September)
• Re: [w3c/webcomponents] [idea] Make use of `observedAttributes` optional (#565) (Thursday, 22 September)
• Re: [w3c/webcomponents] slotchange event should not bubble (#571) (Monday, 19 September)
• Re: [w3c/webcomponents] Is there a way to retrieve the localName from a custom element constructor? (#566) (Monday, 19 September)
• Re: [w3c/webcomponents] Is there a way to retrieve the localName from a custom element constructor? (#566) (Friday, 16 September)
• Re: [w3c/webcomponents] Is there a way to retrieve the localName from a custom element constructor? (#566) (Friday, 16 September)
• Re: [w3c/webcomponents] Is there a way to retrieve the localName from a custom element constructor? (#566) (Friday, 16 September)
• Re: [w3c/webcomponents] Is there a way to retrieve the localName from a custom element constructor? (#566) (Thursday, 15 September)
• Re: [w3c/webcomponents] Is there a way to retrieve the localName from a custom element constructor? (#566) (Thursday, 15 September)
• [w3c/webcomponents] Is there a way to retrieve the localName from a custom element constructor? (#566) (Wednesday, 14 September)

vanupam

• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Friday, 16 September)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Friday, 16 September)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Friday, 16 September)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Friday, 16 September)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Friday, 16 September)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Friday, 16 September)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Friday, 16 September)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Friday, 16 September)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Friday, 16 September)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Friday, 16 September)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Thursday, 15 September)
• Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325) (Friday, 2 September)

Victor Costan

• Re: [w3c/IndexedDB] Specify interaction between transaction abort and index/object store renames (#89) (Thursday, 8 September)
• Re: [w3c/IndexedDB] Specify interaction between transaction abort and index/object store renames (#89) (Thursday, 8 September)
• Re: [w3c/IndexedDB] Abort behavior for renames of newly created stores/indexes, for #89 (#90) (Wednesday, 7 September)
• Re: [w3c/IndexedDB] Specify interaction between transaction abort and index/object store renames (#89) (Wednesday, 7 September)
• [w3c/IndexedDB] Specify interaction between transaction abort and index/object store renames (#89) (Wednesday, 7 September)

Vincent Scheib

• Re: [w3c/pointerlock] pointerlockchange is cancelable, breaking the processing model (#9) (Friday, 30 September)
• [w3c/pointerlock] Events' defaultPrevented attribute has no effect. (#10) (Friday, 30 September)
• Re: [w3c/pointerlock] pointerlockchange is cancelable, breaking the processing model (#9) (Tuesday, 27 September)

wisniewskit

• [whatwg/xhr] The spec needs to reflect legacy behavior for firing multiple LOADING readystatechanges. (#92) (Tuesday, 27 September)
• Re: [whatwg/xhr] Kill the progress event when readyState is 4 (#72) (Thursday, 15 September)
• Re: [whatwg/xhr] Kill the progress event when readyState is 4 (#72) (Thursday, 15 September)
• Re: [whatwg/xhr] Kill the progress event when readyState is 4 (#72) (Wednesday, 14 September)

Xidorn Quan

• Re: [whatwg/fullscreen] What should happen if an element is moved to another document right after requestFullscreen (#33) (Friday, 30 September)
• [whatwg/fullscreen] Element moved into another document after requesting fullscreen should make the request fail (#59) (Thursday, 29 September)
• [whatwg/fullscreen] Fullscreen request on invisible document should be denied (#58) (Thursday, 29 September)
• Re: [w3c/ServiceWorker] Provide a simple synchronous k-v storage for ServiceWorker? (#981) (Sunday, 25 September)
• Re: [whatwg/fullscreen] Should browser UI be able to activate fullscreen even if iframe is missing allowfullscreen (#56) (Sunday, 25 September)
• Re: [w3c/ServiceWorker] Provide a simple synchronous k-v storage for ServiceWorker? (#981) (Sunday, 25 September)
• [whatwg/dom] Consider adding Promise-based API for listerning event (#333) (Saturday, 24 September)
• Re: [w3c/ServiceWorker] Provide a simple synchronous k-v storage for ServiceWorker? (#981) (Saturday, 24 September)
• [w3c/ServiceWorker] Provide a simple synchronous k-v storage for ServiceWorker? (#981) (Saturday, 24 September)
• Re: [whatwg/fullscreen] Allow fullscreen on initial load of a page (#36) (Tuesday, 20 September)
• Re: [whatwg/fullscreen] Allow fullscreen on initial load of a page (#36) (Monday, 19 September)
• Re: [whatwg/fullscreen] Allow fullscreen on initial load of a page (#36) (Monday, 19 September)

ykahlon

• Re: [w3c/ServiceWorker] Provide a simple synchronous k-v storage for ServiceWorker? (#981) (Saturday, 24 September)

Yoav Weiss

• Re: [WICG/modality] tiny typo fix (#27) (Monday, 26 September)
• Re: [WICG/modality] Add a simple example, remove the detailed docs. (#26) (Friday, 23 September)

Yonggang Luo

• Re: [whatwg/encoding] Remove the last 14 characters PUA of GB18030-2005 (#27) (Tuesday, 6 September)

youennf

• Re: [whatwg/fetch] Handling of data URLs (#111) (Friday, 30 September)
• Re: [whatwg/fetch] Handling of data URLs (#111) (Friday, 30 September)
• Re: [whatwg/fetch] Handling of data URLs (#111) (Friday, 30 September)
• Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304) (Monday, 26 September)
• Re: [whatwg/fetch] Same-origin data-URL flag only for fetch and XHR? (#381) (Wednesday, 14 September)
• Re: [whatwg/fetch] There's no reason to make fetch of about:blank same-origin for loads other than navigations and `<object>` (#384) (Wednesday, 14 September)
• Re: [whatwg/fetch] Same-origin data-URL flag only for fetch and XHR? (#381) (Thursday, 8 September)
• Re: [whatwg/fetch] Same-origin data-URL flag only for fetch and XHR? (#381) (Thursday, 8 September)
• Re: [whatwg/fetch] Same-origin data-URL flag only for fetch and XHR? (#381) (Wednesday, 7 September)
• Re: [whatwg/fetch] Same-origin data-URL flag only for fetch and XHR? (#381) (Wednesday, 7 September)
• Re: [whatwg/fetch] Same-origin data-URL flag only for fetch and XHR? (#381) (Wednesday, 7 September)
• Re: [whatwg/fetch] Same-origin data-URL flag only for fetch and XHR? (#381) (Wednesday, 7 September)
• Re: [whatwg/fetch] Same-origin data-URL flag only for fetch and XHR? (#381) (Tuesday, 6 September)
• Re: [whatwg/fetch] Same-origin data-URL flag only for fetch and XHR? (#381) (Tuesday, 6 September)
• Re: [whatwg/fetch] Same-origin data-URL flag only for fetch and XHR? (#381) (Tuesday, 6 September)
• Re: [whatwg/fetch] Same-origin data-URL flag only for fetch and XHR? (#381) (Tuesday, 6 September)
• Re: [whatwg/fetch] Handling of data URLs (#111) (Tuesday, 6 September)
• [whatwg/fetch] Same-origin data-URL flag only for fetch and XHR? (#381) (Tuesday, 6 September)

Yutaka Hirano

• Re: [whatwg/fetch] (WIP) allow Request to outlive environment settings object (#388) (Friday, 23 September)
• Re: [whatwg/fetch] (WIP) allow Request to outlive environment settings object (#388) (Tuesday, 20 September)
• [whatwg/xhr] Fix an obsolete ReadableStream operation name (#87) (Thursday, 1 September)

Yves Lafon

• Re: [w3ctag/spec-reviews] A spec style/structure checklist? (#136) (Tuesday, 27 September)
• Re: [w3c/WebPlatformWG] Add Chong Zhang to attendees (#74) (Sunday, 18 September)
• Re: [w3c/WebPlatformWG] Update 16-09-22TPAC-3.md (#70) (Wednesday, 14 September)
• Re: [w3c/ServiceWorker] Serve subfolder to gh-pages (#966) (Tuesday, 13 September)
• Re: [w3c/ServiceWorker] Serve subfolder to gh-pages (#966) (Tuesday, 13 September)
• Re: [w3c/ServiceWorker] Make cache example easier to understand (#976) (Friday, 9 September)
• Re: [w3c/ServiceWorker] Serve subfolder to gh-pages (#966) (Wednesday, 7 September)
• Re: [w3c/ServiceWorker] Serve subfolder to gh-pages (#966) (Wednesday, 7 September)
• Re: [w3c/ServiceWorker] Serve subfolder to gh-pages (#966) (Wednesday, 7 September)
• Re: [w3c/ServiceWorker] add redirect from /SW/ to /spec/s_w/ (#973) (Wednesday, 7 September)
• [w3c/ServiceWorker] add redirect from /SW/ to /spec/s_w/ (#973) (Wednesday, 7 September)

Zachary Ferraro

• Re: [whatwg/fetch] Request bodies with GET and HEAD (#390) (Thursday, 22 September)
• Re: [whatwg/fetch] Request bodies with GET and HEAD (#390) (Thursday, 22 September)
• [whatwg/fetch] Request bodies with GET and HEAD (#390) (Thursday, 22 September)

Zambonifofex

• Re: [w3c/webcomponents] [Custom]: Need callback for form submit data (bugzilla: 24603) (#187) (Thursday, 15 September)
• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Thursday, 15 September)
• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Thursday, 15 September)
• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Wednesday, 14 September)
• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Wednesday, 14 September)
• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Wednesday, 14 September)
• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Wednesday, 14 September)
• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Wednesday, 14 September)
• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Wednesday, 14 September)
• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Wednesday, 14 September)
• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Wednesday, 14 September)
• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Wednesday, 14 September)
• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Wednesday, 14 September)
• Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Wednesday, 14 September)
• [w3c/webcomponents] accessibility considerations: states and behaviors (#567) (Wednesday, 14 September)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 10 September)
• Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509) (Saturday, 10 September)

Ádám Liszkai

• Re: [w3c/ServiceWorker] Communicate with Native Apps (#960) (Friday, 16 September)

Last message date: Friday, 30 September 2016 23:46:01 UTC