I fixed a similar problem some time ago. Maybe one of these issues will help you come up with a test case: http://code.google.com/p/fbug/issues/list?can=1&q=quirks
What happens here is that Firebug is adding an element into the web page to support the 'console' object and Firebug command line. If the addition happens before Firefox establishes the page's doctype, Firefox concludes that the page (or frame in your case) is quirksmode. In normal pages Firebug injects the element on the first use of either 1) a js file compile, 2) a use of the command line. Either can occur before the load event. I guess the bug is: iframes get the console at the same time as the containing page, without regard to the state of loading the frame. If true, then to expose the bug requires: 1) force the injection on the container page early (eg script tag at the top) 2) iframe needs to exist and be in the process of requesting the page (slow server for that content, maybe lots of content in frame?) 3) iframe needs content that depends on upon doctype (so quirksmode makes a difference). jjb On Jan 20, 6:41 am, "[email protected]" <[email protected]> wrote: > Hello, i habe seen the following bug: > > when i have an iframe and i inspect it with firebug and reload the > page. the iframe content will be loaded in quirksmode. when i close > firebug and reload the page the iframe content will load in standard > compliant mode. > > i think this should be a bug in firebug? > > ill post an example later this day to reproduce this issue. > > greets timo --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
