On Jul 20, 9:57 am, "Iplnts *" <[email protected]> wrote:
> Hi!
>
> I installed this new version on 17.th July 2009.
> I very much like this high-minded tool and welcome every new.
>
> Meanwhile experimenting with it on Mozilla/5.0 (Windows; U; Windows NT
> 5.1; en-GB; rv:1.9.0.11) Gecko/2009060215 Firefox/3.0.11 - Build ID:
> 2009060215
>
> today I noticed something strange had happened.
> When my test page was loaded the firebug window opened automatically,
> (is it otherwise right behavior, if it was previously left allowed On
> this page?) and when I hovered over my mouse on the main active window
> the whole body was deleted from my page.
Sounds like issue 1894
http://code.google.com/p/fbug/issues/detail?id=1894
>
> I'm just developing a new firefox extension, (testing it by the help
> of Firebug 1.4.0 and earlier with its 1.3.3 version which does not
> produced such an error), so I use them altogether for a long time.
>
> I observed the Firebug writes some own codes into a document when it
> have been opened on a site or page
> such ones
>
> <div id="-firebugConsole"...
> some
> <style> elements with many firebug rules #FirebugBody.......
> and several times many empty <style></style> elements. (I don't guess
> those whether why for)
The first one supports the Console panel; the second one supports
inspect.
>
> It is not disturbing until one can not save the document. My extension
> is an editor enhancement tool and such one its main function to save
> the document after editing it. Thus those firebug codes will remain in
> the page as much times they had been written into it, when saving it.
> Thus, I logically wished to delete them before saving. I wrote some
> codes into my extension
> which will delete those firebug written codes before saving.
>
> Taking not so much circumstance with the document.Stylesheets[] and
> cssRule[] collections because those codes do not worked well,
> unfortunately..
>
> so here my simple code to delete them
>
> /* purge the Firebug written code into the file
> before saving */
> while (doc.getElementById("_firebugConsole")){
> doc.getElementById("_firebugConsole").parentNode.removeChild
> (doc.getElementById("_firebugConsole"))
> }
> var StyleColl = doc.getElementsByTagName("style");
>
> deleteStyles =[];
> for (i=0; i<StyleColl.length; i++){
> if (StyleColl[i].innerHTML=="" ||
> StyleColl[i].innerHTML.indexOf
> ("firebug")) deleteStyles.push(StyleColl[i]);
> }
> for(i in deleteStyles){
>
> deleteStyles[i].parentNode.removeChild(deleteStyles[i])
> }
>
> It purged really the written codes from the file, but the firebug
> would had been opened when my extension executed those commands (to
> see them in live working)
>
> However there is something very interesting had been written into the
> page after the page </body> element what I had never seen until.
>
> here is the code:
> </body><body id="firebugBody" contenteditable="false"><div
> style="left: 566px; top: 87px;" class="firebugLayoutBox
> firebugLayoutBoxOffset"><div style="padding: 0px;"
> class="firebugLayoutBox firebugLayoutBoxMargin"><div style="padding:
> 0px;" class="firebugLayoutBox firebugLayoutBoxBorder"><div
> style="padding: 0px;" class="firebugLayoutBox
> firebugLayoutBoxPadding"><div style="width: 32px; height: 32px;"
> class="firebugLayoutBox firebugLayoutBoxContent"></div></div></div></
> div></div></body>
>
> As per my consideration it does not cause the whole body element
> removing under mouse over
> event - and also my above written code could only run when the save
> routine was called,
> So I really don't know what is happening.
That is part of the inspect functionality.
>
> ??????
>
> I suggest to reproduce the error, experimenting with on an empty page.
> Open the Firebug console, it will write its codes into it (sometimes
> yes, sometimes I noticed not, I also does not understand why.) into
> the document. Write a short javascript test as written above to purge
> it. And listen what happens.
>
> May be it would be a good suggestion to delete those codes when the
> firebug console is off or at least somehow to check those be written
> once more.
Just turn Firebug off and reload the page.
We plan to remove all of this stuff in Firebug 1.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
-~----------~----~----~----~------~----~------~--~---
