Last modified: 2007-07-29 18:05:36 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 T12732, 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 10732 - Unlock move permissions checkbox not working correctly
Unlock move permissions checkbox not working correctly
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
unspecified
All All
: High major with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
: 10743 (view as bug list)
Depends on:
Blocks:
  Show dependency tree / graph
 
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: ---

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

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.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links