-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Do-Not-Track spec #281
Comments
I'm fine with this but if the goal is to extract the IDL fragments, that is not going to work. The fact that the document is non-normative (in practice, the fact that (The IDL fragments also need to be fixed but that's a separate issue) |
I guess the IDL extraction is something we'll need to consider in the context of reffy (maybe we can add an exception there if we really want the IDL extracted) |
This adds three requested specs that sit at the boundary of spec selection criteria for browser-specs: 1. DNT, requested in w3c#281 2. SVG 1.1, requested in w3c#273 3. Web App Manifest - App info, requested in w3c#283 The SVG 1.1 entry uses SVG 2 as nightly URL for lack of a better alternative. JSON schema has to be slightly adjusted to account for the "-" in "tracking-dnt.html". Also, a test started to fail because "hr-time-3" is now the default level for HR Time.
This adds three requested specs that sit at the boundary of spec selection criteria for browser-specs: 1. DNT, requested in #281 2. SVG 1.1, requested in #273 3. Web App Manifest - App info, requested in #283 The SVG 1.1 entry uses SVG 2 as nightly URL for lack of a better alternative. JSON schema has to be slightly adjusted to account for the "-" in "tracking-dnt.html". Also, a test started to fail because "hr-time-3" is now the default level for HR Time.
Added to browser-specs, and released in v1.35.0. |
https://www.w3.org/TR/tracking-dnt/ defines WebIDL fragments widely implemented; even though it's been made non-normative, it should probably still be part of browser-specs (as highlighted in #279)
The text was updated successfully, but these errors were encountered: