Last modified: 2013-06-18 16:46:12 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 T21449, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 19449 - move "requires JavaScript" to a own message
move "requires JavaScript" to a own message
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
User preferences (Other open bugs)
unspecified
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2009-06-30 18:35 UTC by Umherirrender
Modified: 2013-06-18 16:46 UTC (History)
3 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Umherirrender 2009-06-30 18:35:37 UTC 
it is possible to move "requires JavaScript" to a own message to reuse it?
This message can set with a new parameter, so extensions can use this easily.

MediaWiki messages (all?):
* Tog-showtoolbar
* Tog-editondblclick
* Tog-editsectiononrightclick
* Tog-usenewrc
* Tog-uselivepreview

Thanks
Comment 1 Niklas Laxström 2009-06-30 19:18:04 UTC 
I'm not sold. Splitting messages into pieces is usually bad thing, as is extensions relying on core messages. Consistency in translations can be achieved with glossaries and and translation memories, and of course by review.
Comment 2 Umherirrender 2009-07-01 16:57:05 UTC 
My idea is, that Extension Gadget can use this message to display it at the end of each definition, which use a js-file. This can also done by a message in Extension Gadget, but a core function for the message is easily to use and to support.

A other idea is, to remove all javascript preferences by setting anything in LocalSetting.php in addition to disable user-js or site-js.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links