3/18/2023 0 Comments Firebug net monitor![]() Taking in to consideration the above performance points (namely the fact that enabling the Console, Script, or Net panels have the potential to incur a global overhead on all browser tabs) a feature was added to help you minimize your use of the panels in errant tabs. Of course, any performance improvements to the debugger will always be helpful.įinally, the overhead of network monitoring (if there really is that much – we haven’t run performance analysis her yet) needs to be diminished in any way possible.Īll of these things are points that the new Mozilla Firebug team is trying to tackle for the upcoming Firebug 1.3 release. Specializing the debugger to only work against a single tab at a time may not be possible (based upon how Firefox works, internally) but if it is that will be an immediate benefit. A number of bugs have been filed on this subject and we hope that some of them will make their way into upcoming versions of Firefox (Firebug will be able to immediately improve when that happens). Second, the JavaScript debugger must be improved. We hope to have something introduced in an upcoming version of Firefox so that we can compensate appropriately in Firebug. This can be done but not without some internal API changes to how Firefox handles and reports error messages. This is a ubiquitous part of Firebug and any global overhead presented by it must be removed. The important question here is: What is being done to stop this?įirst, it must become necessary to not incur any overhead when using the console panel. We don’t have solid numbers on the networking monitoring overhead yet but we imagine it to be much less, although still occurring on a global all-tabs scale which isn’t desirable. Rob Campbell has run some initial numbers and has found that, simply, enabling the script panel anywhere in the browser immediately slows down all JavaScript execution by 25% – for all JavaScript on all tabs in the browser. This means that when you enable a panel, such as the script panel, it will turn on the JavaScript debugger for all JavaScript code in Firefox. Here’s the important point: The Mozilla JavaScript debugger and network monitoring are both global to Firefox not localized to a single window or tab. Network monitoring is, naturally, used for the Net panel. The Mozilla JavaScript debugger is used in two ways in Firebug: First it is used in the Script panel (to debug JavaScript code, naturally), second it is used to figure out where JavaScript errors are coming from in the console. There are two pain points, in particular: The Mozilla JavaScript debugger and network monitoring. These three panels (Console, Script, Net) have the potential to incur a great deal of overhead into any web sites that utilizes them. Some back story is needed in order to explain why the extension is now set up in this manner. When you now click Firebug for a site you’ll encounter an interface that looks something like this: It’s also a, seemingly, bizarre addition to the extension. This is the most drastic UI change of the release. We’ll be discussing the specific nature of these changes once everyone has had enough time to upgrade to Firebug 1.2.Ī list of all the bug fixes can be found in the full release notes. Specifically the Console panel has seen a number of security improvements. They’re all much more performant and have a huge number of bug fixes. The Script panel (the JavaScript debugger), the Net panel (network monitoring), and Console panel have all seen considerable updates. The most common report of Firebug problems has been related to running Firebug 1.1 in Firefox 3 – which is a mess (hence Firebug 1.2). If it’s anything other than 1.2.0bX (where X is a number 1-15) you’ll need to forcefully go to the above Firebug URLs and install the new version (the auto-update isn’t working for older versions). Go to Tools > Add-ons in Firefox and see what version of Firebug you’re running. Now is a good time to verify the version of Firebug that you’re using. If you’ve been using the Firebug 1.2 betas you’re already on top of this. Some of the major points of this release include: There have been a number of improvements made (not to mention countless bug fixes). John J Barton and Jan Odvarko put a ton of work into this release (you may have noticed the rapid-fire series of beta releases last week – just trying to smooth out the rough edges). The release should be up on the Mozilla Add-ons site today, but it’s also up on right now. The final version of Firebug 1.2 has been released.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |