SVG:Specification Issues: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
This page tracks some of the specification issues we've encountered more recently while implementing SVG.
When we discovered SVG specification issues in the past we simply reported them to the SVG working group via their mailing list, believing they would be tracked and (eventually) fixed. However, it has become clear that this system of reporting issues is an utter farce. Any reasonable issue tracking system would at the very least make it possible to:
* search through existing issues without returning non-issue mailing list chatter
* know whether your reports are even actually being treated as issues
* unambiguously mark the status of each issue so everyone can easily and clearly see when an issue has been closed/dropped (thus people can ask for further clarification if the solution is unsatisfactory or unstated, instead of believing that the issue is still open and being worked on)
* make sure the resolution is visible to all when an issue is closed
Unfortunately, using a mailing list for issue reporting fails to provide even these most basic of requirements. This has resulted in countless hours wasted and much hair pulling and resentment on our part. While we may not be able to force the W3C to use a reasonable, public, issue tracking system, we can at least try to publicly track any new issues we find (and maybe even go back and dig up the old issues we've reported at some point). Hence this page.
Ideally issues should be tracked using issue tracking software, but that's often less accessible to "outsiders", and it can take time and many iterations to hash out a good clear description for an issue. In that respect, wiki pages (with their version history and the ability to revert changes) are very useful.
Ideally issues should be tracked using issue tracking software, but that's often less accessible to "outsiders", and it can take time and many iterations to hash out a good clear description for an issue. In that respect, wiki pages (with their version history and the ability to revert changes) are very useful.


Revision as of 18:32, 2 November 2011

Ideally issues should be tracked using issue tracking software, but that's often less accessible to "outsiders", and it can take time and many iterations to hash out a good clear description for an issue. In that respect, wiki pages (with their version history and the ability to revert changes) are very useful.

Resolved in errata

Retrieved from "https://wiki.allizom.org/index.php?title=SVG:Specification_Issues&oldid=363802"