Last modified: 2014-03-09 22:56:33 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 T53673, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 51673 - VisualEditor: Search of parameters in transclusion editor should be case insensitive
VisualEditor: Search of parameters in transclusion editor should be case inse...
Status: RESOLVED FIXED
Product: VisualEditor
Classification: Unclassified
Editing Tools (Other open bugs)
unspecified
All All
: Normal normal
: VE-deploy-2014-03-13
Assigned To: Trevor Parscal
:
Depends on:
Blocks: ve-templatesupport
  Show dependency treegraph
 
Reported: 2013-07-19 10:26 UTC by Chris McKenna
Modified: 2014-03-09 22:56 UTC (History)
4 users (show)

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


Attachments
The parameter search is case sensitive, requiring all lowercase input (14.87 KB, image/png)
2013-07-19 10:26 UTC, Chris McKenna
Details

Description Chris McKenna 2013-07-19 10:26:58 UTC
Created attachment 12894 [details]
The parameter search is case sensitive, requiring all lowercase input

When searching for parameters in the transclusion/template editor the search returns "Unknown parameter" unless the search term is entirely lowercase.
Comment 1 Chris McKenna 2013-07-19 10:31:45 UTC
After a moments though I wonder if this might be the same issue as bug 51670, with the search requiring input that matches the parameter as defined in the source (which the VE user has no way of knowing) rather than the title as displayed in the parameter list.
Comment 2 Chris McKenna 2013-08-25 10:34:21 UTC
*** Bug 52950 has been marked as a duplicate of this bug. ***
Comment 3 James Forrester 2014-03-09 22:56:33 UTC
Done by Gerrit change #117305.

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


Navigation
Links