The SVG Working Group welcomes feedback from authors, users, implementors, vendors, and other standards organizations. For feature requests or issues with our specifications, our test suite, our errata, and other documents, we prefer to use a public issue tracker, where issues can be filed and the progress followed by the general public. For questions and discussion (or if you prefer to operate by email), please send a message to the public SVG mailing list. We hope to operate as openly as possible, given our resources and obligations. If you have questions about our process, or problems with the way the group operates, please contact the W3C Team Contact for SVG, Doug Schepers.
It is important to note that for problems with particular user agents, such as browsers or authoring tools, feedback should be sent directly to that user agent.
Also, please note that the SVG Working Group has limited resources, and any given issue may take considerable time to resolve effectively, so your patience is appreciated. If you have raised an issue with us, and have not received a reply in a reasonable timeframe, please feel free to contact us via the public email list.
File an issue (registration required).
Currently, we are using the Bugzilla bug tracking system. While not ideal for issues (being designed for bugs in software), it can at least serve as a stopgap, and we are assessing what features we need going forward. To raise an issue with any of the SVG documents, including the specifications, the errata, or the test suites, simply fill out the form. Make sure to select the following fields (you can ignore Platform and OS):
This same form can also be used to make feature requests, by selecting that option from Target Milestone (and/or "enhancement" under Severity). Again, apologies for the awkward interface.
Send a message to the public mailing list (archive).
We realize that some people may not wish to fill in a form to submit issues, so of course we will still be taking email requests and discussion. We do strongly encourage using the issue tracker, however, as we think everyone will benefit from a more open process.