Wednesday, 31 October 2018
- Re: [w3ctag/design-reviews] Carriage of Web Resource in ISOBMFF (#285)
- Re: [w3ctag/design-reviews] Carriage of Web Resource in ISOBMFF (#285)
- Re: [w3ctag/design-reviews] Media Capabilities (#218)
- Re: [w3c/push-api] Make PushSubscription.expirationTime mandatory (#302)
- Re: [w3ctag/design-reviews] Privacy Mode (#101)
- Re: [w3ctag/design-reviews] Media Capabilities (#218)
- Re: [w3ctag/design-reviews] Carriage of Web Resource in ISOBMFF (#285)
- Re: [w3ctag/design-reviews] Temporal proposal (#311)
- Re: [w3ctag/design-reviews] OffscreenCanvas new commit() and DedicatedWorker.requestAnimationFrame (#288)
- Re: [w3ctag/design-reviews] Temporal proposal (#311)
- Re: [w3ctag/design-reviews] Privacy Mode (#101)
- Re: [w3ctag/design-reviews] Review Decentralized identifiers (DIDs) (#216)
- [whatwg/fetch] Fixed typo (#823)
- Re: [w3ctag/design-reviews] Background fetch (#279)
- Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69)
- Re: [w3c/ServiceWorker] A way to immediately unregister a service worker (#614)
- Re: [w3c/ServiceWorker] A way to immediately unregister a service worker (#614)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3ctag/design-reviews] Spatial Navigation (#287)
- Re: [w3ctag/design-reviews] Background fetch (#279)
- Re: [whatwg/fetch] Deduplicate 'the' (#822)
- Re: [w3ctag/design-reviews] Temporal proposal (#311)
- Re: [w3ctag/design-reviews] HTTP State Tokens (#297)
- Re: [w3ctag/design-reviews] Review Decentralized identifiers (DIDs) (#216)
- Re: [w3ctag/design-reviews] Temporal proposal (#311)
- Re: [w3ctag/design-reviews] HTTP State Tokens (#297)
- Re: [w3ctag/design-reviews] Temporal proposal (#311)
- Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69)
- Re: [w3ctag/design-reviews] HTTP State Tokens (#297)
- Re: [w3ctag/design-reviews] Temporal proposal (#311)
- Re: [w3ctag/design-reviews] HTTP State Tokens (#297)
- Re: [w3ctag/design-reviews] Background fetch (#279)
- Re: [w3ctag/design-reviews] Async local storage (#278)
- Re: [w3ctag/design-reviews] Async local storage (#278)
- Re: [w3ctag/design-reviews] Async local storage (#278)
- Re: [w3ctag/design-reviews] Async local storage (#278)
- Re: [w3ctag/design-reviews] Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312)
- Re: [w3ctag/design-reviews] `sec-metadata` (#280)
- Re: [w3ctag/design-reviews] `sec-metadata` (#280)
- Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69)
- Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69)
- Re: [w3ctag/design-reviews] Serialization of natural language in data formats such as JSON [I18N] (#178)
- Re: [w3ctag/design-reviews] HTTP State Tokens (#297)
- Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69)
- Re: [w3ctag/design-reviews] User Activation v2 (#295)
- Re: [w3ctag/design-reviews] User Activation v2 (#295)
- Re: [w3ctag/design-reviews] Carriage of Web Resource in ISOBMFF (#285)
- Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69)
- Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69)
- Re: [w3ctag/design-reviews] Layered APIs (#276)
- Re: [w3ctag/design-reviews] Carriage of Web Resource in ISOBMFF (#285)
- Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818)
- Re: [w3ctag/design-reviews] Signed Exchanges (#235)
- [whatwg/fetch] Deduplicate 'the' (#822)
- Re: [w3ctag/design-reviews] Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312)
- Re: [w3ctag/design-reviews] HTTP State Tokens (#297)
- Re: [w3ctag/design-reviews] HTTP State Tokens (#297)
- Re: [w3ctag/design-reviews] Sensor APIs (#207)
- Re: [w3ctag/design-reviews] Sensor APIs (#207)
- Re: [w3ctag/design-reviews] User Activation API (#300)
- Re: [w3ctag/design-reviews] hrefTranslate attribute (#301)
- Re: [w3ctag/design-reviews] hrefTranslate attribute (#301)
- Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818)
- Re: [w3ctag/design-reviews] Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312)
- Re: [w3ctag/design-reviews] User Activation API (#300)
- Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69)
- Re: [w3ctag/design-reviews] Media Capabilities (#218)
- Re: [w3ctag/design-reviews] hrefTranslate attribute (#301)
- Re: [w3ctag/design-reviews] hrefTranslate attribute (#301)
- Re: [w3ctag/design-reviews] User Activation API (#300)
- Re: [w3ctag/design-reviews] hrefTranslate attribute (#301)
- Re: [w3ctag/design-reviews] User Activation API (#300)
- Re: [w3ctag/design-reviews] Gesture Delegation (#199)
- Re: [w3ctag/design-reviews] Gesture Delegation (#199)
- Re: [w3ctag/design-reviews] Screen Capture API (#309)
- Re: [w3ctag/design-reviews] hrefTranslate attribute (#301)
- Re: [w3ctag/design-reviews] Screen Capture API (#309)
- Re: [w3ctag/design-reviews] hrefTranslate attribute (#301)
- Re: [w3ctag/design-reviews] Media Capabilities (#218)
- Re: [w3ctag/design-reviews] hrefTranslate attribute (#301)
- Re: [w3ctag/design-reviews] OffscreenCanvas new commit() and DedicatedWorker.requestAnimationFrame (#288)
- Re: [w3ctag/design-reviews] hrefTranslate attribute (#301)
- Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141)
- Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141)
- Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141)
- Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141)
- Re: [w3ctag/design-reviews] OffscreenCanvas new commit() and DedicatedWorker.requestAnimationFrame (#288)
- Re: [w3ctag/design-reviews] hrefTranslate attribute (#301)
- Re: [w3ctag/design-reviews] hrefTranslate attribute (#301)
- Re: [w3ctag/design-reviews] Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312)
- Re: [w3ctag/design-reviews] Screen Capture API (#309)
- Re: [w3ctag/design-reviews] Screen Capture API (#309)
- Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818)
- Re: [w3ctag/design-reviews] JavaScript Decorators (#314)
- Re: [w3ctag/design-reviews] Review Accessibility Object Model (#134)
- Re: [w3ctag/design-reviews] JavaScript Decorators (#314)
- Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818)
- Re: [whatwg/fetch] Specify restriction for requests with keepalive set (#679)
- Re: [w3ctag/design-reviews] Temporal proposal (#311)
- Re: [w3ctag/design-reviews] Temporal proposal (#311)
- Re: [w3ctag/design-reviews] Temporal proposal (#311)
- Re: [w3ctag/design-reviews] Temporal proposal (#311)
- Re: [whatwg/fetch] Remove Gecko-only quirk (#816)
- Re: [w3ctag/design-reviews] Temporal proposal (#311)
- Re: [w3ctag/design-reviews] Display Locking (#306)
- Re: [w3ctag/design-reviews] Canvas TextMetrics (#302)
- Re: [w3ctag/design-reviews] Canvas TextMetrics (#302)
- Re: [whatwg/dom] Meta: define merge policy and add CONTRIBUTING.md (676fcbe)
- Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818)
- Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818)
- Re: [w3ctag/design-reviews] Support codec and container switching with MSE using SourceBuffer.changeType() (#298)
- Re: [w3ctag/design-reviews] Support codec and container switching with MSE using SourceBuffer.changeType() (#298)
- Re: [w3ctag/design-reviews] Layered APIs (#276)
- Re: [w3ctag/design-reviews] Dusting off Web Speech API? (#214)
- Re: [w3ctag/design-reviews] Dusting off Web Speech API? (#214)
- Re: [whatwg/fetch] Editorial: remove leftover sentence (#815)
- Re: [whatwg/dom] When moving APIs from other specs to DOM spec, ensure MDN is updated (#710)
- Re: [w3ctag/design-reviews] HTML General Review: HTML Ruby (#248)
- Re: [w3ctag/design-reviews] HTML General Review: Server-Sent Events (#267)
- Re: [w3ctag/design-reviews] Stale-While-Revalidate handling in browser (#293)
- Re: [w3ctag/design-reviews] Stale-While-Revalidate handling in browser (#293)
- Re: [w3ctag/design-reviews] Review Request: Priority Hints API (#241)
- Re: [w3ctag/design-reviews] WebUSB on Dedicated and Shared Workers (#277)
- Re: [w3ctag/design-reviews] WebUSB on Dedicated and Shared Workers (#277)
- Re: [w3ctag/design-reviews] import.meta.url, and import.meta generally (#208)
- Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69)
- Re: [w3c/ServiceWorker] Clarify "uncaught runtime script error". (#1346)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3c/ServiceWorker] Clarify "uncaught runtime script error". (#1346)
- Re: [w3c/ServiceWorker] Clarify "uncaught runtime script error". (#1346)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [whatwg/fetch] Consider to add "resolveAtIdleTime" to RequestInit (#821)
- Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69)
- Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3c/webcomponents] Provide an option which allows global CSSes to style elements inside a shadow tree (#769)
- Re: [whatwg/dom] When moving APIs from other specs to DOM spec, ensure MDN is updated (#710)
- Re: [w3ctag/design-reviews] RTCIceTransport (#304)
Tuesday, 30 October 2018
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3ctag/design-reviews] Review Accessibility Object Model (#134)
- Re: [w3c/ServiceWorker] Tee-ing Cache.put()? (#1367)
- Re: [w3c/ServiceWorker] Tee-ing Cache.put()? (#1367)
- Re: [w3ctag/design-reviews] Find-in-page API(s) (#236)
- Re: [w3ctag/design-reviews] Find-in-page API(s) (#236)
- Re: [w3c/IndexedDB] Add IDBFactory/databases() (#240)
- [w3ctag/design-reviews] FetchEvent Worker Timing (#317)
- Re: [w3ctag/design-reviews] Review Decentralized identifiers (DIDs) (#216)
- Re: [w3ctag/design-reviews] Find-in-page API(s) (#236)
- [w3ctag/design-reviews] IndexedDB Transaction Explicit Commit API (#316)
- Re: [w3ctag/design-reviews] Review Decentralized identifiers (DIDs) (#216)
- Re: [w3ctag/design-reviews] TV-Specific Web Subsetting (#105)
- Re: [w3c/webcomponents] Provide an option which allows global CSSes to style elements inside a shadow tree (#769)
- Re: [w3c/ServiceWorker] Tee-ing Cache.put()? (#1367)
- [w3c/ServiceWorker] Tee-ing Cache.put()? (#1367)
- Re: [w3ctag/design-reviews] User Activation v2 (#295)
- Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863)
- Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69)
- Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863)
- Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863)
- Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863)
- Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863)
- [w3ctag/design-reviews] Wide gamut support for Canvas/OffscreenCanvas/ImageBitmap (#315)
- Re: [w3ctag/design-reviews] hrefTranslate attribute (#301)
- Re: [w3ctag/design-reviews] Review Accessibility Object Model (#134)
- [w3c/ServiceWorker] Why does spec set redirect's mode to error ? (#1366)
- Re: [w3ctag/design-reviews] Screen Capture API (#309)
- Re: [w3ctag/design-reviews] TV-Specific Web Subsetting (#105)
- Re: [w3ctag/design-reviews] TV-Specific Web Subsetting (#105)
- Re: [w3ctag/design-reviews] TV-Specific Web Subsetting (#105)
- Re: [w3ctag/design-reviews] Constructable Stylesheets (#308)
- Re: [w3ctag/design-reviews] Constructable Stylesheets (#308)
- Re: [w3ctag/design-reviews] hrefTranslate attribute (#301)
- Re: [w3ctag/design-reviews] Review MathML (#313)
- Re: [w3ctag/design-reviews] Canvas TextMetrics (#302)
- Re: [w3ctag/design-reviews] Constructable Stylesheets (#308)
- Re: [w3ctag/design-reviews] User Activation v2 (#295)
- Re: [w3ctag/design-reviews] Find-in-page API(s) (#236)
- Re: [w3ctag/design-reviews] Constructable Stylesheets (#308)
- Re: [w3ctag/design-reviews] Review MathML (#313)
- Re: [w3ctag/design-reviews] Task Scheduling (#72)
- [w3c/ServiceWorker] Module scripts to be fetched with "same-origin" for credentials (#1365)
- Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818)
- Re: [w3ctag/design-reviews] RTCIceTransport (#304)
- Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818)
- Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818)
- Re: [w3ctag/design-reviews] import.meta.url, and import.meta generally (#208)
- Re: [w3ctag/design-reviews] import.meta.url, and import.meta generally (#208)
- Re: [w3ctag/design-reviews] Review MathML (#313)
- Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818)
- Re: [w3ctag/design-reviews] Review Decentralized identifiers (DIDs) (#216)
- Re: [whatwg/xhr] Limit Content-Type overrides to when charset isn't already UTF-8 (#224)
- Re: [w3ctag/design-reviews] TextEncoderStream and TextDecoderStream (#282)
- Re: [w3ctag/design-reviews] TextEncoderStream and TextDecoderStream (#282)
- Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863)
- Re: [w3ctag/design-reviews] TextEncoderStream and TextDecoderStream (#282)
- Re: [whatwg/dom] When moving APIs from other specs to DOM spec, ensure MDN is updated (#710)
- Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863)
- Re: [w3ctag/design-reviews] TextEncoderStream and TextDecoderStream (#282)
- Re: [w3ctag/design-reviews] TextEncoderStream and TextDecoderStream (#282)
- Re: [w3ctag/design-reviews] TextEncoderStream and TextDecoderStream (#282)
- Re: [w3c/ServiceWorker] A simple globally available store of data per-registration (#1331)
- Re: [whatwg/fetch] "With Credentials" flag possibly inconsistent with web architecture (#517)
- Re: [w3ctag/design-reviews] Privacy Mode (#101)
- Re: [whatwg/fetch] "With Credentials" flag possibly inconsistent with web architecture (#517)
- Re: [w3ctag/design-reviews] Web Components Guidelines Doc? (#227)
- Re: [w3ctag/design-reviews] Web Components Guidelines Doc? (#227)
- Re: [w3ctag/design-reviews] HTML General Review: Web Sockets (#268)
- Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818)
- Re: [w3ctag/design-reviews] Request Formal Review of Vehicle Information Service Specification (VISS) CR (#234)
- Re: [whatwg/fetch] "With Credentials" flag possibly inconsistent with web architecture (#517)
- Re: [w3ctag/design-reviews] <link> rel="modulepreload" (#213)
- Re: [w3ctag/design-reviews] ads.txt (#201)
- Re: [w3ctag/design-reviews] Sensor APIs (#207)
- Re: [w3ctag/design-reviews] Review request for ResizeObserver (#187)
- Re: [w3ctag/design-reviews] Review request for ResizeObserver (#187)
- Re: [w3ctag/design-reviews] Intersection Observer review (#197)
- Re: [w3ctag/design-reviews] Review request for ResizeObserver (#187)
- Re: [w3ctag/design-reviews] Request Review: Gesture Delegation (#199)
- Re: [w3ctag/design-reviews] Timed Text Markup Language 2 (TTML2) (#138)
- Re: [w3ctag/design-reviews] Timed Text Markup Language 2 (TTML2) (#138)
- Re: [w3ctag/design-reviews] Review request for WebVR (#185)
- Re: [whatwg/fetch] "With Credentials" flag possibly inconsistent with web architecture (#517)
- Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818)
- Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863)
- Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863)
- Re: [w3c/ServiceWorker] Formalizing a timeout API (#1292)
- Re: [whatwg/xhr] Limit Content-Type overrides to when charset isn't already UTF-8 (#224)
- Re: [w3ctag/design-reviews] Clear Site Data (#62)
- Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863)
- Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69)
- Re: [w3c/webcomponents] Provide an option which allows global CSSes to style elements inside a shadow tree (#769)
- Re: [whatwg/fetch] Specify restriction for requests with keepalive set (#679)
- Re: [w3c/webcomponents] Provide an option which allows global CSSes to style elements inside a shadow tree (#769)
- Re: [w3c/ServiceWorker] Clarify dynamic-imported scripts are never installed (#1356)
Monday, 29 October 2018
- Re: [w3c/editing] Move execCommand to WICG (#184)
- Re: [w3c/editing] Move execCommand to WICG (#184)
- Re: [w3c/ServiceWorker] Formalizing a timeout API (#1292)
- Re: [w3c/editing] Move execCommand to WICG (#184)
- Re: [w3c/editing] Move execCommand to WICG (#184)
- Re: [w3c/ServiceWorker] A simple globally available store of data per-registration (#1331)
- Re: [w3c/editing] Move execCommand to WICG (#184)
- Re: [w3c/editing] Move execCommand to WICG (#184)
- Re: [w3c/ServiceWorker] A simple globally available store of data per-registration (#1331)
- Re: [w3c/manifest] Add splashscreen as a `purpose` (#510)
- Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179)
- Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179)
- Re: [w3c/ServiceWorker] A simple globally available store of data per-registration (#1331)
- Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179)
- Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179)
- Re: [w3c/ServiceWorker] serviceworker.skipWaiting (#1016)
- Re: [w3c/editing] Move execCommand to WICG (#184)
- Re: [w3c/ServiceWorker] [Proposal] ServiceWorkerContainer.installing(scope) promise (#1364)
- Re: [whatwg/fetch] Consider to add "resolveAtIdleTime" to RequestInit (#821)
- Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69)
- Re: [w3c/webcomponents] JSON "modules" (#770)
- Re: [w3c/webcomponents] JSON "modules" (#770)
- Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69)
- Re: [w3c/webcomponents] JSON "modules" (#770)
- Re: [w3c/webcomponents] JSON "modules" (#770)
- Re: [w3c/ServiceWorker] Add API for postMessage with PostMessageOptions (#1344)
- Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863)
- Re: [w3c/webcomponents] JSON "modules" (#770)
- Re: [w3c/ServiceWorker] Add API for postMessage with PostMessageOptions (#1344)
- Re: [w3ctag/design-reviews] TAG Review Request: Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312)
- Re: [w3ctag/design-reviews] TAG Review Request: Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312)
- Re: [whatwg/fetch] Split `document` destination for top-level and nested contexts. (#819)
- Re: [w3ctag/design-reviews] TAG Review Request: Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3c/ServiceWorker] A simple globally available store of data per-registration (#1331)
- Re: [w3c/webcomponents] Provide an option which allows global CSSes to style elements inside a shadow tree (#769)
- Re: [w3ctag/design-reviews] TAG Review Request: Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312)
- Re: [w3ctag/design-reviews] TAG Review Request: Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312)
- Re: [w3ctag/design-reviews] TAG Review Request: Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312)
- Re: [w3c/ServiceWorker] Should add a “script type” check in the register algorithm. (#1359)
- Re: [w3c/webcomponents] Provide an option which allows global CSSes to style elements inside a shadow tree (#769)
- Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863)
- Re: [w3ctag/design-reviews] TAG Review Request: Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312)
- Re: [whatwg/encoding] TextEncoder#encode - write to existing Uint8Array (#69)
- Re: [w3ctag/design-reviews] HTML General Review: HTML Forms (#253)
- Re: [w3ctag/design-reviews] HTML General Review: HTML Forms (#253)
- Re: [w3ctag/design-reviews] HTML General Review: HTML Forms (#253)
- Re: [w3ctag/design-reviews] HTML General Review: HTML Forms (#253)
- Re: [w3ctag/design-reviews] HTML General Review: HTML Forms (#253)
- Re: [whatwg/fetch] Specify restriction for requests with keepalive set (#679)
- Re: [w3ctag/design-reviews] Review Decentralized identifiers (DIDs) (#216)
- Re: [w3c/webcomponents] Provide an option which allows global CSSes to style elements inside a shadow tree (#769)
- Re: [w3ctag/design-reviews] Review Decentralized identifiers (DIDs) (#216)
- [w3ctag/design-reviews] TAG Review Request: JavaScript Decorators (#314)
- Re: [w3ctag/design-reviews] Review MathML (#313)
- Re: [w3ctag/design-reviews] HTML General Review: HTML Forms (#253)
- [w3ctag/design-reviews] Review MathML (#313)
- Re: [w3ctag/design-reviews] Serialization of natural language in data formats such as JSON [I18N] (#178)
- Re: [w3c/ServiceWorker] [Proposal] ServiceWorkerContainer.installing(scope) promise (#1364)
- Re: [w3c/ServiceWorker] [Proposal] ServiceWorkerContainer.installing(scope) promise (#1364)
- Re: [w3c/ServiceWorker] "no-cors" CSS SOP violation (#719)
- Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863)
- Re: [whatwg/fetch] Consider to add "resolveAtIdleTime" to RequestInit (#821)
- Re: [whatwg/dom] Remove redundant <dd> (#712)
- Re: [whatwg/dom] Remove redundant <dd> (#712)
- Re: [whatwg/dom] Remove redundant <dd> (#712)
- Re: [w3c/ServiceWorker] Add API for postMessage with PostMessageOptions (#1344)
- Re: [whatwg/fetch] Consider to add "resolveAtIdleTime" to RequestInit (#821)
- Re: [w3c/DOM-Parsing] Define the origin of the documents returned from DOMParser (#24)
- Re: [whatwg/fetch] [3.0.0] SSR build error after update from 2.0.4 (#820)
- Re: [whatwg/fetch] Consider to add "resolveAtIdleTime" to RequestInit (#821)
- Re: [whatwg/fetch] [3.0.0] SSR build error after update from 2.0.4 (#820)
- Re: [w3c/ServiceWorker] "no-cors" CSS SOP violation (#719)
- Re: [whatwg/fetch] [3.0.0] SSR build error after update from 2.0.4 (#820)
- Re: [whatwg/fetch] Specify restriction for requests with keepalive set (#679)
- Re: [w3c/webcomponents] Provide an option which allows global CSSes to style elements inside a shadow tree (#769)
- Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179)
- [w3c/webcomponents] JSON "modules" (#770)
- Re: [w3c/ServiceWorker] "no-cors" CSS SOP violation (#719)
- Re: [whatwg/fetch] Consider to add "resolveAtIdleTime" to RequestInit (#821)
- Re: [whatwg/fetch] Consider to add "resolveAtIdleTime" to RequestInit (#821)
- Re: [w3c/webcomponents] CSS Modules (#759)
- Re: [w3c/webcomponents] CSS Modules (#759)
Sunday, 28 October 2018
- Re: [w3c/editing] Need spec for how HTML is serialized to be placed on the clipboard (#181)
- [w3ctag/design-reviews] TAG Review Request: Base used to resolve relative URIs to absolute URIs in HTML5 data-blocks (#312)
- Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818)
- [whatwg/dom] Remove redundant <dd> (#712)
- [w3c/ServiceWorker] [Proposal] ServiceWorkerContainer.installing(scope) promise (#1364)
Saturday, 27 October 2018
- [w3ctag/design-reviews] Tag Review Request: Temporal proposal (#311)
- Re: [w3c/webcomponents] CSS Modules (#759)
- [whatwg/fetch] Consider to add "resolveAtIdleTime" to RequestInit (#821)
- [w3c/webcomponents] Provide an option which allows global CSSes styling elements inside a shadow tree (#769)
- Re: [w3c/webcomponents] CSS Modules (#759)
- Re: [w3c/webcomponents] CSS Modules (#759)
- Re: [w3c/editing] Should browsers support ContentEditable for <option> elements? (#180)
- Re: [w3c/editing] Should browsers support ContentEditable for <option> elements? (#180)
- Re: [w3c/webcomponents] HTML Modules (#645)
- Re: [w3c/editing] Move execCommand to WICG (#184)
- Re: [whatwg/fetch] Specify restriction for requests with keepalive set (#679)
- Re: [w3c/ServiceWorker] Formalizing a timeout API (#1292)
- Re: [w3c/editing] Move execCommand to WICG (#184)
Friday, 26 October 2018
- Re: [w3c/editing] Move execCommand to WICG (#184)
- Re: [w3c/ServiceWorker] Proposal: Allow addEventListener/removeEventListener for 'fetch' to called at anytime (#1195)
- Re: [w3c/ServiceWorker] Proposal: Allow addEventListener/removeEventListener for 'fetch' to called at anytime (#1195)
- Re: [w3c/ServiceWorker] Clarify dynamic-imported scripts are never installed (#1356)
- [whatwg/fetch] [3.0.0] SSR build error after update from 2.0.4 (#820)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3c/gamepad] are timestamps a potential tracking/fingerprinting vector? (#74)
- Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179)
- Re: [w3c/webcomponents] HTML Modules (#645)
- Re: [w3c/webcomponents] Mechanism for setting the tabindex focus flag without sprouting tabindex attribute? (#762)
- [w3c/editing] Move execCommand to WICG (#184)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- Re: [w3c/webcomponents] Mechanism for setting the tabindex focus flag without sprouting tabindex attribute? (#762)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/ServiceWorker] Add API for postMessage with PostMessageOptions (#1344)
- [w3c/ServiceWorker] "waiting for all" definition changed (#1363)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3c/webcomponents] HTMLElement.prototype.offsetParent leaks a node inside a shadow tree (#497)
- Re: [w3c/ServiceWorker] Clarify dynamic-imported scripts are never installed (#1356)
- Re: [whatwg/fetch] Consider splitting `document` into `document` and `nested-document`. (#755)
- [whatwg/fetch] Split `document` destination for top-level and nested contexts. (#819)
- Re: [w3c/gamepad] are timestamps a potential tracking/fingerprinting vector? (#74)
- Re: [w3c/ServiceWorker] Clarify dynamic-imported scripts are never installed (#1356)
- Re: [w3c/ServiceWorker] cache.match should create partial responses if given a range request (#913)
- Re: [w3c/ServiceWorker] A simple globally available store of data per-registration (#1331)
- Re: [w3c/ServiceWorker] Proposal: FetchEvent.navigationLoadType (#1167)
- Re: [w3c/ServiceWorker] Proposal: FetchEvent.navigationLoadType (#1167)
- Re: [w3c/gamepad] are timestamps a potential tracking/fingerprinting vector? (#74)
- Re: [w3c/ServiceWorker] Does changing updateViaCache mint a new ServiceWorkerRegistration or update them all? (#1189)
- Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179)
- Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179)
- Re: [w3c/ServiceWorker] ready promise is kind of weird after you call unregister() (#1279)
- Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278)
- Re: [w3c/gamepad] are timestamps a potential tracking/fingerprinting vector? (#74)
- Re: [w3c/gamepad] are timestamps a potential tracking/fingerprinting vector? (#74)
- Re: [w3c/gamepad] are timestamps a potential tracking/fingerprinting vector? (#74)
- Re: [w3c/gamepad] are timestamps a potential tracking/fingerprinting vector? (#74)
- Re: [w3c/gamepad] are timestamps a potential tracking/fingerprinting vector? (#74)
- Re: [w3c/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756)
- Re: [w3c/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756)
- Re: [whatwg/dom] May return the same HTMLCollection object (#706)
- Re: [whatwg/dom] May return the same HTMLCollection object (#706)
- Re: [w3c/push-api] Security policies WRT Push traffic (#270)
- Re: [w3c/push-api] Security policies WRT Push traffic (#270)
- Re: [whatwg/dom] When moving APIs from other specs to DOM spec, ensure MDN is updated (#710)
- Re: [w3c/gamepad] Obsolete dependencies (#79)
- Re: [w3c/gamepad] Obsolete dependencies (#79)
- Re: [whatwg/fetch] Consider splitting `document` into `document` and `nested-document`. (#755)
- Re: [whatwg/dom] When moving APIs from other specs to DOM spec, ensure MDN is updated (#710)
- Re: [w3c/ServiceWorker] Proposal: Allow addEventListener/removeEventListener for 'fetch' to called at anytime (#1195)
- Re: [w3c/ServiceWorker] Proposal: Allow addEventListener/removeEventListener for 'fetch' to called at anytime (#1195)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- Re: [w3c/webcomponents] HTML Modules (#645)
- Re: [w3c/webcomponents] HTML Modules (#645)
Thursday, 25 October 2018
- Re: [w3c/webcomponents] HTML Modules (#645)
- Re: [whatwg/xhr] Ecommerce Websites (#226)
- Re: [whatwg/xhr] Ecommerce Websites (#226)
- [whatwg/xhr] Ecommerce Websites (#226)
- Re: [w3c/webcomponents] HTML Modules (#645)
- Re: [w3c/webcomponents] HTML Modules (#645)
- Re: [w3c/webcomponents] Presence of disconnectedCallback can expedite an invocation of connectedCallback (#760)
- Re: [w3c/webcomponents] HTML Modules (#645)
- Re: [whatwg/dom] A faster way to find open shadow roots (or shadow hosts) (#665)
- Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3c/ServiceWorker] Confusion around new events after skipWaiting (#1295)
- Re: [w3c/ServiceWorker] Confusion around new events after skipWaiting (#1295)
- [w3c/manifest] Icon matching algorithm: unrecognised purposes can result in "any" (#728)
- Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863)
- Re: [w3c/ServiceWorker] Provide a one-line way to listen for a waiting Service Worker (#1222)
- Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863)
- Re: [w3c/ServiceWorker] Allow caches to opt-in to granular cleanup (#863)
- Re: [w3c/webcomponents] HTML Modules (#645)
- Re: [w3c/webcomponents] HTML Modules (#645)
- Re: [w3c/ServiceWorker] Proposal: Allow addEventListener/removeEventListener for 'fetch' to called at anytime (#1195)
- Re: [w3c/webcomponents] HTML Modules (#645)
- Re: [whatwg/streams] Allow aborting an ongoing pipe operation using AbortSignals (#744)
- Re: [whatwg/streams] Allow aborting an ongoing pipe operation using AbortSignals (#744)
- Re: [w3c/gamepad] Obsolete dependencies (#79)
- Re: [w3c/ServiceWorker] No good way to beacon during activate (#1336)
- Re: [whatwg/dom] window.event and shadow trees (#679)
- Re: [whatwg/dom] window.event and shadow trees (#679)
- Re: [whatwg/dom] Allow <slot> to find slottables by slottables's IDs as well (#677)
- Re: [whatwg/dom] Allow <slot> to find slottables by slottables's IDs as well (#677)
- Re: [w3c/webcomponents] HTML Modules (#645)
- Re: [whatwg/dom] Allow <slot> to find slottables by slottables's IDs as well (#677)
- Re: [whatwg/dom] Allow <menu>, <ul>, <ol>, <li> to attach shadow (#676)
- Re: [whatwg/dom] A faster way to find open shadow roots (or shadow hosts) (#665)
- Re: [whatwg/dom] `compareDocumentPosition` should allow comparison of elements in the same shadow-including root (#320)
- Re: [whatwg/dom] `compareDocumentPosition` should allow comparison of elements in the same shadow-including root (#320)
- Re: [w3c/webcomponents] Presence of disconnectedCallback can expedite an invocation of connectedCallback (#760)
- Re: [w3c/editing] Should contenteditable have break-word behavior by default? (#145)
- Re: [w3c/webcomponents] Presence of disconnectedCallback can expedite an invocation of connectedCallback (#760)
- Re: [w3c/webcomponents] Presence of disconnectedCallback can expedite an invocation of connectedCallback (#760)
- Re: [w3c/webcomponents] Presence of disconnectedCallback can expedite an invocation of connectedCallback (#760)
- Re: [w3c/webcomponents] Presence of disconnectedCallback can expedite an invocation of connectedCallback (#760)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)
- Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)
- [whatwg/dom] Figure out if we want getComposedPath() for Event (#711)
- Re: [w3c/webcomponents] Selection APIs for Shadow DOM (#79)
- Re: [w3c/webcomponents] Selection APIs for Shadow DOM (#79)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- [whatwg/dom] When moving APIs from other specs to DOM spec, ensure MDN is updated (#710)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3c/webcomponents] <iframe> and the History API (#184)
- Re: [w3c/webcomponents] HTML Modules (#645)
- Re: [w3c/webcomponents] <iframe> and the History API (#184)
- Re: [w3c/webcomponents] <iframe> and the History API (#184)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179)
- Re: [w3c/ServiceWorker] is the browser required to start the ServiceWorker for postMessage() if there is no message event handler? (#1200)
- Re: [w3c/ServiceWorker] Proposal: FetchEvent.navigationLoadType (#1167)
- Re: [w3c/ServiceWorker] Does changing updateViaCache mint a new ServiceWorkerRegistration or update them all? (#1189)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3c/ServiceWorker] resurrected service workers don't fire an activate event which may break expectations (#1204)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [whatwg/dom] May return the same HTMLCollection object (#706)
- Re: [w3c/ServiceWorker] Provide a one-line way to listen for a waiting Service Worker (#1222)
- Re: [w3c/ServiceWorker] What is the name for `installing`, `waiting` and `active`? (#1362)
- Re: [w3c/ServiceWorker] What is the name for `installing`, `waiting` and `active`? (#1362)
- Re: [w3c/ServiceWorker] What is the name for `installing`, `waiting` and `active`? (#1362)
- Re: [w3c/webcomponents] HTML Modules (#645)
- Re: [w3c/ServiceWorker] What is the name for `installing`, `waiting` and `active`? (#1362)
- Re: [whatwg/dom] May return the same HTMLCollection object (#706)
- Re: [w3c/DOM-Parsing] innerHTML should be defined on ShadowRoot interface in addition to Element interface (#21)
- Re: [w3c/ServiceWorker] What is the name for `installing`, `waiting` and `active`? (#1362)
Wednesday, 24 October 2018
- Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179)
- Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179)
- Re: [w3c/ServiceWorker] Provide a one-line way to listen for a waiting Service Worker (#1222)
- Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179)
- Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179)
- Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179)
- Re: [w3c/ServiceWorker] Provide a one-line way to listen for a waiting Service Worker (#1222)
- Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179)
- [w3c/ServiceWorker] What is the name for `installing`, `waiting` and `active`? (#1362)
- Re: [w3c/editing] Should contenteditable have break-word behavior by default? (#145)
- Re: [w3c/webcomponents] Custom pseudo-classes for host elements via shadow roots (:state) (#738)
- Re: [whatwg/fetch] Specify restriction for requests with keepalive set (#679)
- Re: [w3c/ServiceWorker] A way to immediately unregister a service worker (#614)
- Re: [w3c/ServiceWorker] Feature request: Provide a way to delay execution of a new service worker (#1208)
- Re: [w3c/ServiceWorker] A way to immediately unregister a service worker (#614)
- Re: [w3c/ServiceWorker] A way to immediately unregister a service worker (#614)
- Re: [w3c/uievents] Need algorithm for how mouse events are fired (#196)
- Re: [w3c/ServiceWorker] A way to immediately unregister a service worker (#614)
- Re: [w3c/ServiceWorker] No good way to beacon during activate (#1336)
- Re: [w3c/ServiceWorker] No good way to beacon during activate (#1336)
- Re: [w3c/ServiceWorker] A way to immediately unregister a service worker (#614)
- Re: [whatwg/fetch] "With Credentials" flag possibly inconsistent with web architecture (#517)
- Re: [w3c/editing] spellchecking - how to give JS devs more control (#166)
- Re: [w3c/editing] spellchecking - how to give JS devs more control (#166)
- Re: [whatwg/fetch] Consider splitting `document` into `document` and `nested-document`. (#755)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3c/ServiceWorker] Should add a “script type” check in the register algorithm. (#1359)
- Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179)
- Re: [w3c/ServiceWorker] Should add a “script type” check in the register algorithm. (#1359)
- Re: [w3c/ServiceWorker] Should add a “script type” check in the register algorithm. (#1359)
Tuesday, 23 October 2018
- [w3c/manifest] API for discovering details about browser heuristics. (#727)
- Re: [w3c/editing] Should browsers support ContentEditable for <option> elements? (#180)
- Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179)
- Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/editing] Need API for retrieving/providing geometry of editing UI (#183)
- Re: [whatwg/dom] Custom element callback/promise for "connected and parsed" (#662)
- [w3c/editing] Need API for retrieving/providing geometry of editing UI (#183)
- [w3c/editing] Browsers should help in maximising the available space (#182)
- Re: [w3c/manifest] Add a way to query whether there is a UA-provided back button (#693)
- Re: [w3c/manifest] Add a way to query whether there is a UA-provided back button (#693)
- Re: [w3c/editing] Need spec for how HTML is serialized to be placed on the clipboard (#181)
- Re: [w3c/editing] copy/cut and text-transform (#178)
- Re: [w3c/editing] copy/cut and text-transform (#178)
- Re: [w3c/editing] Need spec for how HTML is serialized to be placed on the clipboard (#181)
- Re: [w3c/editing] Need spec for how HTML is serialized to be placed on the clipboard (#181)
- [w3c/editing] Need spec for how HTML is serialized to be placed on the clipboard (#181)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3c/DOM-Parsing] Tests (#37)
- Re: [w3ctag/design-reviews] [TPAC][HTML General Review]: how to decide if workers are subresources or separate contexts (#310)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818)
- [w3ctag/design-reviews] [TPAC][HTML General Review]: how to decide if workers are subresources or separate contexts (#310)
- Re: [whatwg/dom] [spec bug?] Element with name attribute breaks Document (#708)
- Re: [whatwg/dom] [spec bug?] Element with name attribute breaks Document (#708)
- Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818)
- Re: [whatwg/fetch] "With Credentials" flag possibly inconsistent with web architecture (#517)
- Re: [w3c/webcomponents] Add new proposal (#768)
- Re: [whatwg/dom] [spec bug?] Element with name attribute breaks Document (#708)
- Re: [w3c/ServiceWorker] NavigationPreloadManager.setHeaderValue should reject invalid HTTP header field values (#1000)
- Re: [w3c/webcomponents] HTML Modules (#645)
Monday, 22 October 2018
- Re: [w3c/manifest] Add a way to query whether there is a UA-provided back button (#693)
- Re: [whatwg/encoding] If gb18030 is revised, consider aligning the Encoding Standard (#27)
- Re: [w3c/gamepad] spec `gamepadbuttondown` and `gamepadbuttonup` events (issue #4) (#15)
- Re: [whatwg/encoding] If gb18030 is revised, consider aligning the Encoding Standard (#27)
- Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)
- Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)
- Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)
- Re: [w3c/editing] Should a styled paragraph maintain its own style when inserting it in a list ? (#179)
- Re: [w3c/editing] Should a styled paragraph maintain its own style when inserting it in a list ? (#179)
- Re: [whatwg/dom] tr (#709)
- [whatwg/dom] tr (#709)
- Re: [whatwg/fetch] "With Credentials" flag possibly inconsistent with web architecture (#517)
- Re: [w3c/DOM-Parsing] Fragment serialization algorithm serializes node itself (#28)
- Re: [w3c/webcomponents] HTML Modules (#645)
- Re: [whatwg/dom] Improving ergonomics of events with Observable (#544)
- Re: [whatwg/dom] Improving ergonomics of events with Observable (#544)
- Re: [w3c/webcomponents] HTML Modules (#645)
- Re: [w3c/DOM-Parsing] innerHTML should be defined on ShadowRoot interface in addition to Element interface (#21)
- Re: [w3c/DOM-Parsing] Serialization algorithm never preserves attribute prefixes (#29)
- [w3c/webcomponents] Add new proposal (#768)
- [w3c/DOM-Parsing] Tests (#37)
- Re: [w3c/DOM-Parsing] DOMParser's parseFromString should have CEReactions (#22)
- Re: [w3c/DOM-Parsing] Serialization algorithm never preserves attribute prefixes (#29)
- Re: [w3c/DOM-Parsing] DOMParser's parseFromString should have CEReactions (#22)
- Re: [w3c/DOM-Parsing] Fragment serialization algorithm serializes node itself (#28)
- Re: [w3c/DOM-Parsing] DOMParser's parseFromString should have CEReactions (#22)
- Re: [w3c/DOM-Parsing] DOMParser's parseFromString should have CEReactions (#22)
- Re: [w3c/DOM-Parsing] Define the origin of the documents returned from DOMParser (#24)
- Re: [w3c/DOM-Parsing] innerHTML should be defined on ShadowRoot interface in addition to Element interface (#21)
- Re: [w3c/DOM-Parsing] innerHTML should be defined on ShadowRoot interface in addition to Element interface (#21)
- Re: [w3c/DOM-Parsing] How should createContextualFragment interact with `<script>` inside `<template>`? (#19)
- Re: [whatwg/fetch] "With Credentials" flag possibly inconsistent with web architecture (#517)
- Re: [w3c/DOM-Parsing] Time at TPAC? (#27)
- Re: [w3c/DOM-Parsing] Time at TPAC? (#27)
- Re: [w3c/DOM-Parsing] Time at TPAC? (#27)
- Re: [w3c/webcomponents] Having slots as element prevents styling empty containers (#701)
- Re: [w3c/webcomponents] Web Components F2F topics for 2018 TPAC (#763)
- Re: [heycam/webidl] Should "perform some steps once a promise is settled" use %PromiseProto_then%? (#583)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3c/webcomponents] Web Components F2F topics for 2018 TPAC (#763)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3c/ServiceWorker] Preventing server-forced updates (#822)
Sunday, 21 October 2018
- [whatwg/dom] [spec bug?] Element with name attribute breaks Document (#708)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/ServiceWorker] Formalizing a timeout API (#1292)
- Re: [w3c/ServiceWorker] Allow active worker to immediately evict itself (#1296)
- Re: [w3c/permissions] Allow Feature Policy-based permission models (#185)
- Re: [w3c/permissions] Allow Feature Policy-based permission models (#185)
Saturday, 20 October 2018
- [w3c/editing] Should browsers support ContentEditable for <option> elements? (#180)
- Re: [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [heycam/webidl] Add [Exposed=*] to expose on all globals (#526)
- Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)
- Re: [whatwg/fetch] Using multipart/form-data with multer occasionally causes React app to crash and refresh (#677)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3ctag/design-reviews] TAG Review Request: RTCIceTransport (#304)
- Re: [w3ctag/design-reviews] TAG review request: User Activation v2 (#295)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/webcomponents] Having slots as element prevents styling empty containers (#701)
- Re: [w3c/permissions] Add 'display' permission for screen-capture. (#184)
Friday, 19 October 2018
- Re: [whatwg/fullscreen] Re-introduce the hierarchy restrictions (#140)
- Re: [heycam/webidl] Intent to use [LegacyNamespace] (#588)
- [heycam/webidl] Intent to use [LegacyNamespace] (#588)
- Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)
- Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)
- Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)
- Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)
- Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)
- Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818)
- [w3c/ServiceWorker] clarify how navigation preload fetches can be measured using performance API (#1361)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [whatwg/streams] Allow aborting an ongoing pipe operation using AbortSignals (#744)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [whatwg/fetch] Redesign "extract header values" and "extract header list values" (#814)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [whatwg/dom] May return the same HTMLCollection object (#706)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550)
- Re: [w3c/webcomponents] Consider adding a childrenChangedCallback or something (#619)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [whatwg/dom] May return the same HTMLCollection object (#706)
- Re: [w3c/permissions] Allow Feature Policy-based permission models (#185)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/webcomponents] Selection APIs for Shadow DOM (#79)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3c/ServiceWorker] Clean up Clients interface methods (#1332)
- Re: [w3c/ServiceWorker] Clean up Clients interface methods (#1332)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3c/ServiceWorker] Remove frameType, maybe add ancestorOrigins (#732)
- Re: [w3c/ServiceWorker] Add Client.frameType back (#1329)
Thursday, 18 October 2018
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818)
- Re: [whatwg/fetch] Redesign "extract header values" and "extract header list values" (#814)
- Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818)
- Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818)
- Re: [w3c/ServiceWorker] What is the correct way to notify the DOM thread about files that have been cached ? (#1260)
- Re: [w3c/ServiceWorker] What is the correct way to notify the DOM thread about files that have been cached ? (#1260)
- Re: [w3c/gamepad] [Extensions] make pulse() more like navigator.vibrate (#66)
- Re: [w3c/gamepad] [Extensions] make pulse() more like navigator.vibrate (#66)
- Re: [w3c/gamepad] About the id (#65)
- Re: [w3c/uievents] Consider to make mouseenter/leave (and pointerenter/leave) uncomposed (#208)
- Re: [whatwg/dom] May return the same HTMLCollection object (#706)
- Re: [whatwg/dom] May return the same HTMLCollection object (#706)
- Re: [whatwg/dom] May return the same HTMLCollection object (#706)
- Re: [whatwg/dom] May return the same HTMLCollection object (#706)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [whatwg/dom] Set event’s target to the target of the last tuple in event’s path, that is either tuple or preceding tuple, whose target is non-null. (#707)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [whatwg/dom] Set event’s target to the target of the last tuple in event’s path, that is either tuple or preceding tuple, whose target is non-null. (#707)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [whatwg/dom] Set event’s target to the target of the last tuple in event’s path, that is either tuple or preceding tuple, whose target is non-null. (#707)
- Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818)
- Re: [whatwg/dom] Set event’s target to the target of the last tuple in event’s path, that is either tuple or preceding tuple, whose target is non-null. (#707)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [whatwg/dom] Set event’s target to the target of the last tuple in event’s path, that is either tuple or preceding tuple, whose target is non-null. (#707)
- Re: [whatwg/streams] WHATWG icon is broken in Chrome in combination with ServiceWorker (#955)
- Re: [whatwg/dom] Set event’s target to the target of the last tuple in event’s path, that is either tuple or preceding tuple, whose target is non-null. (#707)
- Re: [whatwg/dom] Set event’s target to the target of the last tuple in event’s path, that is either tuple or preceding tuple, whose target is non-null. (#707)
- Re: [whatwg/dom] Set event’s target to the target of the last tuple in event’s path, that is either tuple or preceding tuple, whose target is non-null. (#707)
- Re: [whatwg/dom] Set event’s target to the target of the last tuple in event’s path, that is either tuple or preceding tuple, whose target is non-null. (#707)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [whatwg/dom] Set event’s target to the target of the last tuple in event’s path, that is either tuple or preceding tuple, whose target is non-null. (#707)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- [whatwg/dom] Set event’s target to the target of the last tuple in event’s path, that is either tuple or preceding tuple, whose target is non-null. (#707)
- Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818)
- Re: [whatwg/dom] May return the same HTMLCollection object (#706)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [whatwg/dom] May return the same HTMLCollection object (#706)
- [whatwg/dom] May return the same HTMLCollection object (#706)
- Re: [w3c/permissions] A new permission for screen-sharing with getDisplayMedia() (#182)
Wednesday, 17 October 2018
- [w3c/permissions] Allow Feature Policy-based permission models (#185)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [whatwg/encoding] bind encoder to self (#159)
- Re: [w3c/selection-api] edge 中selection.focusOffset计算错误 (#97)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/touch-events] Add getModifierState definition to TouchEvent. This matches the text (#91)
- Re: [w3c/touch-events] Add getModifierState definition to TouchEvent. This matches the text (#91)
- Re: [w3c/touch-events] Add getModifierState definition to TouchEvent. This matches the text (#91)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/touch-events] Add getModifierState definition to TouchEvent. This matches the text (#91)
- Re: [w3c/touch-events] Clarify cancelability during scroll (#79)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/touch-events] Clarify "deprecated in this specification" (#80)
- Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818)
- Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818)
- Re: [whatwg/url] Do not remove newline and tab characters (#419)
- Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [whatwg/fetch] What does "combined value" return for a name not in the header list? (#752)
- [w3c/clipboard-apis] IDL doesn't link correctly (#83)
- Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818)
- [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818)
- [whatwg/fetch] Editorial: drop parenthesis around variables (#817)
- Re: [w3c/touch-events] Clarify "deprecated in this specification" (#80)
- Re: [w3c/touch-events] Clarify "deprecated in this specification" (#80)
- Re: [w3c/gamepad] Cleanup (#84)
- [w3c/selection-api] edge 中selection.focusOffset计算错误 (#97)
- [whatwg/fetch] Remove Gecko-only quirk (#816)
- [whatwg/fetch] Editorial: remove leftover sentence (#815)
- Re: [whatwg/encoding] bind encoder to self (#159)
- Re: [whatwg/encoding] bind encoder to self (#159)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/gamepad] Cleanup (#84)
- Re: [w3c/gamepad] Cleanup (#84)
- Re: [w3c/touch-events] update "Changes Since Last Publication" section (#101)
- [w3c/touch-events] update "Changes Since Last Publication" section (#101)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/touch-events] Remove note about initTouchEvent / createTouchList from the "5 TouchEvent Interface" section (#100)
- [w3c/touch-events] Remove note about initTouchEvent / createTouchList from the "5 TouchEvent Interface" section (#100)
- Re: [whatwg/encoding] ISO 2022-jp encoding/decoding support (#60)
- Re: [whatwg/encoding] ISO 2022-jp encoding/decoding support (#60)
- Re: [whatwg/encoding] Shift-JIS encoding/decoding support (#61)
- Re: [whatwg/encoding] Shift-JIS encoding/decoding support (#61)
- Re: [whatwg/encoding] EUK-kr encoding/decoding support (#62)
- Re: [whatwg/encoding] EUK-kr encoding/decoding support (#62)
- Re: [whatwg/encoding] EUC-jp encoding/decoding support (#59)
- Re: [whatwg/encoding] EUC-jp encoding/decoding support (#59)
- Re: [whatwg/encoding] Big5 encoding/decoding support (#58)
- Re: [whatwg/encoding] Big5 encoding/decoding support (#58)
- Re: [whatwg/encoding] gb18030 encoding/decoding support (#57)
- Re: [whatwg/encoding] GBK encoding/decoding support (#56)
- Re: [w3c/touch-events] Remove createTouch and createTouch list (#96)
- Re: [whatwg/url] Do not remove newline and tab characters (#419)
- Re: [whatwg/url] Do not remove newline and tab characters (#419)
- Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/gamepad] spec vibrationActuator gamepad extension (#68)
- Re: [w3c/gamepad] spec vibrationActuator gamepad extension (#68)
- Re: [w3c/gamepad] spec `gamepadbuttondown` and `gamepadbuttonup` events (issue #4) (#15)
- Re: [w3c/gamepad] Cleanup (#84)
- Re: [w3c/gamepad] Fix Promise type (#78)
- Re: [w3c/gamepad] Fix Promise type (#78)
- Re: [w3c/touch-events] Clarify "deprecated in this specification" (#80)
- Re: [w3c/touch-events] Clarify "deprecated in this specification" (#80)
- Re: [w3c/touch-events] Clarify "deprecated in this specification" (#80)
- Re: [w3c/touch-events] Remove createTouch and createTouch list (#96)
- Re: [w3c/screen-orientation] Fix ReSpec errors (#122)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- [w3c/IndexedDB] Transaction storm in idb-transaction-commit explainer sample (#245)
Tuesday, 16 October 2018
- Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107)
- Re: [w3c/permissions] Add 'display' permission for screen-capture. (#184)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/WebPlatformWG] Updates HTML F2F meeting info (b817ef3)
- Re: [whatwg/url] Do not remove newline and tab characters (#419)
- [whatwg/url] Do not remove newline and tab characters (#419)
- Re: [w3c/WebPlatformWG] Updates HTML F2F meeting info (b817ef3)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/permissions] Add 'display' permission for screen-capture. (#184)
- Re: [whatwg/fetch] Change combined values (#813)
- Re: [whatwg/xhr] cant login to porn (#225)
- [whatwg/xhr] cant login to porn (#225)
- Re: [whatwg/xhr] Limit Content-Type overrides to when charset isn't already UTF-8 (#224)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [whatwg/xhr] Limit Content-Type overrides to when charset isn't already UTF-8 (#224)
- [whatwg/xhr] Limit Content-Type overrides to when charset isn't already UTF-8 (#224)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [whatwg/fetch] "combined value" is wrong (#757)
- Re: [whatwg/fetch] "combined value" is wrong (#757)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3ctag/design-reviews] `sec-metadata` (#280)
- Re: [w3c/screen-orientation] Fix ReSpec errors (#122)
- Re: [w3c/screen-orientation] Fix ReSpec errors (#122)
- Re: [w3c/screen-orientation] Fix ReSpec errors (#122)
- Re: [whatwg/fetch] Change combined values (#813)
- Re: [whatwg/fetch] Change combined values (#813)
- Re: [w3c/screen-orientation] Fix ReSpec errors (#122)
- Re: [w3c/gamepad] Cleanup (#84)
- Re: [w3c/gamepad] Cleanup (#84)
- Re: [w3c/gamepad] fix inline refs (#81)
- Re: [w3c/gamepad] fix inline refs (#81)
- [w3c/gamepad] Cleanup (#84)
- Re: [whatwg/dom] Upstream `delegatesFocus` property of ShadowRootInit from W3C spec. (#367)
- Re: [whatwg/dom] Upstream `delegatesFocus` property of ShadowRootInit from W3C spec. (#367)
- Re: [w3c/screen-orientation] Fix ReSpec errors (#122)
- Re: [w3c/screen-orientation] Fix ReSpec errors (#122)
- Re: [whatwg/fetch] "combined value" is wrong (#757)
- Re: [whatwg/fetch] Change combined values (#813)
- Re: [whatwg/fetch] Change combined values (#813)
- Re: [w3c/FileAPI] Add implementation report link. For issue #111 (#112)
- Re: [w3c/FileAPI] Add implementation report link. For issue #111 (#112)
- Re: [w3c/FileAPI] Add implementation report link. For issue #111 (#112)
Monday, 15 October 2018
- Re: [w3c/selection-api] Specify baseNode/baseOffset/extentNode/extentOffset? (#34)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3c/selection-api] Specify baseNode/baseOffset/extentNode/extentOffset? (#34)
- Re: [w3c/webcomponents] Undocumented behaviour with regards to attributeChangedCallback and DOM access (#767)
- Re: [w3c/webcomponents] Undocumented behaviour with regards to attributeChangedCallback and DOM access (#767)
- Re: [whatwg/dom] Upstream `delegatesFocus` property of ShadowRootInit from W3C spec. (#367)
- Re: [w3c/FileAPI] Add implementation report link. For issue #111 (#112)
- Re: [w3c/FileAPI] Implementer interest in this spec (#111)
- [w3c/FileAPI] Add implementation report link. For issue #111 (#112)
- Re: [whatwg/fetch] Change combined values (#813)
- Re: [w3c/selection-api] Specify baseNode/baseOffset/extentNode/extentOffset? (#34)
- Re: [whatwg/fetch] Change combined values (#813)
- Re: [whatwg/url] How are hosts in custom schemes to be handled? (#418)
- Re: [whatwg/url] new URL('file://').origin is 'null' (#310)
- Re: [whatwg/url] How are hosts in custom schemes to be handled? (#418)
- [whatwg/streams] Demos need updating to use TextDecoderStream (#959)
- Re: [whatwg/url] How are hosts in custom schemes to be handled? (#418)
- Re: [whatwg/url] Consider adding non-throwing URL.parse(input, base) (#372)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [whatwg/url] new URL('file://').origin is 'null' (#310)
- Re: [whatwg/url] new URL('file://').origin is 'null' (#310)
- Re: [w3c/FileAPI] "Null"ing out the Origin of a BLOB (#74)
- Re: [w3c/FileAPI] "Null"ing out the Origin of a BLOB (#74)
- Re: [whatwg/streams] Using fetch streams API without recursion (#958)
- Re: [whatwg/streams] Using fetch streams API without recursion (#958)
- Re: [w3c/selection-api] Specify baseNode/baseOffset/extentNode/extentOffset? (#34)
- Re: [w3c/webcomponents] Undocumented behaviour with regards to attributeChangedCallback and DOM access (#767)
- Re: [w3c/permissions] Add 'display' permission for screen-capture. (#184)
- Re: [w3c/FileAPI] "Null"ing out the Origin of a BLOB (#74)
- [whatwg/streams] Using fetch streams API without recursion (#958)
- Re: [w3c/webcomponents] Undocumented behaviour with regards to attributeChangedCallback and DOM access (#767)
- Re: [w3c/webcomponents] Undocumented behaviour with regards to attributeChangedCallback and DOM access (#767)
- Re: [w3c/webcomponents] Undocumented behaviour with regards to attributeChangedCallback and DOM access (#767)
Sunday, 14 October 2018
- [w3c/webcomponents] Unspecified behaviour with regards to attributeChangedCallback and DOM access (#767)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3c/screen-orientation] Steps for updating orientation information are misleading (#100)
- Re: [whatwg/url] new URL('file://').origin is 'null' (#310)
- Re: [whatwg/url] new URL('file://').origin is 'null' (#310)
- Re: [whatwg/url] new URL('file://').origin is 'null' (#310)
- Re: [whatwg/dom] async disconnectedCallback? (#705)
- Re: [whatwg/dom] async disconnectedCallback? (#705)
- Re: [whatwg/url] Consider adding non-throwing URL.parse(input, base) (#372)
- [whatwg/dom] async disconnectedCallback? (#705)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- [whatwg/url] How are hosts in custom schemes to be handled? (#418)
- Re: [w3c/gamepad] fix inline refs (#81)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
Saturday, 13 October 2018
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/screen-orientation] Fix ReSpec errors (#122)
Friday, 12 October 2018
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/FileAPI] Implementer interest in this spec (#111)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [whatwg/fetch] Change combined values (#813)
- Re: [w3c/FileAPI] Implementer interest in this spec (#111)
- Re: [w3c/FileAPI] Implementer interest in this spec (#111)
- Re: [whatwg/streams] Meta: fix realm issues in reference implementation testing setup (#957)
- Re: [w3c/touch-events] Remove createTouch and createTouch list (#96)
- Re: [w3c/permissions] Add 'display' permission for screen-capture. (#184)
- [w3c/ServiceWorker] Redesign of "extract header list values" expected (#1360)
- Re: [w3c/permissions] Add 'display' permission for screen-capture. (#184)
- Re: [w3c/screen-orientation] Fix ReSpec errors (#122)
- Re: [w3c/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- [whatwg/fetch] Redesign "extract header values" and "extract header list values" (#814)
- [w3c/screen-orientation] Fix ReSpec errors (#122)
- Re: [whatwg/streams] Add explainer for transferable streams (#956)
- Re: [whatwg/streams] Add explainer for transferable streams (#956)
- Re: [w3ctag/design-reviews] TAG Review Request: HTTP State Tokens (#297)
- Re: [w3ctag/design-reviews] TAG Review Request: HTTP State Tokens (#297)
- Re: [whatwg/fetch] What does "combined value" return for a name not in the header list? (#752)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179)
- Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/permissions] Add 'display' permission for screen-capture. (#184)
- Re: [w3c/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940)
- Re: [w3c/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940)
- Re: [w3c/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940)
- Re: [whatwg/streams] Meta: fix realm issues in reference implementation testing setup (#957)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940)
- Re: [w3c/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940)
- Re: [w3c/screen-orientation] Add interaction with WCAG 2.1 (#117)
- Re: [w3c/screen-orientation] Add interaction with WCAG 2.1 (#117)
- Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)
- Re: [w3c/FileAPI] Implementer interest in this spec (#111)
- Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179)
- Re: [w3c/FileAPI] Implementer interest in this spec (#111)
- Re: [w3c/FileAPI] Implementer interest in this spec (#111)
- Re: [w3c/FileAPI] Implementer interest in this spec (#111)
- Re: [w3c/FileAPI] Implementer interest in this spec (#111)
- Re: [w3c/FileAPI] Implementer interest in this spec (#111)
- Re: [w3c/FileAPI] Implementer interest in this spec (#111)
- Re: [w3c/FileAPI] Implementer interest in this spec (#111)
- Re: [w3c/FileAPI] Implementer interest in this spec (#111)
- Re: [w3c/screen-orientation] Add Privacy and Security Considerations section (#115)
- Re: [w3c/selection-api] setBaseAndExtent should clear selection when baseNode or extentNode is null (#72)
- Re: [w3c/FileAPI] Implementer interest in this spec (#111)
- Re: [w3c/screen-orientation] Add Privacy and Security Considerations section (#115)
- [w3c/FileAPI] Implementer interest in this spec (#111)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179)
- Re: [w3c/permissions] Add 'display' permission for screen-capture. (#184)
- Re: [w3c/permissions] Add 'display' permission for screen-capture. (#184)
- Re: [w3c/permissions] Add 'display' permission for screen-capture. (#184)
- Re: [w3c/screen-orientation] Lacks a privacy and security consideration section (#96)
- Re: [w3c/screen-orientation] Add interaction with WCAG 2.1 (#117)
- Re: [w3c/screen-orientation] Add Privacy and Security Considerations section (#115)
- Re: [w3c/screen-orientation] Add Privacy and Security Considerations section (#115)
- Re: [w3c/screen-orientation] Lacks a privacy and security consideration section (#96)
- Re: [w3c/screen-orientation] Add Privacy and Security Considerations section (#115)
- Re: [w3c/screen-orientation] Add Privacy and Security Considerations section (#115)
- Re: [w3c/screen-orientation] Add Privacy and Security Considerations section (#115)
- Re: [w3c/permissions] Add 'display' permission for screen-capture. (#184)
- Re: [w3c/permissions] Add 'display' permission for screen-capture. (#184)
- Re: [w3c/permissions] Add 'display' permission for screen-capture. (#184)
- Re: [w3c/permissions] Add support for permissions that have an associated Feature Policy (#163)
- Re: [w3c/permissions] Add support for permissions that have an associated Feature Policy (#163)
- Re: [w3c/permissions] Add 'display' permission for screen-capture. (#184)
Thursday, 11 October 2018
- Re: [w3c/screen-orientation] Add Privacy and Security Considerations section (#115)
- Re: [w3c/screen-orientation] Add Privacy and Security Considerations section (#115)
- Re: [w3c/screen-orientation] Edit Privacy and Security Consideration Section (#121)
- Re: [w3c/screen-orientation] Add Privacy and Security Considerations section (#115)
- Re: [w3c/screen-orientation] Edit Privacy and Security Consideration Section (#121)
- Re: [w3c/screen-orientation] Edit Privacy and Security Consideration Section (#121)
- [w3c/permissions] Add 'display' permission for screen-capture. (#184)
- Re: [w3c/screen-orientation] Edit Privacy and Security Consideration Section (#121)
- [w3c/screen-orientation] Edit Privacy and Security Consideration Section (#121)
- Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179)
- Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179)
- Re: [whatwg/streams] Add explainer for transferable streams (#956)
- [whatwg/streams] Meta: fix realm issues in reference implementation testing setup (#957)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- Re: [whatwg/streams] Implement pipeTo() abort in the ref impl (2ed62aa)
- Re: [w3c/permissions] Add support for permissions that have an associated Feature Policy (#163)
- Re: [whatwg/fetch] Change combined values (#813)
- Re: [whatwg/fetch] Change combined values (#813)
- [whatwg/fetch] Change combined values (#813)
- Re: [whatwg/streams] Allow aborting an ongoing pipe operation using AbortSignals (#744)
- Re: [whatwg/streams] Allow aborting an ongoing pipe operation using AbortSignals (#744)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- Re: [whatwg/streams] Implement pipeTo() abort in the ref impl (2ed62aa)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- Re: [whatwg/fetch] "combined value" is wrong (#757)
- Re: [w3c/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940)
- Re: [w3c/ServiceWorker] Is it possible to serve service workers from CDN/remote origin? (#940)
- Re: [w3c/ServiceWorker] Order of messages to clients in same unit of related browsing contexts unclear (#1355)
- Re: [whatwg/encoding] Коды (#161)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3ctag/design-reviews] TAG Review Request: HTTP State Tokens (#297)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- Re: [whatwg/streams] Add explainer for transferable streams (#956)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- Re: [w3c/ServiceWorker] Confusion around new events after skipWaiting (#1295)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3c/manifest] Install button on another domain (#726)
Wednesday, 10 October 2018
- Re: [w3c/manifest] [chore] Fix id of Icon masks section. (#725)
- [whatwg/encoding] Коды (#161)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3c/manifest] Install button on another domain (#726)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3c/manifest] Install button on another domain (#726)
- Re: [w3c/ServiceWorker] Confusion around new events after skipWaiting (#1295)
- [w3c/manifest] Install button on another domain (#726)
- Re: [w3c/ServiceWorker] No good way to beacon during activate (#1336)
- Re: [w3c/ServiceWorker] No good way to beacon during activate (#1336)
- Re: [w3c/ServiceWorker] Order of messages to clients in same unit of related browsing contexts unclear (#1355)
- Re: [w3c/ServiceWorker] Formalizing a timeout API (#1292)
- Re: [w3c/ServiceWorker] Confusion around new events after skipWaiting (#1295)
- Re: [w3c/ServiceWorker] Does ServiceWorkerContainer.onmessage also get ExtendableMessageEvent object? (#1301)
- Re: [w3c/ServiceWorker] Is resultingClientId preserved over redirects? (#1316)
- Re: [w3c/ServiceWorker] Is resultingClientId preserved over redirects? (#1316)
- Re: [w3c/ServiceWorker] importScripts() on ServiceWorkerGlobalScope (#1319)
- Re: [w3c/ServiceWorker] No good way to beacon during activate (#1336)
- Re: [w3c/ServiceWorker] Order of messages to clients in same unit of related browsing contexts unclear (#1355)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- Re: [whatwg/streams] Add explainer for transferable streams (#956)
- Re: [w3c/pointerlock] Option needed to disable OS-level adjustment for mouse acceleration (#36)
- [whatwg/streams] Add explainer for transferable streams (#956)
- Re: [w3c/manifest] [chore] Fix id of Icon masks section. (#725)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- Re: [w3c/manifest] [chore] Fix id of Icon masks section. (#725)
- [w3c/manifest] [chore] Fix id of Icon masks section. (#725)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- Re: [w3ctag/design-reviews] TAG Review Request: Form Participation API (#305)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
Tuesday, 9 October 2018
- Re: [w3c/IndexedDB] Add IDBTransaction commit() method (#242)
- Re: [w3c/IndexedDB] Add IDBTransaction commit() method (#242)
- Re: [w3c/IndexedDB] Add IDBTransaction commit() method (#242)
- Re: [w3c/IndexedDB] Add IDBTransaction commit() method (#242)
- [w3ctag/design-reviews] TAG Review Request: Screen Capture API (#309)
- Re: [w3c/IndexedDB] Add IDBTransaction commit() method (#242)
- Re: [w3c/IndexedDB] Add IDBTransaction commit() method (#242)
- Re: [w3c/IndexedDB] Add IDBTransaction commit() method (#242)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- Re: [w3ctag/design-reviews] TAG Review Request: Support codec and container switching with MSE using SourceBuffer.changeType() (#298)
- Re: [w3ctag/design-reviews] TAG Review Request: Support codec and container switching with MSE using SourceBuffer.changeType() (#298)
- Re: [w3ctag/design-reviews] TAG Review Request: Form Participation API (#305)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- Re: [w3ctag/design-reviews] TAG Review Request: RTCIceTransport (#304)
- Re: [w3ctag/design-reviews] TAG Review Request: RTCQuicTransport (#303)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- Re: [w3c/webcomponents] Effect of removing 'Object.setPrototypeOf(MyEl, HTMLElement)' while using ES5 prototype pattern for web components (#766)
- Re: [w3c/webcomponents] Effect of removing 'Object.setPrototypeOf(MyEl, HTMLElement)' while using ES5 prototype pattern for web components (#766)
- Re: [whatwg/url] Add a neato informative table of various URL pieces (#337)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- Re: [w3c/manifest] Added new definition "within scope of a manifest". (#724)
- Re: [w3c/manifest] [chore] Fix normative references in informative sections (#723)
- Re: [w3c/manifest] [chore] Run tidy on new icon masking section. (#722)
- Re: [w3c/manifest] Added new definition "within scope of a manifest". (#724)
- Re: [w3c/manifest] [chore] Fix normative references in informative sections (#723)
- Re: [w3c/manifest] [chore] Run tidy on new icon masking section. (#722)
- [w3c/manifest] Added new definition "within scope of a manifest". (#724)
- [w3c/manifest] [chore] Fix normative references in informative sections (#723)
- [w3c/manifest] [chore] Run tidy on new icon masking section. (#722)
- Re: [w3c/manifest] Breaking: Change requirement to block off-scope navigation. (#701)
- Re: [w3c/manifest] Clarify rule of navigating away from the navigation scope (#646)
- Re: [w3c/manifest] Breaking: Change requirement to block off-scope navigation. (#701)
- Re: [w3c/manifest] Breaking: Change requirement to block off-scope navigation. (#701)
Monday, 8 October 2018
- Re: [w3c/webcomponents] Effect of removing 'Object.setPrototypeOf(MyEl, HTMLElement)' while using ES5 prototype pattern for web components (#766)
- Re: [w3c/webcomponents] Effect of removing 'Object.setPrototypeOf(MyEl, HTMLElement)' while using ES5 prototype pattern for web components (#766)
- Re: [w3c/webcomponents] Effect of removing 'Object.setPrototypeOf(MyEl, HTMLElement)' while using ES5 prototype pattern for web components (#766)
- Re: [w3c/webcomponents] Effect of removing 'Object.setPrototypeOf(MyEl, HTMLElement)' while using ES5 prototype pattern for web components (#766)
- Re: [w3ctag/design-reviews] Tag Review Request: Canvas TextMetrics (#302)
- Re: [w3c/webcomponents] @trusktr you're not returning the right object from the constructor. You're creating an HTMLElement, then implicitly returning MyEl, which is not an HTMLElement. Regardless of setting the prototype and what `instanceof` says, it doesn't wrap a native element object like HTMLElement does. (#766)
- Re: [w3ctag/design-reviews] Tag Review Request: Canvas TextMetrics (#302)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- Re: [whatwg/url] Add a neato informative table of various URL pieces (#337)
- Re: [whatwg/url] Add a neato informative table of various URL pieces (#337)
- Re: [whatwg/url] Add a neato informative table of various URL pieces (#337)
- Re: [whatwg/url] Add a neato informative table of various URL pieces (#337)
- Re: [whatwg/url] Add a neato informative table of various URL pieces (#337)
- Re: [w3c/manifest] Allow for multiple scopes (#449)
- Re: [whatwg/url] Add a neato informative table of various URL pieces (#337)
- Re: [whatwg/url] Add a neato informative table of various URL pieces (#337)
- Re: [whatwg/url] Add a neato informative table of various URL pieces (#337)
- Re: [whatwg/url] Add a neato informative table of various URL pieces (#337)
- Re: [whatwg/dom] Make NodeIterator Iterable (#704)
- Re: [whatwg/dom] Make NodeIterator Iterable (#704)
- Re: [whatwg/url] Add a neato informative table of various URL pieces (#337)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- Re: [whatwg/dom] Make NodeIterator Iterable (#704)
- Re: [whatwg/dom] Make NodeIterator Iterable (#704)
- Re: [whatwg/fetch] upload progress? (#21)
- Re: [w3c/pointerlock] Option needed to disable OS-level adjustment for mouse acceleration (#36)
- Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657)
Sunday, 7 October 2018
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)
- [whatwg/dom] Make NodeIterator Iterable (#704)
Saturday, 6 October 2018
- Re: [w3c/IndexedDB] Proposal: Add explicit IDBTransaction.commit() (was: add "writeonly" mode) (#234)
- Re: [w3c/IndexedDB] Add IDBTransaction commit() method (#242)
- Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681)
- Re: [w3c/webcomponents] @trusktr you're not returning the right object from the constructor. You're creating an HTMLElement, then implicitly returning MyEl, which is not an HTMLElement. Regardless of setting the prototype and what `instanceof` says, it doesn't wrap a native element object like HTMLElement does. (#766)
- Re: [w3c/webcomponents] @trusktr you're not returning the right object from the constructor. You're creating an HTMLElement, then implicitly returning MyEl, which is not an HTMLElement. Regardless of setting the prototype and what `instanceof` says, it doesn't wrap a native element object like HTMLElement does. (#766)
- Re: [w3c/webcomponents] HTML Modules (#645)
Friday, 5 October 2018
- Re: [w3ctag/design-reviews] TAG Review Request: RTCIceTransport & RTCQuicTransport (#296)
- Re: [whatwg/streams] A couple Bikeshed warnings (#929)
- Re: [whatwg/streams] A couple Bikeshed warnings (#929)
- Re: [whatwg/url] Add a neato informative table of various URL pieces (#337)
- Re: [w3c/webcomponents] HTML Modules (#645)
- Re: [w3c/webcomponents] HTML Modules (#645)
- Re: [w3c/webcomponents] HTML Modules (#645)
- Re: [w3c/webcomponents] HTML Modules (#645)
- Re: [w3c/webcomponents] HTML Modules (#645)
- Re: [w3c/editing] contenteditable-disabled (#176)
- Re: [w3c/webcomponents] HTML Modules (#645)
- Re: [whatwg/streams] Implement pipeTo() abort in the ref impl (2ed62aa)
- Re: [w3c/webcomponents] HTML Modules (#645)
- [w3c/webcomponents] @trusktr you're not returning the right object from the constructor. You're creating an HTMLElement, then implicitly returning MyEl, which is not an HTMLElement. Regardless of setting the prototype and what `instanceof` says, it doesn't wrap a native element object like HTMLElement does. (#766)
- Re: [w3c/webcomponents] HTML Modules (#645)
- Re: [w3c/webcomponents] HTML Modules (#645)
- Re: [w3c/webcomponents] HTML Modules (#645)
- Re: [whatwg/streams] Implement pipeTo() abort in the ref impl (2ed62aa)
- Re: [whatwg/streams] Implement pipeTo() abort in the ref impl (2ed62aa)
- Re: [whatwg/streams] Implement pipeTo() abort in the ref impl (2ed62aa)
- Re: [w3c/webcomponents] HTML Modules (#645)
- Re: [w3c/manifest] Add splashscreen as a `purpose` (#510)
- Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425)
- Re: [whatwg/fetch] Developer-controlled streams for request/response (#88)
- Re: [whatwg/streams] Implement pipeTo() abort in the ref impl (2ed62aa)
- Re: [w3c/webcomponents] HTML Modules (#645)
- Re: [whatwg/fetch] Developer-controlled streams for request/response (#88)
- Re: [w3c/webcomponents] HTML Modules (#645)
- Re: [whatwg/fetch] Developer-controlled streams for request/response (#88)
- Re: [whatwg/fetch] Developer-controlled streams for request/response (#88)
- Re: [w3c/webcomponents] HTML module should require a new MIME type (#742)
- Re: [w3c/manifest] MIME type in HTML <link type="application/manifest+json" rel="manifest"> (#721)
- Re: [whatwg/fetch] Developer-controlled streams for request/response (#88)
- Re: [w3c/manifest] MIME type in HTML <link type="application/manifest+json" rel="manifest"> (#721)
- [w3c/manifest] MIME type in HTML <link type="application/manifest+json" rel="manifest"> (#721)
- Re: [whatwg/fetch] Developer-controlled streams for request/response (#88)
- Re: [whatwg/fetch] Developer-controlled streams for request/response (#88)
- Re: [heycam/webidl] Intent to use Constants (#587)
- Re: [whatwg/fetch] Developer-controlled streams for request/response (#88)
- Re: [w3c/webcomponents] Selection APIs for Shadow DOM (#79)
- Re: [w3c/editing] spellchecking - how to give JS devs more control (#166)
- Re: [w3c/manifest] Add splashscreen as a `purpose` (#510)
- Re: [w3c/IndexedDB] Add IDBTransaction commit() method (#242)
- Re: [w3c/ServiceWorker] Should add “script type” and “update via cache” when check two jobs are equivalent. (#1358)
- Re: [w3c/ServiceWorker] Should add a “script type” check in the register algorithm. (#1359)
Thursday, 4 October 2018
- Re: [w3c/webcomponents] HTML Modules (#645)
- Re: [whatwg/fetch] Developer-controlled streams for request/response (#88)
- Re: [whatwg/fetch] Developer-controlled streams for request/response (#88)
- [heycam/webidl] Intent to use Constants (#587)
- Re: [whatwg/fetch] Request should allow WritableStream as body (#378)
- Re: [w3c/editing] spellchecking - how to give JS devs more control (#166)
- Re: [w3c/editing] spellchecking - how to give JS devs more control (#166)
- Re: [w3c/webcomponents] Web Components F2F topics for 2018 TPAC (#763)
- Re: [w3c/editing] spellchecking - how to give JS devs more control (#166)
- Re: [w3c/webcomponents] Selection APIs for Shadow DOM (#79)
- Re: [whatwg/streams] Implement pipeTo() abort in the ref impl (2ed62aa)
- Re: [whatwg/streams] Implement pipeTo() abort in the ref impl (2ed62aa)
- Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657)
- Re: [w3ctag/design-reviews] Review request for WebVR (#185)
- Re: [w3c/FileAPI] Fix "undefined" reference in parsable MIME type Note (#110)
- Re: [w3c/FileAPI] Fix "undefined" reference in parsable MIME type Note (#110)
- Re: [w3c/FileAPI] Fix "undefined" reference in parsable MIME type Note (#110)
- Re: [w3c/editing] spellchecking - how to give JS devs more control (#166)
- Re: [w3c/editing] spellchecking - how to give JS devs more control (#166)
- [w3c/FileAPI] Fix "undefined" reference in parsable MIME type Note (#110)
- Re: [w3c/webcomponents] Selection APIs for Shadow DOM (#79)
- Re: [whatwg/streams] add @@asyncIterator to ReadableStream (#954)
- Re: [whatwg/streams] add @@asyncIterator to ReadableStream (#954)
- Re: [whatwg/streams] Implement pipeTo() abort in the ref impl (2ed62aa)
- Re: [whatwg/streams] Implement pipeTo() abort in the ref impl (2ed62aa)
- Re: [whatwg/streams] add @@asyncIterator to ReadableStream (#954)
- Re: [whatwg/streams] Allow aborting an ongoing pipe operation using AbortSignals (#744)
- Re: [whatwg/xhr] Spell out implicit serialization (#223)
- Re: [whatwg/xhr] Spell out implicit serialization (#223)
- Re: [whatwg/xhr] Spell out implicit serialization (#223)
- Re: [w3c/editing] spellchecking - how to give JS devs more control (#166)
- Re: [w3c/editing] spellchecking - how to give JS devs more control (#166)
- Re: [w3c/editing] spellchecking - how to give JS devs more control (#166)
- Re: [w3c/editing] spellchecking - how to give JS devs more control (#166)
- Re: [whatwg/streams] Allow aborting an ongoing pipe operation using AbortSignals (#744)
- Re: [w3c/editing] spellchecking - how to give JS devs more control (#166)
- [whatwg/xhr] Spell out implicit serialization (#223)
- Re: [w3c/ServiceWorker] Clean up Clients interface methods (#1332)
- Re: [w3c/ServiceWorker] Add Client.frameType back (#1329)
- Re: [w3c/ServiceWorker] Make Client.postMessage to unloaded client not throw (#1293)
- Re: [w3c/ServiceWorker] Use ASCII serialization for origins (#1151)
- Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657)
- Re: [w3c/manifest] Icon shapes and masking (#555)
- Re: [w3c/manifest] Icon shapes and masking (#555)
- Re: [w3c/editing] spellchecking - how to give JS devs more control (#166)
- Re: [w3c/editing] spellchecking - how to give JS devs more control (#166)
- [w3c/ServiceWorker] Should add a “script type” check in the register algorithm. (#1359)
- [w3c/ServiceWorker] Should add “script type” and “update via cache” when check two jobs are equivalent. (#1358)
- Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657)
- Re: [w3c/editing] spellchecking - how to give JS devs more control (#166)
- Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657)
Wednesday, 3 October 2018
- Re: [w3c/editing] spellching - how to give JS devs more control (#166)
- Re: [w3c/editing] contenteditable-disabled (#176)
- Re: [w3c/editing] contenteditable-disabled (#176)
- Re: [w3c/manifest] Add splashscreen as a `purpose` (#510)
- [w3ctag/design-reviews] TAG Review Request: Constructable Stylesheets (#308)
- [w3c/ServiceWorker] Should CacheStorage.match allow partial matches on cache names? (#1357)
- Re: [w3c/editing] contenteditable-disabled (#176)
- Re: [w3c/editing] contenteditable-disabled (#176)
- Re: [w3c/editing] contenteditable-disabled (#176)
- Re: [w3c/editing] contenteditable-disabled (#176)
- Re: [w3c/webcomponents] Web Components F2F topics for 2018 TPAC (#763)
- Re: [w3c/webcomponents] Web Components F2F topics for 2018 TPAC (#763)
- Re: [w3c/webcomponents] Web Components F2F topics for 2018 TPAC (#763)
- Re: [w3c/webcomponents] Web Components F2F topics for 2018 TPAC (#763)
- Re: [w3c/webcomponents] Web Components F2F topics for 2018 TPAC (#763)
Tuesday, 2 October 2018
- Re: [whatwg/fetch] Check Feature Policy before attaching Client Hints (#811)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3ctag/design-reviews] TAG review request: WebAssembly Threads (#299)
- Re: [w3c/WebPlatformWG] Agendas: TPAC 2018 (#120)
- Re: [w3ctag/design-reviews] TAG Review Request: User Activation API (#300)
- Re: [w3ctag/design-reviews] TAG review request: WebAssembly Threads (#299)
- Re: [w3ctag/design-reviews] TAG review request: WebAssembly Threads (#299)
- Re: [w3c/pointerlock] Option needed to disable OS-level adjustment for mouse acceleration (#36)
- Re: [w3ctag/design-reviews] TAG Review Request: RTCIceTransport (#304)
- Re: [whatwg/fetch] Check Feature Policy before attaching Client Hints (#811)
- Re: [w3ctag/design-reviews] Tag Review Request: Canvas TextMetrics (#302)
- Re: [w3ctag/design-reviews] Tag Review Request: Canvas TextMetrics (#302)
Monday, 1 October 2018
- Re: [w3c/manifest] Add a 'masking' purpose, for allowing the UA to supercompose such icons (#657)
- Re: [whatwg/xhr] Do not reset override MIME type (#218)
- Re: [w3c/ServiceWorker] Prevent opaque requests being used in response to client requests (#590)
- Re: [whatwg/streams] Allow aborting an ongoing pipe operation using AbortSignals (#744)
- Re: [whatwg/streams] Allow aborting an ongoing pipe operation using AbortSignals (#744)
- Re: [w3c/ServiceWorker] Prevent opaque requests being used in response to client requests (#590)
- [w3c/push-api] Make PushSubscription.expirationTime mandatory (#302)
- Re: [whatwg/encoding] bind encoder to self (#159)
- Re: [whatwg/encoding] bind encoder to self (#159)
- Re: [whatwg/encoding] Bad (#160)
- Re: [whatwg/fetch] Check Feature Policy before attaching Client Hints (#811)
- [w3ctag/design-reviews] TAG Review Request: FetchEvent.resultingClientId (#307)
- Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107)
- Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107)
- Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107)
- Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107)
- Re: [whatwg/dom] MohammedNoh (#703)
- Re: [whatwg/dom] MohammedNoh (#703)
- Re: [whatwg/dom] MohammedNoh (#703)
- [whatwg/dom] MohammedNoh (#703)