Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Troubleshooting addons efficiently

  • Gjin antwurden
  • 0 hawwe dit probleem
more options

This morning, my browser was having problems accessing the pages I use at work.

I restarted in Troubleshooting mode, and the problems went away, great.

Now I want to figure out which addon / extension caused the problem.

The "best" way I've found online is to enable half of them and restart in regular mode, if the problem is gone, then enable half of the remainder, see if the problem is gone, etc. until the problem comes back. This involves a lot of restarting and keeping track of which ones have been tested.

What I'd really like is a way to do all this from troubleshooting mode, enabling one addon at a time and testing a certain website until it breaks or I run out of addons, like Git Bisect or similar. Maybe sort the addons in reverse chronological order of addition or update, since the most recently added/updated addons are the most likely to be the problem.

This is one of those times where the feature has to be part of the browser, not an addon. :-)

Is this already implemented and I just haven't looked hard enough or recognized what I was seeing?

Thanks

This morning, my browser was having problems accessing the pages I use at work. I restarted in Troubleshooting mode, and the problems went away, great. Now I want to figure out which addon / extension caused the problem. The "best" way I've found online is to enable half of them and restart in regular mode, if the problem is gone, then enable half of the remainder, see if the problem is gone, etc. until the problem comes back. This involves a lot of restarting and keeping track of which ones have been tested. What I'd really like is a way to do all this from troubleshooting mode, enabling one addon at a time and testing a certain website until it breaks or I run out of addons, like Git Bisect or similar. Maybe sort the addons in reverse chronological order of addition or update, since the most recently added/updated addons are the most likely to be the problem. This is one of those times where the feature has to be part of the browser, not an addon. :-) Is this already implemented and I just haven't looked hard enough or recognized what I was seeing? Thanks

Jo moatte jo oanmelde by jo account om op berjochten te antwurdzjen. Stel in nije fraach as jo noch gjin account hawwe.