Last modified: 2010-05-15 16:03:52 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 14399 - mwsuggest.js: Case-insensitive search
mwsuggest.js: Case-insensitive search
Product: MediaWiki
Classification: Unclassified
Search (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2008-06-03 21:21 UTC by Dan Barrett
Modified: 2010-05-15 16:03 UTC (History)
0 users

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


Description Dan Barrett 2008-06-03 21:21:48 UTC
Please provide a $wg... configuration setting, or a user preference, to make the AJAX autosuggest feature case-insensitive.

Right now it is case-sensitive, which can mislead users into believing there is no match for a title, when in fact, they have just typed it in lowercase and there is an uppercase match.

Search is case-insensitive.  Therefore, auto-suggest should be case-insensitive too, at least optionally.

Comment 1 Brion Vibber 2008-06-03 21:23:23 UTC
This is provided by TitleKey extension and ties into general exact- and prefix/suggestion match searches ('go' search, opensearch suggest, ajax search, mwsuggest).
Comment 2 Dan Barrett 2008-07-24 18:14:48 UTC
Sorry, TitleKey does not solve this problem; I just verified on MW 1.13 release candidate 1.

Case Study:

0. Install MediaWiki 1.13 release candidate 1 with no other extensions.
1. Create a wiki article called "McGee"
2. Install TitleKey from svn, run "php rebuildTitleKeys.php"
3. In LocalSettings.php, add:

$wgEnableMWSuggest = true;

Verify on Special:Version that the extension is installed.

4. Watch what happens when we type various things:

You type:          Autosuggest contains "McGee"?
Mcg                yes
mcg                NO
mcge               yes
mc                 NO
Mc                 NO
MC                 yes ?!?

In each of the "NO" cases, there are other autosuggest results, but McGee is not present among them.

5. Now disable TitleKey and repeat the previous tests. The results are exactly the same. TitleKey seems to be having no effect whatsoever on the results.

Every single "NO" result will mislead users that "McGee" doesn't exist. It's better to have no autosuggest at all, rather than a wrong autosuggest list.
Comment 3 Brion Vibber 2008-07-30 22:27:19 UTC
Works fine on my local installation and on Wikipedia.
Comment 4 Dan Barrett 2008-07-31 00:25:32 UTC
Could the difference be related to the choice of Lucene vs. mySQL-full-text search?

Also I'm running on Windows 2003 Server, if that could be responsible for the different behavior.

Speaking of extension behavior, Brion, could you please describe -- either here or at -- the exact, user-visible effect of TitleKey?  All the wiki page says is, "case-insensitive title prefix search" but does not describe the effect beyond that.  What should it do when it interacts with autosuggest, etc?
Comment 5 Dan Barrett 2008-07-31 00:40:04 UTC
I think I understand what's happening here...

Autosuggest displays only a *subset* of matches, perhaps the first 10 or so.  That means if McGee isn't in the first 10, it's not being displayed.

Not the behavior I expected, and it can be misleading (i.e., I was certainly misled).  But with millions of articles on Wikipedia, I see why limiting the number of suggestions makes sense.

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