Closed
Bug 1220315
Opened 9 years ago
Closed 9 years ago
Set a homepage preference has the wrong theme on Lollipop+
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(firefox44 verified, firefox45 verified, firefox46 verified, b2g-v2.5 fixed, fennec44+)
RESOLVED
FIXED
Firefox 45
People
(Reporter: mcomella, Assigned: mcomella)
References
Details
Attachments
(4 files, 1 obsolete file)
95.15 KB,
image/png
|
Details | |
100.40 KB,
image/png
|
Details | |
40 bytes,
text/x-review-board-request
|
sebastian
:
review+
ritu
:
approval-mozilla-aurora+
|
Details |
2.18 KB,
patch
|
ritu
:
approval-mozilla-beta+
|
Details | Diff | Splinter Review |
accentColor is not used.
Unclear if this is related to theme-appcompat changes.
Comment 1•9 years ago
|
||
so. many. regressions.
Assignee | ||
Comment 2•9 years ago
|
||
Set homepage is set behind a Nightly flag – blocking that bug and not prioritizing it for now.
Assignee | ||
Comment 3•9 years ago
|
||
GeckoPreferences uses the system theme so this is only a problem on Lollipop+ where accentColor is used.
Summary: Set a homepage preference has the wrong theme → Set a homepage preference has the wrong theme on Lollipop+
Assignee | ||
Comment 4•9 years ago
|
||
It looks like we don't extend `android.support.v7.preference.DialogPreference` because the v7 prefs library is not included in our builds. However, DialogPreference is pretty explicit to say we should extend AppCompatActivity, which GeckoPreferences does not (bug 1205124). But then again, we don't do this for GeckoApp yet either (bug 1220309).
Let's try it out!
An alternative quick fix: set the style of the dialog separately using built-in styles, not AppCompat.
Assignee | ||
Comment 5•9 years ago
|
||
We uplifted this and may want to uplift this fix, in which case, perhaps the quick fix is more appropriate.
Assignee | ||
Comment 6•9 years ago
|
||
Motivation for my approach with the upcoming patch:
11:57 <sebastian> mcomella: Did you try just duplicating accentColor? Having it with and without prefix?
11:58 <mcomella> sebastian: Yeah – I started to look into where the style comes from... There's no theme set when creating the dialog, so it uses the default styles http://androidxref.com/4.4.4_r1/xref/frameworks/base/core/java/android/preference/DialogPreference.java#281
11:58 <mcomella> sebastian: But there's this: http://androidxref.com/4.4.4_r1/xref/frameworks/base/core/java/android/preference/DialogPreference.java#281
11:58 <mcomella> sebastian: Which we never declare ever, afaict
11:58 <mcomella> sebastian: So I'm trying that out
Assignee | ||
Comment 7•9 years ago
|
||
Assignee | ||
Comment 8•9 years ago
|
||
Bug 1220315 - Use alertDialogTheme on v21+ to add accentColor. r=sebastian
Attachment #8694946 -
Flags: review?(s.kaspari)
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → michael.l.comella
Comment 9•9 years ago
|
||
Comment on attachment 8694946 [details]
MozReview Request: Bug 1220315 - Use alertDialogTheme on v21+ to add accentColor. r=sebastian
https://reviewboard.mozilla.org/r/26941/#review24609
Attachment #8694946 -
Flags: review?(s.kaspari) → review+
Assignee | ||
Comment 10•9 years ago
|
||
https://hg.mozilla.org/integration/fx-team/rev/c17fc2bbaaff6784b836eb03caeee7d81356f5cd
Bug 1220315 - Use alertDialogTheme on v21+ to add accentColor. r=sebastian
Assignee | ||
Comment 11•9 years ago
|
||
I also found that the Site Settings dialog's theme (which also uses an AlertDialog) is incorrect before this patch (i.e. has some default colors) and is fixed after this patch.
Assignee | ||
Comment 12•9 years ago
|
||
Comment on attachment 8694946 [details]
MozReview Request: Bug 1220315 - Use alertDialogTheme on v21+ to add accentColor. r=sebastian
Approval Request Comment
[Feature/regressing bug #]: bug 1227322
[User impact if declined]: Users will see the homepage preference dialog with the wrong theme, which basically is the rest of preferences has our Firefox orange accent color but this dialog has a green accent color.
[Describe test coverage new/current, TreeHerder]: Tested locally.
[Risks and why]: Low – we started using a previously unused attribute, alertDialogTheme, and set it to get the dialog to appear as expected. Things look correct in this dialog (and the site settings dialog) but it's not guaranteed we didn't change the style of another alert dialog. We only set the attribute on API 21+ devices, so the potential negative effects are limited.
[String/UUID change made/needed]: None
Attachment #8694946 -
Flags: approval-mozilla-aurora?
Comment 13•9 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 45
Comment on attachment 8694946 [details]
MozReview Request: Bug 1220315 - Use alertDialogTheme on v21+ to add accentColor. r=sebastian
This has been in Nightly for a few days, seems safe to uplift to Aurora44.
Attachment #8694946 -
Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Comment 15•9 years ago
|
||
has problems uplifting to aurora:
grafting 318523:c17fc2bbaaff "Bug 1220315 - Use alertDialogTheme on v21+ to add accentColor. r=sebastian"
merging mobile/android/base/resources/values-v21/themes.xml
warning: conflicts while merging mobile/android/base/resources/values-v21/themes.xml! (edit, then use 'hg resolve --mark')
abort: unresolved conflicts, can't continue
(use hg resolve and hg graft --continue)
Flags: needinfo?(michael.l.comella)
Assignee | ||
Comment 16•9 years ago
|
||
I didn't have time to compile this but this should be the fix.
Flags: needinfo?(michael.l.comella)
Updated•9 years ago
|
Attachment #8697661 -
Attachment is patch: true
Flags: needinfo?(cbook)
Comment 18•9 years ago
|
||
seems there are still conflicts adding 1220315 to series file
renamed 1220315 -> file_1220315.txt
applying file_1220315.txt
patching file mobile/android/base/resources/values-v21/themes.xml
Hunk #1 FAILED at 10
1 out of 1 hunks FAILED -- saving rejects to file mobile/android/base/resources/values-v21/themes.xml.rej
patch failed, unable to continue (try -v)
Flags: needinfo?(michael.l.comella)
Assignee | ||
Comment 19•9 years ago
|
||
Looks like my exported patch had ^M EOL characters, causing the patch to not apply properly – I'm not sure why that is.
Attachment #8697661 -
Attachment is obsolete: true
Flags: needinfo?(michael.l.comella) → needinfo?(cbook)
Assignee | ||
Comment 21•9 years ago
|
||
Comment on attachment 8698117 [details] [diff] [review]
44 (beta) branch patch
Missed merge so let's get this into 44.
Approval Request Comment – see comment 12
Attachment #8698117 -
Flags: approval-mozilla-beta?
Assignee | ||
Updated•9 years ago
|
Attachment #8698117 -
Attachment description: 44 (aurora) branch patch → 44 (beta) branch patch
Comment 22•9 years ago
|
||
Verified as fixed using:
Device: Nexus 5 (Android 5.1)
Builds: Firefox for Android 45.0a2 and 46.0a1 (2015-12-22)
status-firefox46:
--- → verified
Comment on attachment 8698117 [details] [diff] [review]
44 (beta) branch patch
Fix was verified, Beta44+
Attachment #8698117 -
Flags: approval-mozilla-beta? → approval-mozilla-beta+
Comment 24•9 years ago
|
||
bugherder uplift |
Comment 25•9 years ago
|
||
bugherder uplift |
status-b2g-v2.5:
--- → fixed
Comment 27•9 years ago
|
||
Verified as fixed in Firefox 44 Beta 8;
Device: Asus ZenPad 8 (Android 5.0.2).
Updated•4 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
•