709778 - Aggressive canvas or viewport resizing on page load

Status: RESOLVED DUPLICATE of bug 709492

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

Description

[Aaron Train [:aaronmt]]

On load of CNN.com as an example site, I see what seems to be some sort of aggressive canvas resizing which is rather annoying (why is it red?)

[1] http://www.youtube.com/watch?v=dqn5itFR61c

I dont visually see this behaviour in any other browser.

Samsung Galaxy SII (Android 2.3.6)
20111211040259
http://hg.mozilla.org/integration/mozilla-inbound/rev/f5578fdc50ef

Comment 1

[Aaron Train [:aaronmt]]

Opening about:home from preferences does the same thing too.

Comment 2

[Aaron Train [:aaronmt]]

Also see this opening the Add-ons Manager in an hourly from (12/13)

20111213113518
http://hg.mozilla.org/mozilla-central/rev/a111d03d465c

Comment 3

[Tony Chung [:tchung]]

also repro'd this when loading planet.mozilla.org.  

SGS2, 12-16-2011 nightly.

one way to reproduce is to keep tapping the canvas area as the page is still loading.  screen tries to resize like a madman, and eventually it turned red.

Comment 4

[Aaron Train [:aaronmt]]

Still reproducible, still annoying

Comment 5

[Patrick Walton (:pcwalton)]

Is this a dupe of bug 709492 or is it something else?

Comment 6

[Kartikaya Gupta (email:[e-mail])]

It's different. In fact, it's a dupe of bug 711232, and should be fixed. It's red because it's scaling the 1x1 pixel in the top-left corner to the entire viewport.

Comment 7

[Kartikaya Gupta (email:[e-mail])]

It occurs to me that my previous patch will not help much with the very first tab loaded, because gScreenWidth and gScreenHeight will be zero or one. The patch on bug 710297 should improve this further, but initializing gScreenWidth and gScreenHeight to screen-size should also take care of this. The problem is we don't have the screen size at that point, and so maybe a better solution is to not do a draw at all until we have the screen size in browser.js.

Comment 8

[Mark Finkle (:mfinkle) (use needinfo?)]

Bug 711232 is fixed, but this really seems like a dupe of bug 709492. If this bug is not actually fixed, I assume this a dupe of bug 709492 and marking as such.