Closed
Bug 559829
Opened 14 years ago
Closed 14 years ago
Click on an entry in search suggestions drop-down activates a link underneath (the list is click-transparent)
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: Aleksej, Assigned: mfinkle)
References
()
Details
(Whiteboard: [MobFx1.1Betatestday])
Attachments
(1 file, 1 obsolete file)
5.17 KB,
patch
|
mfinkle
:
review+
|
Details | Diff | Splinter Review |
Fennec, branch 1.9.2, i686, on Debian GNU/Linux. Version=1.1a2pre BuildID=20100416015257 Steps to reproduce: 1. Go to http://www.google.com/search?newwindow=1&q=sleep&lr=&aq=f&aqi=g9g-s1&aql=&oq=&gs_rfai= 2. Click the search field and type a space (to get "sleep " and a search suggestions drop-down). 3. Click a suggestion displayed over a link, so that if there were no suggestions you would hit the link instead. Actual results: The link on the page is clicked. Expected results: The suggestion entry is used. If you miss the link area underneath the drop-down, this is what happens.
Comment 1•14 years ago
|
||
I have a patch for that which need just a few polish.
Comment 2•14 years ago
|
||
This patch move the check to know if the element is click-able or not under the call to nodesFromRect. This way we're able to look if the container of the element is click-able through the nsIEventListenerService.
Assignee: nobody → 21
Attachment #439587 -
Flags: review?(mark.finkle)
Assignee | ||
Comment 3•14 years ago
|
||
Comment on attachment 439587 [details] [diff] [review] Patch This looks like it could be a time consuming block of code.
Comment 4•14 years ago
|
||
(In reply to comment #3) > (From update of attachment 439587 [details] [diff] [review]) > This looks like it could be a time consuming block of code. + + // If possible looks in the parents node to find a target + if (aElementsInRect) { + let count = aElementsInRect.length; + for (let i = 0; i < count; i++) { + if (aElement.parentNode == aElementsInRect[i]) { + let isParentClickable = this._isElementClickable(aElement.parentNode, aElementsInRect); + if (isParentClickable) + return true; + } + } + } Right. I can probably refactor the code to be less time consuming.
Comment 5•14 years ago
|
||
Same things but without recursion and with a shorter path. Because the result of nodesFromRect is ordered we can also optimize to update the parentNode once we have a hit between odesFromRect[i] == parentNode
Attachment #439587 -
Attachment is obsolete: true
Attachment #439930 -
Flags: review?(mark.finkle)
Attachment #439587 -
Flags: review?(mark.finkle)
Assignee | ||
Comment 6•14 years ago
|
||
Initial tests on my N900 show this patch working sometimes, but failing other times. Fail == clicks a button or link under the suggestion list. I'll make sure my mozilla-192 tree is up to date
Assignee | ||
Comment 7•14 years ago
|
||
(In reply to comment #6) > Initial tests on my N900 show this patch working sometimes, but failing other > times. Fail == clicks a button or link under the suggestion list. > > I'll make sure my mozilla-192 tree is up to date I updated and rebuilt my mozilla-192 tree. There was a problem with my previous builds. My current build is working much better. I'll keep testing for now.
Assignee | ||
Comment 8•14 years ago
|
||
Comment on attachment 439930 [details] [diff] [review] Patch v0.2 Works very well
Attachment #439930 -
Flags: review?(mark.finkle) → review+
Assignee | ||
Comment 9•14 years ago
|
||
pushed m-b: http://hg.mozilla.org/mobile-browser/rev/1c14e68a8418 pushed m-1.1: http://hg.mozilla.org/releases/mobile-1.1/rev/829466780f23
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 10•14 years ago
|
||
verified FIXED on builds: Mozilla/5.0 (X11; U; Linux armv7l; Nokia N900; en-US; rv:1.9.2.5pre) Gecko/20100506 Namoroka/3.6.5pre Fennec/1.1b2pre and Mozilla/5.0 (X11; U; Linux armv71; Nokia N900; en-US; rv:1.9.3a5pre) Gecko/20100506 Namoroka/3.7a5pre Fennec/2.0a1pre This would be a nice addition to our FFTs under the autocomplete group
Status: RESOLVED → VERIFIED
Flags: in-litmus?
Reporter | ||
Comment 11•14 years ago
|
||
Verified with the 20100506 builds for i686, too.
Comment 12•14 years ago
|
||
I'm reassigning this to myself for adding litmus testcases for this (aakashd discussed this on irc with blassey and ted on #mobile).
Assignee: 21 → martijn.martijn
Updated•14 years ago
|
Assignee: martijn.martijn → mark.finkle
Flags: in-litmus? → in-litmus?(martijn.martijn)
Comment 13•13 years ago
|
||
https://litmus.mozilla.org/show_test.cgi?id=15193
Flags: in-litmus?(martijn.martijn) → in-litmus+
You need to log in
before you can comment on or make changes to this bug.
Description
•