On Nov 2, 12:47 am, woomla <[email protected]> wrote:
> While I'm at it, how relevant are all FBTrace error messages?
>
> I get some errors from browser.xul,
> some errors saying that certain css rules are dropped (isn't this just
> a warning?),
The ERRORS flag in FBTrace reports all traffic through the error
handler.
> ally.js saying $'("bStatusPrefix") is null,
> chrome.panelBarReady saying getElementByClass is not defined.
> etc.
These are all bugs that need to be fixed.
>
> It looks like there are a lot of chrome errors displayed (show chrome
> errors is not checked!).
> Other errors are more relevant I think.
>
> I'm always using the HEAD revision of FB 1.5 of FF 3.5.4 on Windows XP
> SP3.
>
> I know it is a development snapshot and I'm quite comfortable with
> that, just wonder if I should ignore it or what?
That is exactly why all of the errors need to be fixed.
Some of the errors are from Firefox.
jjb
--
You received this message because you are subscribed to the Google Groups
"Firebug" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/firebug?hl=en.
