Monday, 30 April 2018
- [w3c/touch-events] It is unclear how targetTouches should work with Shadow DOM (#97)
- Re: [w3c/IndexedDB] How should commit() failures be surfaced when freezing / unloading (#237)
- Re: [whatwg/fetch] CORB: blocking of nosniff and 206 responses (#686)
- Re: [whatwg/fetch] CORB: blocking of nosniff and 206 responses (#686)
- Re: [whatwg/url] UrlSearchParams.set stringifier clarification (#383)
- Re: [whatwg/url] UrlSearchParams.set stringifier clarification (#383)
- Re: [whatwg/fetch] CORB: blocking of nosniff and 206 responses (#686)
- Re: [whatwg/fetch] CORB: blocking of nosniff and 206 responses (#686)
- Re: [whatwg/fetch] CORB: blocking of nosniff and 206 responses (#686)
- Re: [whatwg/fetch] CORB: blocking of nosniff and 206 responses (#686)
- Re: [w3ctag/design-reviews] Review Request: WebUSB on Dedicated and Shared Workers (#277)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [whatwg/dom] Introduce "remove all event listeners" primitive (#641)
- Re: [whatwg/dom] Introduce "remove all event listeners" primitive (#641)
- Re: [w3c/touch-events] 'Retargeting steps' expose closed Shadow DOM to the outside world (#92)
- Re: [heycam/webidl] Introduce new string type for names/keys with length limit (#552)
- Re: [heycam/webidl] Introduce new string type for names/keys with length limit (#552)
- Re: [whatwg/dom] createElement() does not put things in the HTML namespace correctly (#643)
- Re: [whatwg/dom] createElement() does not put things in the HTML namespace correctly (#643)
- Re: [whatwg/dom] createElement() does not put things in the HTML namespace correctly (#643)
- Re: [whatwg/dom] createElement() does not put things in the HTML namespace correctly (#643)
- Re: [w3c/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624)
- Re: [w3ctag/design-reviews] Review Request: WebUSB on Dedicated and Shared Workers (#277)
- Re: [w3c/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624)
- Re: [w3c/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624)
- Re: [w3c/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624)
- Re: [w3c/editing] Should backspace merge text with last cell's content of a table above ? (#164)
- Re: [w3c/editing] Should backspace merge text with last cell's content of a table above ? (#164)
- Re: [whatwg/url] UrlSearchParams.set stringifier clarification (#383)
- Re: [whatwg/dom] createElement() does not put things in the HTML namespace correctly (#643)
- Re: [whatwg/dom] createElement() does not put things in the HTML namespace correctly (#643)
- Re: [w3c/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624)
- Re: [whatwg/dom] createElement() does not put things in the HTML namespace correctly (#643)
- Re: [w3c/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624)
Sunday, 29 April 2018
- [whatwg/dom] createElement() does not put things in the HTML namespace correctly (#643)
- Re: [heycam/webidl] Disallow [LegacyArrayClass] on globals (#545)
- Re: [w3c/editing] Should backspace merge text with last cell's content of a table above ? (#164)
- Re: [heycam/webidl] Disallow [LegacyArrayClass] on globals (#545)
- [whatwg/url] UrlSearchParams.set stringifier clarification (#383)
- Re: [heycam/webidl] Remove [LegacyArrayClass] (#291)
- Re: [heycam/webidl] Remove [LegacyArrayClass] (#551)
- Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141)
- Re: [whatwg/dom] "Otherwise, if hasSeenCurrentTarget is true and ..." (#642)
- Re: [whatwg/dom] "Otherwise, if hasSeenCurrentTarget is true and ..." (#642)
Saturday, 28 April 2018
- Re: [w3c/editing] insertParagraph definition is different from current browsers' behavior when selection is collapsed at end of inline element(s) (#172)
- Re: [w3c/editing] Should backspace merge text with last cell's content of a table above ? (#164)
- Re: [w3c/editing] Should backspace merge text with last cell's content of a table above ? (#164)
- Re: [w3c/editing] Standardize execCommand("insertParagraph") in inline editing host (#175)
- Re: [w3c/editing] make need of execCommand to hide table controls go away on FF (#171)
- Re: [w3c/editing] input setSelection() method workflow, when text overflows input container (#173)
- Re: [w3c/editing] input setSelection() method workflow, when text overflows input container (#173)
- Re: [w3c/editing] Clarification of events to fire when gaining and losing focus (#174)
- [whatwg/dom] "Otherwise, if hasSeenCurrentTarget is true and ..." (#642)
- Re: [heycam/webidl] Introduce new string type for names/keys with length limit (#552)
- Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587)
Friday, 27 April 2018
- Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587)
- Re: [w3ctag/design-reviews] Review Request: WebUSB on Dedicated and Shared Workers (#277)
- Re: [w3c/ServiceWorker] Replaying POST requests (#693)
- [w3ctag/design-reviews] Review Request: WebUSB on Dedicated and Shared Workers (#277)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [heycam/webidl] Introduce new string type for names/keys with length limit (#552)
- Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587)
- Re: [heycam/webidl] Introduce new string type for names/keys with length limit (#552)
- Re: [heycam/webidl] Introduce new string type for names/keys with length limit (#552)
- [heycam/webidl] Introduce new string type for names/keys with length limit (#552)
- Re: [w3c/ServiceWorker] spec says `update()` should resolve to a registration, but browsers do different things (#1304)
- Re: [w3c/ServiceWorker] Size constraints for cache names? (#1310)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [w3c/webcomponents] Element Behaviors, and the has="" attribute. A useful alternative to Custom Elements in many cases! (#727)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [w3c/webcomponents] Element Behaviors, and the has="" attribute. A useful alternative to Custom Elements in many cases! (#727)
- Re: [w3c/ServiceWorker] Size constraints for cache names? (#1310)
- Re: [whatwg/fetch] From-Origin (#687)
- [w3c/ServiceWorker] Size constraints for cache names? (#1310)
- Re: [w3c/IndexedDB] How should commit() failures be surfaced when freezing / unloading (#237)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [w3c/ServiceWorker] How to handle redirected URL for login authentication offline. (#1226)
- Re: [w3c/IndexedDB] How should commit() failures be surfaced when freezing / unloading (#237)
- Re: [w3c/ServiceWorker] How to handle redirected URL for login authentication offline. (#1226)
- Re: [whatwg/dom] Introduce "remove an event listener" primitive (#641)
- [whatwg/dom] Introduce "remove an event listener" primitive (#641)
- Re: [w3c/ServiceWorker] There should be no such thing as "fail to activate" (#659)
- [whatwg/dom] document.open()'s mutation event suprression (#640)
- Re: [whatwg/fetch] WindowOrWorkerGlobalScope is a mixin (#719)
- Re: [w3c/ServiceWorker] Allowing multiple scopes (& should scopes be primary key?) (#566)
- [w3c/IndexedDB] WindowOrWorkerGlobalScope is a mixin (#238)
- Re: [w3c/ServiceWorker] Allowing multiple scopes (& should scopes be primary key?) (#566)
- [w3c/ServiceWorker] WindowOrWorkerGlobalScope is a mixin (#1309)
- Re: [whatwg/fetch] WindowOrWorkerGlobalScope is a mixin (#719)
- Re: [whatwg/fetch] WindowOrWorkerGlobalScope is a mixin (#719)
- Re: [w3c/ServiceWorker] Allowing multiple scopes (& should scopes be primary key?) (#566)
- [whatwg/fetch] WindowOrWorkerGlobalScope is a mixin (#719)
- Re: [w3c/ServiceWorker] There should be no such thing as "fail to activate" (#659)
- Re: [w3c/ServiceWorker] There should be no such thing as "fail to activate" (#659)
- Re: [w3c/ServiceWorker] There should be no such thing as "fail to activate" (#659)
- Re: [heycam/webidl] Remove [LegacyArrayClass] (#551)
- [heycam/webidl] Remove [LegacyArrayClass] (#551)
- Re: [whatwg/fetch] Add Request's isHistoryNavigation (#718)
- Re: [whatwg/fetch] Add a `prefetch` initiator (#659)
- Re: [whatwg/fetch] Request.destination for `<link rel=prefetch>` (#658)
- Re: [whatwg/fetch] Add a `prefetch` initiator (#659)
- Re: [whatwg/url] Remove _charset_ handling. (#382)
- Re: [whatwg/fetch] Add a `prefetch` initiator (#659)
- [whatwg/fetch] Add Request's isHistoryNavigation (#718)
- Re: [whatwg/fetch] just do it (048d10e)
- Re: [whatwg/fetch] just do it (048d10e)
- Re: [whatwg/url] Remove _charset_ handling. (#382)
- Re: [whatwg/url] Remove _charset_ handling. (#382)
- Re: [whatwg/fetch] just do it (048d10e)
- Re: [w3c/ServiceWorker] Proposal: FetchEvent.navigationLoadType (#1167)
- Re: [whatwg/fetch] Introduce reload-navigation flag (#685)
- Re: [whatwg/fetch] Introduce reload-navigation flag (#685)
- Re: [whatwg/streams] Communication between workers/windows via Streams API (#244)
- Re: [w3ctag/design-reviews] Web Share Target API (#221)
- Re: [w3c/touch-events] Add note to mention UA might adjusting touch target (#95)
- Re: [w3c/touch-events] Should spec mention “touch adjustment" behavior? (#93)
- Re: [w3c/touch-events] Add note to mention UA might adjusting touch target (#95)
- Re: [w3c/touch-events] Add note to mention UA might adjusting touch target (#95)
- Re: [w3c/touch-events] Should spec mention “touch adjustment" behavior? (#93)
- Re: [w3c/touch-events] Add note to mention UA might adjusting touch target (#95)
- Re: [w3c/touch-events] Add note to mention UA might adjusting touch target (#95)
Thursday, 26 April 2018
- Re: [w3c/touch-events] Should spec mention “touch adjustment" behavior? (#93)
- Re: [whatwg/fetch] Introduce reload-navigation flag (#685)
- [w3c/IndexedDB] How should commit() failures be surfaced when freezing / unloading (#237)
- Re: [w3c/touch-events] Should spec mention “touch adjustment" behavior? (#93)
- Re: [w3c/touch-events] Remove createTouch and createTouch list (#96)
- [w3ctag/design-reviews] Layered APIs (#276)
- Re: [whatwg/fetch] Add a `prefetch` initiator (#659)
- Re: [whatwg/fetch] Add a `prefetch` initiator (#659)
- Re: [whatwg/fetch] Add a `prefetch` initiator (#659)
- Re: [whatwg/fetch] Add a `prefetch` initiator (#659)
- Re: [whatwg/fetch] Add a `prefetch` initiator (#659)
- Re: [whatwg/fetch] Add a `prefetch` initiator (#659)
- Re: [whatwg/fetch] Add a `prefetch` initiator (#659)
- Re: [whatwg/fetch] Add a `prefetch` initiator (#659)
- Re: [whatwg/encoding] Identity encoding? (#138)
- Re: [w3c/touch-events] Clarify "deprecated in this specification" (#80)
- [w3c/touch-events] Remove createTouch and createTouch list (#96)
- [whatwg/encoding] Identity encoding? (#138)
- Re: [w3c/WebPlatformWG] Add Job van Achterberg to Observers for 18-06-2018 meeting (#118)
- Re: [w3c/touch-events] Should spec mention “touch adjustment" behavior? (#93)
- [w3c/touch-events] Add note to mention UI might adjusting touch target (#95)
- Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717)
- Re: [w3c/webcomponents] Customized Autonomous Elements (#750)
- Re: [w3c/webcomponents] Customized Autonomous Elements (#750)
- Re: [whatwg/fetch] Add a `prefetch` initiator (#659)
- Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717)
- Re: [whatwg/fetch] CORB: nosniff handling (#686)
- Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717)
- Re: [whatwg/encoding] When encoding U+301C to legacy Japanese encodings, consider encoding as U+FF5E (#114)
- Re: [whatwg/encoding] When encoding U+301C to legacy Japanese encodings, consider encoding as U+FF5E (#114)
- Re: [whatwg/encoding] When encoding U+301C to legacy Japanese encodings, consider encoding as U+FF5E (#114)
- Re: [whatwg/fetch] CORB: nosniff handling (#686)
- Re: [whatwg/fetch] Use Infra's abort when (#702)
- Re: [whatwg/fetch] CORB: nosniff handling (#686)
- Re: [whatwg/fetch] Use Infra's abort when (#702)
- Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717)
- Re: [whatwg/fetch] Use Infra's abort when (#702)
- [w3c/WebPlatformWG] Add Job van Achterberg to Observers for 18-06-2018 meeting (#118)
- [w3ctag/design-reviews] Request TAG review of HTML5.3 (#275)
- Re: [whatwg/fetch] Use Infra's abort when (#702)
- Re: [whatwg/fetch] Use Infra's abort when (#702)
- Re: [whatwg/fetch] Use Infra's abort when (#702)
- Re: [whatwg/fetch] CORB: nosniff handling (#686)
- Re: [whatwg/fetch] CORB: nosniff handling (#686)
- Re: [whatwg/fetch] Fetching with a particular destination (#521)
- Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [whatwg/fetch] Fetching with a particular destination (#521)
- Re: [whatwg/fetch] Fetching with a particular destination (#521)
- Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717)
- Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717)
- Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717)
- Re: [whatwg/fetch] Fetching with a particular destination (#521)
- Re: [whatwg/fetch] Fetching with a particular destination (#521)
- Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717)
- Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717)
- Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717)
- Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717)
- Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717)
- Re: [w3c/permissions] Using Web IDL to describe WebDriver JSON is a bit unusual (#174)
- Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717)
- Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717)
- Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717)
- Re: [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717)
- Re: [w3ctag/design-reviews] Keyboard Map (#238)
Wednesday, 25 April 2018
- Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20)
- Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)
- Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)
- Re: [w3c/permissions] Using Web IDL to describe WebDriver JSON is a bit unusual (#174)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [whatwg/streams] Communication between workers/windows via Streams API (#244)
- Re: [whatwg/fetch] Update Fetch to support Token Binding (#715)
- Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)
- [whatwg/fetch] Consider preserving destination on `new Request(request)` (#717)
- 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: [heycam/webidl] Poorly worded normative requirement could be improved (#548)
- Re: [whatwg/fetch] CORB: nosniff handling (#686)
- Re: [whatwg/fetch] CORB: nosniff handling (#686)
- Re: [whatwg/fetch] CORB: nosniff handling (#686)
- Re: [heycam/webidl] Remove [LegacyArrayClass] (#291)
- Re: [heycam/webidl] Remove [LegacyArrayClass] (#291)
- Re: [heycam/webidl] Remove [LegacyArrayClass] (#291)
- Re: [heycam/webidl] Disallow [LegacyArrayClass] on globals (#545)
- Re: [whatwg/fetch] CORB: nosniff handling (#686)
- Re: [heycam/webidl] Poorly worded normative requirement could be improved (#548)
- Re: [whatwg/fetch] CORB: nosniff handling (#686)
- Re: [whatwg/fetch] CORB: nosniff handling (#686)
- Re: [heycam/webidl] Poorly worded normative requirement could be improved (#548)
- Re: [whatwg/fetch] Introduce reload-navigation flag (#685)
- Re: [w3ctag/design-reviews] Review request for WebVR (#185)
- Re: [whatwg/encoding] Be clearer on which user agents the API applies to (#136)
- Re: [whatwg/encoding] Be clearer on which user agents the API applies to (#136)
- [whatwg/encoding] Give clearer advice on hooks for standards (#137)
- Re: [whatwg/encoding] Be clearer on which user agents the API applies to (#136)
- [whatwg/encoding] Be clearer on which user agents the API applies to (#136)
- Re: [whatwg/encoding] Editorial: Charset alias matching link (#134)
- Re: [whatwg/encoding] Need more changes for common deploy (#126)
- Re: [whatwg/encoding] Need more changes for common deploy (#126)
- Re: [whatwg/encoding] Concatenating two ISO-2022-JP outputs from a conforming encoder doesn't result in conforming input (#115)
- Re: [whatwg/encoding] When encoding U+301C to legacy Japanese encodings, consider encoding as U+FF5E (#114)
- Re: [whatwg/url] Don't coerce numbers to strings for port checking (#377)
- Re: [whatwg/encoding] Meta: TF-8 decode without BOM or fail is used at least once (#124)
- Re: [whatwg/url] Don't coerce numbers to strings for port checking (#377)
- Re: [whatwg/url] Don't coerce numbers to strings for port checking (#377)
- Re: [whatwg/encoding] Meta: TF-8 decode without BOM or fail is used at least once (#124)
- Re: [whatwg/encoding] gb18030 encoding/decoding support (#57)
- Re: [heycam/webidl] Poorly worded normative requirement could be improved (#548)
- Re: [whatwg/url] Don't coerce numbers to strings for port checking (#377)
- Re: [whatwg/url] Don't coerce numbers to strings for port checking (#377)
- Re: [whatwg/url] Remove _charset_ handling. (#382)
- Re: [whatwg/url] Remove _charset_ handling. (#382)
- Re: [whatwg/url] Don't coerce numbers to strings for port checking (#377)
- Re: [whatwg/fetch] Introduce reload-navigation flag (#685)
- [whatwg/url] Remove _charset_ handling. (#382)
- Re: [whatwg/url] Remove _charset_ handling. (#382)
- Re: [w3c/ServiceWorker] spec says `update()` should resolve to a registration, but browsers do different things (#1304)
- Re: [w3c/ServiceWorker] spec says `update()` should resolve to a registration, but browsers do different things (#1304)
- Re: [w3c/ServiceWorker] spec says `update()` should resolve to a registration, but browsers do different things (#1304)
- Re: [w3ctag/design-reviews] CSS Selectors 4, :focus-visible. (#233)
Tuesday, 24 April 2018
- Re: [w3ctag/design-reviews] Review request for WebVR (#185)
- Re: [whatwg/fetch] Response.redirect() results in status message still being OK? (#664)
- Re: [whatwg/fetch] Make status message default the empty byte sequence (#600)
- Re: [whatwg/fetch] Response `statusText` is ambiguous and unclear for HTTP/2 (#599)
- Re: [w3ctag/design-reviews] HTML General Review (#174)
- Re: [w3ctag/design-reviews] HTML General Review (#174)
- Re: [whatwg/fetch] CORB: nosniff handling (#686)
- Re: [w3c/clipboard-apis] User gesture requirement for Clipboard API access (#52)
- Re: [w3c/clipboard-apis] User gesture requirement for Clipboard API access (#52)
- Re: [w3ctag/design-reviews] HTML General Review (#174)
- Re: [w3ctag/design-reviews] Keyboard Map (#238)
- Re: [w3ctag/design-reviews] HTML General Review (#174)
- Re: [w3c/ServiceWorker] Correct link to nightly version (#1306)
- Re: [w3ctag/design-reviews] CSS Selectors 4, :focus-visible. (#233)
- Re: [w3ctag/design-reviews] HTML General Review (#174)
- Re: [w3ctag/design-reviews] HTML General Review (#174)
- Re: [w3ctag/design-reviews] HTML General Review (#174)
- Re: [whatwg/url] Remove mention of MediaStream (#380)
- Re: [whatwg/url] URL's object can no longer be a MediaStream (#381)
- Re: [whatwg/url] URL's object can no longer be a MediaStream (#381)
- Re: [whatwg/fetch] CORB: nosniff handling (#686)
- Re: [whatwg/fetch] CORB: nosniff handling (#686)
- Re: [w3ctag/design-reviews] BCP56bis (#232)
- Re: [w3ctag/design-reviews] Review request for WebVR (#185)
- Re: [w3c/ServiceWorker] spec says `update()` should resolve to a registration, but browsers do different things (#1304)
- Re: [w3c/clipboard-apis] User gesture requirement for Clipboard API access (#52)
- Re: [w3c/ServiceWorker] spec says `update()` should resolve to a registration, but browsers do different things (#1304)
- Re: [whatwg/fetch] Content codings (Content-Encoding) (#716)
- Re: [whatwg/fetch] Define the "Preload Cache" (#590)
- Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917)
- Re: [whatwg/streams] Fix internal links for class ReadableStreamBYOBRequest (#923)
- Re: [whatwg/streams] Fix internal links for class ReadableStreamBYOBRequest (#923)
- Re: [w3c/manifest] Create test suite to check Web App Manifest feature support (#666)
- Re: [whatwg/fetch] Use Infra for header list (#711)
- Re: [whatwg/fetch] Editorial: use Infra to define header list (#713)
- Re: [whatwg/fetch] Editorial: use Infra to define header list (#713)
- Re: [whatwg/fetch] Introduce reload-navigation flag (#685)
- Re: [whatwg/fetch] Define the "Preload Cache" (#590)
- Re: [whatwg/fetch] Introduce reload-navigation flag (#685)
- Re: [whatwg/streams] Revise property access order (#922)
- Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917)
- [whatwg/streams] Fix internal links for class ReadableStreamBYOBRequest (#923)
- Re: [whatwg/fetch] Client hints difference between navigation and subresources (#707)
- Re: [whatwg/fetch] Client hints difference between navigation and subresources (#707)
- Re: [whatwg/streams] Revise property access order (#922)
- Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917)
- Re: [whatwg/xhr] The logic in the WPT send-authentication-competing-names-passwords.htm does not match the spec. (#191)
- Re: [whatwg/fetch] Editorial: use Infra to define header list (#713)
- Re: [w3c/ServiceWorker] "no-cors" CSS SOP violation (#719)
- Re: [whatwg/fetch] Introduce reload-navigation flag (#685)
- Re: [whatwg/fetch] Introduce reload-navigation flag (#685)
- Re: [whatwg/fetch] Introduce reload-navigation flag (#685)
- Re: [whatwg/streams] Communication between workers/windows via Streams API (#244)
- Re: [whatwg/fetch] CORB: nosniff handling (#686)
- Re: [heycam/webidl] [LegacyArrayClass] is gone from CSSOM. (#550)
- Re: [heycam/webidl] [LegacyArrayClass] is gone from CSSOM. (#550)
- Re: [heycam/webidl] [LegacyArrayClass] is gone from CSSOM. (#550)
- Re: [whatwg/dom] downloads (#639)
- Re: [heycam/webidl] [LegacyArrayClass] is gone from CSSOM. (#550)
- Re: [heycam/webidl] [LegacyArrayClass] is gone from CSSOM. (#550)
- Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)
- Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)
- Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)
- Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)
- Re: [whatwg/streams] Communication between workers/windows via Streams API (#244)
- Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)
- Re: [whatwg/streams] Communication between workers/windows via Streams API (#244)
- Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)
- Re: [heycam/webidl] [LegacyArrayClass] is gone from CSSOM. (#550)
Monday, 23 April 2018
- [whatwg/dom] downloads (#639)
- [heycam/webidl] [LegacyArrayClass] is gone from CSSOM. (#550)
- Re: [whatwg/fetch] CORB: nosniff handling (#686)
- Re: [whatwg/fetch] CORB: nosniff handling (#686)
- Re: [w3c/manifest] Create test suite to check Web App Manifest feature support (#666)
- Re: [w3c/ServiceWorker] windowClients state change events - loaded/unloaded (#1269)
- Re: [whatwg/fetch] Make status message default the empty byte sequence (#600)
- Re: [whatwg/fetch] Handle failure while handling content codings (#710)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [whatwg/fetch] Use of response's cache state (#376)
- Re: [whatwg/fetch] Add response's cache state back (#705)
- [w3c/ServiceWorker] Response's cache state is back (#1308)
- Re: [whatwg/fetch] Editorial: remove most substep usage (#709)
- Re: [whatwg/fetch] Editorial: remove most substep usage (#709)
- Re: [whatwg/fetch] Editorial: remove most substep usage (#709)
- Re: [whatwg/xhr] Editorial: move Feature Policy Integration section (#199)
- Re: [whatwg/xhr] Editorial: move feature policy integration section (#204)
- Re: [whatwg/xhr] Editorial: move feature policy integration section (#204)
- Re: [whatwg/xhr] Editorial: move feature policy integration section (#204)
- Re: [whatwg/fetch] Handle failure while handling content codings (#710)
- Re: [whatwg/fetch] Content codings (Content-Encoding) (#716)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [whatwg/fetch] Editorial: remove most substep usage (#709)
- Re: [whatwg/xhr] Editorial: move feature policy integration section (#204)
- Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917)
- Re: [whatwg/fetch] Make status message default the empty byte sequence (#600)
- Re: [whatwg/fetch] Handle failure while handling content codings (#710)
- Re: [whatwg/xhr] Editorial: rewrite send()'s body/content-type processing (#205)
- Re: [whatwg/xhr] Editorial: rewrite send()'s body/content-type processing (#205)
- Re: [whatwg/xhr] Editorial: less-confusing content-type manipulation algorithm for send() (#197)
- Re: [whatwg/streams] Revise property access order (#922)
- Re: [whatwg/xhr] Editorial: rewrite send()'s body/content-type processing (#205)
- Re: [whatwg/fetch] Introduce reload-navigation flag (#685)
- Re: [whatwg/xhr] Editorial: rewrite send()'s body/content-type processing (#205)
- Re: [whatwg/fetch] Introduce reload-navigation flag (#685)
- Re: [whatwg/xhr] Editorial: rewrite send()'s body/content-type processing (#205)
- Re: [whatwg/fetch] Use request's current url as base URL in redirects (#633)
- Re: [whatwg/xhr] Editorial: rewrite send()'s body/content-type processing (#205)
- Re: [whatwg/xhr] Editorial: rewrite send()'s body/content-type processing (#205)
- Re: [whatwg/fetch] Introduce reload-navigation flag (#685)
- Re: [whatwg/fetch] Introduce reload-navigation flag (#685)
- Re: [whatwg/fetch] Introduce reload-navigation flag (#685)
- Re: [whatwg/xhr] Editorial: rewrite send()'s body/content-type processing (#205)
- Re: [whatwg/xhr] Editorial: rewrite send()'s body/content-type processing (#205)
- Re: [whatwg/xhr] Editorial: rewrite send()'s body/content-type processing (#205)
- Re: [whatwg/xhr] Editorial: rewrite send()'s body/content-type processing (#205)
- Re: [whatwg/fetch] Define how to handle bad content encoding (#657)
- Re: [whatwg/fetch] Handle failure while handling content codings (#710)
- Re: [whatwg/fetch] Handle failure while handling content codings (#710)
- Re: [whatwg/streams] Communication between workers/windows via Streams API (#244)
- Re: [whatwg/fetch] Content codings (Content-Encoding) (#716)
- Re: [whatwg/fetch] Handle failure while handling content codings (#710)
- Re: [whatwg/fetch] Content codings (Content-Encoding) (#716)
- [whatwg/fetch] Content codings (Content-Encoding) (#716)
- Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)
- Re: [whatwg/fetch] Make status message default the empty byte sequence (#600)
- Re: [whatwg/fetch] Preventing some CRLF header injection attacks (#375)
- Re: [w3c/ServiceWorker] postMessage keeps service workers alive indefinitely (#980)
- Re: [whatwg/xhr] Editorial: rewrite send()'s body/content-type processing (#205)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [whatwg/fetch] Update Fetch to support Token Binding (#715)
- Re: [whatwg/streams] Add two demos using streams for PNG manipulation (#911)
- Re: [w3c/manifest] Create test suite to check Web App Manifest feature support (#666)
- Re: [w3c/manifest] Create test suite to check Web App Manifest feature support (#666)
- Re: [w3c/manifest] Create test suite to check Web App Manifest feature support (#666)
- Re: [w3c/manifest] Create test suite to check Web App Manifest feature support (#666)
- Re: [w3c/manifest] Create test suite to check Web App Manifest feature support (#666)
- Re: [w3c/uievents] Event order between "compositionend" and "input" (#202)
- Re: [whatwg/fetch] Introduce reload-navigation flag (#685)
- Re: [w3c/manifest] Create test suite to check Web App Manifest feature support (#666)
- Re: [w3c/manifest] Create test suite to check Web App Manifest feature support (#666)
- Re: [w3c/manifest] Create test suite to check Web App Manifest feature support (#666)
- Re: [whatwg/fetch] Introduce reload-navigation flag (#685)
- Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685)
- Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685)
- Re: [w3c/manifest] Create test suite to check Web App Manifest feature support (#666)
- Re: [whatwg/streams] Communication between workers/windows via Streams API (#244)
- Re: [whatwg/streams] Communication between workers/windows via Streams API (#244)
- Re: [w3c/manifest] Worried about IDL changes (#667)
- Re: [w3c/manifest] Worried about IDL changes (#667)
- [w3c/manifest] Worried about IDL changes (#667)
- Re: [w3c/manifest] Create test suite to check Web App Manifest feature support (#666)
- [w3c/ServiceWorker] Service-Worker-Allowed can be cross-origin to the script URL. (#1307)
- Re: [whatwg/streams] Could a byte stream read directly into and out of a SAB (w/o transfer)? (#757)
Sunday, 22 April 2018
- [w3c/ServiceWorker] Correct link to nightly version (#1306)
- Re: [w3c/manifest] Create test suite to check Web App Manifest feature support (#666)
- [w3c/manifest] Create test suite to check Web App Manifest feature support (#666)
Saturday, 21 April 2018
- Re: [w3c/webcomponents] [templates] How featureful should the default processor be? (#682)
- Re: [whatwg/dom] Meta: fix service worker reference (#634)
- Re: [w3c/uievents] Event order between "compositionend" and "input" (#202)
- [w3c/uievents] Event order between "compositionend" and "input" (#202)
- Re: [whatwg/fetch] Use Infra's abort when (#702)
- Re: [whatwg/fetch] Use Infra's abort when (#702)
- Re: [whatwg/fetch] Make fetch() use "same-origin" credentials by default (#585)
- [whatwg/xhr] Editorial: rewrite send()'s body/content-type processing (#205)
Friday, 20 April 2018
- Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681)
- Re: [whatwg/streams] Add two demos using streams for PNG manipulation (#911)
- Re: [w3c/manifest] Support window preferred/initial (minimal?) sizes (#436)
- [w3c/ServiceWorker] how can unregister()'s same-origin check ever fail? (#1305)
- Re: [w3c/ServiceWorker] spec says `update()` should resolve to a registration, but browsers do different things (#1304)
- [w3c/ServiceWorker] spec says `update()` should resolve to a registration, but browsers resolve to undefined (#1304)
- Re: [whatwg/fetch] Make fetch() use "same-origin" credentials by default (#585)
- [whatwg/url] URL's object can no longer be a MediaStream (#381)
- [w3c/ServiceWorker] Create F2F agenda - 25 October 2018 (#1303)
- Re: [whatwg/fetch] CORB: nosniff handling (#686)
- Re: [whatwg/fetch] Make fetch() use "same-origin" credentials by default (#585)
- Re: [whatwg/fetch] Make fetch() use "same-origin" credentials by default (#585)
- Re: [whatwg/fetch] Make fetch() use "same-origin" credentials by default (#585)
- Re: [whatwg/fetch] Preventing some CRLF header injection attacks (#375)
- Re: [whatwg/fetch] Make fetch() use "same-origin" credentials by default (#585)
- Re: [whatwg/fetch] Handle failure while handling content codings (#710)
- Re: [whatwg/fetch] Handle failure while handling content codings (#710)
- Re: [whatwg/fetch] Handle failure while handling content codings (#710)
- Re: [heycam/webidl] Editorial: use SetFunctionLength abstract ops (#549)
- Re: [whatwg/fetch] CORB: nosniff handling (#686)
- Re: [w3c/screen-orientation] Link Screen Orientation with Fullscreen more cleanly (#62)
- Re: [whatwg/fetch] CORB: nosniff handling (#686)
- Re: [whatwg/fetch] Allow custom headers on no-cors requests (#380)
- Re: [w3c/screen-orientation] Link Screen Orientation with Fullscreen more cleanly (#62)
- Re: [whatwg/fetch] Allow custom headers on no-cors requests (#380)
- Re: [w3c/screen-orientation] Test suite (#95)
- Re: [w3c/screen-orientation] Test suite (#95)
Thursday, 19 April 2018
- Re: [heycam/webidl] Editorial: use SetFunctionLength abstract ops (#549)
- Re: [whatwg/fetch] Allow custom headers on no-cors requests (#380)
- Re: [whatwg/fetch] Allow custom headers on no-cors requests (#380)
- Re: [whatwg/fetch] Allow custom headers on no-cors requests (#380)
- [heycam/webidl] Editorial: use SetFunctionLength abstract ops (#549)
- Re: [whatwg/fetch] Allow custom headers on no-cors requests (#380)
- Re: [whatwg/fetch] Handle failure while handling content codings (#710)
- Re: [whatwg/fetch] Allow custom headers on no-cors requests (#380)
- 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] Allow custom headers on no-cors requests (#380)
- Re: [whatwg/fetch] Allow custom headers on no-cors requests (#380)
- Re: [whatwg/fetch] Allow custom headers on no-cors requests (#380)
- Re: [whatwg/storage] Issue (#61)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- [whatwg/fetch] Update Fetch to support Token Binding (#715)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700)
- [whatwg/storage] Issue (#61)
- Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700)
- Re: [whatwg/fetch] CORB: nosniff handling (#686)
- Re: [whatwg/fetch] CORB: nosniff handling (#686)
- Re: [whatwg/fetch] The comma-delimited combined value definition does not support Set-Cookie headers (#345)
- [whatwg/fetch] Clarify how Headers does not support Set-Cookie (#714)
- [whatwg/fetch] Editorial: use Infra to define header list (#713)
- Re: [whatwg/fetch] Allow custom headers on no-cors requests (#380)
- Re: [w3c/ServiceWorker] consult document CSP in Register algorithm (#755)
- Re: [whatwg/xhr] Editorial: move feature policy integration section (#204)
- [whatwg/xhr] Editorial: move feature policy integration section (#204)
- Re: [whatwg/xhr] responseXML should maybe drop HTML support (#203)
- Re: [whatwg/xhr] responseXML should maybe drop HTML support (#203)
- Re: [whatwg/fetch] "Extract a MIME type" algorithm should pick the first entry? (#529)
- Re: [w3c/FileAPI] Implementations allow all values in type getter (#43)
- [whatwg/xhr] responseXML should maybe drop HTML support (#203)
- Re: [whatwg/streams] Add two demos using streams for PNG manipulation (#911)
- Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20)
- Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685)
- Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685)
- Re: [whatwg/fetch] FetchObserver (for a single fetch) (#607)
- Re: [w3c/ServiceWorker] consult document CSP in Register algorithm (#755)
- Re: [w3c/permissions] Using Web IDL to describe WebDriver JSON is a bit unusual (#174)
Wednesday, 18 April 2018
- Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20)
- Re: [whatwg/fetch] FetchObserver (for a single fetch) (#607)
- Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20)
- Re: [w3c/ServiceWorker] consult document CSP in Register algorithm (#755)
- Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20)
- [w3c/webcomponents] Customized Autonomous Elements (#750)
- Re: [heycam/webidl] Poorly worded normative requirement could be improved (#548)
- Re: [whatwg/fetch] Client hints difference between navigation and subresources (#707)
- Re: [whatwg/fetch] Client hints difference between navigation and subresources (#707)
- Re: [whatwg/fetch] Handle failure while handling content codings (#710)
- Re: [whatwg/fetch] CORB: nosniff handling (#686)
- Re: [whatwg/fetch] Client hints difference between navigation and subresources (#707)
- Re: [whatwg/fetch] CORB: nosniff handling (#686)
- Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700)
- Re: [whatwg/fetch] Handle failure while handling content codings (#710)
- Re: [whatwg/fetch] Handle failure while handling content codings (#710)
- Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20)
- Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20)
- [whatwg/fetch] Use forgiving base64-encode for WebSocket (#712)
- Re: [whatwg/fetch] Return network error for scheme-fetch for ftp/file (#699)
- Re: [whatwg/fetch] Return network error for scheme-fetch for ftp/file (#699)
- [whatwg/fetch] Use Infra for header list (#711)
- Re: [whatwg/fetch] Getting all bytes in a body (#661)
- Re: [whatwg/fetch] Handle failure while handling content codings (#710)
- Re: [whatwg/fetch] fetch assumes a url's object is always a Blob (#457)
- Re: [whatwg/fetch] Only allow blob: URLs that point to Blob objects (#708)
- Re: [whatwg/fetch] Only allow blob: URLs that point to Blob objects (#708)
- Re: [whatwg/fetch] Only allow blob: URLs that point to Blob objects (#708)
- Re: [whatwg/fetch] Only allow blob: URLs that point to Blob objects (#708)
- Re: [whatwg/fetch] Only allow blob: URLs that point to Blob objects (#708)
- Re: [whatwg/fetch] Request.destination for `<link rel=prefetch>` (#658)
- Re: [whatwg/fetch] Handle failure while handling content codings (#710)
- [whatwg/fetch] Handle failure while handling content codings (#710)
- [whatwg/xhr] Allow FormData constructor to accept array or object too (#202)
- Re: [whatwg/fetch] Only allow blob: URLs that point to Blob objects (#708)
- Re: [heycam/webidl] Describe JSON-LD with WebIDL - How to handle @ tags (#541)
- Re: [w3c/permissions] Using Web IDL to describe WebDriver JSON is a bit unusual (#174)
- [w3c/permissions] Using Web IDL to describe WebDriver JSON is a bit unusual (#174)
- [whatwg/url] Remove mention of MediaStream (#380)
- Re: [whatwg/fetch] Only allow blob: URLs that point to Blob objects (#708)
- Re: [whatwg/fetch] Termination's aborted flag (#703)
- [whatwg/fetch] Editorial: remove most substep usage (#709)
- Re: [w3c/manifest] Allow for multiple scopes (#449)
- Re: [whatwg/fetch] Use Infra's abort when (#702)
- Re: [w3c/screen-orientation] Test suite (#95)
Tuesday, 17 April 2018
- Re: [w3c/manifest] Proposal: Display Mode 'standalone-no-ui' (#659)
- Re: [w3c/manifest] Proposal: Display Mode 'standalone-no-ui' (#659)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [w3c/manifest] Proposal: Display Mode 'standalone-no-ui' (#659)
- Re: [w3c/manifest] Proposal: Display Mode 'standalone-no-ui' (#659)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [whatwg/fetch] Termination's aborted flag (#703)
- Re: [w3ctag/design-reviews] CSS Selectors 4, :focus-visible. (#233)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [w3c/IndexedDB] Proposal: Add "writeonly" transaction mode (#234)
- Re: [w3ctag/design-reviews] CSS Selectors 4, :focus-visible. (#233)
- Re: [w3c/FileAPI] Refine StructuredSerializeForStorage behavior (#98)
- [w3ctag/design-reviews] HTML General Review: App Cache (#263)
- [w3ctag/design-reviews] HTML General Review: Web Storage (#271)
- [w3ctag/design-reviews] HTML General Review: HTML Obsolete Features (#273)
- [w3ctag/design-reviews] HTML General Review: IANA Registries (#274)
- [w3ctag/design-reviews] HTML General Review: XML Infrastructure (#272)
- [w3ctag/design-reviews] HTML General Review: Web Sockets (#268)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- [w3ctag/design-reviews] HTML General Review: Web Workers (#270)
- [w3ctag/design-reviews] HTML General Review: Cross-Document Messaging (#269)
- [w3ctag/design-reviews] HTML General Review: Server-Sent Events (#267)
- [w3ctag/design-reviews] HTML General Review: HTML Timers and Timeslicing (#266)
- [w3ctag/design-reviews] HTML General Review: HTML Utilities (#264)
- [w3ctag/design-reviews] HTML General Review: HTML Parsing (#265)
- [w3ctag/design-reviews] HTML General Review: Navigation and Browsing History (#262)
- [w3ctag/design-reviews] HTML General Review: Microdata (#261)
- [w3ctag/design-reviews] HTML General Review: HTML Drawing (#260)
- [w3ctag/design-reviews] HTML General Review: HTML Templates (#259)
- [w3ctag/design-reviews] HTML General Review: HTML Option Lists (#255)
- [w3ctag/design-reviews] HTML General Review: HTML Scripting (#258)
- [w3ctag/design-reviews] HTML General Review: HTML Focus (#257)
- [w3ctag/design-reviews] HTML General Review: HTML User Interaction (#256)
- [w3ctag/design-reviews] HTML General Review: HTML Input (#254)
- [w3ctag/design-reviews] HTML General Review: HTML Forms (#253)
- [w3ctag/design-reviews] HTML General Review: Browsing Contexts and Security (#250)
- [w3ctag/design-reviews] HTML General Review: HTML Tables (#252)
- [w3ctag/design-reviews] HTML General Review: HTML Media (#251)
- [w3ctag/design-reviews] HTML General Review: Structured Serialize/Deserialize (#243)
- [w3ctag/design-reviews] HTML General Review: HTML Images (#249)
- [w3ctag/design-reviews] HTML General Review: HTML Ruby (#248)
- [w3ctag/design-reviews] HTML General Review: HTML Lists (#247)
- [w3ctag/design-reviews] HTML General Review: Custom Elements (#244)
- [w3ctag/design-reviews] HTML General Review: HTML Styling (#246)
- [w3ctag/design-reviews] HTML General Review: HTML Linking (#245)
- [w3ctag/design-reviews] HTML General Review: HTML Document and Elements (#242)
- [w3c/FileAPI] Refine StructuredSerializeForStorage behavior (#98)
- Re: [w3c/IndexedDB] Define storage operation of non-trivial StructuredSerializeForStorage records (e.g. Blob/File) (#203)
- Re: [w3c/IndexedDB] Define storage operation of non-trivial StructuredSerializeForStorage records (e.g. Blob/File) (#203)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [whatwg/fetch] Termination's aborted flag (#703)
- Re: [whatwg/fetch] Only allow blob: URLs that point to Blob objects (#708)
- [whatwg/fetch] Only allow blob: URLs that point to Blob objects (#708)
- Re: [w3c/ServiceWorker] should prefetch loads trigger FetchEvents? (#1302)
- Re: [whatwg/fetch] fetch assumes a url's object is always a Blob (#457)
- Re: [w3c/ServiceWorker] should prefetch loads trigger FetchEvents? (#1302)
- Re: [w3c/ServiceWorker] should prefetch loads trigger FetchEvents? (#1302)
- Re: [w3c/ServiceWorker] should prefetch loads trigger FetchEvents? (#1302)
- Re: [whatwg/fetch] Termination's aborted flag (#703)
- Re: [whatwg/fetch] Add response's cache mode back (#705)
- Re: [whatwg/fetch] Add response's cache mode back (#705)
- Re: [whatwg/fetch] Add response's cache mode back (#705)
- Re: [whatwg/fetch] Add response's cache mode back (#705)
- Re: [whatwg/fetch] Editorial: client hints are sometimes strings; should always be byte sequences (#561)
- Re: [w3ctag/design-reviews] Web Lifecycle for system initiated Discarding & Stopping (#205)
- Re: [w3ctag/design-reviews] Web Lifecycle for system initiated Discarding & Stopping (#205)
- Re: [whatwg/fetch] Casing of client headers is maybe not accurate (#475)
- Re: [whatwg/fetch] Adjust casing of client hints (#704)
- [whatwg/fetch] Client hints difference between navigation and subresources (#707)
- Re: [whatwg/fetch] Adjust casing of client hints (#704)
- Re: [w3ctag/design-reviews] Deprecating nonsecure cookie delivery. (#239)
- Re: [whatwg/fetch] Adjust casing of client hints (#704)
- [whatwg/fetch] Abort refactoring led to variable errors (#706)
- Re: [w3ctag/design-reviews] Permission Delegation (#225)
- Re: [whatwg/fetch] Add response's cache mode back (#705)
- [whatwg/fetch] Add response's cache mode back (#705)
- Re: [w3ctag/design-reviews] Web Components Guidelines Doc? (#227)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [whatwg/xhr] Editorial: less-confusing content-type manipulation algorithm for send() (#197)
- Re: [w3ctag/design-reviews] CSS Selectors 4, :focus-visible. (#233)
- Re: [w3ctag/design-reviews] CSS Selectors 4, :focus-visible. (#233)
- Re: [w3ctag/design-reviews] CSS Selectors 4, :focus-visible. (#233)
- Re: [whatwg/fetch] Use of response's cache state (#376)
- Re: [whatwg/fetch] Use of response's cache state (#376)
- Re: [whatwg/fetch] Use of response's cache state (#376)
- Re: [w3ctag/design-reviews] Web Lifecycle for system initiated Discarding & Stopping (#205)
- Re: [whatwg/fetch] Use of response's cache state (#376)
- Re: [whatwg/fetch] Allowing user provided CORS exceptions? (#644)
- Re: [whatwg/fetch] Allowing user provided CORS exceptions? (#644)
- [w3c/ServiceWorker] should prefetch loads trigger FetchEvents? (#1302)
- Re: [whatwg/fetch] Adjust casing of client hints (#704)
- Re: [whatwg/fetch] Adjust casing of client hints (#704)
- [whatwg/fetch] Adjust casing of client hints (#704)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [whatwg/fetch] fetch assumes a url's object is always a Blob (#457)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [whatwg/fetch] consider exposing and allowing script to set Request priority (#436)
- Re: [whatwg/fetch] Add { 548, 'afp' } to the blocked bad ports (#694)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [whatwg/fetch] should Response.blob() type include parameters like charset? (#540)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [w3c/manifest] Proposal: Display Mode 'standalone-no-ui' (#659)
- Re: [w3c/manifest] Proposal: Display Mode 'standalone-no-ui' (#659)
- [whatwg/fetch] Termination's aborted flag (#703)
- [whatwg/fetch] Use Infra's abort when (#702)
- Re: [whatwg/fetch] Set response's CSP list once (#701)
- Re: [whatwg/fetch] Should "set response's CSP list" be in Main fetch? (#364)
- Re: [whatwg/fetch] Set response's CSP list once (#701)
- Re: [whatwg/fetch] Does terminating a fetch before headers come back reject the promise? (#416)
- Re: [whatwg/fetch] Does terminating a fetch before headers come back reject the promise? (#416)
- Re: [whatwg/fetch] Use of response's cache state (#376)
- Re: [whatwg/fetch] Set response's CSP list once (#701)
- [whatwg/fetch] Set response's CSP list once (#701)
- Re: [whatwg/xhr] Editorial: uppercase UTF-8 (and other encodings, if any) (#196)
- [whatwg/xhr] overrideMIMEType and XML (#201)
- Re: [whatwg/xhr] Clean up remaining MIME type usage (#175)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [whatwg/xhr] Kill anonymous mode since nobody implemented it per specification. (7c4b8cb)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [whatwg/xhr] Kill anonymous mode since nobody implemented it per specification. (7c4b8cb)
- Re: [whatwg/xhr] Kill anonymous mode since nobody implemented it per specification. (7c4b8cb)
- Re: [w3c/manifest] Proposal: Display Mode 'standalone-no-ui' (#659)
- Re: [w3c/manifest] Add support for "share_target" property (#665)
- Re: [whatwg/xhr] Kill anonymous mode since nobody implemented it per specification. (7c4b8cb)
- Re: [whatwg/xhr] Look at overrideMimeType() again (#157)
- Re: [whatwg/xhr] Fix overrideMimeType() again (#174)
- Re: [whatwg/xhr] Fix overrideMimeType() again (#174)
- Re: [whatwg/xhr] Kill anonymous mode since nobody implemented it per specification. (7c4b8cb)
- Re: [whatwg/xhr] Kill anonymous mode since nobody implemented it per specification. (7c4b8cb)
- Re: [whatwg/xhr] Kill anonymous mode since nobody implemented it per specification. (7c4b8cb)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [w3c/screen-orientation] Link Screen Orientation with Fullscreen more cleanly (#62)
- Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371)
- Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700)
- Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371)
- Re: [w3c/manifest] Proposal: Display Mode 'standalone-no-ui' (#659)
- Re: [w3c/manifest] Clarify rule of navigating away from the navigation scope (#646)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [w3c/manifest] Clarify rule of navigating away from the navigation scope (#646)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [w3c/manifest] Clarify rule of navigating away from the navigation scope (#646)
- Re: [whatwg/dom] Editorial: reference "set an existing attribute value" (#638)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
Monday, 16 April 2018
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [heycam/webidl] Consider [LegacyStringClass] (#547)
- Re: [heycam/webidl] Consider [LegacyStringClass] (#547)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700)
- Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700)
- Re: [w3c/IndexedDB] Proposal: Add "writeonly" transaction mode (#234)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [whatwg/dom] Editorial: reference "set an existing attribute value" (#638)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700)
- Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700)
- Re: [whatwg/fetch] Use request's current url as base URL in redirects (#633)
- Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700)
- Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700)
- Re: [whatwg/dom] "Set an existing attribute value" not cross-linking correctly (#637)
- Re: [whatwg/dom] Editorial: reference "set an existing attribute value" (#638)
- Re: [whatwg/dom] Editorial: reference "set an existing attribute value" (#638)
- Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371)
- Re: [whatwg/fetch] Use request's current url as base URL in redirects (#633)
- Re: [whatwg/dom] Consider removing `document.origin` (#410)
- Re: [whatwg/dom] Consider removing `document.origin` (#410)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700)
- Re: [whatwg/xhr] Fix send() charset overriding to use new MIME type infrastructure (#188)
- Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176)
- Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176)
- Re: [whatwg/dom] Consider removing `document.origin` (#410)
- Re: [whatwg/dom] Consider removing `document.origin` (#410)
- Re: [whatwg/fetch] Use request's current url as base URL in redirects (#633)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [w3c/manifest] Add support for "share_target" property (#665)
- Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700)
- Re: [w3c/manifest] Add support for "share_target" property (#665)
- Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700)
- Re: [w3c/manifest] Add support for "share_target" property (#665)
- Re: [w3c/manifest] Add support for "share_target" property (#665)
- Re: [w3c/manifest] Add support for "share_target" property (#665)
- Re: [w3c/manifest] Add support for "share_target" property (#665)
- [w3c/manifest] Add support for "share_target" property (#665)
- Re: [whatwg/dom] Editorial: reference "set an existing attribute value" (#638)
- [whatwg/dom] Editorial: reference "set an existing attribute value" (#638)
- Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700)
- Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700)
- Re: [whatwg/xhr] How is the about:blank case in send-non-same-origin supported by the spec? (#194)
- Re: [whatwg/dom] Editorial: note that CDATASections are Texts inside switches (#636)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- Re: [whatwg/dom] Editorial: note that CDATASections are Texts inside switches (#636)
- Re: [whatwg/dom] Editorial: note that CDATASections are Texts inside switches (#636)
- Re: [whatwg/dom] `cloneNode` should preserve element prototype (#565)
- [whatwg/dom] "Set an existing attribute value" not cross-linking correctly (#637)
- [whatwg/dom] Editorial: note that CDATASections are Texts inside switches (#636)
Sunday, 15 April 2018
- Re: [whatwg/dom] Add window.event as a legacy compat requirement (#407)
- Re: [w3c/webcomponents] [templates] How featureful should the default processor be? (#682)
- Re: [whatwg/dom] `cloneNode` should preserve element prototype (#565)
- [w3ctag/design-reviews] Review Request: Priority Hints API (#241)
- Re: [whatwg/fetch] upload progress? (#21)
- Re: [whatwg/fetch] upload progress? (#21)
- Re: [whatwg/fetch] Use request's current url as base URL in redirects (#633)
- Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700)
- Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587)
- Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587)
- Re: [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700)
- Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681)
Saturday, 14 April 2018
- Re: [w3c/webcomponents] [templates] How featureful should the default processor be? (#682)
- Re: [w3c/webcomponents] [templates] Allow removal of boolean attributes (#705)
- Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681)
- Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681)
- Re: [whatwg/fetch] CORB: nosniff handling (#686)
- [whatwg/fetch] Proposal: `Sec-Site` should capture information about the requester of a resource (#700)
- [w3c/ServiceWorker] Does ServiceWorkerContainer.onmessage also get ExtendableMessageEvent object? (#1301)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [w3c/uievents] Add a note about inheritance of UIEvent. (#178)
- Re: [w3c/uievents] MouseEvent.fromElement/toElement (#84)
Friday, 13 April 2018
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [whatwg/fetch] CORB: nosniff handling (#686)
- Re: [whatwg/fetch] CORB: nosniff handling (#686)
- Re: [w3c/IndexedDB] Proposal: Add "writeonly" transaction mode (#234)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [heycam/webidl] Poorly worded normative requirement could be improved (#548)
- Re: [heycam/webidl] Poorly worded normative requirement could be improved (#548)
- Re: [heycam/webidl] Poorly worded normative requirement could be improved (#548)
- Re: [whatwg/streams] Revise property access order (#922)
- Re: [whatwg/streams] Revise property access order (#922)
- [whatwg/streams] Revise property access order (#922)
- Re: [whatwg/fetch] Return network error for scheme-fetch for ftp/file (#699)
- Re: [heycam/webidl] Is a subclass still a platform object? (#540)
- Re: [heycam/webidl] Is a subclass still a platform object? (#540)
- Re: [w3c/ServiceWorker] PUT request payload is lost (#1300)
- Re: [w3c/ServiceWorker] PUT request payload is lost (#1300)
- Re: [w3c/ServiceWorker] PUT request payload is lost (#1300)
- [w3c/ServiceWorker] PUT request payload is lost (#1300)
- Re: [w3c/push-api] Update privacy and server choice... (#294)
- Re: [w3c/push-api] Update privacy and server choice... (#294)
- Re: [w3c/push-api] Update privacy and server choice... (#294)
- Re: [w3c/push-api] Update privacy and server choice... (#294)
- Re: [w3c/push-api] Update privacy and server choice... (#294)
- [whatwg/fetch] Return network error for scheme-fetch for ftp/file (#699)
- Re: [heycam/webidl] Is a subclass still a platform object? (#540)
- Re: [whatwg/fetch] More informative error types (#526)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [whatwg/dom] `cloneNode` should preserve element prototype (#565)
- Re: [whatwg/dom] Dom (#635)
- Re: [whatwg/fetch] More informative error types (#526)
- Re: [whatwg/fetch] From-Origin (#687)
- [whatwg/dom] Dom (#635)
Thursday, 12 April 2018
- Re: [whatwg/fullscreen] Request Fullscreen take additional options (#123)
- [heycam/webidl] Poorly worded normative requirement could be improved (#548)
- Re: [w3ctag/design-reviews] Web Lifecycle for system initiated Discarding & Stopping (#205)
- Re: [whatwg/streams] ReadableStream should be an async iterable (#778)
- Re: [whatwg/fullscreen] Request Fullscreen take additional options (#123)
- Re: [w3c/push-api] Update privacy and server choice... (#294)
- Re: [whatwg/fullscreen] Request Fullscreen take additional options (#123)
- Re: [whatwg/fullscreen] Request Fullscreen take additional options (#123)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [whatwg/fetch] Define the "Preload Cache" (#590)
- Re: [heycam/webidl] Consider [LegacyStringClass] (#547)
- Re: [whatwg/fullscreen] Request Fullscreen take additional options (#123)
- Re: [whatwg/fetch] CORB: nosniff handling (#686)
- Re: [whatwg/fullscreen] Request Fullscreen take additional options (#123)
- Re: [whatwg/fullscreen] Request Fullscreen take additional options (#123)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [whatwg/fullscreen] Request Fullscreen take additional options (#123)
- Re: [whatwg/fullscreen] Request Fullscreen take additional options (#123)
- Re: [whatwg/streams] Numeric conversion is not done on autoAllocateChunkSize (#921)
- Re: [whatwg/fullscreen] Request Fullscreen take additional options (#123)
- Re: [whatwg/fetch] Change new Response() statusText default? (#698)
- Re: [whatwg/fetch] Change new Response() statusText default? (#698)
- Re: [whatwg/streams] ReadableStream should be an async iterable (#778)
- Re: [w3ctag/design-reviews] Payment Handler (#231)
- Re: [whatwg/streams] ReadableStream should be an async iterable (#778)
- Re: [heycam/webidl] Consider [LegacyStringClass] (#547)
- Re: [heycam/webidl] Consider [LegacyStringClass] (#547)
- Re: [whatwg/streams] ReadableStream should be an async iterable (#778)
- Re: [heycam/webidl] Consider [LegacyStringClass] (#547)
- Re: [heycam/webidl] Consider [LegacyStringClass] (#547)
- Re: [w3ctag/design-reviews] Dusting off Web Speech API? (#214)
- Re: [heycam/webidl] Consider [LegacyStringClass] (#547)
- Re: [heycam/webidl] Consider [LegacyStringClass] (#547)
- Re: [whatwg/fullscreen] Request Fullscreen take additional options (#123)
- Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165)
- Re: [whatwg/fetch] Casing of client headers is maybe not accurate (#475)
- Re: [whatwg/fetch] Stop censoring fragments (#696)
- Re: [whatwg/fetch] Stop censoring fragments (#696)
- Re: [whatwg/fetch] Stop censoring fragments (#696)
- Re: [whatwg/fetch] Stop censoring fragments (#696)
- Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206)
- Re: [w3c/push-api] Rephrase the bit about the UA chosing the push service (#287)
- Re: [w3c/ServiceWorker] Does changing updateViaCache mint a new ServiceWorkerRegistration or update them all? (#1189)
- [w3c/push-api] Update privacy and server choice... (#294)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [whatwg/fetch] More informative error types (#526)
- Re: [whatwg/fetch] More informative error types (#526)
- Re: [whatwg/fetch] Safelist Last-Event-ID (#568)
- Re: [whatwg/fetch] Use auto-linking for CSP3. (#410)
- Re: [whatwg/fetch] Use auto-linking for CSP3. (#410)
- Re: [whatwg/fetch] Response.redirect() results in status message still being OK? (#664)
- Re: [whatwg/fetch] Make status message default the empty byte sequence (#600)
- Re: [whatwg/fetch] Make status message default the empty byte sequence (#600)
- [whatwg/fetch] Change new Response() statusText default? (#698)
- Re: [whatwg/fetch] Make status message default the empty byte sequence (#600)
- Re: [whatwg/fetch] Response.redirect() results in status message still being OK? (#664)
- Re: [heycam/webidl] Consider [LegacyStringClass] (#547)
- Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505)
- Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505)
- Re: [whatwg/fetch] More informative error types (#526)
- Re: [whatwg/fetch] More informative error types (#526)
- Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505)
- Re: [whatwg/fetch] More informative error types (#526)
- Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505)
- Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505)
- [whatwg/xhr] Stop censoring responseURL's fragment (#200)
- Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505)
- Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505)
- [whatwg/fetch] Editorial: spell URL concepts uppercase (#697)
- Re: [whatwg/fetch] Stop censoring fragments (#696)
- Re: [whatwg/url] Need an "unreserved" character set (and better define how to percent-encode arbitrary strings) (#369)
- Re: [w3c/uievents] [Question] select change + mousedown behavior (#201)
- [whatwg/fetch] Stop censoring fragments (#696)
- Re: [whatwg/fetch] Requests cant "live" longer than 5 minutes? (#647)
- Re: [whatwg/fetch] Requests cant "live" longer than 5 minutes? (#647)
- Re: [whatwg/fetch] Provide ability to encode content from browser/runtime in fetch API. (#653)
- Re: [whatwg/fetch] Casing of client headers is maybe not accurate (#475)
- Re: [whatwg/fetch] More informative error types (#526)
- Re: [whatwg/fetch] More informative error types (#526)
- Re: [whatwg/fetch] Casing of client headers is maybe not accurate (#475)
- Re: [whatwg/fetch] Casing of client headers is maybe not accurate (#475)
- Re: [w3c/ServiceWorker] Does changing updateViaCache mint a new ServiceWorkerRegistration or update them all? (#1189)
- Re: [whatwg/url] Need an "unreserved" character set (and better define how to percent-encode arbitrary strings) (#369)
- Re: [w3c/webcomponents] Need callback for form submit data (#187)
- Re: [whatwg/fetch] More informative error types (#526)
- [whatwg/streams] Numeric conversion is not done on autoAllocateChunkSize (#921)
- Re: [whatwg/fetch] Casing of client headers is maybe not accurate (#475)
- Re: [whatwg/url] Need an "unreserved" character set (and better define how to percent-encode arbitrary strings) (#369)
- Re: [heycam/webidl] Consider [LegacyStringClass] (#547)
- Re: [heycam/webidl] Consider [LegacyStringClass] (#547)
- Re: [whatwg/fetch] Casing of client headers is maybe not accurate (#475)
- Re: [heycam/webidl] Consider [LegacyStringClass] (#547)
- Re: [w3c/ServiceWorker] need AsyncLocalStorage (was #904) (#906)
- Re: [whatwg/url] Need an "unreserved" character set (and better define how to percent-encode arbitrary strings) (#369)
- Re: [w3c/push-api] Security policies WRT Push traffic (#270)
- Re: [w3c/push-api] Rephrase the bit about the UA chosing the push service (#287)
- Re: [w3c/push-api] Rephrase the bit about the UA chosing the push service (#287)
- Re: [heycam/webidl] Consider [LegacyStringClass] (#547)
- [heycam/webidl] Consider [LegacyStringClass] (#547)
Wednesday, 11 April 2018
- Re: [w3ctag/design-reviews] The web platform needs a service discovery mechanism (#240)
- Re: [w3c/IndexedDB] Proposal: Add "writeonly" transaction mode (#234)
- Re: [w3c/IndexedDB] Async LocalStorage (transactionless key-value API over IDB) (#91)
- Re: [w3c/ServiceWorker] need AsyncLocalStorage (was #904) (#906)
- Re: [w3c/IndexedDB] Proposal: Add "writeonly" transaction mode (#234)
- Re: [w3c/IndexedDB] Async LocalStorage (transactionless key-value API over IDB) (#91)
- Re: [w3ctag/design-reviews] Find-in-page API(s) (#236)
- Re: [w3ctag/design-reviews] Find-in-page API(s) (#236)
- Re: [w3c/IndexedDB] Shouldn't keyPath properties be (DOMString or sequence<DOMString>)? (#235)
- Re: [w3c/IndexedDB] Shouldn't keyPath properties be (DOMString or sequence<DOMString>)? (#235)
- Re: [w3c/IndexedDB] Shouldn't keyPath properties be (DOMString or sequence<DOMString>)? (#235)
- Re: [w3ctag/design-reviews] Find-in-page API(s) (#236)
- Re: [w3c/IndexedDB] Use (DOMString or sequence<DOMString>) for keyPath (#236)
- Re: [w3c/IndexedDB] Use (DOMString or sequence<DOMString>) for keyPath (#236)
- Re: [w3c/IndexedDB] Shouldn't keyPath properties be (DOMString or sequence<DOMString>)? (#235)
- Re: [w3c/IndexedDB] Shouldn't keyPath properties be (DOMString or sequence<DOMString>)? (#235)
- Re: [w3ctag/design-reviews] Find-in-page API(s) (#236)
- Re: [w3ctag/design-reviews] Find-in-page API(s) (#236)
- Re: [w3c/IndexedDB] Use (DOMString or sequence<DOMString>) for keyPath (#236)
- [w3c/IndexedDB] Use (DOMString or sequence<DOMString>) for keyPath (#236)
- [w3c/IndexedDB] Shouldn't keyPath properties be (DOMString or sequence<DOMString>)? (#235)
- Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505)
- Re: [whatwg/fetch] Make status message default the empty byte sequence (#600)
- Re: [whatwg/fetch] Make status message default the empty byte sequence (#600)
- Re: [whatwg/fetch] Linkify "present" for dictionaries (#513)
- Re: [whatwg/fetch] Fetching with a particular destination (#521)
- Re: [whatwg/fetch] Casing of client headers is maybe not accurate (#475)
- Re: [whatwg/fetch] Casing of client headers is maybe not accurate (#475)
- Re: [w3ctag/packaging-on-the-web] Ungutted (#36)
- Re: [whatwg/fetch] Exempt HSTS-upgraded resources from mixed content blocking (#150)
- Re: [whatwg/fetch] should Response.blob() type include parameters like charset? (#540)
- Re: [whatwg/fetch] Allowing user provided CORS exceptions? (#644)
- [whatwg/xhr] Editorial: move Feature Policy Integration section (#199)
- Re: [whatwg/xhr] Editorial: use Infra for FormData (#198)
- Re: [whatwg/xhr] Editorial: use Infra for FormData (#198)
- [whatwg/dom] Meta: fix service worker reference (#634)
- Re: [whatwg/fetch] Add timeout option (#20)
- [whatwg/xhr] Editorial: use Infra for FormData (#198)
- Re: [whatwg/url] Need an "unreserved" character set (and better define how to percent-encode arbitrary strings) (#369)
- Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165)
- Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165)
- Re: [w3c/ServiceWorker] Does changing updateViaCache mint a new ServiceWorkerRegistration or update them all? (#1189)
- Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165)
- Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165)
- Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176)
- Re: [w3c/webcomponents] Need callback for form submit data (#187)
- Re: [whatwg/xhr] Fix overrideMimeType() again (#174)
- Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165)
- Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165)
- Re: [whatwg/xhr] How is the about:blank case in send-non-same-origin supported by the spec? (#194)
- Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165)
- Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165)
- Re: [whatwg/xhr] How is the about:blank case in send-non-same-origin supported by the spec? (#194)
- Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165)
- Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165)
- Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165)
- Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165)
- Re: [whatwg/xhr] Why does headers-normalize-response.htm expect null bytes to be allowed? (#165)
- Re: [whatwg/url] query state: Parser generates invalid URLs (#379)
- Re: [whatwg/url] query state: Parser generates invalid URLs (#379)
- Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587)
- Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176)
- Re: [whatwg/url] query state: Parser generates invalid URLs (#379)
- Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587)
- Re: [whatwg/xhr] Editorial: less-confusing content-type manipulation algorithm for send() (#197)
- Re: [w3c/webcomponents] Need callback for form submit data (#187)
- Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176)
- Re: [whatwg/xhr] Fix overrideMimeType() again (#174)
- Re: [whatwg/xhr] Fix overrideMimeType() again (#174)
- Re: [whatwg/url] query state: Parser generates invalid URLs (#379)
- Re: [whatwg/url] query state: Parser generates invalid URLs (#379)
- Re: [whatwg/fetch] Define the "Preload Cache" (#590)
- Re: [whatwg/url] query state: Parser generates invalid URLs (#379)
- Re: [whatwg/url] query state: Parser generates invalid URLs (#379)
- Re: [whatwg/url] query state: Parser generates invalid URLs (#379)
- Re: [w3c/ServiceWorker] Does changing updateViaCache mint a new ServiceWorkerRegistration or update them all? (#1189)
- Re: [whatwg/url] query state: Parser generates invalid URLs (#379)
- Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587)
- Re: [whatwg/url] query state: Parser generates invalid URLs (#379)
- Re: [whatwg/url] query state: Parser generates invalid URLs (#379)
- Re: [whatwg/dom] Meta: export event listener's fields (#632)
- Re: [whatwg/dom] Meta: export event listener's fields (#632)
- Re: [whatwg/dom] Meta: export event listener's fields (#632)
- Re: [whatwg/dom] Meta: export event listener's fields (#632)
- Re: [whatwg/dom] "Let capture, passive, and once be the result of flattening more options" (#633)
- Re: [whatwg/dom] "Let capture, passive, and once be the result of flattening more options" (#633)
- Re: [whatwg/dom] Meta: export event listener's fields (#632)
- Re: [whatwg/dom] "Let capture, passive, and once be the result of flattening more options" (#633)
- Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)
- [whatwg/dom] "Let capture, passive, and once be the result of flattening more options" (#633)
Tuesday, 10 April 2018
- [whatwg/dom] Meta: export event listener's fields (#632)
- Re: [w3ctag/design-reviews] Modeling media auto-playing as a permission? (#203)
- Re: [whatwg/url] query state: Parser generates invalid URLs (#379)
- Re: [w3ctag/design-reviews] Find-in-page API(s) (#236)
- Re: [whatwg/url] query state: Parser generates invalid URLs (#379)
- [whatwg/url] "For each byte in buffer: If byte is less than ..." (#379)
- Re: [w3c/IndexedDB] Proposal: Add "writeonly" transaction mode (#234)
- [w3c/IndexedDB] Proposal: Add "writeonly" transaction mode (#234)
- Re: [w3c/uievents] Need procedural algorithms for all events (#200)
- Re: [whatwg/xhr] Fix overrideMimeType() again (#174)
- Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176)
- Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176)
- [whatwg/xhr] Editorial: less-confusing content-type manipulation algorithm for send() (#197)
- Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176)
- Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176)
- Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176)
- Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176)
- Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176)
- Re: [w3ctag/design-reviews] TV-Specific Web Subsetting (#105)
- [whatwg/xhr] Editorial: uppercase UTF-8 (and other encodings, if any) (#196)
- Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176)
- Re: [whatwg/xhr] Fix overrideMimeType() again (#174)
- Re: [whatwg/url] "The fragment percent-encode set is the C0 contr..." (#378)
- Re: [heycam/webidl] Meta: remove label info from README (#546)
- Re: [whatwg/url] "The fragment percent-encode set is the C0 contr..." (#378)
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- Re: [heycam/webidl] Prototype of @@unscopable object (#496)
- [heycam/webidl] Meta: remove label info from README (#546)
- Re: [heycam/webidl] Fix broken labels (#543)
- Re: [heycam/webidl] Fix broken labels (#543)
- Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176)
- Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176)
- [heycam/webidl] Disallow [LegacyArrayClass] on globals (#545)
- Re: [whatwg/xhr] Editorial: use "{{ExceptionType!!exception}}" {{DOMException}} throughout (#173)
- Re: [whatwg/xhr] Editorial: cleanup exception terminology (#195)
- Re: [whatwg/dom] Standardize srcElement, returnValue, and window.event (#334)
- Re: [whatwg/xhr] Editorial: cleanup exception terminology (#195)
- Re: [whatwg/dom] Standardize srcElement, returnValue, and window.event (#334)
- Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681)
- [w3c/uievents] [Question] select change + mousedown behavior (#201)
- Re: [whatwg/dom] Standardize srcElement, returnValue, and window.event (#334)
- Re: [whatwg/encoding] Add Streams support (#72)
- Re: [whatwg/dom] Standardize srcElement, returnValue, and window.event (#334)
- [whatwg/xhr] Editorial: cleanup exception terminology (#195)
- Re: [whatwg/fetch] Allow range header to be set by APIs (#560)
- Re: [whatwg/fetch] Allow range header to be set by APIs (#560)
- Re: [whatwg/dom] Standardize srcElement, returnValue, and window.event (#334)
- Re: [whatwg/encoding] Add Streams support (#72)
- Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176)
- Re: [whatwg/fetch] Allow range header to be set by APIs (#560)
- Re: [whatwg/dom] NodeIterator's pre-removing steps need to account for node being root (#615)
- Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176)
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- [heycam/webidl] Should an {{@@unscopables}} property also be defined for globals? (#544)
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- [heycam/webidl] Fix broken labels (#543)
- [heycam/webidl] Remove section numbers from ES references (#542)
- Re: [whatwg/xhr] Fix overrideMimeType() again (#174)
- Re: [whatwg/fetch] "Internal response" for "internal"? (#695)
- Re: [whatwg/fetch] "Internal response" for "internal"? (#695)
- Re: [whatwg/fetch] CORB: nosniff handling (#686)
- Re: [w3ctag/design-reviews] CSS Selectors 4 (#219)
- Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681)
- Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681)
- Re: [whatwg/fetch] "Internal response" for "internal"? (#695)
- [whatwg/fetch] "Internal response" for "internal"? (#695)
- [whatwg/dom] Editorial: make traverser object associations more explicit (#631)
- Re: [whatwg/fetch] Add { 548, 'afp' } to the blocked bad ports (#694)
- [whatwg/fetch] Add { 548, 'afp' } to the blocked bad ports (#694)
- Re: [whatwg/dom] NodeIterator's pre-removing steps need to account for node being root (#615)
- Re: [whatwg/dom] NodeIterator pre-removing steps seem incorrect (#496)
- Re: [whatwg/dom] NodeIterator's pre-removing steps need to account for node being root (#615)
- Re: [whatwg/dom] Note retargeting usage in Fullscreen (#630)
- Re: [whatwg/dom] Consider moving "retargeting" to the dispatch section (#620)
- Re: [w3ctag/design-reviews] TV-Specific Web Subsetting (#105)
- Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [w3ctag/design-reviews] TV-Specific Web Subsetting (#105)
- Re: [w3ctag/design-reviews] TV-Specific Web Subsetting (#105)
- Re: [whatwg/url] "The fragment percent-encode set is the C0 contr..." (#378)
- Re: [w3c/uievents] Need algorithm for how events are fired for key presses (#142)
- Re: [w3c/uievents] Need algorithm for how mouse events are fired (#196)
- Re: [w3c/uievents] Need algorithm for how focus events are fired (#195)
- Re: [w3c/uievents] Need algorithm for how events are fired for key presses (#142)
- Re: [w3c/screen-orientation] Where are terms 'primary' and 'secondary' defined within spec? (#113)
- Re: [w3c/uievents] Need algorithm for how mouse click events are fired (#197)
- Re: [whatwg/xhr] final readystatechange (readyState === 3) (#161)
- Re: [w3c/permissions] Possibly add 'vibration' to Permission Registry Enum? (#173)
- [w3c/permissions] Possibly add 'vibration' to Permission Registry Enum? (#173)
- Re: [whatwg/url] "The fragment percent-encode set is the C0 contr..." (#378)
Monday, 9 April 2018
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- [whatwg/url] "The fragment percent-encode set is the C0 contr..." (#378)
- Re: [w3c/uievents] Need algorithm for how input events are fired (#198)
- Re: [w3c/uievents] Need algorithm for how composition events are fired (#199)
- Re: [w3c/uievents] Need algorithm for how mouse click events are fired (#197)
- [w3c/uievents] Need algorithm for how focus events are fired (#195)
- [w3c/uievents] Need procedural algorithms for all events (#200)
- [w3c/uievents] Need algorithm for how composition events are fired (#199)
- [w3c/uievents] Need algorithm for how input events are fired (#198)
- Re: [whatwg/streams] Linkify all class definitions (#913)
- [w3c/uievents] Need algorithm for how mouse click events are fired (#197)
- Re: [w3c/uievents] Need algorithm for how focus events are fired (#195)
- Re: [whatwg/streams] Linkify all class definitions (#913)
- [w3c/uievents] Need algorithm for how mouse events are fired (#196)
- Re: [whatwg/streams] Linkify all class definitions (#913)
- Re: [whatwg/streams] Linkify all class definitions (#913)
- Re: [w3ctag/design-reviews] Web Lifecycle for system initiated Discarding & Stopping (#205)
- Re: [w3c/ServiceWorker] Cache API: Cache-Control headers and Opaque Responses (#1299)
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- [whatwg/fetch] Pass site-for-cookies through Fetch (#693)
- Re: [whatwg/dom] Abort controller design (#438)
- Re: [whatwg/fetch] Allow range header to be set by APIs (#560)
- Re: [whatwg/dom] Abort controller design (#438)
- [whatwg/dom] Note retargeting usage in Fullscreen (#630)
- Re: [whatwg/dom] Should we really support modifying an already dispatched event via initEvent()? (#523)
- Re: [whatwg/dom] Should we really support modifying an already dispatched event via initEvent()? (#523)
- Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371)
- Re: [heycam/webidl] Describe JSON-LD with WebIDL - How to handle @ tags (#541)
- Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371)
- Re: [heycam/webidl] Describe JSON-LD with WebIDL - How to handle @ tags (#541)
- Re: [w3c/ServiceWorker] if a worker script redirects from an in-scope URL to an out-of-scope URL, what is the worker's final controller? (#1239)
- Re: [whatwg/fetch] Allow range header to be set by APIs (#560)
- Re: [w3c/ServiceWorker] if a worker script redirects from an in-scope URL to an out-of-scope URL, what is the worker's final controller? (#1239)
- Re: [whatwg/dom] Editorial: cleanup TreeWalker (#616)
- Re: [heycam/webidl] Describe JSON-LD with WebIDL - How to handle @ tags (#541)
- Re: [whatwg/dom] Fix TreeWalker's nextNode() (#612)
- Re: [whatwg/dom] setAttribute is missing a domintro? (#448)
- Re: [whatwg/dom] Add more domintro boxes (#601)
- [whatwg/dom] Add NonDocumentFragmentParentNode (#629)
- Re: [whatwg/dom] NodeIterator's pre-removing steps need to account for node being root (#615)
- Re: [w3ctag/design-reviews] CSS Layout API (#224)
- Re: [w3ctag/design-reviews] CSS Layout API (#224)
- Re: [whatwg/fetch] Allow range header to be set by APIs (#560)
- Re: [whatwg/fetch] Allow range header to be set by APIs (#560)
- Re: [whatwg/dom] Editorial: add range's common ancestor (#608)
- Re: [whatwg/dom] Editorial: add range's common ancestor (#608)
- Re: [whatwg/dom] Define Event.srcElement and Event.returnValue (#626)
- Re: [whatwg/dom] Flag refs in preventDefault()'s description missing "context object’s" qualifier (#627)
- Re: [whatwg/dom] Define Event.srcElement and Event.returnValue (#625)
- Re: [whatwg/dom] Define Event.srcElement and Event.returnValue (#626)
- Re: [w3ctag/design-reviews] Permission Delegation (#225)
- Re: [whatwg/dom] Standardize srcElement, returnValue, and window.event (#334)
- Re: [w3ctag/design-reviews] Permission Delegation (#225)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [w3ctag/design-reviews] Find-in-page API(s) (#236)
- Re: [whatwg/dom] Standardize srcElement, returnValue, and window.event (#334)
- Re: [whatwg/dom] Standardize srcElement, returnValue, and window.event (#334)
- Re: [w3ctag/design-reviews] TV-Specific Web Subsetting (#105)
- Re: [whatwg/dom] Define Event.srcElement and Event.returnValue (#626)
- Re: [whatwg/dom] Standardize srcElement, returnValue, and window.event (#334)
- Re: [whatwg/dom] Define Event.srcElement and Event.returnValue (#626)
- Re: [whatwg/dom] Define Event.srcElement and Event.returnValue (#626)
- Re: [whatwg/dom] Define Event.srcElement and Event.returnValue (#626)
- Re: [heycam/webidl] Describe JSON-LD with WebIDL - How to handle @ tags (#541)
- Re: [whatwg/dom] Define Event.srcElement and Event.returnValue (#626)
- Re: [whatwg/fetch] Allow range header to be set by APIs (#560)
- Re: [w3ctag/design-reviews] Deprecating nonsecure cookie delivery. (#239)
- Re: [whatwg/dom] Hook for SVG and HTML script element insertion (#575)
- Re: [whatwg/dom] Hook for SVG and HTML script element insertion (#575)
- Re: [whatwg/dom] Standardize srcElement, returnValue, and window.event (#334)
- Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917)
- Re: [whatwg/dom] "Use these attribute change steps to update an element's ID" (#628)
- Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917)
- Re: [whatwg/fetch] Java run bug report (#692)
- Re: [w3c/manifest] New Boolean members to control interaction with related applications (#658)
- Re: [w3ctag/design-reviews] Deprecating nonsecure cookie delivery. (#239)
- Re: [w3ctag/design-reviews] Permission Delegation (#225)
- [whatwg/dom] "Use these attribute change steps to update an element's ID" (#628)
Sunday, 8 April 2018
- [whatwg/fetch] Java run bug report (#692)
- Re: [w3ctag/design-reviews] Changing requirements for Well-Known URIs (#237)
- Re: [whatwg/fetch] Java run bug report (#692)
- Re: [w3ctag/design-reviews] BCP56bis (#232)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- Re: [whatwg/dom] Un-merge Document and HTMLDocument (#221)
- Re: [heycam/webidl] Note regarding old vs new Mixin syntax (#536)
- Re: [heycam/webidl] Note regarding old vs new Mixin syntax (#536)
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- Re: [heycam/webidl] Make interface prototype object creation imperative (#494)
- Re: [w3ctag/design-reviews] Signed Exchanges (#235)
- Re: [w3ctag/design-reviews] BCP56bis (#232)
- Re: [w3c/permissions] autoplay permission (#172)
- Re: [w3c/permissions] autoplay permission (#172)
- Re: [whatwg/fetch] Expose Stream Watermarks (#689)
Saturday, 7 April 2018
- Re: [whatwg/fetch] Expose Stream Watermarks (#689)
- Re: [whatwg/fetch] Expose Stream Watermarks (#689)
- Re: [whatwg/fetch] Expose Stream Watermarks (#689)
- Re: [whatwg/fetch] Expose Stream Watermarks (#689)
- Re: [whatwg/fetch] Expose Stream Watermarks (#689)
- Re: [whatwg/fetch] Expose Stream Watermarks (#689)
- Re: [whatwg/fetch] Expose Stream Watermarks (#689)
- Re: [whatwg/fetch] Expose Stream Watermarks (#689)
- Re: [whatwg/fetch] Expose Stream Watermarks (#689)
- Re: [whatwg/fetch] Expose Stream Watermarks (#689)
- Re: [whatwg/fetch] Expose Stream Watermarks (#689)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [heycam/webidl] Editorial: minor copy editing (#538)
- Re: [w3ctag/design-reviews] Signed Exchanges (#235)
- Re: [w3ctag/design-reviews] TV-Specific Web Subsetting (#105)
- Re: [w3ctag/design-reviews] Deprecating nonsecure cookie delivery. (#239)
- Re: [w3ctag/design-reviews] Deprecating nonsecure cookie delivery. (#239)
- Re: [w3ctag/design-reviews] BCP56bis (#232)
- Re: [w3ctag/design-reviews] TV-Specific Web Subsetting (#105)
- Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141)
- Re: [w3ctag/design-reviews] Clear Site Data (#62)
- Re: [w3ctag/design-reviews] Permission Delegation (#225)
- Re: [w3ctag/design-reviews] Permission Delegation (#225)
- Re: [w3ctag/design-reviews] Permission Delegation (#225)
- Re: [w3ctag/design-reviews] CSS Layout API (#224)
- Re: [w3ctag/design-reviews] Web Locks API (#217)
- Re: [w3ctag/design-reviews] Web Locks API (#217)
- Re: [w3ctag/design-reviews] Request review of (text only) Async Clipboard API (#222)
- Re: [w3ctag/design-reviews] Request review of (text only) Async Clipboard API (#222)
- Re: [w3ctag/design-reviews] Request review of (text only) Async Clipboard API (#222)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [w3ctag/design-reviews] Request review of (text only) Async Clipboard API (#222)
- Re: [w3ctag/design-reviews] Request review of (text only) Async Clipboard API (#222)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [w3ctag/design-reviews] Deprecating nonsecure cookie delivery. (#239)
- Re: [w3c/permissions] autoplay permission (#172)
- Re: [w3ctag/design-reviews] Deprecating nonsecure cookie delivery. (#239)
- Re: [w3ctag/design-reviews] Modeling media auto-playing as a permission? (#203)
- Re: [w3ctag/design-reviews] Modeling media auto-playing as a permission? (#203)
- Re: [w3ctag/design-reviews] Review of signature-based resource loading restrictions. (#186)
- Re: [w3ctag/design-reviews] Review of signature-based resource loading restrictions. (#186)
- Re: [w3ctag/design-reviews] Payment Handler (#231)
- Re: [w3ctag/design-reviews] Payment Handler (#231)
- Re: [w3ctag/design-reviews] Payment Handler (#231)
- Re: [w3ctag/design-reviews] BCP56bis (#232)
- Re: [w3ctag/design-reviews] BCP56bis (#232)
- Re: [w3ctag/design-reviews] Payment Handler (#231)
- [w3ctag/design-reviews] The web platform needs a service discovery mechanism (#240)
- Re: [w3ctag/design-reviews] Changing requirements for Well-Known URIs (#237)
- Re: [w3ctag/design-reviews] <link> rel="modulepreload" (#213)
- Re: [w3ctag/design-reviews] <link> rel="modulepreload" (#213)
- Re: [w3ctag/design-reviews] <link> rel="modulepreload" (#213)
- Re: [w3ctag/design-reviews] <link> rel="modulepreload" (#213)
- Re: [w3ctag/design-reviews] <link> rel="modulepreload" (#213)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [w3ctag/design-reviews] Signed Exchanges (#235)
- Re: [w3ctag/design-reviews] Signed Exchanges (#235)
- Re: [w3ctag/design-reviews] Signed Exchanges (#235)
- Re: [w3ctag/design-reviews] Signed Exchanges (#235)
- Re: [w3ctag/design-reviews] Signed Exchanges (#235)
- Re: [w3ctag/design-reviews] Signed Exchanges (#235)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [w3ctag/design-reviews] Signed Exchanges (#235)
- Re: [w3ctag/design-reviews] Keyboard Map (#238)
- Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206)
- Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206)
- Re: [w3ctag/design-reviews] CSS Selectors 4, :focus-visible. (#233)
- Re: [w3ctag/design-reviews] Keyboard Map (#238)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
Friday, 6 April 2018
- Re: [w3c/uievents] Support queryKeyCap (#156)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [w3c/ServiceWorker] Configure script's settings and realm for service workers (#1294)
- Re: [w3ctag/design-reviews] Web Lifecycle for system initiated Discarding & Stopping (#205)
- Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917)
- Re: [whatwg/dom] Fixes #625. Define Event.srcElement and Event.returnValue for compat. (#626)
- Re: [whatwg/dom] Standardize srcElement, returnValue, and window.event (#334)
- Re: [heycam/webidl] Describe JSON-LD with WebIDL - How to handle @ tags (#541)
- [w3ctag/design-reviews] Deprecating nonsecure cookie delivery. (#239)
- Re: [whatwg/dom] Standardize srcElement, returnValue, and window.event (#334)
- Re: [whatwg/dom] Fixes #625. Define Event.srcElement and Event.returnValue for compat. (#626)
- Re: [whatwg/dom] Standardize srcElement, returnValue, and window.event (#334)
- Re: [whatwg/dom] Standardize srcElement, returnValue, and window.event (#334)
- Re: [heycam/webidl] Describe JSON-LD with WebIDL - How to handle @ tags (#541)
- Re: [whatwg/dom] NodeIterator's pre-removing steps need to account for node being root (#615)
- Re: [whatwg/dom] NodeIterator's pre-removing steps need to account for node being root (#615)
- Re: [whatwg/dom] "create an event" doesn't work for certain UI events (#414)
- Re: [whatwg/dom] Define event constructing steps (#614)
- Re: [w3c/uievents] Define "event constructing steps" for complicated events (#194)
- [w3c/touch-events] Define "event constructing steps" (#94)
- [w3c/uievents] Define "event constructing steps" for complicated events (#194)
- Re: [whatwg/fetch] Specify restriction for requests with keepalive set (#679)
- Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685)
- Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685)
- Re: [whatwg/dom] Add window.event as a legacy compat requirement (#407)
- Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685)
- Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334)
- Re: [whatwg/dom] Standardize certain Microsoft event extensions (#334)
- Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681)
- Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917)
- Re: [heycam/webidl] Describe JSON-LD with WebIDL - How to handle @ tags (#541)
- Re: [whatwg/fetch] Allow range header to be set by APIs (#560)
- Re: [whatwg/fetch] Allow range header to be set by APIs (#560)
- Re: [whatwg/fetch] Allow range header to be set by APIs (#560)
- [heycam/webidl] Describe JSON-LD with WebIDL - How to handle @ tags (#541)
- Re: [whatwg/fetch] Allow range header to be set by APIs (#560)
- Re: [whatwg/dom] Flag refs in preventDefault()'s description missing "context object’s" qualifier (#627)
- Re: [whatwg/dom] Fixes #625. Define Event.srcElement and Event.returnValue for compat. (#626)
- Re: [whatwg/dom] Fixes #625. Define Event.srcElement and Event.returnValue for compat. (#626)
- Re: [whatwg/fetch] Specify restriction for requests with keepalive set (#679)
- Re: [whatwg/fetch] Specify restriction for requests with keepalive set (#679)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/editing] make need of execCommand to hide table controls go away on FF (#171)
- Re: [w3ctag/design-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76)
- Re: [w3ctag/design-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76)
- Re: [w3ctag/design-reviews] Files and Directory Entries API with webkit prefixes! (#215)
- Re: [w3ctag/design-reviews] Files and Directory Entries API with webkit prefixes! (#215)
- Re: [w3ctag/design-reviews] Web Lifecycle for system initiated Discarding & Stopping (#205)
- Re: [w3ctag/design-reviews] Find-in-page API(s) (#236)
- Re: [w3ctag/design-reviews] Request review for Keyboard Map (#238)
- Re: [w3ctag/design-reviews] Request review for Keyboard Map (#238)
- Re: [w3ctag/design-reviews] "With Credentials" flag possibly inconsistent with web architecture (#76)
- [whatwg/dom] Flag refs in preventDefault()'s description missing "context object’s" qualifier (#627)
- Re: [whatwg/dom] Fixes #625. Define Event.srcElement and Event.returnValue for compat. (#626)
- Re: [w3ctag/design-reviews] Review OffscreenCanvas, including ImageBitmapRenderingContext (#141)
- Re: [w3ctag/design-reviews] HTML General Review (#174)
- Re: [w3c/ServiceWorker] Formalizing a timeout API (#1292)
- [w3ctag/design-reviews] Request review for Keyboard Map (#238)
Thursday, 5 April 2018
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [whatwg/dom] Fixes #625. Define Event.srcElement and Event.returnValue for compat. (#626)
- Re: [whatwg/dom] Fixes #625. Define Event.srcElement and Event.returnValue for compat. (#626)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/clipboard-apis] Request TAG review for initial (text only) API (#59)
- Re: [w3c/clipboard-apis] Request TAG review for initial (text only) API (#59)
- Re: [w3c/ServiceWorker] Cache API: Cache-Control headers and Opaque Responses (#1299)
- [w3c/ServiceWorker] Cache API: Cache-Control headers and Opaque Responses (#1299)
- Re: [w3c/ServiceWorker] Intecepts progress event of AJAX calls (#1298)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- [w3c/ServiceWorker] Intecepts progress event of AJAX calls (#1298)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [heycam/webidl] Is a subclass still a platform object? (#540)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [heycam/webidl] Is a subclass still a platform object? (#540)
- Re: [heycam/webidl] Remove [LegacyArrayClass] (#291)
- Re: [heycam/webidl] Is a subclass still a platform object? (#540)
- Re: [whatwg/fetch] Specify restriction for requests with keepalive set (#679)
- Re: [whatwg/fetch] Allow range header to be set by APIs (#560)
- Re: [whatwg/fetch] Allow range header to be set by APIs (#560)
- Re: [whatwg/fetch] Allow range header to be set by APIs (#560)
- Re: [whatwg/fetch] Allow range header to be set by APIs (#560)
- Re: [whatwg/dom] Add window.event as a legacy compat requirement (#407)
- Re: [whatwg/dom] Add window.event as a legacy compat requirement (#407)
- Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917)
- Re: [heycam/webidl] Is a subclass still a platform object? (#540)
- Re: [heycam/webidl] Is a subclass still a platform object? (#540)
- Re: [whatwg/fetch] Allow range header to be set by APIs (#560)
- Re: [whatwg/fetch] Allow range header to be set by APIs (#560)
- Re: [whatwg/fetch] Allow range header to be set by APIs (#560)
- Re: [whatwg/fetch] Allow range header to be set by APIs (#560)
- Re: [heycam/webidl] Is a subclass still a platform object? (#540)
- [heycam/webidl] Is a subclass still a platform object? (#540)
- Re: [whatwg/dom] Add window.event as a legacy compat requirement (#407)
- Re: [whatwg/dom] Add window.event as a legacy compat requirement (#407)
- Re: [whatwg/dom] Add window.event as a legacy compat requirement (#407)
- Re: [whatwg/fetch] Specify restriction for requests with keepalive set (#679)
- Re: [whatwg/dom] Add window.event as a legacy compat requirement (#407)
- 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] Document same-origin policy more centrally (#691)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [whatwg/fetch] Document same-origin policy more centrally (#691)
- 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)
- [whatwg/fetch] Document same-origin policy more centrally (#691)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/uievents] Standardizing event.layerX and event.layerY (#193)
- Re: [w3c/uievents] Standardizing event.layerX and event.layerY (#193)
- Re: [w3c/uievents] Standardize layerX/layerY on MouseEvent (#135)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [w3c/uievents] Standardizing event.layerX and event.layerY (#193)
- Re: [w3ctag/design-reviews] Signed Exchanges (#235)
- [w3c/uievents] Standardizing event.layerX and event.layerY (#193)
- Re: [whatwg/fetch] Make fetch() use "same-origin" credentials by default (#585)
- Re: [whatwg/fetch] Make fetch() use "same-origin" credentials by default (#585)
- Re: [w3ctag/design-reviews] Transform Streams (#211)
- Re: [w3ctag/design-reviews] Transform Streams (#211)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [w3ctag/design-reviews] CSS Selectors 4 (#219)
- Re: [w3ctag/design-reviews] CSS Selectors 4 (#219)
- Re: [whatwg/fetch] Handling Partial Content / 206 (#144)
- Re: [whatwg/fetch] Handling Partial Content / 206 (#144)
- Re: [whatwg/fetch] Handling Partial Content / 206 (#144)
- Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [w3ctag/design-reviews] CSS Layout API (#224)
- Re: [w3ctag/design-reviews] CSS Layout API (#224)
- Re: [w3ctag/design-reviews] Web Components Guidelines Doc? (#227)
- Re: [w3ctag/design-reviews] Web Components Guidelines Doc? (#227)
- Re: [w3ctag/design-reviews] Signed Exchanges (#235)
- Re: [w3ctag/design-reviews] Signed Exchanges (#235)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206)
- Re: [whatwg/fetch] Specify restriction for requests with keepalive set (#679)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3ctag/design-reviews] Should WebRTC be [SecureContext] (#228)
- Re: [w3ctag/design-reviews] Should WebRTC be [SecureContext] (#228)
- Re: [w3ctag/design-reviews] Should WebRTC be [SecureContext] (#228)
- Re: [w3ctag/design-reviews] CSS Selectors 4, :focus-visible. (#233)
- Re: [w3ctag/design-reviews] BCP56bis (#232)
Wednesday, 4 April 2018
- Re: [w3c/ServiceWorker] Improve.ready and Activate (#1277) (4cc72bd)
- Re: [whatwg/fullscreen] Request Fullscreen take additional options (#123)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917)
- Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587)
- Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587)
- Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681)
- Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587)
- Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587)
- Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587)
- Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681)
- Re: [whatwg/fetch] Allow range header to be set by APIs (#560)
- [w3c/ServiceWorker] Give a fine grade to the Service Worker's lifetime (#1297)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917)
- Re: [whatwg/streams] What are the preconditions for ReadableStreamDefaultControllerError? (#920)
- Re: [whatwg/fetch] Allow range header to be set by APIs (#560)
- Re: [whatwg/fetch] Allow range header to be set by APIs (#560)
- Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681)
- Re: [whatwg/fetch] Allow range header to be set by APIs (#560)
- Re: [heycam/webidl] No location for constants on callback interface (#539)
- Re: [heycam/webidl] No location for constants on callback interface (#539)
- Re: [whatwg/fetch] Allow range header to be set by APIs (#560)
- Re: [whatwg/fetch] Allow range header to be set by APIs (#560)
- Re: [heycam/webidl] No location for constants on callback interface (#539)
- [heycam/webidl] No location for constants on callback interface (#539)
- Re: [w3c/webcomponents] Need callback for form submit data (#187)
- Re: [w3c/webcomponents] Need callback for form submit data (#187)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/webcomponents] Need callback for form submit data (#187)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/webcomponents] Need callback for form submit data (#187)
- Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917)
- [whatwg/streams] What are the preconditions for ReadableStreamDefaultControllerError? (#920)
- Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685)
- Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
Tuesday, 3 April 2018
- Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685)
- Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685)
- Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685)
- Re: [w3c/permissions] autoplay permission (#172)
- Re: [w3ctag/design-reviews] Review request for ResizeObserver (#187)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917)
- Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917)
- Re: [whatwg/streams] ReadableStream constructor: standard text and reference implementation doesn't match (#917)
- Re: [whatwg/fetch] Expose Stream Watermarks (#689)
- Re: [whatwg/fetch] Expose Stream Watermarks (#689)
- Re: [whatwg/fetch] Expose Stream Watermarks (#689)
- Re: [whatwg/fetch] Expose Stream Watermarks (#689)
- Re: [whatwg/fetch] Typo2018 (#690)
- Re: [w3c/ServiceWorker] Improve.ready and Activate (#1277) (4cc72bd)
- Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371)
- Re: [w3c/ServiceWorker] Formalizing a timeout API (#1292)
- [whatwg/fetch] Typo2018 (#690)
- Re: [whatwg/fetch] Typo2018 (#690)
- Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371)
- Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371)
- Re: [whatwg/fetch] Expose Stream Watermarks (#689)
- Re: [whatwg/fetch] Expose Stream Watermarks (#689)
- Re: [whatwg/fetch] Expose Stream Watermarks (#689)
- Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371)
- Re: [whatwg/fetch] Expose Stream Watermarks (#689)
- Re: [whatwg/fetch] Expose Stream Watermarks (#689)
- Re: [whatwg/fetch] Expose Stream Watermarks (#689)
- Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371)
- Re: [whatwg/fetch] Expose Stream Watermarks (#689)
- Re: [w3c/ServiceWorker] Improve.ready and Activate (#1277) (4cc72bd)
- Re: [whatwg/fetch] CORB: nosniff handling (#686)
- Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681)
- Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371)
- Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371)
- Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371)
- [w3c/clipboard-apis] Clarify promise rejection value (#76)
- Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371)
- Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371)
- Re: [w3c/ServiceWorker] .ready promise should be resolved after updating registration.state properties (#1011)
- Re: [w3c/ServiceWorker] Improve.ready and Activate (#1277)
- Re: [w3c/manifest] Minor text tweaks (#664)
- Re: [w3c/manifest] Minor text tweaks (#664)
- [w3c/manifest] Minor text tweaks (#664)
- Re: [w3c/IndexedDB] Allow BigInts as IndexedDB keys (#231)
- [whatwg/streams] Assert that desiredSize is non-null in ReadableStreamDefaultControllerShouldCallPull (#919)
- Re: [w3c/ServiceWorker] Track ancestorOrigins privacy issues (#1075)
- Re: [w3c/ServiceWorker] Improve.ready and Activate (#1277)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/fetch] Expose Stream Watermarks (#689)
- Re: [whatwg/url] "Let pointer be a pointer to first code point in..." (#373)
- Re: [whatwg/fetch] Expose Stream Watermarks (#689)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/dom] Issue #625. Define Event.srcElement and Event.returnValue for compat. (#626)
- Re: [whatwg/fetch] From-Origin (#687)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [w3c/IndexedDB] Allow BigInts as IndexedDB keys (#231)
- Re: [whatwg/fetch] Expose Stream Watermarks (#689)
- Re: [w3c/ServiceWorker] Remove frameType, maybe add ancestorOrigins (#732)
- Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371)
- Re: [whatwg/dom] `cloneNode` should preserve element prototype (#565)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/fetch] Expose Stream Watermarks (#689)
- Re: [whatwg/fetch] Expose Stream Watermarks (#689)
- Re: [whatwg/dom] `cloneNode` should preserve element prototype (#565)
- Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
Monday, 2 April 2018
- Re: [w3c/permissions] Add support for permissions that have an associated Feature Policy (#163)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- [w3ctag/design-reviews] Changing requirements for Well-Known URIs (#237)
- Re: [whatwg/streams] Fix a reference to [[queueSize]] (#918)
- Re: [whatwg/streams] Constructor: replace _readableStrategy_ with _strategy_ (#916)
- Re: [whatwg/streams] Fix a reference to [[queueSize]] (#918)
- Re: [whatwg/streams] Constructor: replace _readableStrategy_ with _strategy_ (#916)
- Re: [whatwg/url] "Let pointer be a pointer to first code point in..." (#373)
- Re: [whatwg/fullscreen] Impossible to customize the style of a dialog's ::backdrop residing inside a Shadow DOM. (#124)
- Re: [whatwg/dom] Issue #625. Define Event.srcElement and Event.returnValue for compat. (#626)
- Re: [whatwg/dom] Issue #625. Define Event.srcElement and Event.returnValue for compat. (#626)
- Re: [whatwg/fetch] Expose Stream Watermarks (#689)
- [whatwg/fetch] Expose Stream Watermarks (#689)
- Re: [w3c/selection-api] fixup some ReSpec issues (#95)
- Re: [whatwg/fetch] Question — Why can I not read the stream again ? (#196)
- Re: [whatwg/fullscreen] Request Fullscreen take additional options (#123)
- [whatwg/streams] Fix a reference to [[queueSize]] (#918)
- Re: [w3c/selection-api] fixup some ReSpec issues (#95)
- Re: [w3c/selection-api] fixup some ReSpec issues (#95)
- Re: [w3c/selection-api] fixup some ReSpec issues (#95)
- Re: [w3c/selection-api] fixup some ReSpec issues (#95)
- Re: [w3c/selection-api] fixup some ReSpec issues (#95)
- Re: [w3c/selection-api] fixup some ReSpec issues (#95)
- [w3c/selection-api] fixup some ReSpec issues (#95)
- Re: [w3c/ServiceWorker] should FetchEvent.request.cache reflect non-fetch browser cache controls? (#875)