Closed
Bug 1093621
Opened 10 years ago
Closed 10 years ago
Enable new tablet UI by default on Nightly/Aurora
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
Firefox 36
People
(Reporter: lucasr, Assigned: lucasr)
References
Details
Attachments
(1 file)
2.30 KB,
patch
|
mcomella
:
review+
|
Details | Diff | Splinter Review |
The UI structure is in place now. Time to get wider feedback.
Assignee | ||
Comment 1•10 years ago
|
||
Assignee | ||
Comment 2•10 years ago
|
||
Comment on attachment 8516728 [details] [diff] [review]
Enable new tablet UI by default in Nightly (r=mcomella)
Here we go.
Attachment #8516728 -
Flags: review?(michael.l.comella)
Comment on attachment 8516728 [details] [diff] [review]
Enable new tablet UI by default in Nightly (r=mcomella)
Review of attachment 8516728 [details] [diff] [review]:
-----------------------------------------------------------------
::: mobile/android/base/NewTabletUI.java
@@ +11,5 @@
> import org.mozilla.gecko.preferences.GeckoPreferences;
> import org.mozilla.gecko.util.HardwareUtils;
>
> public class NewTabletUI {
> // This value should be in sync with preferences_display.xml.
Add to this comment to mention how "being in sync" makes sense despite the fact that this is not "true", i.e. what you told me IRL about how the preference is removed in release builds.
Attachment #8516728 -
Flags: review?(michael.l.comella) → review+
Status: NEW → ASSIGNED
Assignee | ||
Comment 4•10 years ago
|
||
Comment 5•10 years ago
|
||
This may have caused a regression:
Regression: Fx-Team - Robocop Checkerboarding Real User Benchmark - Android 4.0.4 - 65.9% increase
--------------------------------------------------------------------------------------------------
Previous: avg 17.092 stddev 1.432 of 12 runs up to revision fb567390cb92
New : avg 28.347 stddev 0.242 of 12 runs since revision 3b36af7151ec
Change : +11.255 (65.9% / z=7.862)
Graph : http://mzl.la/1sfsKk0
Changeset range: http://hg.mozilla.org/integration/fx-team/pushloghtml?fromchange=fb567390cb92&tochange=3b36af7151ec
Assignee | ||
Comment 6•10 years ago
|
||
Backed out due to talos regressions:
https://hg.mozilla.org/integration/fx-team/rev/e7488d6c9af8
Comment 7•10 years ago
|
||
Merge of backout:
https://hg.mozilla.org/mozilla-central/rev/e7488d6c9af8
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 36
Assignee | ||
Comment 10•10 years ago
|
||
Patches from bug 1093621 fix the talos regression. Let's try this again:
https://hg.mozilla.org/integration/fx-team/rev/7ef4eeeace2e
Comment 11•10 years ago
|
||
(In reply to Lucas Rocha (:lucasr) from comment #10)
> Patches from bug 1093621 fix the talos regression.
Wrong bug nr.
Assignee | ||
Comment 12•10 years ago
|
||
I meant bug 1091519.
Assignee | ||
Comment 13•10 years ago
|
||
Backed out again, talos regressions still there.
https://hg.mozilla.org/integration/fx-team/rev/fc30354927a2
Comment 14•10 years ago
|
||
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
Comment 15•10 years ago
|
||
dammit
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Target Milestone: Firefox 36 → ---
Assignee | ||
Comment 16•10 years ago
|
||
Quick update: I narrowed down the cause of the regression. It seems the affected talos test doesn't like the fact that we change the toolbar height in the new tablet UI:
http://dxr.mozilla.org/mozilla-central/source/mobile/android/base/toolbar/ActionBarViewFlipper.java#32
Working on a patch now.
Assignee | ||
Comment 17•10 years ago
|
||
Patch is bug 1097316 works around the regression. I'll continue investigating the real cause of the regression in bug 1097318.
https://hg.mozilla.org/integration/fx-team/rev/b8490f38c4da
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 36
Comment 19•10 years ago
|
||
Forgot to remove the toast notification I think, see above bug.
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
•