Well, it it's just for me, I don't mind to continue to locally patch firebug.js once in a while.
However, I'm pretty sure I'm not the only one who liked the per-domain side of the previous activation model. "sir_brizz" and Trevan Richins brought up the same point a few weeks ago in this thread. IMHO having an option to switch from "per-url" to "per-domain" for the activation model would probably make sense - if I'm able to force a "per-domain" activation model by modifying 4 lines of code, making that an option is not likely to be too hard for someone who knows where to look at. NH johnjbarton wrote: > As you can probably tell from reading the URLSelector source, Firebug > extensions can implement alternative activation schemes. The basic > idea is to register a TabWatcher listener: > TabWatcher.addListener(Firebug.URLSelector); > then implement > shouldCreateContext(browser, url, userCommands) > where browser is the Firefox tab, url is the page URL, and > userCommands is true if the user wanted the page debugged. The first > call to shouldCreateContext that returns 'true' will cause the page to > be debugged. > > Honza has a tutorial on putting together an extension: > http://www.softwareishard.com/blog/firebug-tutorial/extending-firebug-hello-world-part-i/ > > Currently there is no simple way to attach a listener without > implementing a Firebug module. We could add this if you would use it. > > jjb > > > On May 26, 6:38 pm, Nicolas Hatier <[email protected]> wrote: > >> I think the new model makes sense, except for one thing - we need to be >> able to enable it (and keep it enabled) on a per-domain basis. >> >> Most people debug websites with Firebug. But while I debug websites, I >> (and several other people as it seems) also pages on specialized systems >> whose URL may contain a session id (webmail, for instance) >> -http://example.com/Session/jo48j7svo8467shsjeo4f76se46/webmail.html >> >> For us, it doesn't make sense for firebug to remember it is enabled on a >> per-page basis, as the page URL changes each time we open a new session >> on our system. >> >> For now, I'm able to use the latest firebug alpha by applying a small >> patch to firebug.js each time a new version is released, basically >> adding getDomain at three or four places into the URLSelector functions. >> But it would be great not having to do this, even if it's a hidden >> feature accessible only using about:config... >> >> Regards >> NH >> >> Jan Odvarko wrote: >> >>> I have written a post about the Firebug 1.4 activation model. >>> http://www.softwareishard.com/blog/firebug/how-to-enable-and-disable-... >>> >>> The post explains the logic of the current implementation. If >>> something isn't clear or doesn't work as described, please let us >>> know, or file a new bug >>> http://code.google.com/p/fbug/issues/list >>> >>> Thanks! >>> Honza >>> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
