krutohelper.blogg.se

> + const reloadButton = targetElement.querySelector(". ::: devtools/client/aboutdebugging/test/browser_addons_reload.js:30 > + yield waitForInitialAddonList(document) > - AddonManager.getAllAddons(addons => = yield openAboutDebugging("addons") ::: devtools/client/aboutdebugging/components/addons-tab.js:85 using listAddons and the actors (addons-tab.js modification + actors/addon.js (only isRestartless and iconURL) + I imagine some tests fixesīut again, just a bonus, your patch isn't terribly complex/big. devtools/ r? again me once comments are addressedīonus point if you also split the /devtools/ part in two: I have a bunch of simplications here and there but it looks good overall!

"Stopped": the service worker is installed and activated, but has been terminated after being idle.MozReview Request: Bug 1246030 - Allow reloading an add-on in about:debugging.

It would be great if you could load a temporary add-on into your current running Firefox from web-ext. 0 steps in Chrome - they are loaded automatically. Menu > Addons > Cogwheel > Debug Addons > Click on 'Enable Addon Debugging' > Load Temporary Add-On > Navigate to addon folder > Open 'manifest.json'. However, we have a button for this same work flow in Firefox. I'm browser Addons/Extensions developer, and every time i open Firefox i need to manually add Addons i develop. It's installed and activated, and is currently handling events. The install/run command landed in 90 and by default this creates a temporary profile, opens Firefox, and loads an extension.

"Running": the service worker is currently running.

That is, it subsumes the "installing", "activating", and "waiting" states.

"Registering": this covers all states between the service worker's initial registration, and its assuming control of pages.

You can connect the developer tools to each worker, and send push notifications to service workers.įrom Firefox 52, the list of service workers shows the state of the service worker in its lifecycle.

Other workers, including Chrome Workers and Dedicated Workers.

The Workers page shows your workers, categorised as follows: See bug 1212802 for the latest on this work.

Note that this feature isn't that immediately useful to debugging desktop tabs - you can open up a toolbox to debug a tab easily enough already - but this will become far more useful when about:debugging starts to support remote debugging, and this page can begin to list tabs available for debugging on mobile device browsers, simulators, etc.