-
Notifications
You must be signed in to change notification settings - Fork 22.5k
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
Use {{Specifications}} macro for svg/element/* #5856
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR will make us loose some information, @Elchi3.
Especially the comments column (see https://pr5856.content.dev.mdn.mozit.cloud/en-US/docs/Web/SVG/Element/image for example).
However, I don't see, how this could be avoided using the new macro.
Perhaps worth to pull it out of the table and into paragraphs below?
In this example, the information in the comment column is the difference between two versions of specification. They are useless for the web developer. AFAIK, there shouldn't be useful info (for the webdev) in this column (it is different for the "historian" digging into the evolution of a feature) |
Our thoughts on removing these notes have been:
|
The spec titles here are often "SVG 1.1" when they should be "SVG 2", see https://pr5856.content.dev.mdn.mozit.cloud/en-US/docs/Web/SVG/Element/image#specifications. The link to SVG 2 is correct there but not the title. I filed w3c/browser-specs#312 to see if the data source could be changed. If not, I need to tweak the code that generates our specification tables to fix this bug. No follow-up required on mdn/content, though. Thanks for rolling this out to more pages! |
This is part #1146.
This converts SVG elements to the {{Specifications}} macros. This is my first PR of this type, so a thorough review is needed.
There were no comments in the section, so it was pretty trivial to replace.
reviewer: @Elchi3