Open Bug 867371 Opened 8 years ago Updated 2 years ago
[Meta] Settings UI Changes
No description provided.
This bug tracks Fennec settings UI changes. This includes reorganizing the settings hierarchy, adding/changing preferences to be controlled, and using full preference screens throughout (instead of dialogs).
Rough outline of settings hierarchy: https://etherpad.mozilla.org/settings-reorg
Future: make sure to remove the comment in GeckoPreferences.java that refers to this bug!
Even though the settings UI has several areas that are still unimplemented, I think the right approach will be to reorder at a higher level and then start inserting features as they get finished, because most of the subcategories have at least a two items. One thing to consider is whether we want to have any "Basic" preferences that are top-level (such as Sync and import) so users can see them without having to dig through any menus.
Hi Teodora, can you try this build on your device, to see if the problem still exists in this build? It will install as a Nightly app, not an Aurora one. http://people.mozilla.com/~liuche/bug-871978/no-switch-nightly.apk Alternatively, can QA check that this fixes the bug on an Android device of the same version as the reporters? This should be any device between v11 and v13, inclusive.
(Sorry, wrong bug!)
We use the relnote flag for things that are fixed already or are known issues that need to be noted, not for a meta bug on a feature that hasn't been implemented yet. Please renom when this is within a targeted release (ideally fixed on trunk).
(In reply to Lukas Blakk [:lsblakk] from comment #7) > We use the relnote flag for things that are fixed already or are known > issues that need to be noted, not for a meta bug on a feature that hasn't > been implemented yet. Please renom when this is within a targeted release > (ideally fixed on trunk). If memory serves I nomed this bug to capture the group of changes that went in to Firefox 25 or 26. At any rate, no need to keep this nom as it's mighty old.
You need to log in before you can comment on or make changes to this bug.