Closed
Bug 966258
Opened 11 years ago
Closed 11 years ago
quickmobile.ro loads zoomed in and can not be zoomed out
Categories
(Firefox for Android Graveyard :: Toolbar, defect)
Tracking
(firefox26 unaffected, firefox27 unaffected, firefox28 verified, firefox29 verified)
VERIFIED
FIXED
Firefox 29
Tracking | Status | |
---|---|---|
firefox26 | --- | unaffected |
firefox27 | --- | unaffected |
firefox28 | --- | verified |
firefox29 | --- | verified |
People
(Reporter: cos_flaviu, Unassigned)
References
Details
Attachments
(1 file)
756.29 KB,
image/png
|
Details |
Environment:
Device: Google Nexus 5 (Android 4.4.2);
Build: Nightly 29.0a1 (2014-01-31);
Steps to reproduce:
1. Go to quickmobile.ro
2. Check if the page is correctly loaded.
Expected result:
The site loads successfully and panning and zooming works as expected.
Actual result:
The page loads zoomed in and can not be zoomed out or pan around.
Notes:
The bug is not reproducible on FF26, FF27 or Chrome.
Check the attached screen shot.
Reporter | ||
Updated•11 years ago
|
status-firefox26:
--- → unaffected
status-firefox27:
--- → unaffected
status-firefox28:
--- → affected
status-firefox29:
--- → affected
Comment 1•11 years ago
|
||
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=7e79536aca0a&tochange=73eefb421e2a
Looks like bug 962791 again.
Blocks: 962791
Comment 2•11 years ago
|
||
Similar behavior on http://www.reddit.com/r/naut
Comment 3•11 years ago
|
||
Looking at the layer dumps on these two pages shows that both examples as well as the example in bug 966282 have the same problem: a scrollable element gets a scroll info layer rather than a scrollable layer even after a displayport is set.
Comment 4•11 years ago
|
||
Should be fixed per the backout of the blocking bug here.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Target Milestone: --- → Firefox 29
Comment 5•11 years ago
|
||
Verified with Today's trunk/aurora.
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
•