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)
Tracking
(firefox13 affected, firefox14 verified, firefox15 verified, blocking-fennec1.0 beta+)
VERIFIED
FIXED
Firefox 14
People
(Reporter: nhirata, Assigned: kats)
References
()
Details
(Whiteboard: mwc-demo [gfx])
Attachments
(4 files)
213.32 KB,
image/png
|
Details | |
1.29 KB,
patch
|
cwiiis
:
review+
|
Details | Diff | Splinter Review |
3.33 KB,
patch
|
cwiiis
:
review+
|
Details | Diff | Splinter Review |
7.01 KB,
patch
|
cwiiis
:
review+
|
Details | Diff | Splinter Review |
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?
Reporter | ||
Comment 1•13 years ago
|
||
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.
Updated•13 years ago
|
Keywords: fennecnative-betablocker
Reporter | ||
Comment 2•13 years ago
|
||
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.
Updated•13 years ago
|
blocking-fennec1.0: --- → beta+
Comment 3•13 years ago
|
||
Kats, I bet this will be fixed with your rewrite.
Assignee | ||
Updated•13 years ago
|
Assignee: nobody → bugmail.mozilla
Updated•13 years ago
|
Priority: -- → P2
Updated•13 years ago
|
Whiteboard: mwc-demo → mwc-demo [gfx]
Comment 4•13 years ago
|
||
Seems to happen with latest maple still
Assignee | ||
Comment 6•13 years ago
|
||
Didn't want to file a new bug just for this :)
Attachment #605962 -
Flags: review?(chrislord.net)
Assignee | ||
Comment 7•13 years ago
|
||
Attachment #605964 -
Flags: review?(chrislord.net)
Assignee | ||
Comment 8•13 years ago
|
||
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 9•13 years ago
|
||
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 10•13 years ago
|
||
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 11•13 years ago
|
||
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+
Assignee | ||
Comment 12•13 years ago
|
||
(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
Comment 13•13 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/353c5afe3b2c
https://hg.mozilla.org/mozilla-central/rev/4d51f2f3e8e8
https://hg.mozilla.org/mozilla-central/rev/39a08a81947e
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•13 years ago
|
status-firefox13:
--- → affected
status-firefox14:
--- → fixed
Updated•13 years ago
|
Comment 14•13 years ago
|
||
Verified fixed on:
Firefox 15.0a1 (2012-04-30)
Firefox 14.0a2 (2012-04-30)
Device: Samsung Captivate
OS: Android 2.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
•