Closed Bug 857120 Opened 11 years ago Closed 3 years ago

Display issue when changing the orientation of device in Awesomescreen

Categories

(Firefox for Android Graveyard :: General, defect)

19 Branch
ARM
Android
defect
Not set
normal

Tracking

(firefox20 wontfix, firefox21 affected, firefox22- affected, firefox23- affected, firefox24 affected, firefox25 affected, firefox26 affected, firefox27 affected, firefox28 affected, firefox29 affected, fennec-)

RESOLVED INCOMPLETE
Firefox 23
Tracking Status
firefox20 --- wontfix
firefox21 --- affected
firefox22 - affected
firefox23 - affected
firefox24 --- affected
firefox25 --- affected
firefox26 --- affected
firefox27 --- affected
firefox28 --- affected
firefox29 --- affected
fennec - ---

People

(Reporter: TeoVermesan, Unassigned)

Details

(Keywords: regression)

Attachments

(3 files)

Attached image Nightly (2013-04-02)
Firefox 22.0a1 (2013-04-02)
Device: Samsung Galaxy Nexus
OS: Android 4.1.1

Steps to reproduce:
1. Tap on the URL bar to display the Awesomescreen with the URL selected.
2. Tap on Bookmars tab.
3. Swipe left in order to navigate to History tab.
4. While performing step 3, change the orientation of the device from portrait to landscape or viceversa.

Expected result:
- The correct tab is opened without any issues.

Actual result:
- Sometimes the History tab is empty, and sometimes both contents are not aligned correctly.
Note: Please see attached screenshots.
Please find a regression range.
tracking-fennec: --- → ?
Flags: needinfo?(teodora.vermesan)
Awesome-Screen overdraw issue too :( ?
Flags: needinfo?(sriram)
Attached patch PatchSplinter Review
This adds back the windowBackground from the light theme. As long as we depend on Android's ActionBar -- which has an animation, I don't find another option to solve this.
Attachment #732456 - Flags: review?(mark.finkle)
Flags: needinfo?(sriram)
Attachment #732456 - Flags: review?(mark.finkle) → review+
Swipe between screens in AwesomeScreen  was implemented on the Nighty build from 13th of November. And I see the issue since then. So, the regression range is between 12.11.2012 and 13.11.2012. 
The pushlog is: 
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=b2bdbfe06b10&tochange=1b0226622e94
Flags: needinfo?(teodora.vermesan)
https://hg.mozilla.org/mozilla-central/rev/9dc4053ff155
Assignee: nobody → sriram
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 23
Sriram - Uplift needed?
Comment on attachment 732456 [details] [diff] [review]
Patch

[Approval Request Comment]
Bug caused by (feature/regressing bug #): Bug 844984.
User impact if declined: There will be visual glitches due to animations in AwesomeBar.
Testing completed (on m-c, etc.): Landed in m-c on 04/03
Risk to taking this patch (and alternatives if risky): None. This restores back the windowBackground that we used to have.
String or IDL/UUID changes made by this patch: None.
Attachment #732456 - Flags: approval-mozilla-aurora?
Comment on attachment 732456 [details] [diff] [review]
Patch

Are the affected flags on this bug correct? a+ for Aurora regardless.
Attachment #732456 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Version: Firefox 22 → Firefox 19
The issue is still reproducing on latest Nightly 23.0a1 (2013-04-19) on both tablet and phone. Reopening bug.

I've used the steps presented in bug in order to reproduce this issue:
1. Tap on the URL bar to display the Awesomescreen with the URL selected.
2. Tap on Bookmars tab.
3. Swipe left in order to navigate to History tab.
4. While performing step 3, change the orientation of the device from portrait to landscape or viceversa.
NOTE!: You should try a few times to reproduce this issue since there is only a small time interval between swiping and changing orientation when this issue is reproducing.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Please find a regression-range.
Flags: needinfo?(mihai.g.pop)
The patch seems to not have fixed this issue, since this is reproducible on Nightly 23.0a1 (2013-04-03) and Nightly 23.0a1 (2013-04-04) in which the patch has landed. Therefore, the regression range remains the same as presented in Comment 4
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=b2bdbfe06b10&tochange=1b0226622e94.
Flags: needinfo?(mihai.g.pop)
tracking-fennec: ? → 22+
Given the STR, this bug should not be tracking.
tracking-fennec: 22+ → -
Agreed that we shouldn't track here because STR in comment 11 makes this sound not very easily reproducible but do we want to keep this patch landed (in Aurora at least) when it doesn't seem to have done anything effective?
Sriram can you address comment 15? Should we back out the landing in comment 10 from aurora given that it seems not to work?
Flags: needinfo?(sriram)
Sriram's out for a few weeks; maybe Lucas?
Flags: needinfo?(lucasr.at.mozilla)
(In reply to lsblakk@mozilla.com from comment #16)
> Sriram can you address comment 15? Should we back out the landing in comment
> 10 from aurora given that it seems not to work?

My concern here is the possibility of causing another regression by backing it out because of changes made after this patch landed.

Maybe a safer option is back it out in Nightly first? If it doesn't cause any problems, we can then back it out in Aurora. Agree?
Flags: needinfo?(lucasr.at.mozilla)
Sriram - can you do the backout on Nightly and confirm whether a backout on Aurora will be safe as well?
Sorry - I meant to ask Lucas since Sriram is out.
Flags: needinfo?(lucasr.at.mozilla)
Flags: needinfo?(sriram)
We'll untrack since the risk of regression from a back out is greater than the user impact of this bug.
Flags: needinfo?(lucasr.at.mozilla)
Mihai -- I'm guessing this is fixed now with the new home redesign, so can you verify that's the case and mark this resolved if so? Thanks.
Flags: needinfo?(mihai.g.pop)
Attached image screenshot
Flags: needinfo?(mihai.g.pop)
The issue is reproducing in a similar way, but I was able to reproduce it so far only by changing from Reading list tab to History tab and viceversa. Please see attached screenshot.
What were your exact steps to reproduce and device used?
Assignee: sriram.mozilla → nobody
Device: Samsung Galaxy Tab (Android 4.0.4)

Steps to reproduce:
1. Open Firefox and open about:home.
2. Tap on Reading list.
3. Swipe left in order to navigate to History tab.
4. While performing step 3, change the orientation of the device from portrait to landscape or viceversa.
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: REOPENED → RESOLVED
Closed: 11 years ago3 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: