1. Regarding issue 3305 [1], using Firefox 4.0b7pre (nightly build
[2]) and Firebug 1.7X.0a3, I'm still unable to get any kind of script
debugging. :-(
I've tried HTML pages and SVG documents, both in remote servers and
using a locally hosted site. I've also tried light and heavy weight
pages (in terms of JS code included), again with no luck: I always get
either the "No Javascript on this page" or "Script Panel was inactive
during page load" messages.
2. As a related note, the displayed warning (for the "No Javascript on
this page" message) is:
If <script> tags have a "type" attribute it should equal "text/
javascript" or "application/javascript"
This is fine when for HTML but, for SVG, the script types should be
"text/ecmascript" or "application/ecmascript" [3] (I guess "text/
ecmascript" was deprecated, just as "text/javascript", but I'm sure it
will also be around for a while). Does that mean that debugging for
SVG won't be supported in this version? If not, then I'd suggest
reworking the warning in some way (maybe simply adding "text/
ecmascript" or "application/ecmascript" to the list).
> 1. Regarding issue 3305 [1], using Firefox 4.0b7pre (nightly build
> [2]) and Firebug 1.7X.0a3, I'm still unable to get any kind of script
> debugging. :-(
> I've tried HTML pages and SVG documents, both in remote servers and
> using a locally hosted site. I've also tried light and heavy weight
> pages (in terms of JS code included), again with no luck: I always get
> either the "No Javascript on this page" or "Script Panel was inactive
> during page load" messages.
> 2. As a related note, the displayed warning (for the "No Javascript on
> this page" message) is:
> If <script> tags have a "type" attribute it should equal "text/
> javascript" or "application/javascript"
> This is fine when for HTML but, for SVG, the script types should be
> "text/ecmascript" or "application/ecmascript" [3] (I guess "text/
> ecmascript" was deprecated, just as "text/javascript", but I'm sure it
> will also be around for a while). Does that mean that debugging for
> SVG won't be supported in this version? If not, then I'd suggest
> reworking the warning in some way (maybe simply adding "text/
> ecmascript" or "application/ecmascript" to the list).
> > 1. Regarding issue 3305 [1], using Firefox 4.0b7pre (nightly build
> > [2]) and Firebug 1.7X.0a3, I'm still unable to get any kind of script
> > debugging. :-(
> > I've tried HTML pages and SVG documents, both in remote servers and
> > using a locally hosted site. I've also tried light and heavy weight
> > pages (in terms of JS code included), again with no luck: I always get
> > either the "No Javascript on this page" or "Script Panel was inactive
> > during page load" messages.
Thanks for the info, Honza. In fact, I guess I had read something
about that in the Firebug blog or release notes. ;-)
> > 2. As a related note, the displayed warning (for the "No Javascript on
> > this page" message) is:
> > If <script> tags have a "type" attribute it should equal "text/
> > javascript" or "application/javascript"
> > This is fine when for HTML but, for SVG, the script types should be
> > "text/ecmascript" or "application/ecmascript" [3] (I guess "text/
> > ecmascript" was deprecated, just as "text/javascript", but I'm sure it
> > will also be around for a while). Does that mean that debugging for
> > SVG won't be supported in this version? If not, then I'd suggest
> > reworking the warning in some way (maybe simply adding "text/
> > ecmascript" or "application/ecmascript" to the list).
This idea is still valid. Should I file a bug to avoid this getting
lost?
Another issue I'm experiencing (although not exclusively related with
this release) is dual-faced: Firefox and Firebug. The Firefox one is
that, since the removal of the status bar, using nightly builds I'm
unable to display it (i.e., I can't find any menu option or preference
for that). The related Firebug issue is that, at least in Firebug
1.5.x, few options are apparently only accessible from the status bar
icon (such as "On for all pages" or "Clear activation list"). Am I
missing something (are those parameters no longer configurable?) or
the Firebug menu (of Firefox options) needs a few more items?
> Another issue I'm experiencing (although not exclusively related with
> this release) is dual-faced: Firefox and Firebug. The Firefox one is
> that, since the removal of the status bar, using nightly builds I'm
> unable to display it (i.e., I can't find any menu option or preference
> for that). The related Firebug issue is that, at least in Firebug
> 1.5.x, few options are apparently only accessible from the status bar
> icon (such as "On for all pages" or "Clear activation list"). Am I
> missing something (are those parameters no longer configurable?) or
> the Firebug menu (of Firefox options) needs a few more items?
> Another issue I'm experiencing (although not exclusively related with
> this release) is dual-faced: Firefox and Firebug. The Firefox one is
> that, since the removal of the status bar, using nightly builds I'm
> unable to display it (i.e., I can't find any menu option or preference
> for that).
