Closed
Bug 981636
Opened 10 years ago
Closed 10 years ago
Double tap to zoom in does not work on tablets in landscape mode
Categories
(Firefox for Android Graveyard :: Toolbar, defect)
Tracking
(firefox29 unaffected, firefox30 verified, firefox31 verified, fennec30+)
VERIFIED
FIXED
Firefox 30
Tracking | Status | |
---|---|---|
firefox29 | --- | unaffected |
firefox30 | --- | verified |
firefox31 | --- | verified |
fennec | 30+ | --- |
People
(Reporter: cos_flaviu, Assigned: kats)
References
Details
(Keywords: regression, reproducible)
Attachments
(1 file)
2.18 KB,
patch
|
mbrubeck
:
review+
|
Details | Diff | Splinter Review |
Environment: Device: Lenovo Yoga Tab 10 (Android 4.2.2); Build: Nightly 30.0a1 (2014-03-04); Steps to reproduce: 1. Go to planet.mozilla.org; 2. Change the orientation to landscape; 3. Double tap to zoom in. Expected result: The page is successfully zoomed in. Actual result: Double tap does not work in landscape. Notes: Also reproducible on Asus Transformer Tab (Android 4.0.3); The bug might be tablet specific since is not reproducible on Google Nexus 5 (Android 4.4.2).
Updated•10 years ago
|
tracking-fennec: --- → ?
status-firefox29:
--- → ?
status-firefox30:
--- → affected
Keywords: regression
Updated•10 years ago
|
Severity: normal → major
Assignee | ||
Comment 2•10 years ago
|
||
Actually, maybe not. If that were the case I'd expect it to fail on the N5 as well. Removing depedency for now; but if this is a regression then getting a regression-window to confirm that dependency would be a good first step.
No longer blocks: 941995
Updated•10 years ago
|
Flags: needinfo?(flaviu.cos)
Keywords: regressionwindow-wanted
Reporter | ||
Comment 3•10 years ago
|
||
Last good revision: 6e3ec93efe1d (2014-02-18) First bad revision: 8122ffa9e1aa (2014-02-19) Pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=6e3ec93efe1d&tochange=8122ffa9e1aa
Flags: needinfo?(flaviu.cos)
Reporter | ||
Updated•10 years ago
|
Keywords: regressionwindow-wanted
Comment 4•10 years ago
|
||
This is not reproducible on my Asus Nexus 7 (2013, Android 4.4.2), but is reproducible on my Sony Xperia Z Tablet (Android 4.3) The above window-range does not look right in comment #3. Testing locally yields: Last good revision: a19e4c6dc2a9 First bad revision: ff2a1d3d39f2 Pushlog: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=a19e4c6dc2a9&tochange=ff2a1d3d39f2 Of which has already been mentioned here.
Blocks: 941995
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → bugmail.mozilla
Assignee | ||
Comment 6•10 years ago
|
||
I have a patch to fix this; will upload once Bugzilla attachments work again.
Status: NEW → ASSIGNED
Assignee | ||
Comment 7•10 years ago
|
||
Attachment #8388675 -
Flags: review?(mbrubeck)
Assignee | ||
Updated•10 years ago
|
Attachment #8388675 -
Flags: review?(mbrubeck)
Comment 8•10 years ago
|
||
Comment on attachment 8388675 [details] [diff] [review] Only disable double-tap if a viewport is specified Review of attachment 8388675 [details] [diff] [review]: ----------------------------------------------------------------- What does Chrome do in this case?
Attachment #8388675 -
Flags: review?(mbrubeck)
Attachment #8388675 -
Flags: review+
Assignee | ||
Comment 9•10 years ago
|
||
ni? AaronMT to check Chrome on a tablet. I don't have any tablets other than the Tab running Honeycomb and it can't run Chrome.
Flags: needinfo?(aaron.train)
Comment 10•10 years ago
|
||
In Chrome, when I double-tap the page zooms out, when I double-tap again the page restores to how it loaded: Before: http://people.mozilla.org/~atrain/mobile/tests/981636-chrome-before.png After: http://people.mozilla.org/~atrain/mobile/tests/981636-chrome-after.png
Flags: needinfo?(aaron.train)
Assignee | ||
Updated•10 years ago
|
Keywords: checkin-needed
Comment 11•10 years ago
|
||
https://hg.mozilla.org/integration/fx-team/rev/6cecd6870c69
Keywords: checkin-needed
Whiteboard: [fixed-in-fx-team]
Comment 12•10 years ago
|
||
Kats, should we just back out bug 941995? What effective change does the combo of this and bug 941995 make?
tracking-fennec: ? → 29+
Flags: needinfo?(bugmail.mozilla)
Assignee | ||
Comment 13•10 years ago
|
||
Why 29+? It only affects 30, because that's where bug 941995 landed. And no I think the patch in this bug fixes an obvious error in my previous patch; we can just let them ride the trains together - no need to back anything out.
Flags: needinfo?(blassey.bugs)
Assignee | ||
Updated•10 years ago
|
Flags: needinfo?(bugmail.mozilla)
Comment 14•10 years ago
|
||
(In reply to Kartikaya Gupta (email:kats@mozilla.com) from comment #13) > Why 29+? It only affects 30, because that's where bug 941995 landed. bug 941995 is tracking 29. If there is no intent to uplift, let's bump them both down.
Flags: needinfo?(blassey.bugs)
Assignee | ||
Comment 15•10 years ago
|
||
Yeah I'd rather not uplift either.
https://hg.mozilla.org/mozilla-central/rev/6cecd6870c69
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Whiteboard: [fixed-in-fx-team]
Target Milestone: --- → Firefox 30
Updated•10 years ago
|
tracking-fennec: 29+ → 30+
Updated•10 years ago
|
Comment 17•10 years ago
|
||
Verified as fixed in builds: - 30.0a2 (2014-03-31); - 31.0a1 (2014-03-31); Device: Asus Transformer (Android 4.2.1) and Acer Iconia (Android 3.2.1)
Status: RESOLVED → VERIFIED
Updated•10 years ago
|
status-firefox31:
--- → verified
Updated•3 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
•