> In firebug 1.0.5, the firebug panel div's name is "panelNode panelNode- > HelloWorld"; in firebug 1.2.0, it changes to "panelNode panelNode- > HelloWorld contextUID=39873". My extension needs to get this div and > appends my html source code. Notice that there is set of helper functions that you can use to find an element by class (lib.js: getChildByClass, getAncestorByClass, getElementByClass). These methods look within the class attribute for the specific class-name so, even if there is more classes specified it works well. All these methods use hasClass method, which does the search within the class attribute.
> FBTrace is really well, I like it :) So, the good news is that the FBTrace console is core part of Firebug 1.3. > I use class name to get this div, it's not strong enough. > I wonder that is there any other good methods to get the firebug panel > and append my html source code ? The best way how to get access to the panel's DOM node (the node that represents panel's content) is probably to use "panelNode" member variable of the specific panel. This member is initialized within Firebug.Panel method. Honza On Sep 2, 6:51 am, 马良 <[EMAIL PROTECTED]> wrote: > Hi, > I studied your article about FBTrace Console and tried to debug my > extension. > I got the reason. > > In firebug 1.0.5, the firebug panel div's name is "panelNode panelNode- > HelloWorld"; in firebug 1.2.0, it changes to "panelNode panelNode- > HelloWorld contextUID=39873". My extension needs to get this div and > appends my html source code. > > FBTrace is really well, I like it :) > > I use class name to get this div, it's not strong enough. > I wonder that is there any other good methods to get the firebug panel > and append my html source code ? > > On Sep 2, 1:43 am, Jan Odvarko <[EMAIL PROTECTED]> wrote: > > > Hm, it's not enough info to find out the problem... > > > 1) Try to download a version 1.2X with tracing > > from:http://getfirebug.com/releases/firebug. (this version dump logs into > > the system console) > > 2) Run Firefox from the command line (or with -console parameter) so, > > you can see the console. > > 3) Activate FBTrace tab and press ERRORS. > > 4) Watch the console for error messages > > 5) Make sure browser.dom.window.dump.enabled is true > > > You can also check the Firefox Tools->Error Console > > > If you find more put it here. > > > Honza > > > On Sep 1, 5:23 pm, 马良 <[EMAIL PROTECTED]> wrote: > > > > I have developed a firebug extension. It works well on Firefox 2 + > > > Firebug 1.0.5. > > > I updated Firefox 2 to 3 and Firebug 1.0.5 to 1.2.0. After that, I > > > can't open my extension panel. > > > I get an error in error console, here is the error message. > > > > Error: uncaught exception: [Exception... "Component returned failure > > > code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIChannel.open]" > > > nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS > > > frame :: chrome://firebug/content/lib.js :: anonymous :: line 2552" > > > data: no] > > > > What does this mean? > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
