FBTrace relevance for 1.5 HEAD

[woomla]

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?),
ally.js saying $'("bStatusPrefix") is null,
chrome.panelBarReady saying getElementByClass is not defined.
etc.


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?

W.

[John J Barton]

On Nov 2, 12:47 am, woomla <woo...@gmail.com> 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

[woomla]

Yes, errors need to be fixed! Or reported if the come from Firefox.

But as a developer myself, I don't want my test team to report issues
from the HEAD of the revision. Only when I tag or branch a revision or
otherwise indicate a (pre)release build.

But I'm more then willing to do so if you like. Should I submit an
issue for every error I see (and think is relevant) or post a message?

wo

[John J Barton]

On Nov 3, 2:30 am, woomla <woo...@gmail.com> wrote:
> On 2 nov, 18:17, John J Barton <johnjbar...@johnjbarton.com> wrote:
>
> > On Nov 2, 12:47 am, woomla <woo...@gmail.com> wrote:
>
> > > 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.
>
> Yes, errors need to be fixed! Or reported if the come from Firefox.

I only see one error now,
https://bugzilla.mozilla.org/show_bug.cgi?id=499568

>
> But as a developer myself, I don't want my test team to report issues
> from the HEAD of the revision. Only when I tag or branch a revision or
> otherwise indicate a (pre)release build.
>
> But I'm more then willing to do so if you like. Should I submit an
> issue for every error I see (and think is relevant) or post a message?

I guess you are correct: report error seen on the release versions.
We'll clean up the svn errors that we see before a release.
jjb

>
> wo