-
Notifications
You must be signed in to change notification settings - Fork 46
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
Include SVG 1.1 #273
Comments
For specs that have multiple versions, the approach we've taken so far to determine whether previous versions should be added to the list is to look at what the version-less shortname redirects to. In this case, https://www.w3.org/TR/SVG/ redirects to SVG 2, published as a Candidate Recommendation (which should convey some notion of stability). That spec presents itself as building "upon SVG 1.1 Second Edition by improving the usability and precision of the language". It should not only include additions or changes to SVG 1. What is missing exactly? FYI, the bits you provided would be automatically generated by the generating code. All that is needed to add SVG 1.1 to the list is to add a line |
My apologies - by missing I meant the attributes that have been deprecated by SVG2. My only argument for including SVG1 is that most browsers do not support SVG2 in full (AFAIK) and further that some of those deprecated features are still in use. Though, I also understand and agree with your reasoning for only including SVG2. |
MDN also documents a few SVG 1.1 only features. I haven't checked if the docs should rather be archived but given they currently exist, it would also be useful for us if browser-specs had SVG 1.1. Here's what mdn-browser-compat-data references right now and I believe these things aren't in SVG2. Happy to discuss what to do about these.
|
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.
I added SVG 1.1 to browser-specs, released in v1.35.0. There is no dedicated nightly document for SVG 1.1, so the |
Currently, only the SVG2 (and related) specs are included. However, SVG2 only includes additions or changes to the SVG 1 specification. For completeness, it would be useful to include the SVG1.1 spec as well.
Note, some of these values may be incorrect. I based these entries on the SVG2 spec definition.
The text was updated successfully, but these errors were encountered: