W3C home > Mailing lists > Public > public-svg-ig@w3.org > April to June 2010

Re: Debugging SVG (and Firebug)

From: Doug Schepers <schepers@w3.org>
Date: Mon, 03 May 2010 09:47:37 -0400
Message-ID: <4BDED3F9.3040908@w3.org>
To: David Storey <dstorey@opera.com>
CC: SVG IG List <public-svg-ig@w3.org>
Hi, David-

David Storey wrote (on 5/3/10 8:38 AM):
> As the product manager of the rival Opera Dragonfly, I can't comment too
> much on issues with Firebug. It would be fantastic to see improved
> support in Firebug and other tools however. We on the DFL team have
> looked into SVG support however. We haven't fleshed out everything that
> we'd want to add for SVG debugging yet, but we have some ideas. DFL
> doesn't work too badly for SVG at the moment, but there could certainly
> be some improvements. The box model view in the layout panel, which is
> great for CSS doesn't make so much sense for SVG, as there is no box
> model. Other metrics such as the bounding box perhaps make more sense to
> show there instead.The element highlight could probably be improved in
> the same way: see
> http://my.opera.com/MacDev_ed/blog/getting-screen-boundingboxes-in-svg
> for example.

Yes, I mentioned Firebug explicitly because one of their dev team 
approached me about it, but as I mentioned, it would be great to collect 
bugs, feature requests, and use-cases for all of the browser-based 
debuggers regarding SVG support.

Perhaps we should make a wiki page, identifying all the different 
debuggers and how each of them could improve their SVG support (and what 
they get right!).

Regards-
-Doug Schepers
W3C Team Contact, SVG and WebApps WGs
Received on Monday, 3 May 2010 13:47:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 3 May 2010 13:47:39 GMT