Closed
Bug 1043022
Opened 10 years ago
Closed 10 years ago
Clicking on links in the browser doesn't seem to work
Categories
(Core :: DOM: Events, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox32 | --- | unaffected |
firefox33 | --- | fixed |
firefox34 | --- | fixed |
b2g-v2.1 | --- | verified |
b2g-v2.2 | --- | verified |
People
(Reporter: kats, Assigned: kats)
References
Details
(Keywords: regression)
Attachments
(2 files)
5.25 KB,
text/plain
|
Details | |
6.49 KB,
patch
|
Sylvestre
:
approval-mozilla-aurora+
|
Details | Diff | Splinter Review |
STR: 1. On a master B2G build (Flame) load a page like https://bugzilla.mozilla.org/show_bug.cgi?id=989403 2. Zoom in and scroll down to the attachments section 3. Click on the attachment for the "standalone test case" Expected: - The link activates and the browser navigates Actual: - The link might flash active for a split second but quickly goes inactive again. It doesn't navigate to the page though. If I long-press on the link it does give me the context menu and I can successfully open the link in a new tab. This might be a platform bug but filing it in browser for now because that's the only place I'm seeing it. I haven't looked into it yet but I can do that tomorrow if nobody else gets to it first.
Assignee | ||
Comment 2•10 years ago
|
||
Regression from 1016481.
Assignee: nobody → bugmail.mozilla
Blocks: 1016481
Component: Gaia::Browser → DOM: Events
Keywords: qawanted → regression
OS: Mac OS X → Gonk (Firefox OS)
Product: Firefox OS → Core
Hardware: x86 → All
Version: unspecified → 33 Branch
Assignee | ||
Updated•10 years ago
|
status-firefox32:
--- → unaffected
status-firefox33:
--- → affected
status-firefox34:
--- → affected
Assignee | ||
Comment 3•10 years ago
|
||
Basically the problem is that on a page that allows double-tap, the notification at http://mxr.mozilla.org/mozilla-central/source/dom/ipc/TabChild.cpp?rev=c452b1384965#1913 happens before the SetSingleTapOccurred() call at http://mxr.mozilla.org/mozilla-central/source/gfx/layers/apz/src/AsyncPanZoomController.cpp?rev=9bc64b0290c2#1432 and so mTouchIsClick ends up having a value of IsNotClick.
Assignee | ||
Comment 4•10 years ago
|
||
This screams out for automated testing.
Assignee | ||
Comment 6•10 years ago
|
||
Last I checked we don't have any test frameworks that can simulate actual user input from the hardware side. Not on B2G anyway.
Comment 8•10 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #7) > [Blocking Requested - why for this release]: Functional regression with basic functionality of browser content.
Assignee | ||
Comment 9•10 years ago
|
||
I backed out bug 1016481 to fix this, since I couldn't immediately think of a good fix. https://hg.mozilla.org/integration/mozilla-inbound/rev/bf3d32fac6b3
Assignee | ||
Comment 10•10 years ago
|
||
Approval Request Comment [Feature/regressing bug #]: bug 1016481 (landed recently on 33) [User impact if declined]: often clicking links in the B2G browser doesn't work [Describe test coverage new/current, TBPL]: this is a backout of bug 1016481, so it restores the old tested behavior [Risks and why]: low-risk, it was a recent landing. backout was clean. [String/UUID change made/needed]: none
Attachment #8461461 -
Flags: approval-mozilla-aurora?
(In reply to Kartikaya Gupta (email:kats@mozilla.com) from comment #9) > I backed out bug 1016481 to fix this, since I couldn't immediately think of > a good fix. > > https://hg.mozilla.org/integration/mozilla-inbound/rev/bf3d32fac6b3 https://hg.mozilla.org/mozilla-central/rev/bf3d32fac6b3
Assignee | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla34
Updated•10 years ago
|
Attachment #8461461 -
Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Comment 12•10 years ago
|
||
https://hg.mozilla.org/releases/mozilla-aurora/rev/13739ffbc777
status-b2g-v2.1:
--- → fixed
Comment 13•10 years ago
|
||
Switching the 2.1?->2.1+, on these fixed bugs as these are regression. Nothing to land here, its just flag-cleanup of 2.1? list. Please Ni me if there is confusion/disagreement.
blocking-b2g: 2.1? → 2.1+
Comment 14•10 years ago
|
||
Issue verified as fixed on Flame 2.1 and Flame 2.2 Device: Flame 2.1 KK (319mb) (Full Flash) BuildID: 20141011000201 Gaia: f5d4ff60ffed8961f7d0380ada9d0facfdfd56b1 Gecko: d813d79d3eae Gonk: 52c909e821d107d414f851e267dedcd7aae2cebf Version: 34.0a2 (2.1) Firmware: V180 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Device: Flame 2.2 Master KK (319mb) (Full Flash) BuildID: 20141011040204 Gaia: 95f580a1522ffd0f09302372b78200dab9b6f322 Gecko: 3f6a51950eb5 Gonk: 52c909e821d107d414f851e267dedcd7aae2cebf Version: 35.0a1 (2.2 Master) Firmware: V180 User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0 User clicking on browser links opens new page. Tested URL from Comment 0 as well as multiple other urls. Double-checked current master to ensure verification
Status: RESOLVED → VERIFIED
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.2:
--- → verified
Flags: needinfo?(ktucker)
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
You need to log in
before you can comment on or make changes to this bug.
Description
•