Last modified: 2012-09-07 15:24:53 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 T30740, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 28740 - Category suggestion is case sensitive
Category suggestion is case sensitive
Status: RESOLVED DUPLICATE of bug 40076
Product: MediaWiki extensions
Classification: Unclassified
UploadWizard (Other open bugs)
unspecified
All All
: Normal normal with 1 vote (vote)
: ---
Assigned To: Jeroen De Dauw
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-04-28 19:20 UTC by Neil Kandalgaonkar
Modified: 2012-09-07 15:24 UTC (History)
6 users (show)

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


Attachments

Description Neil Kandalgaonkar 2011-04-28 19:20:52 UTC
From the feedback...

> When I upload a picture of The Bronx and start typing a category of "the bro..." the selector offers "The bronze..." but not "The Bronx..." presumably because I didn't capitalize the place name. Other programs with autocompletion don't mind whether we use caps or not and this one also should offer both upper and lower case completions.  [[User:Jim.henderson|Jim.henderson]]


There does not seem to be any option for the builtin 'query' API to treat the query as case-insensitive.

The Commons search box uses the OpenSearch API (from Extension:OpenSearch) which seems to be case insensitive by default. It is possible to limit an opensearch query to a particular namespace, so this could be used with the category suggest. The result format is slightly different though.
Comment 1 Brion Vibber 2011-04-29 18:17:46 UTC
Using the opensearch interface is probably the right thing to do; it'll also pick up improvements on the search like not being limited to strict prefix matches in an advanced search engine.

We should make sure that there's a dead-easy way to slap a standard typeahead search suggestion box with given namespace limit settings onto any field, since this is going to be pretty common in advanced editing tools.
Comment 2 Bawolff (Brian Wolff) 2011-04-29 18:22:15 UTC
We actually already have some js that sort of does that - os_initHandlers(<id of input box>,<id of form element>,<inout element>); which will look at hidden input fields to determine which namespaces to search, but its not exactly very jQuery-esq.
Comment 3 Roan Kattouw 2011-04-29 18:22:45 UTC
(In reply to comment #2)
> We actually already have some js that sort of does that - os_initHandlers(<id
> of input box>,<id of form element>,<inout element>); which will look at hidden
> input fields to determine which namespaces to search, but its not exactly very
> jQuery-esq.

resources/jquery/jquery.suggestions.js
Comment 4 Brion Vibber 2011-04-29 18:27:02 UTC
Roan suggests nipping the bits from WikiEditor's link dialog as a model; it uses the opensearch lookup and the jquery.suggestion plugin to handle all the actual drop-down controls.

Probably one could merge that into a common module that can be called from both places for future maintainability.

The goodies are in jquery.wikiEditor.dialogs.config.js -- find the 'Title suggestions' section where it sets the field up.
Comment 5 Bugmeister Bot 2011-08-19 19:12:39 UTC
Unassigning default assignments. http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/54734
Comment 6 Jeroen De Dauw 2011-09-16 14:01:52 UTC
Seems like the bug is still on trunk. I'll have a go at it.
Comment 7 Jeroen De Dauw 2011-09-18 18:51:33 UTC
(In reply to comment #4)
> Roan suggests nipping the bits from WikiEditor's link dialog as a model; it
> uses the opensearch lookup and the jquery.suggestion plugin to handle all the
> actual drop-down controls.

I just tried it out, and it appears to be case-sensitive as well. Is this intended, or should it also be fixed?
Comment 8 Bawolff (Brian Wolff) 2011-09-18 19:53:15 UTC
(In reply to comment #7)
> (In reply to comment #4)
> > Roan suggests nipping the bits from WikiEditor's link dialog as a model; it
> > uses the opensearch lookup and the jquery.suggestion plugin to handle all the
> > actual drop-down controls.
> 
> I just tried it out, and it appears to be case-sensitive as well. Is this
> intended, or should it also be fixed?

Is that on wikimedia, or on your own wiki. Case-insensitivity is provided by [[extension:TitleKey]] I believe.
Comment 9 Jeroen De Dauw 2011-09-18 21:40:10 UTC
My local wiki; will have a look at that extension.
Comment 10 Jeroen De Dauw 2011-11-21 16:44:34 UTC
I just had another look at this, and it appears to have been fixed in the meanwhile already.
Comment 11 Mark Holmquist 2012-09-07 15:24:53 UTC

*** This bug has been marked as a duplicate of bug 40076 ***

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


Navigation
Links