Last modified: 2007-07-29 18:05:36 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 10732 - Unlock move permissions checkbox not working correctly
Unlock move permissions checkbox not working correctly
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
All All
: High major with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
: 10743 (view as bug list)
Depends on:
  Show dependency treegraph
Reported: 2007-07-28 22:23 UTC by Mets501
Modified: 2007-07-29 18:05 UTC (History)
2 users (show)

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


Description Mets501 2007-07-28 22:23:51 UTC
The "Unlock move permissions" checkbox is not enabling or disabling the box above it which allows you to select the level of move protection (id = mwProtect-level-move).  If it is checked by default, then unchecking it links the two boxes (mwProtect-level-move and mwProtect-level-edit) but does not disable mwProtect-level-move, so you can still select a level there (but it will be mirrored in mwProtect-level-edit).  If it is not checked by default, there is no way to separate move and edit permissions.
Comment 1 Rob Church 2007-07-28 23:09:43 UTC
Fixed in r24419.
Comment 2 AlexSm 2007-07-29 04:46:08 UTC
Did you mean "fixed for DOM-compliant browsers"? IE doesn't support addEventListener.

I would suggest adding (into wikibits.js) another function, say addEvent(), similar to hookEvent() but taking the object name as the 1st parameter, and then using this function instead. This function is pretty much standart amonng Javascript developers.
Comment 3 Rob Church 2007-07-29 14:52:58 UTC
Should be fixed for "non DOM-compliant browsers" in r24427.
Comment 4 Rob Church 2007-07-29 18:05:36 UTC
*** Bug 10743 has been marked as a duplicate of this bug. ***

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