Debugging SVG (and Firebug)

Hey, SVG heroes-

At my recent presentation on SVG at the WWW 2010 conference, I was 
approached by someone from the Firebug team.  Firebug is a kick-ass 
debugging extension for Firefox which lets you dig into the DOM, script, 
and CSS, and even lets you walk the code with breakpoints; there are 
similar tools for other browsers, and they are a healthy part of any Web 
developer's breakfast.

The question put to me was, what low-hanging fruit can the Firebug team 
pluck to make SVG developing better?  I know I've run into quirks once 
in while, but failed to catalog them.

Have you run into any problems debugging SVG in Firebug (or any other 
browser-based debugging tool)?  This is a great opportunity to get these 
fixed (or at least examined).

I followed up with him via email, and here was his reply:

[[
Short term: what fails when Firebug works on SVG?
http://code.google.com/p/fbug/issues/list

Mid: when a new experimental feature is added, does Firebug work? If
not let's talk.

Long term: typically difficult-to-debug SVG issues. This is harder
since most devs think the bug is simple...once they have found it!
]]

Thoughts?

Regards-
-Doug Schepers
W3C Team Contact, SVG and WebApps WGs

Received on Sunday, 2 May 2010 17:50:10 UTC