Last modified: 2014-02-12 23:53:17 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T34146, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 32146 - MobileFrontend beta search suggestions: tapping on a blank portion of result line closes list or has no effect
MobileFrontend beta search suggestions: tapping on a blank portion of result ...
Status: RESOLVED FIXED
Product: MobileFrontend
Classification: Unclassified
stable (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Nobody - You can work on this!
http://en.m.wikipedia.org/
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-11-02 17:55 UTC by Brion Vibber
Modified: 2014-02-12 23:53 UTC (History)
9 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Brion Vibber 2011-11-02 17:55:15 UTC
If a search suggestion is short-ish -- or you're on a desktop or tablet so the screen is wide -- there may be a lot of blank space between the text of a search result and the + at the right-hand side of each result list item.

Tapping/clicking in that middle area  doesn't trigger loading the page as expected. Exact behavior seems to vary on browsers...

Steps to reproduce:
* go to http://en.m.wikipedia.org/
* type "supreme"
* tap in the white space after the "Supreme court" entry

Closes the suggestions list and passes click through to whatever lies beneath; Probably related to bug 32093 - trying to scroll triggers similar closing menus:
* Android Browser 2.3.6 / Nexus 1
* Opera Mobile 11.50 / Android 2.3.6 / Nexus 1
* Safari / iOS 5.0 / iPhone simulator

Highlights the row and closes the on-screen keyboard (if applicable):
* Firefox 8/Android
* Firefox 7.0.1/desktop
Comment 1 Patrick Reilly 2011-11-02 18:15:08 UTC
This should now be fixed in r101645.
Comment 2 Brion Vibber 2011-11-02 18:58:44 UTC
This seems to make Safari match Firefox's behavior, but still isn't quite activating the link. :)
Comment 3 Brion Vibber 2011-11-02 19:02:31 UTC
Ok we confirmed that was an issue with a file not being updated/miscached. Looks good now!

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links