The main goal of this button is to mitigate any legacy settings or extensions that may be slowing Firefox down. If the button disables extensions, it should exclude web extensions. TODO: in the future we could monitor reports of slow web extensions and offer to disable those, but this would need to be a data-driven list.
Anything changed since bug 1017919? Can this be done in the proposed schedule given what's said on the bug 1017919?
(In reply to Tim Guan-tin Chien [:timdream] (please needinfo) from comment #1) > Anything changed since bug 1017919? Can this be done in the proposed > schedule given what's said on the bug 1017919? Well, I haven't seen any detailed specs regarding what this button would do, where it would go, what it would affect, etc. Given that, it is not in scope and with reduced availability for most of the team I'm not sure who would work on it. Which schedule/release did you have in mind?
I was referring to Photon schedule in general. It's already being communicated can't reach 55. Just like everything with Photon I would like to help product mgmt figure out feasibility sooner than later. Having an open bug left for the "Reset Firefox" feature look like this is something we'll have to pay special attention to. Thanks.
We would also need to worry about bug 1276998 BTW...
We are not going to implement this for shipping bug 1329342.
Pending research results--> ongoing discussion on research team's resource availability
confirmed with UX, not valid anymore