1073701 - Need a way to "untheme"/"unpref" developer edition to get back "vanilla" aurora

Status: RESOLVED DUPLICATE of bug 1086936

(DevTools :: General, defect)

Description

[cmtalbert]

For this dev edition, it would be fundamental to have a way to untheme and unpref the browser to get it back to the "vanilla" edition of aurora. The use case is as follows:
* We see a bug in the dev edition of aurora (particularly now in the run up to this thing)
* We want to make certain this bug is not brought on by the pref/theme changes, so we hit this button that reverts the changes, potentially restart the browser if necessary and we repro the bug.

This will give us a nice ability to separate concerns from these changes versus other bugs that are found during hte aurora testing process. This will result in better bug reporting, which is extremely important as we are in a compressed cycle to get this thing out the door.

Comment 1

[Axel Hecht [:Pike]]

This is important also for the l10n aspect of the current aurora channel, and the value of that testing for release.

This is probably also important when we migrate existing users, and might very well call for a UX for existing users to potentially opt-in to the new dev worlds.

We shouldn't risk to alienate and loose existing users, when we want to get new ones.

Comment 2

[Brian Grinstead [:bgrins]]

There is a button in the customize mode UI for turning off the theme (bug 1082108).  The plan for the other changes is to have a set of prefs that are on by default for the Developer Edition channel (it would be possible to get back to vanilla aurora by flipping these).

Would it be OK to have a list of prefs to toggle, or would you prefer there is something in the UI?  An alternative could be to have a single pref that has a listener that sets all of these relevant prefs on/off when it changes.

Comment 3

[Joe Walker [:jwalker]]

One part of this is the bug Brian noted, bug 1082108, and the other is bug 1086936 which I'm duping this to.

There are prefs that are changed by Developer Edition (e.g. turning off self-xss protection), and we'll have those clearly documented. I don't have a plan for how to mass undo them, I suspect that mostly having them in a single UI switch would create a bigger problem than it solved.