Closed Bug 729646 Opened 13 years ago Closed 13 years ago

mwc-demo : Runfield will zoom in if it is in a background tab and the phone is rotated.

Categories

(Firefox for Android Graveyard :: General, defect, P2)

13 Branch
ARM
Android
defect

Tracking

(firefox13 affected, firefox14 verified, firefox15 verified, blocking-fennec1.0 beta+)

VERIFIED FIXED
Firefox 14
Tracking Status
firefox13 --- affected
firefox14 --- verified
firefox15 --- verified
blocking-fennec1.0 --- beta+

People

(Reporter: nhirata, Assigned: kats)

References

()

Details

(Whiteboard: mwc-demo [gfx])

Attachments

(4 files)

1. go to runfield demo 2. switch to landscape 3. open a new tab to the mwc-demo front page 4. change orientations to portrait 4. switch to the runfield demo expected: runfield demo is not zoomed in actual: runfield demo is zoomed in Note: 1. occurs on : nightly 02/22/2012 on galaxy nexus, htc desire 2. occurs on : maple 02/22/2012 on galaxy nexus, htc desire 3. changing orientations after this will continue to have runfield zoomed in. 4. Runfield remains at "Loading..." on Samsung Galaxy S II on nightly; does not seem to load at all on Maple; Server not found error?
scratch point 4. I think it was something in my cache causing Runfield not to load. Galaxy S II also exhibits this issue on Nightly and Maple.
A different test case: 1. sign into hahlo.com in portrait 2. hit the home button 3. rotate the phone 4. go back to fennec 5. scroll all the way down Expected: the layers will be the same size Actual: part of the layers resized, part of it did not; see screenshot I believe that this might be the same underlying issue.
blocking-fennec1.0: --- → beta+
Kats, I bet this will be fixed with your rewrite.
Assignee: nobody → bugmail.mozilla
Priority: -- → P2
Whiteboard: mwc-demo → mwc-demo [gfx]
Seems to happen with latest maple still
Didn't want to file a new bug just for this :)
Attachment #605962 - Flags: review?(chrislord.net)
Without this we have the wrong display port set after we switch to a different tab after a rotation. The wrong display port manifests as either a temporary glitch or a more permanent paint error (which goes away on panning or other user input), but both of these are undesirable.
Attachment #605965 - Flags: review?(chrislord.net)
Comment on attachment 605962 [details] [diff] [review] (1/3) Remove some annoying logging Review of attachment 605962 [details] [diff] [review]: ----------------------------------------------------------------- Looks good to me.
Attachment #605962 - Flags: review?(chrislord.net) → review+
Comment on attachment 605964 [details] [diff] [review] (2/3) Do CSS viewport resizing on background tabs Review of attachment 605964 [details] [diff] [review]: ----------------------------------------------------------------- Looks good to me, but would like to know about the comment below. ::: mobile/android/chrome/content/browser.js @@ +2051,5 @@ > if (!browser) > return; > > + let screenW = window.outerWidth; > + let screenH = window.outerHeight; Would we not still want to use gScreenWidth/Height here? They ought to always be the same, and it's probably faster to access the former(?)
Attachment #605964 - Flags: review?(chrislord.net) → review+
Comment on attachment 605965 [details] [diff] [review] (3/3) Update display port on background tabs as well Review of attachment 605965 [details] [diff] [review]: ----------------------------------------------------------------- Looks good.
Attachment #605965 - Flags: review?(chrislord.net) → review+
(In reply to Chris Lord [:cwiiis] from comment #10) > > Would we not still want to use gScreenWidth/Height here? They ought to > always be the same, and it's probably faster to access the former(?) Yeah, I changed it back on landing. I think I put in the window.* as an intermediate change and forgot to clean it up. Landed on inbound: https://hg.mozilla.org/integration/mozilla-inbound/rev/353c5afe3b2c https://hg.mozilla.org/integration/mozilla-inbound/rev/4d51f2f3e8e8 https://hg.mozilla.org/integration/mozilla-inbound/rev/39a08a81947e
Target Milestone: --- → Firefox 14
Verified fixed on: Firefox 15.0a1 (2012-04-30) Firefox 14.0a2 (2012-04-30) Device: Samsung Captivate OS: Android 2.2
Status: RESOLVED → VERIFIED
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: