[webidl] typo in the definition of an unrestricted double? (#51)
[dom] Proposal: Node#appendSibling/prependSibling (#38)
Re: [manifest] camelCase more suitable to JSON and JS API (#72)
[permissions] status of this document: reached FPWD (#36)
[clipboard-apis] What should happen when copying content with a CANVAS tag in?` (#8)
[IndexedDB] Allow renaming object stores and indexes (#22)
Re: [editing] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
Re: [editing] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
Re: [editing] What intentions do we need? (#52)
- Re: [editing] What intentions do we need? (#52)
- Re: [editing] What intentions do we need? (#52)
- Re: [editing] What intentions do we need? (#52)
- Re: [editing] What intentions do we need? (#52)
- Re: [editing] What intentions do we need? (#52)
- Re: [editing] What intentions do we need? (#52)
[streams] More concrete examples of "optimization" of pipeTo (#359)
[ServiceWorker] What's proper SW name? :) (#705)
Re: [webcomponents] Describe focus navigation order for the case with tabindex=-1 (#35)
Re: [webcomponents] Change the order of insertion points which are involved in a re-distribution in event path (W3C bug 23887) (#42)
Re: [streams] Transform streams and acknowledgement of writes (#329)
- Re: [streams] Transform streams and acknowledgement of writes (#329)
- Re: [streams] Transform streams and acknowledgement of writes (#329)
- Re: [streams] Transform streams and acknowledgement of writes (#329)
- Re: [streams] Transform streams and acknowledgement of writes (#329)
- Re: [streams] Transform streams and acknowledgement of writes (#329)
- Re: [streams] Transform streams and acknowledgement of writes (#329)
[filesystem-api] Observable is not appropriate for directory listing; async iterable would be better (#4)
- Re: [filesystem-api] Observable is not appropriate for directory listing; async iterable would be better (#4)
- Re: [filesystem-api] Observable is not appropriate for directory listing; async iterable would be better (#4)
- Re: [filesystem-api] Observable is not appropriate for directory listing; async iterable would be better (#4)
- Re: [filesystem-api] Observable is not appropriate for directory listing; async iterable would be better (#4)
- Re: [filesystem-api] Observable is not appropriate for directory listing; async iterable would be better (#4)
- Re: [filesystem-api] Observable is not appropriate for directory listing; async iterable would be better (#4)
[xhr] Abandon hope of removing sync XHR from the web platform? (#20)
- Re: [xhr] Abandon hope of removing sync XHR from the web platform? (#20)
- Re: [xhr] Abandon hope of removing sync XHR from the web platform? (#20)
- Re: [xhr] Abandon hope of removing sync XHR from the web platform? (#20)
- Re: [xhr] Abandon hope of removing sync XHR from the web platform? (#20)
Re: [ServiceWorker] Workers & SharedWorkers within ServiceWorkers (#678)
[fetch] response.bodyUsed is an ambiguous name (#57)
[streams] Never-released lock / getReader({unreleasable: true}) (#358)
[FileAPI] Controlling Blob URL's (#8)
[editing-explainer] what intentions do we need? (#52)
- Re: [editing-explainer] What intentions do we need? (#52)
- Re: [editing-explainer] What intentions do we need? (#52)
- Re: [editing-explainer] What intentions do we need? (#52)
- Re: [editing-explainer] What intentions do we need? (#52)
- Re: [editing-explainer] What intentions do we need? (#52)
- Re: [editing-explainer] What intentions do we need? (#52)
[IndexedDB] Support binary keys (#21)
Re: [editing-explainer] What should be the target element for Responsive Input Events? (#24)
Re: [ServiceWorker] Define the lifetime of a blob URL created inside a service worker (#688)
Re: [editing-explainer] Need to be clear about users having control, then sites, then browser (#13)
[ServiceWorker] How to deal with cookie bombing (#704)
[ServiceWorker] Receivers of ranged responses must ensure all ranges come from the same underlying resource (#703)
[editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handeling? (#57)
- Re: [editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
- Re: [editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
- Re: [editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
- Re: [editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
- Re: [editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
- Re: [editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
- Re: [editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
- Re: [editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
- Re: [editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
- Re: [editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
- Re: [editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
- Re: [editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
- Re: [editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
- Re: [editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
- Re: [editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
- Re: [editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
- Re: [editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
- Re: [editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
- Re: [editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
- Re: [editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
- Re: [editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
- Re: [editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
- Re: [editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
- Re: [editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
- Re: [editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
- Re: [editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
- Re: [editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
- Re: [editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
- Re: [editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
- Re: [editing-explainer] Can we use textnodes, and block/inline nodes as shadow roots for transparent IME handling? (#57)
[editing-explainer] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing-explainer] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing-explainer] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing-explainer] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing-explainer] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing-explainer] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing-explainer] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing-explainer] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing-explainer] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing-explainer] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing-explainer] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing-explainer] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing-explainer] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing-explainer] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing-explainer] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing-explainer] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing-explainer] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing-explainer] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing-explainer] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing-explainer] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing-explainer] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing-explainer] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing-explainer] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing-explainer] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
- Re: [editing-explainer] What browser internals can be exposed to help us move the caret in (and against) the block direction? (#56)
[editing-explainer] switch caret between overtype and insert (#55)
Re: [editing-explainer] How can we integrate with rich forms and validation? (#6)
Re: [editing-explainer] Should sites be able to control Responsive Input Language? (#31)
Re: [editing-explainer] How does cE=typing work with overtype (insert key is on) (#28)
[editing-explainer] What to do with execCommand (#53)
[editing-explainer] What to do with contentEditableTrue? (#54)
Re: [editing-explainer] Notification after completion of Responsive Input Event (especially "custom" event types) (#17)
[fetch] Document usage for GET requests with URI parameters (#56)
[webcomponents] [Shadow]: Focus navigation in distributed content (#103)
- Re: [webcomponents] [Shadow]: Focus navigation in distributed content (#103)
- Re: [webcomponents] [Shadow]: Focus navigation in distributed content (#103)
- Re: [webcomponents] [Shadow]: Focus navigation in distributed content (#103)
- Re: [webcomponents] [Shadow]: Focus navigation in distributed content (#103)
- Re: [webcomponents] [Shadow]: Focus navigation in distributed content (#103)
- Re: [webcomponents] [Shadow]: Focus navigation in distributed content (#103)
- Re: [webcomponents] [Shadow]: Focus navigation in distributed content (#103)
- Re: [webcomponents] [Shadow]: Focus navigation in distributed content (#103)
- Re: [webcomponents] [Shadow]: Focus navigation in distributed content (#103)
- Re: [webcomponents] [Shadow]: Focus navigation in distributed content (#103)
[editing-explainer] legal caret states (#51)
- Re: [editing-explainer] What caret positions do we need to allow? (#51)
- Re: [editing-explainer] What caret positions do we need to allow? (#51)
- Re: [editing-explainer] What caret positions do we need to allow? (#51)
- Re: [editing-explainer] What caret positions do we need to allow? (#51)
- Re: [editing-explainer] What caret positions do we need to allow? (#51)
- Re: [editing-explainer] What caret positions do we need to allow? (#51)
[push-api] getSubscription() should permission check (#150)
[IndexedDB] Ensure connection/handle properties are snapshots (#20)
[xhr] Remove XMLHttpRequest from ServiceWorkerGlobalScope (#19)
[dom] Consider new method: getNodesByType (#37)
- Re: [dom] Consider new method: getNodesByType (#37)
- Re: [dom] Consider new method: getNodesByType (#37)
- Re: [dom] Consider new method: getNodesByType (#37)
- Re: [dom] Consider new method: getNodesByType (#37)
- Re: [dom] Consider new method: getNodesByType (#37)
- Re: [dom] Consider new method: getNodesByType (#37)
[webidl] Distinguishability of buffers source types needs to be defined better (#50)
Re: [editing-explainer] ContentEditable with UserSelect=None needs to be documented (#20)
- Re: [editing-explainer] ContentEditable with UserSelect=None needs to be documented (#20)
- Re: [editing-explainer] ContentEditable with UserSelect=None needs to be documented (#20)
- Re: [editing-explainer] ContentEditable with UserSelect=None needs to be documented (#20)
- Re: [editing-explainer] ContentEditable with UserSelect=None needs to be documented (#20)
- Re: [editing-explainer] ContentEditable with UserSelect=None needs to be documented (#20)
- Re: [editing-explainer] ContentEditable with UserSelect=None needs to be documented (#20)
- Re: [editing-explainer] ContentEditable with UserSelect=None needs to be documented (#20)
- Re: [editing-explainer] ContentEditable with UserSelect=None needs to be documented (#20)
- Re: [editing-explainer] ContentEditable with UserSelect=None needs to be documented (#20)
- Re: [editing-explainer] ContentEditable with UserSelect=None needs to be documented (#20)
Re: [editing-explainer] Target range in device independent events (#39)
[editing-explainer] replaceText input event could span multiple Typing Nodes (#50)
- Re: [editing-explainer] replaceText input event could span multiple Typing Nodes (#50)
- Re: [editing-explainer] replaceText input event could span multiple Typing Nodes (#50)
- Re: [editing-explainer] replaceText input event could span multiple Typing Nodes (#50)
- Re: [editing-explainer] replaceText input event could span multiple Typing Nodes (#50)
- Re: [editing-explainer] replaceText input event could span multiple Typing Nodes (#50)
- Re: [editing-explainer] replaceText input event could span multiple Typing Nodes (#50)
- Re: [editing-explainer] replaceText input event could span multiple Typing Nodes (#50)
- Re: [editing-explainer] replaceText input event could span multiple Typing Nodes (#50)
- Re: [editing-explainer] replaceText input event could span multiple Typing Nodes (#50)
- Re: [editing-explainer] replaceText input event could span multiple Typing Nodes (#50)
- Re: [editing-explainer] replaceText input event could span multiple Typing Nodes (#50)
- Re: [editing-explainer] replaceText input event could span multiple Typing Nodes (#50)
- Re: [editing-explainer] replaceText input event could span multiple Typing Nodes (#50)
- Re: [editing-explainer] replaceText input event could span multiple Typing Nodes (#50)
- Re: [editing-explainer] replaceText input event could span multiple Typing Nodes (#50)
- Re: [editing-explainer] replaceText input event could span multiple Typing Nodes (#50)
- Re: [editing-explainer] spell checking should be able to span multiple Typing Nodes (#50)
- Re: [editing-explainer] spell checking should be able to span multiple Typing Nodes (#50)
- Re: [editing-explainer] spell checking should be able to span multiple Typing Nodes (#50)
- Re: [editing-explainer] spell checking should be able to span multiple Typing Nodes (#50)
- Re: [editing-explainer] spell checking should be able to span multiple Typing Nodes (#50)
- Re: [editing-explainer] spell checking should be able to span multiple Typing Nodes (#50)
- Re: [editing-explainer] spell checking should be able to span multiple Typing Nodes (#50)
- Re: [editing-explainer] spell checking should be able to span multiple Typing Nodes (#50)
- Re: [editing-explainer] spell checking should be able to span multiple Typing Nodes (#50)
- Re: [editing-explainer] spell checking should be able to span multiple Typing Nodes (#50)
- Re: [editing-explainer] spell checking should be able to span multiple Typing Nodes (#50)
- Re: [editing-explainer] spell checking should be able to span multiple Typing Nodes (#50)
- Re: [editing-explainer] spell checking should be able to span multiple Typing Nodes (#50)
- Re: [editing-explainer] spell checking should be able to span multiple Typing Nodes (#50)
- Re: [editing-explainer] spell checking should be able to span multiple Typing Nodes (#50)
Re: [editing-explainer] intents originating from components resp. scripts (#16)
Re: [editing-explainer] Support for custom Responsive Input events (#14)
Re: [editing-explainer] Prevent recursive beforeInput calls (#44)
Re: [editing-explainer] How can sites access browser spellchecking? (#36)
- Re: [editing-explainer] How can sites access browser spellchecking? (#36)
- Re: [editing-explainer] How can sites access browser spellchecking? (#36)
- Re: [editing-explainer] How can sites access browser spellchecking? (#36)
- Re: [editing-explainer] How can sites access browser spellchecking? (#36)
- Re: [editing-explainer] How can sites access browser spellchecking? (#36)
- Re: [editing-explainer] How can sites access browser spellchecking? (#36)
- Re: [editing-explainer] How can sites access browser spellchecking? (#36)
- Re: [editing-explainer] How can sites access browser spellchecking? (#36)
- Re: [editing-explainer] How can sites access browser spellchecking? (#36)
- Re: [editing-explainer] How can sites access browser spellchecking? (#36)
- Re: [editing-explainer] How can sites access browser spellchecking? (#36)
- Re: [editing-explainer] How can sites access browser spellchecking? (#36)
- Re: [editing-explainer] How can sites access browser spellchecking? (#36)
- Re: [editing-explainer] How can sites access browser spellchecking? (#36)
- Re: [editing-explainer] How can sites access browser spellchecking? (#36)
- Re: [editing-explainer] How can sites access browser spellchecking? (#36)
[editing-explainer] formatting events (#49)
Re: [editing-explainer] Should undo/redo be beforeInput events? (#30)
- Re: [editing-explainer] Should undo/redo be beforeInput events? (#30)
- Re: [editing-explainer] Should undo/redo be beforeInput events? (#30)
Re: [editing-explainer] D3E defines input event should be fired immediately after the DOM as been updated but it shouldn't be so if the editor value is changed by setting value attribute (#41)
Re: [editing-explainer] beforeinput should be fired only when the DOM change is caused by direct input by keypress or composition (#43)
Re: [editing-explainer] how does cE=typing handle autocorrect and spelling suggestions? (#37)
Re: [ServiceWorker] WebRTC and getUserMedia within Service Worker (#670)
- Re: [ServiceWorker] WebRTC and getUserMedia within Service Worker (#670)
- Re: [ServiceWorker] WebRTC and getUserMedia within Service Worker (#670)
- Re: [ServiceWorker] WebRTC and getUserMedia within Service Worker (#670)
- Re: [ServiceWorker] WebRTC and getUserMedia within Service Worker (#670)
- Re: [ServiceWorker] WebRTC and getUserMedia within Service Worker (#670)
- Re: [ServiceWorker] WebRTC and getUserMedia within Service Worker (#670)
- Re: [ServiceWorker] WebRTC and getUserMedia within Service Worker (#670)
- Re: [ServiceWorker] WebRTC and getUserMedia within Service Worker (#670)
- Re: [ServiceWorker] WebRTC and getUserMedia within Service Worker (#670)
[webcomponents] [Shadow] Change the order of insertion points which are involved in a re-distribution in event path (bugzilla: 23887) (#98)
[webcomponents] [Shadow]: The return type of Event.path should leverage WebIDL sequences (bugzilla: 25458) (#101)
- Re: [webcomponents] [Shadow]: The return type of Event.path should leverage WebIDL sequences (bugzilla: 25458) (#101)
- Re: [webcomponents] [Shadow]: The return type of Event.path should leverage WebIDL sequences (bugzilla: 25458) (#101)
[webcomponents] [Shadow]: Add "closed" flag to createShadowRoot (bugzilla: 20144) (#100)
[webcomponents] [Shadow]: Consider a notion of shared stylesheet (bugzilla: 15818) (#99)
[webcomponents] [Shadow]: Element.createShadowRoot() throws an exception for some elements (bugzilla: 27844) (#102)
[webcomponents] [Shadow]: how is the autofocus attribute supposed to be handled? (bugzilla: 27757) (#97)
[webcomponents] [Shadow]: There's isn't a way to append shadow elements in SVG (bugzilla: 24181) (#96)
[webcomponents] [Shadow]: <content> usage in a place where non-flow content is expected (bugzilla: 22107) (#95)
[webcomponents] [Shadow]: Consider explicitly exporting CSS Variables across a shadow boundary (bugzilla: 17143) (#94)
[webcomponents] [Shadow]: Inheritance Model for Shadow DOM (bugzilla: 28587) (#93)
[webcomponents] [Shadow]: rename <content> to <slot> (bugzilla: 28561) (#92)
- Re: [webcomponents] [Shadow]: rename <content> to <slot> (bugzilla: 28561) (#92)
- Re: [webcomponents] [Shadow]: rename <content> to <slot> (bugzilla: 28561) (#92)
- Re: [webcomponents] [Shadow]: rename <content> to <slot> (bugzilla: 28561) (#92)
- Re: [webcomponents] [Shadow]: rename <content> to <slot> (bugzilla: 28561) (#92)
- Re: [webcomponents] [Shadow]: rename <content> to <slot> (bugzilla: 28561) (#92)
- Re: [webcomponents] [Shadow]: rename <content> to <slot> (bugzilla: 28561) (#92)
- Re: [webcomponents] [Shadow]: rename <content> to <slot> (bugzilla: 28561) (#92)
- Re: [webcomponents] [Shadow]: rename <content> to <slot> (bugzilla: 28561) (#92)
- Re: [webcomponents] [Shadow]: rename <content> to <slot> (bugzilla: 28561) (#92)
[webcomponents] [Shadow]: Have a common interface between Document and ShadowRoot (bugzilla: 28493) (#91)
[webcomponents] [Shadow]: Consider removal of multiple shadow roots (bugzilla: 28446) (#90)
[webcomponents] [Shadow]: Make event retargeting optional (bugzilla: 28444) (#89)
[webcomponents] [Shadow]: inappropriate reference to CSS3-UI nav-index spec in focus navigation order (bugzilla: 28079) (#88)
[webcomponents] [Shadow]: Define the behavior of *closed* shadow trees. (bugzilla: 27775) (#85)
[webcomponents] [Shadow]: Multiple trees are introduced to explain encapsulation. (bugzilla: 23481) (#83)
[webcomponents] [Shadow]: Distribution needs to not be observable (bugzilla: 27994) (#87)
[webcomponents] [Shadow]: Shadow host with tabindex=-1, all descendent tree should be ignored for tab navigation (bugzilla: 27965) (#86)
[webcomponents] [Shadow]: Need mechanism to tell if an element in a ShadowRoot has been inserted into the Document (bugzilla: 22141) (#81)
[webcomponents] [Shadow]: Each section on the spec needs examples (bugzilla: 24639) (#84)
[webcomponents] [Shadow]: Add support for external stylesheets using link rel="stylesheet" (bugzilla: 22539) (#82)
[webcomponents] [Shadow]: Node should expose their scope so that shared state can be scoped to components. (bugzilla: 22080) (#80)
[webcomponents] [Shadow]: Find a way for selection to work across shadow DOM subtrees (bugzilla: 15444) (#79)
[webcomponents] [Shadow]: Figure out a good replacement for /deep/ in testing scenarios (bugzilla: 28591) (#78)
[webcomponents] [Shadow]: Event model (bugzilla: 28564) (#77)
[webcomponents] [Shadow] investigate if there should be deepRelatedTargets and touch.deepTargets (bugzilla: 28560) (#76)
[webcomponents] [Shadow]: Shadow DOM v1 (bugzilla: 28552) (#75)
- Re: [webcomponents] [Shadow]: Shadow DOM v1 (bugzilla: 28552) (#75)
- Re: [webcomponents] [Shadow]: Shadow DOM v1 (bugzilla: 28552) (#75)
[webcomponents] [Shadow]: Add [TreatNullAs=EmptyString] to ShadowRoot.innerHTML (bugzilla: 28549) (#74)
[webcomponents] [Shadow]: Specify distribution in terms of event loop (bugzilla: 28443) (#73)
[webcomponents] [Shadow]: Fully explore composition (bugzilla: 27401) (#69)
[webcomponents] [Shadow]: Isolated Shadow trees (bugzilla: 28442) (#72)
[webcomponents] [Shadow]: Consider not using AT_TARGET more than once in the event path (bugzilla: 26892) (#68)
[webcomponents] [Shadow]: Declarative Shadow DOM (bugzilla: 28441) (#71)
[webcomponents] [Shadow]: Need to define what .styleSheets actually does on a shadow root (bugzilla: 27418) (#70)
[webcomponents] [Shadow]: elementFromPoint should return the host when you hit a Text node (bugzilla: 24638) (#67)
[webcomponents] [Shadow]: url fragment identifiers should be followed into ShadowDOM (bugzilla: 23161) (#66)
[webcomponents] [Shadow]: Form elements crossing shadow boundary (bugzilla: 22443) (#65)
[webcomponents] [Shadow]: Consider a <content> selector for "nodes not otherwise distributed" (bugzilla: 22268) (#64)
[webcomponents] [Shadow]: Need an equivalent definition of 'in a Document' for shadow trees (bugzilla: 26365) (#57)
[webcomponents] [Shadow]: Shadow DOM-based components could benefit from a way to detect when light DOM contents change (bugzilla: 21149) (#62)
[webcomponents] [Shadow]: Shadow trees should somehow contain base URL information (bugzilla: 22255) (#63)
[webcomponents] [Shadow]: Update constraints around stopping events (bugzilla: 20247) (#61)
[webcomponents] [Shadow]: Specify imperative API for node distribution (bugzilla: 18429) (#60)
[webcomponents] [Shadow]: Consider augmenting HTML parser to parse <shadow> and <content> just like <template> (bugzilla: 15616) (#59)
[webcomponents] [Shadow]: Shadow DOM V2 (bugzilla: 15480) (#58)
- Re: [webcomponents] [Shadow]: Shadow DOM V2 (bugzilla: 15480) (#58)
- Re: [webcomponents] [Shadow]: Shadow DOM V2 (bugzilla: 15480) (#58)
[webcomponents] [Shadow]: Style element should specify when to create and add style sheet in shadow DOM (bugzilla: 26850) (#56)
Re: [editing-explainer] How does cE=typing support IME text replacement? (#34)
- Re: [editing-explainer] How does cE=typing support IME text replacement? (#34)
- Re: [editing-explainer] How does cE=typing support IME text replacement? (#34)
Re: [editing-explainer] How should custom controls declare their Responsive Input mapping? (#18)
- Re: [editing-explainer] How should custom controls declare their Responsive Input mapping? (#18)
- Re: [editing-explainer] How should custom controls declare their Responsive Input mapping? (#18)
Re: [editing-explainer] behavior of text nodes inside cE=typing (#22)
Re: [fetch] Add about:unicorn easter egg. (de21fbc)
[IndexedDB] Introduce IDBKeySet (#19)
[IndexedDB] Add scope attribute to IDBTransaction (#18)
[dom] Add [TreatNullAs=EmptyString] to Attr.nodeValue/textContent (#36)
- Re: [dom] Add [TreatNullAs=EmptyString] to Attr.nodeValue/textContent (#36)
- Re: [dom] Add [TreatNullAs=EmptyString] to Attr.nodeValue/textContent (#36)
[ServiceWorker] Cache API shouldn't be available outside the service workers (#702)
- Re: [ServiceWorker] Cache API shouldn't be available outside the service workers (#702)
- Re: [ServiceWorker] Cache API shouldn't be available outside the service workers (#702)
[webcomponents] id -> name (#55)
Re: [spec-reviews] rough in fingerprinting (ba748e3)
- Re: [spec-reviews] rough in fingerprinting (ba748e3)
- Re: [spec-reviews] rough in fingerprinting (ba748e3)
- Re: [spec-reviews] rough in fingerprinting (ba748e3)
- Re: [spec-reviews] rough in fingerprinting (ba748e3)
- Re: [spec-reviews] rough in fingerprinting (ba748e3)
[webcomponents] Typo ;) (#54)
Re: [spec-reviews] Navigation Error Logging (#24)
[IndexedDB] transaction (concept) should have an error property (#17)
[IndexedDB] Replace DOMError with DOMException (#16)
[webcomponents] Added a couple of algorithms and definitions. (#53)
- Re: [webcomponents] Added a couple of algorithms and definitions. (#53)
- Re: [webcomponents] Added a couple of algorithms and definitions. (#53)
- Re: [webcomponents] Added a couple of algorithms and definitions. (#53)
Re: [spec-reviews] CSS Font Loading (#20)
- Re: [spec-reviews] CSS Font Loading (#20)
- Re: [spec-reviews] CSS Font Loading (#20)
- Re: [spec-reviews] CSS Font Loading (#20)
- Re: [spec-reviews] CSS Font Loading (#20)
- Re: [spec-reviews] CSS Font Loading (#20)
[push-api] pushregistrationlost isn't documented (#149)
- Re: [push-api] pushregistrationlost isn't documented (#149)
- Re: [push-api] pushregistrationlost isn't documented (#149)
- Re: [push-api] pushregistrationlost isn't documented (#149)
- Re: [push-api] pushregistrationlost isn't documented (#149)
- Re: [push-api] pushregistrationlost isn't documented (#149)
- Re: [push-api] pushregistrationlost isn't documented (#149)
Re: [push-api] Fire pushsubscriptionchange when user revokes permission (#116)
[push-api] Making cardinality clear (#148)
Re: [spec-reviews] Browser Fingerprinting Document (#38)
Re: [spec-reviews] Credential Management API (#49)
Re: [spec-reviews] CSV on the Web (#55)
Re: [fetch] Cache state: partial content (#38)
Re: [push-api] Push events should Soft Update service worker (#115)
[ServiceWorker] Consider dropping initServiceWorkerMessageEvent() (#701)
- Re: [ServiceWorker] Consider dropping initServiceWorkerMessageEvent() (#701)
- Re: [ServiceWorker] Consider dropping initServiceWorkerMessageEvent() (#701)
- Re: [ServiceWorker] Consider dropping initServiceWorkerMessageEvent() (#701)
- Re: [ServiceWorker] Consider dropping initServiceWorkerMessageEvent() (#701)
[IndexedDB] Import issues from Bugzilla (#15)
[webcomponents] Stubbed out Slots proposal. (#52)
[IndexedDB] Add openCursor(key, primaryKey) and continuePrimaryKey (#14)
[IndexedDB] Consider introducing "unbounded range" (#13)
[IndexedDB] Standardize key-or-keyrange argument handling (#12)
[fetch] Request constructor does not check used flag on null body (#55)
[clipboard-apis] Behavior of queryCommandEnabled (#7)
[fetch] Rename `response` in HTTP fetch 3.1.1-2 (#54)
Re: [editing-explainer] execCommand has now been spec'd to trigger a "User Intent" for cut/copy/paste (#47)
Re: [ServiceWorker] A header/something to kill SWs (#614)
Re: [ServiceWorker] Navigating clients from the SW context? (#681)
- Re: [ServiceWorker] Navigating clients from the SW context? (#681)
- Re: [ServiceWorker] Navigating clients from the SW context? (#681)
- Re: [ServiceWorker] Navigating clients from the SW context? (#681)
[encoding] Benefits of "Legacy" Encodings – Byte Counter (#4)
- Re: [encoding] Benefits of "Legacy" Encodings – Byte Counter (#4)
- Re: [encoding] Benefits of "Legacy" Encodings – Byte Counter (#4)
- Re: [encoding] Benefits of "Legacy" Encodings – Byte Counter (#4)
- Re: [encoding] Benefits of "Legacy" Encodings – Byte Counter (#4)
- Re: [encoding] Benefits of "Legacy" Encodings – Byte Counter (#4)
- Re: [encoding] Benefits of "Legacy" Encodings – Byte Counter (#4)
Re: [streams] Add readableStream.locked getter (0c57047)
- Re: [streams] Add readableStream.locked getter (0c57047)
- Re: [streams] Add readableStream.locked getter (0c57047)
- Re: [streams] Add readableStream.locked getter (0c57047)
- Re: [streams] Add readableStream.locked getter (0c57047)
[ServiceWorker] ServiceWorker registration fails inside an https-origin IFRAME when the top-level page is not secure (e.g. http or data URI) (#700)
- Re: [ServiceWorker] ServiceWorker registration fails inside an https-origin IFRAME when the top-level page is not secure (e.g. http or data URI) (#700)
- Re: [ServiceWorker] ServiceWorker registration fails inside an https-origin IFRAME when the top-level page is not secure (e.g. http or data URI) (#700)
- Re: [ServiceWorker] ServiceWorker registration fails inside an https-origin IFRAME when the top-level page is not secure (e.g. http or data URI) (#700)
- Re: [ServiceWorker] ServiceWorker registration fails inside an https-origin IFRAME when the top-level page is not secure (e.g. http or data URI) (#700)
- Re: [ServiceWorker] ServiceWorker registration fails inside an https-origin IFRAME when the top-level page is not secure (e.g. http or data URI) (#700)
- Re: [ServiceWorker] ServiceWorker registration fails inside an https-origin IFRAME when the top-level page is not secure (e.g. http or data URI) (#700)
[streams] Add readableStream.locked getter (#357)
[IndexedDB] Validate exception ordering against implementations (#11)
[IndexedDB] Standardize relationship between concept-objects and interface-objects (#10)
[editing-explainer] define relation to HTML Editing APIs (#48)
- Re: [editing-explainer] define relation to HTML Editing APIs (#48)
- Re: [editing-explainer] define relation to HTML Editing APIs (#48)
- Re: [editing-explainer] define relation to HTML Editing APIs (#48)
- Re: [editing-explainer] define relation to HTML Editing APIs (#48)
- Re: [editing-explainer] define relation to HTML Editing APIs (#48)
- Re: [editing-explainer] define relation to HTML Editing APIs (#48)
- Re: [editing-explainer] define relation to HTML Editing APIs (#48)
Re: [ServiceWorker] navigator.serviceWorker is not defined (#689)
[ServiceWorker] Restrict openWindow() to http(s) schemes? (#699)
[fetch] Abort fetch upon unload document unload (#53)
[fetch] CSP Request Header and CORS preflight fetch. (#52)
- Re: [fetch] CSP Request Header and CORS preflight fetch. (#52)
- Re: [fetch] CSP Request Header and CORS preflight fetch. (#52)
Re: [manifest] Ability to define platform-specific icon style (#361)
[webstorage] Make sample code indent consistent (#3)
[IndexedDB] task behavior for open requests is poorly specified (#9)
Re: [IndexedDB] Asynchronously completed operations should "queue a task" (#1)
Re: [IndexedDB] Define key extraction/injection using [[DefineOwnProperty]] and [[Get]] (#2)
[fetch] HTTP/2 server push support (#51)
Re: [fetch] Access to the HTTP trailer (#34)
- Re: [fetch] Access to the HTTP trailer (#34)
- Re: [fetch] Access to the HTTP trailer (#34)
- Re: [fetch] Access to the HTTP trailer (#34)
- Re: [fetch] Access to the HTTP trailer (#34)
- Re: [fetch] Access to the HTTP trailer (#34)
Re: [manifest] i18n: No localization model; [I18N-ISSUE-412] (#338)
- Re: [manifest] i18n: No localization model; [I18N-ISSUE-412] (#338)
- Re: [manifest] i18n: No localization model; [I18N-ISSUE-412] (#338)
- Re: [manifest] i18n: No localization model; [I18N-ISSUE-412] (#338)
- Re: [manifest] i18n: No localization model; [I18N-ISSUE-412] (#338)
- Re: [manifest] i18n: No localization model; [I18N-ISSUE-412] (#338)
- Re: [manifest] i18n: No localization model; [I18N-ISSUE-412] (#338)
- Re: [manifest] i18n: No localization model; [I18N-ISSUE-412] (#338)
Re: [fetch] XHR option to trigger busy indicators (#19)
- Re: [fetch] XHR option to trigger busy indicators (#19)
- Re: [fetch] XHR option to trigger busy indicators (#19)
- Re: [fetch] XHR option to trigger busy indicators (#19)
- Re: [fetch] XHR option to trigger busy indicators (#19)
- Re: [fetch] XHR option to trigger busy indicators (#19)
- Re: [fetch] XHR option to trigger busy indicators (#19)
- Re: [fetch] XHR option to trigger busy indicators (#19)
- Re: [fetch] XHR option to trigger busy indicators (#19)
- Re: [fetch] XHR option to trigger busy indicators (#19)
- Re: [fetch] XHR option to trigger busy indicators (#19)
- Re: [fetch] XHR option to trigger busy indicators (#19)
- Re: [fetch] XHR option to trigger busy indicators (#19)
- Re: [fetch] XHR option to trigger busy indicators (#19)
[IndexedDB] Introduce Upgrades as concept section (#8)
- Re: [IndexedDB] Introduce Upgrades as concept section (#8)
- Re: [IndexedDB] Introduce Upgrades as concept section (#8)
[webcomponents] Timing experiment (#51)
Re: [streams] Added some more readable stream tests (#315)
- Re: [streams] Added some more readable stream tests (#315)
- Re: [streams] Added some more readable stream tests (#315)
[dom] Add hint that `event.bubbles` is configurable. (#35)
[webstorage] w3c stylesheet needs to be httpS (#2)
Re: [webstorage] Add link to "live" version of the spec. (#1)
Re: [ServiceWorker] under what conditions should sandboxed iframes be intercepted? (#648)
- Re: [ServiceWorker] under what conditions should sandboxed iframes be intercepted? (#648)
- Re: [ServiceWorker] under what conditions should sandboxed iframes be intercepted? (#648)
- Re: [ServiceWorker] under what conditions should sandboxed iframes be intercepted? (#648)
- Re: [ServiceWorker] under what conditions should sandboxed iframes be intercepted? (#648)
Re: [manifest] What's the use case for theme_color? (#356)
[IndexedDB] Specify 'deleted' property of stores/indexes (#7)
- Re: [IndexedDB] Specify 'deleted' property of stores/indexes (#7)
- Re: [IndexedDB] Specify 'deleted' property of stores/indexes (#7)
- Re: [IndexedDB] Specify 'deleted' property of stores/indexes (#7)
[ServiceWorker] Should window.caches be removed (or readonly) for security reasons? (#698)
- Re: [ServiceWorker] Should window.caches be removed (or readonly) for security reasons? (#698)
- Re: [ServiceWorker] Should window.caches be removed (or readonly) for security reasons? (#698)
- Re: [ServiceWorker] Should window.caches be removed (or readonly) for security reasons? (#698)
- Re: [ServiceWorker] Should window.caches be removed (or readonly) for security reasons? (#698)
- Re: [ServiceWorker] Should window.caches be removed (or readonly) for security reasons? (#698)
- Re: [ServiceWorker] Should window.caches be removed (or readonly) for security reasons? (#698)
- Re: [ServiceWorker] Should window.caches be removed (or readonly) for security reasons? (#698)
- Re: [ServiceWorker] Should window.caches be removed (or readonly) for security reasons? (#698)
- Re: [ServiceWorker] Should window.caches be removed (or readonly) for security reasons? (#698)
- Re: [ServiceWorker] Should window.caches be removed (or readonly) for security reasons? (#698)
- Re: [ServiceWorker] Should window.caches be removed (or readonly) for security reasons? (#698)
- Re: [ServiceWorker] Should window.caches be removed (or readonly) for security reasons? (#698)
- Re: [ServiceWorker] Should window.caches be removed (or readonly) for security reasons? (#698)
- Re: [ServiceWorker] Should window.caches be removed (or readonly) for security reasons? (#698)
- Re: [ServiceWorker] Should window.caches be removed (or readonly) for security reasons? (#698)
- Re: [ServiceWorker] Should window.caches be removed (or readonly) for security reasons? (#698)
- Re: [ServiceWorker] Should window.caches be removed (or readonly) for security reasons? (#698)
- Re: [ServiceWorker] Should window.caches be removed (or readonly) for security reasons? (#698)
- Re: [ServiceWorker] Should window.caches be removed (or readonly) for security reasons? (#698)
- Re: [ServiceWorker] Should window.caches be removed (or readonly) for security reasons? (#698)
- Re: [ServiceWorker] Should window.caches be removed (or readonly) for security reasons? (#698)
- Re: [ServiceWorker] Should window.caches be removed (or readonly) for security reasons? (#698)
- Re: [ServiceWorker] Should window.caches be removed (or readonly) for security reasons? (#698)
- Re: [ServiceWorker] Should window.caches be removed (or readonly) for security reasons? (#698)
- Re: [ServiceWorker] Should window.caches be removed (or readonly) for security reasons? (#698)
- Re: [ServiceWorker] Should window.caches be removed (or readonly) for security reasons? (#698)
[IndexedDB] database version in deleteDatabase is not defined (#6)
Re: [ServiceWorker] You don't need any flags in Chrome today :) (#686)
[spec-reviews] Remove 'signal upgrade' section in upgrade-insecure review (#58)
[dom] insert/remove hooks need to be invoked for ancestor changes too (#34)
Re: [manifest] Are "hosted apps" in scope? (#340)
Re: [manifest] Won't related_application be needed at page load? (#364)
[manifest] Provide better examples of scope (#380)
- Re: [manifest] Provide better examples of scope (#380)
- Re: [manifest] Provide better examples of scope (#380)
- Re: [manifest] Provide better examples of scope (#380)
- Re: [manifest] Provide better examples of scope (#380)
- Re: [manifest] Provide better examples of scope (#380)
[clipboard-apis] Fix the handling of the default cut action when we're not in an editable context (#6)
[clipboard-apis] Fix the handling of password fields with the copy and cut actions (#5)
- Re: [clipboard-apis] Fix the handling of password fields with the copy and cut actions (#5)
- Re: [clipboard-apis] Fix the handling of password fields with the copy and cut actions (#5)
[IndexedDB] Convert remaining methods to "algorithmic style" (#5)
- Re: [IndexedDB] Convert remaining methods to "algorithmic style" (#5)
- Re: [IndexedDB] Convert remaining methods to "algorithmic style" (#5)
[IndexedDB] Keypath evaluation steps yield a value, not a key (#4)
[touch-events] Spec should be explicit on whether the of elements in TouchLists is relevant (#13)
- Re: [touch-events] Spec should be explicit on whether the of elements in TouchLists is relevant (#13)
- Re: [touch-events] Spec should be explicit on whether the of elements in TouchLists is relevant (#13)
- Re: [touch-events] Spec should be explicit on whether the of elements in TouchLists is relevant (#13)
- Re: [touch-events] Spec should be explicit on whether the of elements in TouchLists is relevant (#13)
- Re: [touch-events] Spec should be explicit on whether the of elements in TouchLists is relevant (#13)
[ServiceWorker] Fallback to App Cache (#697)
- Re: [ServiceWorker] Fallback to App Cache (#697)
- Re: [ServiceWorker] Fallback to App Cache (#697)
- Re: [ServiceWorker] Fallback to App Cache (#697)
- Re: [ServiceWorker] Fallback to App Cache (#697)
[clipboard-apis] Should queryCommandEnabled(cut|copy|paste) trigger onbefore* events? (#4)
Re: [streams] rsReader.readBatch(numberOfChunks)? rbsReader.read(view, { waitUntilDone: true })? (#320)
- Re: [streams] rsReader.readBatch(numberOfChunks)? rbsReader.read(view, { waitUntilDone: true })? (#320)
- Re: [streams] rsReader.readBatch(numberOfChunks)? rbsReader.read(view, { waitUntilDone: true })? (#320)
- Re: [streams] rsReader.readBatch(numberOfChunks)? rbsReader.read(view, { waitUntilDone: true })? (#320)
- Re: [streams] rsReader.readBatch(numberOfChunks)? rbsReader.read(view, { waitUntilDone: true })? (#320)
- Re: [streams] rsReader.readBatch(numberOfChunks)? rbsReader.read(view, { waitUntilDone: true })? (#320)
Re: [ServiceWorker] There should be no such thing as "fail to activate" (#659)
- Re: [ServiceWorker] There should be no such thing as "fail to activate" (#659)
- Re: [ServiceWorker] There should be no such thing as "fail to activate" (#659)
Re: [webcomponents] [Shadow DOM] [Bug 27775] Update Element.getDestinationInsertionPoints(), using the 'an unclosed node of' relation'. (644a0fa)
- Re: [webcomponents] [Shadow DOM] [Bug 27775] Update Element.getDestinationInsertionPoints(), using the 'an unclosed node of' relation'. (644a0fa)
- Re: [webcomponents] [Shadow DOM] [Bug 27775] Update Element.getDestinationInsertionPoints(), using the 'an unclosed node of' relation'. (644a0fa)
Re: [webcomponents] [Shadow DOM] Define the non-symmetric relation, called 'an unclosed tree of', between two node trees. (503e27c)
- Re: [webcomponents] [Shadow DOM] Define the non-symmetric relation, called 'an unclosed tree of', between two node trees. (503e27c)
- Re: [webcomponents] [Shadow DOM] Define the non-symmetric relation, called 'an unclosed tree of', between two node trees. (503e27c)
- Re: [webcomponents] [Shadow DOM] Define the non-symmetric relation, called 'an unclosed tree of', between two node trees. (503e27c)
[IndexedDB] Distinguish object store from thing IDBObjectStore represents (#3)
- Re: [IndexedDB] Distinguish object store from thing IDBObjectStore represents (#3)
- Re: [IndexedDB] Distinguish object store from thing IDBObjectStore represents (#3)
- Re: [IndexedDB] Distinguish object store from thing IDBObjectStore represents (#3)
- Re: [IndexedDB] Distinguish object store from thing IDBObjectStore represents (#3)
Re: [spec-reviews] Upgrade Insecure Requests (#50)
Re: [spec-reviews] Subresource Integrity (#43)
[ServiceWorker] about:blank handling in openWindow doesn't make much sense (#696)
Re: [fetch] Say something rather vague about priority to at least acknowledge it exists. Fixes the remainder of #43. (600ccb7)
[ServiceWorker] Step 5.4 of openWindow uses the incumbent settings object, which makes no sense (#695)
- Re: [ServiceWorker] Step 5.4 of openWindow uses the incumbent settings object, which makes no sense (#695)
- Re: [ServiceWorker] Step 5.4 of openWindow uses the incumbent settings object, which makes no sense (#695)
- Re: [ServiceWorker] Step 5.4 of openWindow uses the incumbent settings object, which makes no sense (#695)
[ServiceWorker] Step 5.3 of openWindow does "exceptions enabled" which doesn't make sense (#694)
- Re: [ServiceWorker] Step 5.3 of openWindow does "exceptions enabled" which doesn't make sense (#694)
- Re: [ServiceWorker] Step 5.3 of openWindow does "exceptions enabled" which doesn't make sense (#694)
- Re: [ServiceWorker] Step 5.3 of openWindow does "exceptions enabled" which doesn't make sense (#694)
- Re: [ServiceWorker] Step 5.3 of openWindow does "exceptions enabled" which doesn't make sense (#694)
- Re: [ServiceWorker] Step 5.3 of openWindow does "exceptions enabled" which doesn't make sense (#694)
- Re: [ServiceWorker] Step 5.3 of openWindow does "exceptions enabled" which doesn't make sense (#694)
Re: [fetch] `user-agent` header control (#37)
[fetch] PATCH verb (#50)
Re: [ServiceWorker] Consider producing distinct objects for the same entity to enable garbage collection (#416)
- Re: [ServiceWorker] Consider producing distinct objects for the same entity to enable garbage collection (#416)
- Re: [ServiceWorker] Consider producing distinct objects for the same entity to enable garbage collection (#416)
- Re: [ServiceWorker] Consider producing distinct objects for the same entity to enable garbage collection (#416)
- Re: [ServiceWorker] Consider producing distinct objects for the same entity to enable garbage collection (#416)
- Re: [ServiceWorker] Consider producing distinct objects for the same entity to enable garbage collection (#416)
- Re: [ServiceWorker] Consider producing distinct objects for the same entity to enable garbage collection (#416)
- Re: [ServiceWorker] Consider producing distinct objects for the same entity to enable garbage collection (#416)
[fetch] Feed a Response to existing APIs (#49)
- Re: [fetch] Feed a Response to existing APIs (#49)
- Re: [fetch] Feed a Response to existing APIs (#49)
- Re: [fetch] Feed a Response to existing APIs (#49)
- Re: [fetch] Feed a Response to existing APIs (#49)
- Re: [fetch] Feed a Response to existing APIs (#49)
[fetch] Allow context to be set (#48)
Re: [fetch] Cache mode: security review (#39)
[ServiceWorker] Replaying POST requests (#693)
- Re: [ServiceWorker] Replaying POST requests (#693)
- Re: [ServiceWorker] Replaying POST requests (#693)
- Re: [ServiceWorker] Replaying POST requests (#693)
- Re: [ServiceWorker] Replaying POST requests (#693)
[fullscreen] Make fullscreenElement and fullscreenEnabled [Replaceable]? (#2)
- Re: [fullscreen] Make fullscreenElement and fullscreenEnabled [Replaceable]? (#2)
- Re: [fullscreen] Make fullscreenElement and fullscreenEnabled [Replaceable]? (#2)
[push-api] Push event shouldn't be dispatched to an activating worker (#147)
Re: [streams] Add descriptions to ReadableStreamController methods (4d5a2a3)
Re: [streams] Update local build instructions (c80e15e)
Re: [ServiceWorker] Privacy consideration about the "cache" parameter of the Request object (#585)
- Re: [ServiceWorker] Privacy consideration about the "cache" parameter of the Request object (#585)
- Re: [ServiceWorker] Privacy consideration about the "cache" parameter of the Request object (#585)
Re: [ServiceWorker] How are unloaded tabs represented? (#626)
Re: [permissions] What should "retrieve the permission state" do for context related permissions? (#9)
Re: [permissions] What should "retrieve the permission state" do for pickers? (#8)
[webcomponents] Started on partial redistributions analysis. (#50)
[streams] Make the context be the transform object when calling transform and flush (#356)
- Re: [streams] Make the context be the transform object when calling transform and flush (#356)
- Re: [streams] Make the context be the transform object when calling transform and flush (#356)
- Re: [streams] Make the context be the transform object when calling transform and flush (#356)
- Re: [streams] Make the context be the transform object when calling transform and flush (#356)
- Re: [streams] Make the context be the transform object when calling transform and flush (#356)
- Re: [streams] Make the context be the transform object when calling transform and flush (#356)
- Re: [streams] Make the context be the transform object when calling transform and flush (#356)
- Re: [streams] Make the context be the transform object when calling transform and flush (#356)
[dom] Add a common conjugation of "case-sensitive" (#33)
Re: [spec-reviews] Strawman spec review for upgrade insecure requests (#54)
- Re: [spec-reviews] Strawman spec review for upgrade insecure requests (#54)
- Re: [spec-reviews] Strawman spec review for upgrade insecure requests (#54)
- Re: [spec-reviews] Strawman spec review for upgrade insecure requests (#54)
- Re: [spec-reviews] Strawman spec review for upgrade insecure requests (#54)
- Re: [spec-reviews] Strawman spec review for upgrade insecure requests (#54)
- Re: [spec-reviews] Strawman spec review for upgrade insecure requests (#54)
- Re: [spec-reviews] Strawman spec review for upgrade insecure requests (#54)
- Re: [spec-reviews] Strawman spec review for upgrade insecure requests (#54)
- Re: [spec-reviews] Strawman spec review for upgrade insecure requests (#54)
- Re: [spec-reviews] Strawman spec review for upgrade insecure requests (#54)
- Re: [spec-reviews] Strawman spec review for upgrade insecure requests (#54)
- Re: [spec-reviews] Strawman spec review for upgrade insecure requests (#54)
- Re: [spec-reviews] Strawman spec review for upgrade insecure requests (#54)
Re: [FileAPI] Use "index.html" as the filename of the spec. (#1)
[FileAPI] Use ASCII origin in blob URLs (#7)
[permissions] Remove global variables (#35)
[permissions] Tackle origin (#34)
- Re: [permissions] Tackle origin (#34)
- Re: [permissions] Tackle origin (#34)
- Re: [permissions] Tackle origin (#34)
- Re: [permissions] Tackle origin (#34)
- Re: [permissions] Tackle origin (#34)
[permissions] Define underlying infrastructure (#33)
[spec-reviews] Media Capture and Streams (#57)
[manifest] Typo fix (#379)
Re: [manifest] A means to control how long a splash screen should remain on screen. (#372)
- Re: [manifest] A means to control how long a splash screen should remain on screen. (#372)
- Re: [manifest] A means to control how long a splash screen should remain on screen. (#372)
- Re: [manifest] A means to control how long a splash screen should remain on screen. (#372)
- Re: [manifest] A means to control how long a splash screen should remain on screen. (#372)
- Re: [manifest] A means to control how long a splash screen should remain on screen. (#372)
- Re: [manifest] A means to control how long a splash screen should remain on screen. (#372)
- Re: [manifest] A means to control how long a splash screen should remain on screen. (#372)
- Re: [manifest] A means to control how long a splash screen should remain on screen. (#372)
[fetch] Automatically set request's "Content-Type" to "application/json" for POJOs (#47)
- Re: [fetch] Automatically set request's "Content-Type" to "application/json" for POJOs (#47)
- Re: [fetch] Automatically set request's "Content-Type" to "application/json" for POJOs (#47)
- Re: [fetch] Automatically set request's "Content-Type" to "application/json" for POJOs (#47)
- Re: [fetch] Automatically set request's "Content-Type" to "application/json" for POJOs (#47)
- Re: [fetch] Automatically set request's "Content-Type" to "application/json" for POJOs (#47)
- Re: [fetch] Automatically set request's "Content-Type" to "application/json" for POJOs (#47)
- Re: [fetch] Automatically set request's "Content-Type" to "application/json" for POJOs (#47)
- Re: [fetch] Automatically set request's "Content-Type" to "application/json" for POJOs (#47)
- Re: [fetch] Automatically set request's "Content-Type" to "application/json" for POJOs (#47)
- Re: [fetch] Automatically set request's "Content-Type" to "application/json" for POJOs (#47)
- Re: [fetch] Automatically set request's "Content-Type" to "application/json" for POJOs (#47)
- Re: [fetch] Automatically set request's "Content-Type" to "application/json" for POJOs (#47)
- Re: [fetch] Automatically set request's "Content-Type" to "application/json" for POJOs (#47)
- Re: [fetch] Automatically set request's "Content-Type" to "application/json" for POJOs (#47)
- Re: [fetch] Automatically set request's "Content-Type" to "application/json" for POJOs (#47)
Re: [manifest] Manifest format should support some way of including a splash screen (#9)
- Re: [manifest] Manifest format should support some way of including a splash screen (#9)
- Re: [manifest] Manifest format should support some way of including a splash screen (#9)
- Re: [manifest] Manifest format should support some way of including a splash screen (#9)
- Re: [manifest] Manifest format should support some way of including a splash screen (#9)
- Re: [manifest] Manifest format should support some way of including a splash screen (#9)
- Re: [manifest] Manifest format should support some way of including a splash screen (#9)
Re: [manifest] Added splashscreens member (closes #9) (8711327)
[manifest] Added splashscreens member (closes #9) (#378)
Re: [manifest] Added splash_screens member (closes #9) (#371)
Re: [manifest] Add meta tags equivs. for features were possible (#350)
Re: [manifest] Made using fallbacks normative (closes #350) (#351)
Re: [manifest] Must manifests be same-origin? (#360)
- Re: [manifest] Must manifests be same-origin? (#360)
- Re: [manifest] Must manifests be same-origin? (#360)
- Re: [manifest] Must manifests be same-origin? (#360)
Re: [manifest] Resolve start_url against manifest URL (#330)
Re: [manifest] From a security perspective, why should the manifest be same origin? (#375)
Re: [manifest] Make manifest authoritative + allow CORS (closes #376, #375, #360, #330, #351, #272) (4145171)
[manifest] Make manifest authoritative + allow CORS (closes #376, #375, #360, #330,#351, #272) (#377)
Re: [fetch] Added manifest-src directive to request rel. table (1d51c7c)
- Re: [fetch] Added manifest-src directive to request rel. table (1d51c7c)
- Re: [fetch] Added manifest-src directive to request rel. table (1d51c7c)
[fetch] Added manifest-src directive to request rel. table (#46)
- Re: [fetch] Added manifest-src directive to request rel. table (#46)
- Re: [fetch] Added manifest-src directive to request rel. table (#46)
- Re: [fetch] Added manifest-src directive to request rel. table (#46)
- Re: [fetch] Added manifest-src directive to request rel. table (#46)
- Re: [fetch] Added manifest-src directive to request rel. table (#46)
Re: [fetch] Add support for federated token binding to fetch (#30)
Re: [fetch] Add `preload` and `prerender` contexts (#36)
- Re: [fetch] Add `preload` and `prerender` contexts (#36)
- Re: [fetch] Add `preload` and `prerender` contexts (#36)
- Re: [fetch] Add `preload` and `prerender` contexts (#36)
- Re: [fetch] Add `preload` and `prerender` contexts (#36)
[dom] Rewrite replaceWith/before/after algorithms (#32)
Re: [ServiceWorker] Unable to easily distinguish top-level navigations (#673)
- Re: [ServiceWorker] Unable to easily distinguish top-level navigations (#673)
- Re: [ServiceWorker] Unable to easily distinguish top-level navigations (#673)
[webcomponents] Update Imperative-API-for-Node-Distribution-in-Shadow-DOM.md (#49)
- Re: [webcomponents] Update Imperative-API-for-Node-Distribution-in-Shadow-DOM.md (#49)
- Re: [webcomponents] Update Imperative-API-for-Node-Distribution-in-Shadow-DOM.md (#49)
- Re: [webcomponents] Update Imperative-API-for-Node-Distribution-in-Shadow-DOM.md (#49)
Re: [streams] Support reading bytes into buffers allocated by user code on platforms where only async read is available (#253)
Re: [manifest] Obtaining a Manifest should follow usual CORS rules with credentials. (#353)
- Re: [manifest] Obtaining a Manifest should follow usual CORS rules with credentials. (#353)
- Re: [manifest] Obtaining a Manifest should follow usual CORS rules with credentials. (#353)
Re: [selection-api] Specify Selection.modify()? (#37)
Re: [permissions] Why "prompt" instead of "default"? (#25)
- Re: [permissions] Why "prompt" instead of "default"? (#25)
- Re: [permissions] Why "prompt" instead of "default"? (#25)
- Re: [permissions] Why "prompt" instead of "default"? (#25)
- Re: [permissions] Why "prompt" instead of "default"? (#25)
- Re: [permissions] Why "prompt" instead of "default"? (#25)
- Re: [permissions] Why "prompt" instead of "default"? (#25)
- Re: [permissions] Why "prompt" instead of "default"? (#25)
- Re: [permissions] Why "prompt" instead of "default"? (#25)
- Re: [permissions] Why "prompt" instead of "default"? (#25)
- Re: [permissions] Why "prompt" instead of "default"? (#25)
- Re: [permissions] Why "prompt" instead of "default"? (#25)
- Re: [permissions] Why "prompt" instead of "default"? (#25)
- Re: [permissions] Why "prompt" instead of "default"? (#25)
- Re: [permissions] Why "prompt" instead of "default"? (#25)
[ServiceWorker] add [NewObject] where appropriate (#692)
- Re: [ServiceWorker] add [NewObject] where appropriate (#692)
- Re: [ServiceWorker] add [NewObject] where appropriate (#692)
- Re: [ServiceWorker] add [NewObject] where appropriate (#692)
- Re: [ServiceWorker] add [NewObject] where appropriate (#692)
- Re: [ServiceWorker] add [NewObject] where appropriate (#692)
- Re: [ServiceWorker] add [NewObject] where appropriate (#692)
- Re: [ServiceWorker] add [NewObject] where appropriate (#692)
- Re: [ServiceWorker] add [NewObject] where appropriate (#692)
Re: [xhr] Remove extraneous "=" in mail subject (#18)
Re: [ServiceWorker] MessageEvent within the SW global should have waitUntil() (#669)
- Re: [ServiceWorker] MessageEvent within the SW global should have waitUntil() (#669)
- Re: [ServiceWorker] MessageEvent within the SW global should have waitUntil() (#669)
- Re: [ServiceWorker] MessageEvent within the SW global should have waitUntil() (#669)
- Re: [ServiceWorker] MessageEvent within the SW global should have waitUntil() (#669)
- Re: [ServiceWorker] MessageEvent within the SW global should have waitUntil() (#669)
- Re: [ServiceWorker] MessageEvent within the SW global should have waitUntil() (#669)
Re: [ServiceWorker] self.caches should spec what to do for "untrusted" origins (#687)
Re: [streams] WritableStream constructor: strategy should be set before sync with queue (#346)
Re: [streams] Non-normative descriptions are missing for ReadableStreamController (#350)
[streams] ReadableByteStream needs reference implementation/tests (#355)
[streams] ReadableByteStream underlying source/controller design: return a promise vs. c.something (#354)
[streams] Readable byte streams should support an internal queue (#353)
- Re: [streams] Readable byte streams should support an internal queue (#353)
- Re: [streams] Readable byte streams should support an internal queue (#353)
- Re: [streams] Readable byte streams should support an internal queue (#353)
- Re: [streams] Readable byte streams should support an internal queue (#353)
- Re: [streams] Readable byte streams should support an internal queue (#353)
- Re: [streams] Readable byte streams should support an internal queue (#353)
- Re: [streams] Readable byte streams should support an internal queue (#353)
- Re: [streams] Readable byte streams should support an internal queue (#353)
- Re: [streams] Readable byte streams should support an internal queue (#353)
- Re: [streams] Readable byte streams should support an internal queue (#353)
- Re: [streams] Readable byte streams should support an internal queue (#353)
- Re: [streams] Readable byte streams should support an internal queue (#353)
[dom] Attribute lowercasing does not appear to match browsers or web-platform-tests (#31)
- Re: [dom] Attribute lowercasing does not appear to match browsers or web-platform-tests (#31)
- Re: [dom] Attribute lowercasing does not appear to match browsers or web-platform-tests (#31)
- Re: [dom] Attribute lowercasing does not appear to match browsers or web-platform-tests (#31)
[dom] cloneNode underspecified for attribute copying (#30)
- Re: [dom] cloneNode underspecified for attribute copying (#30)
- Re: [dom] cloneNode underspecified for attribute copying (#30)
[webcomponents] Added fastdom callback idea. (#48)
- Re: [webcomponents] Added fastdom callback idea. (#48)
- Re: [webcomponents] Added fastdom callback idea. (#48)
[ServiceWorker] allow self-signed certificates (#691)
- Re: [ServiceWorker] allow self-signed certificates (#691)
- Re: [ServiceWorker] allow self-signed certificates (#691)
- Re: [ServiceWorker] allow self-signed certificates (#691)
- Re: [ServiceWorker] allow self-signed certificates (#691)
- Re: [ServiceWorker] allow self-signed certificates (#691)
[webcomponents] Added pure functions idea to the timing alternatives. (#47)
- Re: [webcomponents] Added pure functions idea to the timing alternatives. (#47)
- Re: [webcomponents] Added pure functions idea to the timing alternatives. (#47)
- Re: [webcomponents] Added pure functions idea to the timing alternatives. (#47)
- Re: [webcomponents] Added pure functions idea to the timing alternatives. (#47)
- Re: [webcomponents] Added pure functions idea to the timing alternatives. (#47)
- Re: [webcomponents] Added pure functions idea to the timing alternatives. (#47)
Re: [spec-reviews] CSSOM View document.scrollingElement (#51)
- Re: [spec-reviews] CSSOM View document.scrollingElement (#51)
- Re: [spec-reviews] CSSOM View document.scrollingElement (#51)
- Re: [spec-reviews] CSSOM View document.scrollingElement (#51)
Re: [streams] Add SNAPSHOT-LINK argument to the bikeshed command line in README.md (#348)
Re: [dom] Several references are now wrong after Bikeshed conversion (#17)
Re: [manifest] Should a manifest unambigiously and authoritively be the app's metadata? (#376)
- Re: [manifest] Should a manifest unambigiously and authoritively be the app's metadata? (#376)
- Re: [manifest] Should a manifest unambigiously and authoritively be the app's metadata? (#376)
- Re: [manifest] Should a manifest unambigiously and authoritively be the app's metadata? (#376)
- Re: [manifest] Should a manifest unambigiously and authoritively be the app's metadata? (#376)
Re: [manifest] Define identity of a web app. (#272)
- Re: [manifest] Define identity of a web app. (#272)
- Re: [manifest] Define identity of a web app. (#272)
- Re: [manifest] Define identity of a web app. (#272)
- Re: [manifest] Define identity of a web app. (#272)
- Re: [manifest] Define identity of a web app. (#272)
Re: [push-api] Rename hasPermission (#136)
[ServiceWorker] should SW MessageEvents inherit ExtendableEvent? (#690)
- Re: [ServiceWorker] should SW MessageEvents inherit ExtendableEvent? (#690)
- Re: [ServiceWorker] should SW MessageEvents inherit ExtendableEvent? (#690)
Re: [push-api] userVisible -> userVisibleOnly (#137)
Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
- Re: [fetch] Aborting a fetch (#27)
[webcomponents] Fix the table-chart example (#46)
[webcomponents] Make proposals more clear (#45)
- Re: [webcomponents] Make proposals more clear (#45)
- Re: [webcomponents] Make proposals more clear (#45)
[packaging-on-the-web] Link headers as an alternative? (#26)
[streams] Remove closedPromise from ReadableStream's internal slot list (#352)
Re: [streams] Add ReadableByteStream definition (#343)
- Re: [streams] Add ReadableByteStream definition (#343)
- Re: [streams] Add ReadableByteStream definition (#343)
- Re: [streams] Add ReadableByteStream definition (#343)
- Re: [streams] Add ReadableByteStream definition (#343)
- Re: [streams] Add ReadableByteStream definition (#343)
- Re: [streams] Add ReadableByteStream definition (#343)
- Re: [streams] Add ReadableByteStream definition (#343)
- Re: [streams] Add ReadableByteStream definition (#343)
Re: [streams] Byte streams tracking bug (#300)
[streams] Update byte stream spec (#351)
Re: [streams] Add tests for checking that tee() branches are errored/closed when the o... (#349)
Re: [fetch] Initializing context/content specific fetch defaults (#43)
- Re: [fetch] Initializing context/content specific fetch defaults (#43)
- Re: [fetch] Initializing context/content specific fetch defaults (#43)
- Re: [fetch] Initializing context/content specific fetch defaults (#43)
- Re: [fetch] Initializing context/content specific fetch defaults (#43)
- Re: [fetch] Initializing context/content specific fetch defaults (#43)
- Re: [fetch] Initializing context/content specific fetch defaults (#43)
- Re: [fetch] Initializing context/content specific fetch defaults (#43)
- Re: [fetch] Initializing context/content specific fetch defaults (#43)
- Re: [fetch] Initializing context/content specific fetch defaults (#43)
- Re: [fetch] Initializing context/content specific fetch defaults (#43)
- Re: [fetch] Initializing context/content specific fetch defaults (#43)