How did you decide it was in quirks mode? We have a bug report about the problem: http://code.google.com/p/fbug/issues/detail?id=1190 but no clue. (This problem also happens in 1.2 but much less common).
But quirks mode is a great hint: maybe the console injection is interfering with doctype detection? jjb On Oct 5, 11:12 am, jjathman <[EMAIL PROTECTED]> wrote: > It looks like 1.3a3 seems to be putting my site in to quirks mode > incorrectly. When I revert to 1.3a2 the site looks normal again. I'm > not really sure how to help debug this, but I can give as more > information if someone tells me what to look for. The site is only > internal so I can't give a link to it, sorry. > > Joe > > On Oct 2, 4:59 pm, John J Barton <[EMAIL PROTECTED]> wrote: > > > getfirebug.com/releases should offer Firebug 1.3a3 shortly. This > > version has more changes than earlier alphas: > > 1) 1.3X traceConsole added, FBTrace panel removed. Tracing now need > > not go to the OS console window but rather is presented in the new > > Firebug Trace Console using Firebug technology for display. > > 2) Re-write of Firebug console implementation. Attempt to address > > intermittent "console undefined" messages. Many console bugs fixed. > > 3) Array presentation bugs fixed. > > 4) Added scope chain to Watches panel when stopped in debugger > > 4) different algorithm for routing debugger info. > > So its possible that a3 will be a bit rougher that a2. > > > We plan to start 1.3 beta on Monday Oct. 6. > > > 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 -~----------~----~----~----~------~----~------~--~---
