FYI, we don't test with html5.enable true. jjb
On Jan 27, 8:11 pm, John Pisello <[email protected]> wrote: > FWIW, I found this error message occurs if you enable Firefox 3.6's > HTML5 parser (via the html5.enable option in about:config). Disabling > the option eliminated the error message. This was under FF 3.6 and FB > 1.5.0 under WinXP. > > On Jan 20, 12:06 am, John J Barton <[email protected]> > wrote: > > > On Jan 19, 6:10 pm, Alucard <[email protected]> wrote: > > > > This error still exists. > > > Well I would way "A bug with the same symptoms appeared". Other bugs > > with that symptom are fixed and their test cases no long fail. Without > > another test case there is not one thing we can do for you. > > > > FF version: 3.5.7 > > > FB version: 1.5 > > > > When I openfirebugfirst and then reload the page, a list of the same > > > errors appear in FB: > > > >Firebugcannotfind_firebugConsoleelementtrueWindow x > > >Firebugcannotfind_firebugConsoleelementtrueWindow x > > >Firebugcannotfind_firebugConsoleelementtrueWindow x > > >Firebugcannotfind_firebugConsoleelementtrueWindow x > > >Firebugcannotfind_firebugConsoleelementtrueWindow x > > > If you open a new bug report with a complete test case we can look > > into it. > > > > ... > > > > x is the window name. > > > > Yes, I know that I am using FB the wrong way, I should load the page > > > first and then load FB. > > > This is not correct information.Firebugshould be open and active > > before the page loads if you want it to be fully effective. > > > 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.
