Hi there, Could we add the blocking flag "WebExtensions" to more components? It's already available on Product=toolkit Component=WebExtensions: untriaged Ideally we could use a wildcard to make available to toolkit | WebExtensions* (since sometimes we need to add other sub categories). Otherwise the exact components that need it are under Product=Toolkit, Component= WebExtensions: Android WebExtensions: Compatibility WebExtensions: Developer Tools WebExtensions: Experiments WebExtensions: Frontend WebExtensions: General WebExtensions: Request Handling WebExtensions: Untriaged already has it beyond setting the "?" that anyone can do - Rights to set the flag to +,-,+next should go to anyone in Firefox-backlog-drivers and the following people (if they aren't already in firefox-backlog-drivers) Bob Silverberg bSilverberg@mozilla.com Matthew Wein mwein@mozilla.com Andy McKay andym@mozilla.com Luca Greco Lgreco@mozilla.com Shane Caraveo scaraveo@mozilla.com Kris Maglione kmaglione@mozilla.com Kev Needham kneedham@mozilla.com Krupa Raj kraj@mozilla.com Jorge Villalobos jorge@mozilla.com Andrew Swan awan@mozilla.com Chris Grebs cgrebs@mozilla.com Stuart Colville scolville@mozilla.com Andrew Williamson awilliamson@mozilla.com Mathieu Pillard mpillard@mozilla.com Kumar McMillan kMcMillan@mozilla.com Shell Escalante sescalante@mozilla.com

(In reply to :shell escalante from comment #0) > Hi there, > > Could we add the blocking flag "WebExtensions" to more components? It's > already available on Product=toolkit Component=WebExtensions: untriaged > > Ideally we could use a wildcard to make available to toolkit | > WebExtensions* (since sometimes we need to add other sub categories). > > Otherwise the exact components that need it are under Product=Toolkit, > Component= > WebExtensions: Android > WebExtensions: Compatibility > WebExtensions: Developer Tools > WebExtensions: Experiments > WebExtensions: Frontend > WebExtensions: General > WebExtensions: Request Handling > > WebExtensions: Untriaged already has it Done > beyond setting the "?" that anyone can do - Rights to set the flag to > +,-,+next should go to anyone in Firefox-backlog-drivers and the following > people (if they aren't already in firefox-backlog-drivers) Done > Bob Silverberg bSilverberg@mozilla.com Needs a BMO account > Matthew Wein mwein@mozilla.com > Andy McKay andym@mozilla.com > Luca Greco Lgreco@mozilla.com > Shane Caraveo scaraveo@mozilla.com > Kris Maglione kmaglione@mozilla.com > Kev Needham kneedham@mozilla.com > Krupa Raj kraj@mozilla.com > Jorge Villalobos jorge@mozilla.com > Andrew Swan awan@mozilla.com > Chris Grebs cgrebs@mozilla.com > Stuart Colville scolville@mozilla.com > Andrew Williamson awilliamson@mozilla.com > Mathieu Pillard mpillard@mozilla.com > Kumar McMillan kMcMillan@mozilla.com > Shell Escalante sescalante@mozilla.com Rest is done. dkl

> > Bob Silverberg bSilverberg@mozilla.com > > Needs a BMO account Thanks for this and it's actually bob.silverberg@gmail.com.

I can't find this flag on https://bugzilla.mozilla.org/show_bug.cgi?id=1288902, am I looking in the wrong place? https://www.dropbox.com/s/r2ac4st30hcs0c0/Screenshot%202016-12-15%2016.46.01.png?dl=0

Hi dkl, Sorry but we can't see the blocking flag option under any area other than Toolkit :: webextensions:untriaged (where it was originally) If we can't see the blocking flag option on those other areas - should we put it as a "tracking flag" instead?

(In reply to :shell escalante from comment #4) > Hi dkl, > > Sorry but we can't see the blocking flag option under any area other than > Toolkit :: webextensions:untriaged (where it was originally) > > If we can't see the blocking flag option on those other areas - should we > put it as a "tracking flag" instead? Ah. Sorry for the confusion. There is also a blocking-webextensions bug flag that is not a tracking flag (similar to the review/feedback/checkin) flags and that is the one that I edited. Confusing I know. I have now made the changes to the right flag and you should see them properly. dkl