Re: Debugging SVG (and Firebug)

Hi Doug, all,

that's good news, that the Firebug team focuses
on SVG support! Thinking of it, I just have one point for immediate
improvement on my mind, but if I remember more, I'll write them back to
the list.

It's not literally a bug, but in the tab
"calculated style" the entries for "fill",
"stroke" and so on are missing (which is clear, since the
entries are composed based on the CSS and not the SVG spec). However, it
would be nice to have this information gathered (and be it only to not
have to look into the spec for the default).

Cheers,
Manuel

Doug Schepers schrieb:
> 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
>