|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
|
|
FBTrace relevance for 1.5 HEADWhile 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. -- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to firebug@.... To unsubscribe from this group, send email to firebug+unsubscribe@.... For more options, visit this group at http://groups.google.com/group/firebug?hl=en. |
|
|
Re: FBTrace relevance for 1.5 HEADOn Nov 2, 12:47 am, woomla <woo...@...> 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 firebug@.... To unsubscribe from this group, send email to firebug+unsubscribe@.... For more options, visit this group at http://groups.google.com/group/firebug?hl=en. |
|
|
Re: FBTrace relevance for 1.5 HEADOn 2 nov, 18:17, John J Barton <johnjbar...@...> wrote: > On Nov 2, 12:47 am, woomla <woo...@...> 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. 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 -- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to firebug@.... To unsubscribe from this group, send email to firebug+unsubscribe@.... For more options, visit this group at http://groups.google.com/group/firebug?hl=en. |
|
|
Re: FBTrace relevance for 1.5 HEADOn Nov 3, 2:30 am, woomla <woo...@...> wrote: > On 2 nov, 18:17, John J Barton <johnjbar...@...> wrote: > > > On Nov 2, 12:47 am, woomla <woo...@...> 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 -- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to firebug@.... To unsubscribe from this group, send email to firebug+unsubscribe@.... For more options, visit this group at http://groups.google.com/group/firebug?hl=en. |
| Free embeddable forum powered by Nabble | Forum Help |