Last modified: 2008-03-18 23:33:08 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 6319 - Problematic characters for AJAX search autosuggestion
Problematic characters for AJAX search autosuggestion
Status: RESOLVED WORKSFORME
Product: MediaWiki
Classification: Unclassified
Search (Other open bugs)
1.7.x
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: patch, patch-need-review
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-06-15 18:31 UTC by Mormegil
Modified: 2008-03-18 23:33 UTC (History)
0 users

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


Attachments
Patch to solve the described issues (4.02 KB, patch)
2006-06-15 18:31 UTC, Mormegil
Details

Description Mormegil 2006-06-15 18:31:06 UTC
The AJAX search autosuggestion incorrectly handles some inputs:
* High ASCII (Latin-1) characters (U+0080 through U+00FF) are encoded to %xx and then incorrectly used literally 
instead of conversion to UTF-8.
* The plus character (+) is passed unencoded, and is decoded to space server-side.

In addition, a few minor issues:
* GUI displays "low-level" search string with underscores instead of spaces.
* The search does not handle duplicate and leading/trailing spaces.
Comment 1 Mormegil 2006-06-15 18:31:49 UTC
Created attachment 1960 [details]
Patch to solve the described issues
Comment 2 Brion Vibber 2008-03-18 23:33:08 UTC
Issues seem to have been since fixed.

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


Navigation
Links