Last modified: 2014-11-04 22:52:42 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 4964 - Parameter names in templates should be case-insensitive
Parameter names in templates should be case-insensitive
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
Templates (Other open bugs)
1.16.x
All All
: Lowest enhancement with 3 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
: easy
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-02-11 19:31 UTC by Splash
Modified: 2014-11-04 22:52 UTC (History)
8 users (show)

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


Attachments

Description Splash 2006-02-11 19:31:24 UTC
Exactly as it says on the tin for which I can't find a current bug.

So that there is no need to code either conditional templates or entirely
separate templates along with all the associated drudge work to go from one
caseing to another *and* to avoid the many inconsistencies we have at present.

{{template|Par1=val1|Par2=val2...}}

should be exactly the same as far as the editor is concerned as

{{template|par1=val1|par2=val2...}}}

At present, if the templates is coded as either of these, it will fail if the
editor uses the other caseing.
Comment 1 stux 2007-09-29 18:07:43 UTC
This makes sense, since I've run into several improperly used template, but doing so will likely break other templates where users may have (inappropriately) taken advantage of case sensitivity:

{{template|par1=val1|PAR1=val2...}}

I think parameter case sensitivity should be treated as a "template standard" and so template "programmers" (i.e. users) should be informed of this issue (i.e. the information widely disseminated through as many channels as possible).  
Comment 2 Aryeh Gregor (not reading bugmail, please e-mail directly) 2009-12-14 23:43:05 UTC
This might or might not have been a good idea to start with, but by now there's way too much legacy content.  Also, case-sensitivity of template parameters matches case-sensitivity of the template names themselves.  Given the relatively marginal benefit of allowing case-insensitive parameters to begin with (is it really hard to always use lowercase?), I would suggest WONTFIX.
Comment 3 Alex Z. 2009-12-15 01:00:25 UTC
I was considering doing this, but with a config variable to enable it (disabled by default), but if people think that's excessive, I'm not especially attached to the idea.
Comment 4 Aryeh Gregor (not reading bugmail, please e-mail directly) 2009-12-15 14:35:54 UTC
I don't think a config option would be useful here.  It would potentially break copying content between wikis, e.g., Wikipedia.
Comment 5 Chad H. 2009-12-16 14:37:31 UTC
(In reply to comment #4)
> I don't think a config option would be useful here.  It would potentially break
> copying content between wikis, e.g., Wikipedia.
> 

I agree completely. This should either be fixed or not fixed, introducing a variable here would just create incompatibilities between wikis and make Import/Export unreliable.

(In reply to comment #2)
> This might or might not have been a good idea to start with, but by now there's
> way too much legacy content.  Also, case-sensitivity of template parameters
> matches case-sensitivity of the template names themselves.  Given the
> relatively marginal benefit of allowing case-insensitive parameters to begin
> with (is it really hard to always use lowercase?), I would suggest WONTFIX.
> 

I'm inclined to agree here. This seems like it would've been a great idea when it was being designed, but it's too late now.

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


Navigation
Links