Last modified: 2014-10-07 05:54:35 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 T67676, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 65676 - Need to click twice in search overlay
Need to click twice in search overlay
Status: RESOLVED FIXED
Product: MobileFrontend
Classification: Unclassified
stable (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-05-23 14:15 UTC by Juliusz Gonera
Modified: 2014-10-07 05:54 UTC (History)
8 users (show)

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


Attachments
Height of search input (2.78 KB, image/png)
2014-06-17 05:28 UTC, Florian
Details

Description Juliusz Gonera 2014-05-23 14:15:16 UTC
Search for something on enwiki in desktop Chrome, click one of the results. Search overlay closes but I stay on the same page. When I repeat the same steps second time, it works.

Can't reproduce on Android Chrome, so not sure how serious it is, but it feels alarming.
Comment 1 Bingle 2014-05-23 14:15:24 UTC
Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/v11pdWWl
Comment 2 Jon 2014-05-23 16:28:39 UTC
Yeh I think Arthur raised this issue a while ago and I occasionally see it. I can't work out why though :-/
Comment 3 Jon 2014-05-23 16:29:14 UTC
It seems to be related to tap area. I've been able to produce it on my Chrome mobile and occasionally desktop chrome but never reliably.
Comment 4 Gerrit Notification Bot 2014-05-28 18:33:39 UTC
Change 135820 had a related patch set uploaded by Jdlrobson:
Avoid bugs in Chrome with clicking links in search overlay

https://gerrit.wikimedia.org/r/135820
Comment 5 Gerrit Notification Bot 2014-05-28 18:42:45 UTC
Change 135820 merged by jenkins-bot:
Avoid bugs in Chrome with clicking links in search overlay

https://gerrit.wikimedia.org/r/135820
Comment 6 Juliusz Gonera 2014-06-12 00:27:59 UTC
This is still happening for me now and then. I also saw other people hitting it when testing on tablets.
Comment 7 Paul Henry 2014-06-12 00:39:22 UTC
This also regularly happens for me. The bug is present in both the desktop and Android versions of Chrome.
Comment 8 Ryan Kaldari 2014-06-16 22:56:06 UTC
I have not been able to reproduce this bug on desktop or mobile. Tried Chrome and Firefox on desktop and Mobile Safari on iOS.
Comment 9 Florian 2014-06-17 05:27:49 UTC
I've noticed it in Chrome on desktop sometimes, but not very often. Maybe it's only because of the input field isn't big as the header (see attachement for what i mean), so maybe sometimes i click besides :)
Comment 10 Florian 2014-06-17 05:28:17 UTC
Created attachment 15671 [details]
Height of search input
Comment 11 Ryan Kaldari 2014-06-20 23:43:30 UTC
Still not able to reproduce. Could someone provide more details about how they are producing this bug? What page are you starting your search from on en.wiki? What are you searching for? What are you clicking on? Any further details would be appreciated.
Comment 12 Maryana Pinchuk 2014-06-23 17:41:08 UTC
I've tried reproing this on a phone and tablet (iPhone 4 and iPad), in alpha, beta, and stable, in production as well as beta labs, and I don't see it. However, on desktop (Chrome), both in prod and on beta labs, I *do* see it. 

Here's what's up:

1) Visit en.m.wikipedia.org in your desktop browser
2) Click into search and type "San Francisco"
3) Click on the word "San Francisco" -- you'll be taken to the page as expected

But!

4) Click into search again and type another term, say "Barack Obama"
5) Click on the whitespace around the words Barack Obama but not on the words themselves -- nothing happens.
Comment 13 Florian 2014-06-23 17:48:05 UTC
Hmm, on desktop chrome i can reproduce this in beta and stable, not in alpha. And there aren't any infos/errors in console :/
Comment 14 Ryan Kaldari 2014-06-23 18:55:06 UTC
Still can't reproduce it :(
Comment 15 Gerrit Notification Bot 2014-06-27 22:39:52 UTC
Change 142743 had a related patch set uploaded by JGonera:
Fix double tap/click bug in search overlay

https://gerrit.wikimedia.org/r/142743
Comment 16 Gerrit Notification Bot 2014-06-27 23:34:20 UTC
Change 142743 merged by jenkins-bot:
Fix double tap/click bug in search overlay

https://gerrit.wikimedia.org/r/142743
Comment 17 Paul Henry 2014-06-28 15:30:15 UTC
1. Visit en.m.wikipedia.org in Chrome on Android or Windows. I recommend doing it in Incognito Mode to guarantee a "fresh" browser experience, but the bug is present either way.
2. Click or tap in the search area and enter "The Hound"
3. Click/tap on "The Hound of the Baskervilles"

Expected: Browser navigates to the "The Hound of the Baskervilles" page.
What actually happens: Nothing.

On desktop Chrome, if I then repeat steps 2 and 3, the correct page loads. On Android Chrome, it does not--although this technique seems to work for certain other pages on Android.

These steps have been verified just now in Chrome 35.0.1916.141 running on Android 4.4.4 KitKat on a Google Nexus 7 tablet, and in Chrome 35.0.1916.153 running on Windows 8.1.
Comment 18 Florian 2014-06-28 15:45:33 UTC
> What actually happens: Nothing.

Reproduced on Chrome mobile (not on HTC Stpck browser). But if i'm right, the merged PS of JGonera isn't deployed on Wikipedia Wikis, so we wait until the patchset is deployed and test, ok? :)
Comment 19 Gerrit Notification Bot 2014-10-06 18:04:48 UTC
Change 165029 had a related patch set uploaded by Robmoen:
Longer timeout for history update on search click

https://gerrit.wikimedia.org/r/165029
Comment 20 Gerrit Notification Bot 2014-10-07 00:33:57 UTC
Change 165029 merged by jenkins-bot:
Wait for back history before going to search page

https://gerrit.wikimedia.org/r/165029

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


Navigation
Links