Closed
Bug 1229925
Opened 8 years ago
Closed 8 years ago
Consider switching to android.support.v7.preference
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: mcomella, Unassigned)
References
Details
SetHomepagePreference extends DialogFragment, but it should be the v7 DialogFragment, not the built in. Investigate whether this is worthwhile and what the effects are. This may be necessary after bug 1205124 lands. Note that preferences and AppCompat are apparently really funky business.
Reporter | ||
Comment 1•8 years ago
|
||
Don't forget to add it to the builds [1] (like bug 1171288)! [1]: http://developer.android.com/tools/support-library/features.html#v7-preference
Reporter | ||
Comment 2•8 years ago
|
||
Andrzej, you have the context here – do we need to do anything with this?
Flags: needinfo?(ahunt)
Comment 3•8 years ago
|
||
(In reply to Michael Comella (:mcomella) from comment #2) > Andrzej, you have the context here – do we need to do anything with this? I don't think we need to do anything immediately, using AppCompatActivity around Preferences doesn't seem to result in any issues. Switching to the v7 DialogFragment would probably result in us using the support library dialog as opposed to the native dialog when setting a custom homepage. Since we're producing native (non-support library dialogs) in the rest of preferences, we probably wouldn't want to do that, unless we can switch all of preferences to use support library dialogs. (IIRC the PreferenceFragment that we use elsewhere spawns native Android dialogs - it looks like we might be able to upgrade to PreferenceFragmentCompat instead?)
Flags: needinfo?(ahunt)
Reporter | ||
Comment 4•8 years ago
|
||
Okay, I'm going to close this and we can reopen or file a new bug if we decide to do any of the options in comment 3.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
Assignee | ||
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•