Page MenuHomePhabricator

Problems with autocompletion in Search bar
Closed, DuplicatePublicBUG REPORT

Assigned To
None
Authored By
Sannita
Oct 26 2022, 12:05 PM
Referenced Files
F35631302: Screen Shot 2022-10-26 at 10.33.48 AM.png
Oct 26 2022, 2:36 PM
F35630367: Screen Shot 2022-10-26 at 08.42.10.png
Oct 26 2022, 12:43 PM
F35629885: Screenshot 7.png
Oct 26 2022, 12:05 PM
F35629891: Screenshot 9.png
Oct 26 2022, 12:05 PM
F35629892: Screenshot 8.png
Oct 26 2022, 12:05 PM
F35629884: Screenshot 6.png
Oct 26 2022, 12:05 PM
F35629889: Screenshot 4.png
Oct 26 2022, 12:05 PM
F35629890: Screenshot 5.png
Oct 26 2022, 12:05 PM

Description

Steps to replicate the issue (include links if applicable):

  • Type something into Search bar on any Wikipedia

What happens?:
When the user types something in the Search bar, autocompletion suggestions are - in the user's words - incoherent, bizarre, unhelpful and non-relevant (see screenshots attached).

Screenshot 2.png (274×305 px, 26 KB)
Screenshot 1.png (288×309 px, 28 KB)
Screenshot 3.png (278×299 px, 25 KB)

It also seems that typing the full name of the article doesn't show any results, where there should be some (see screenshots attached).

Screenshot 5.png (80×299 px, 12 KB)
Screenshot 4.png (81×305 px, 13 KB)
Screenshot 6.png (83×301 px, 12 KB)

The only solution the user was able to find was to change their Wikipedia account settings to "Classic prefix search" in the "Search" section, which seems to be restoring "normal function" to searches (see screenshots attached).

Screenshot 8.png (279×301 px, 25 KB)
Screenshot 9.png (278×302 px, 26 KB)
Screenshot 7.png (282×306 px, 28 KB)

What should have happened instead?:
Relevant content should be shown when typing in the full name of the article. Possibly relevant and coherent results should be shown during autocompletion.

Software version (skip for WMF-hosted wikis like Wikipedia):

Other information (browser name/version, screenshots, etc.):
This bug report was sent through VRT system. I'm not encountering the problems the user has, I'm just reporting them. I asked them to provide me an account to be sure we can get in contact with them.

Event Timeline

I am unable to replicate this issue as described:

Screen Shot 2022-10-26 at 08.42.10.png (784×787 px, 194 KB)

Is there something I'm missing?

Aklapper changed the task status from Open to Stalled.Oct 26 2022, 1:20 PM
Aklapper edited projects, added CirrusSearch; removed MediaWiki-Search.

Wikimedia servers do not use the MediaWiki-Search codebase.

Type something into Search bar on any Wikipedia

We always need specific information about URLs and systems used (screenshots don't show an image preview, why?), otherwise nobody might be able to reproduce a problem... Please see https://www.mediawiki.org/wiki/How_to_report_a_bug

screenshots don't show an image preview, why?

If you are logged out on English Wikipedia you get the Vector Legacy skin. You can also choose it in your preferences.

When the user types something in the Search bar, autocompletion suggestions are - in the user's words - incoherent, bizarre, unhelpful and non-relevant

The examples are all single-letter queries. In general, single-letter queries aren't going to be great, because there's not really any information to go on. Other than the exact title match for the article about the letter (top result each time), you just get the most popular pages that start with that letter (or have redirects that start with that letter). That's going to be a fairly random selection.

That said, the specific results in the screenshots are not reproducible at this time. I'm fairly sure that the "u" screenshot it from English Wikipedia because it's the only wiki with an article titled "U2360° the the Rose Bowl" (thanks, global search!).

My current "u" results on English Wikipedia are a little more predictable (still a fairly arbitray collection). Screenshot from a search while not logged in:

Screen Shot 2022-10-26 at 10.33.48 AM.png (524×440 px, 44 KB)

Random additional thought: It's possible that there was a transient problem with the generation of the autocomplete data, but it is regenerated daily and it seems to be working fine today. My best explanation is that this was a problem for a day, but now it is fixed. I'll bring it up in today's meeting and see if there's any evidence of a problem in the last few days.

This looks like a repeat of T317381: Reduction in helpfulness and quantity of autocomplete search results. It even uses the same examples as the linked Village Pump discussion. This was a transient error caused by the Elasticsearch 7 update, and has been resolved for a while. If there are no fresh reports of problems, I suggest closing this ticket.