Thanks, for your quick response! On Jul 20, 7:50 pm, johnjbarton <[email protected]> wrote: > On Jul 20, 9:57 am, "Iplnts *" <[email protected]> wrote: > > > Hi! > >> ... when I hovered over my mouse on the main active window > > the whole body was deleted from my page. > > Sounds like issue 1894http://code.google.com/p/fbug/issues/detail?id=1894 > > I will read over this issue with more perusal. I guessed at first read it > may refer to something would be wrong at when running a javascipt
> > <div id="-firebugConsole"... > > some > > <style> elements with many firebug rules #FirebugBody....... > > The first one supports the Console panel; the second one supports > inspect. Thank you. The inspect functionality is big I like it. (as the more ones also :) > > > and several times many empty <style></style> elements. (I don't guess > > those whether why for) ??? > > > 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. > > > 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. This resolution not problem for me, - I understand, - and at the moment I could throw an alert for the user who will probably use my extension to turn off firebug before saving! However it is not the more elegant solution because even if one noticed he/she also may commit to leave the firebug on unfortunately, when saving an edited document, (as I also committed), and one will be surprised too (as I was) when the whole edited document will vanish. So forth, the problem would be a general user who probably may use my extension also with your ones to experiment with each other. I strongly will suggest yours also using with mine because of firebug really a must use enhancement in web development and editing. By the way, could you suggest me whether which firebug command could programatically turn off the firebug console? I can use it then called from my extension immediately before running its save functionality. Thus the user may observe the firebug somehow has been turned off, but it is the better case than probably left turned on and unfortunately may happen the delete. Surely, I can hunt out by the Chrome explorer which code in firebug can turn off the consol, but you would save my time if you could aid me until the below release which I also welcome! > > We plan to remove all of this stuff in Firebug 1.6. Thank you answering me! iplnts > > 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 -~----------~----~----~----~------~----~------~--~---
