Closed
Bug 651534
Opened 14 years ago
Closed 11 years ago
permaorange: browser_click_content.js | Test timed out
Categories
(Firefox for Android Graveyard :: General, defect)
Firefox for Android Graveyard
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: philor, Unassigned)
References
Details
(Whiteboard: [test disabled on Android])
Attachments
(1 file, 1 obsolete file)
2.71 KB,
patch
|
mfinkle
:
review+
|
Details | Diff | Splinter Review |
TEST-PASS | chrome://mochitests/content/browser/mobile/chrome/browser_click_content.js | URL Matches newly created Tab
TEST-INFO | chrome://mochitests/content/browser/mobile/chrome/browser_click_content.js | Console message: [JavaScript Error: "uncaught exception: waitFor timeout"]
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/mobile/chrome/browser_click_content.js | Test timed out
Reporter | ||
Comment 1•14 years ago
|
||
Not actually Android-specific, n900s do the same thing.
OS: Android → All
Hardware: ARM → All
Comment 2•14 years ago
|
||
I haven't ever seen this happen on desktop, but it seems likely to me its just a timing issue.
Attachment #527684 -
Flags: review?(mark.finkle)
Comment 3•14 years ago
|
||
Comment on attachment 527684 [details] [diff] [review]
Potential Fix
>- element.addEventListener("click", clickFired, true);
>+ element.addEventListener("click", function(aEvent) {
You should remove the event handler here using the arguments.callee trick
>+ clickFired(aEvent);
>+ checkClick();
>+ }, true);
>
> EventUtils.synthesizeMouseForContent(element, 1, 1, {}, window);
>- waitFor(checkClick, function() { return isClickFired });
> }
>
> function checkClick() {
> ok(isClickFired, "Click handler fired");
> element.removeEventListener("click", clickFired, true);
This one ^
>- element.addEventListener("click", clickFired, true);
>+ element.addEventListener("click", function(aEvent) {
Same thing
>+ clickFired(aEvent);
>+ checkPosition();
>+ }, true);
>
> let rect = getBoundingContentRect(element);
> EventUtils.synthesizeMouse(element, 1, rect.height + 10, {}, window);
>- waitFor(checkPosition, function() { return isClickFired });
> }
>
> function checkPosition() {
> element.removeEventListener("click", clickFired, true);
This one ^
Can we also remove isClickFired ?
r- but close, and make sure this doesn't break on desktop
Attachment #527684 -
Flags: review?(mark.finkle) → review-
Comment 4•14 years ago
|
||
Updated to notes. Also removed the isClickFired checks.
Assignee: nobody → wjohnston
Attachment #527684 -
Attachment is obsolete: true
Status: NEW → ASSIGNED
Attachment #527807 -
Flags: review?(mark.finkle)
Updated•14 years ago
|
Attachment #527807 -
Attachment is patch: true
Attachment #527807 -
Attachment mime type: application/octet-stream → text/plain
Updated•14 years ago
|
Attachment #527807 -
Flags: review?(mark.finkle) → review+
Comment 5•14 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 6•14 years ago
|
||
Still failing every time.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Reporter | ||
Comment 7•14 years ago
|
||
Not sure whether this is significant, but the n900 failures come with a screenshot in the log, which shows that iframe-1, the one where we're firing a click at 1,1, is almost completely out of view, so we're firing a click at something offscreen.
Reporter | ||
Comment 8•14 years ago
|
||
Disabled on Android in http://hg.mozilla.org/mozilla-central/rev/d0583d604249
Whiteboard: [test disabled on Android]
Updated•12 years ago
|
Assignee: wjohnston → nobody
Reporter | ||
Updated•11 years ago
|
Status: REOPENED → RESOLVED
Closed: 14 years ago → 11 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•