Last modified: 2008-05-30 21:54:40 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 14344 - Enter button in Renameuser form has wrong behaviour
Enter button in Renameuser form has wrong behaviour
Product: MediaWiki extensions
Classification: Unclassified
Renameuser (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2008-05-30 13:09 UTC by Jon Harald Søby
Modified: 2008-05-30 21:54 UTC (History)
0 users

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


Description Jon Harald Søby 2008-05-30 13:09:26 UTC
After entering all the fields in Special:Renameuser, then pressing "Enter", I (and presumably everybody else) would expect that it leads to renaming the user, but insteads it has the same effect as clicking the "Block log" button in the same form. The behaviour should be changed to the same as clicking the "Rename user" button.

(Also, as an aside: Would it be possible to add accesskey="s" to the "Rename user" button?)
Comment 1 Brion Vibber 2008-05-30 21:54:40 UTC
Moved the block log button down in r35625 so it doesn't interfere with the normal order of operations.

It's still kind of weird and strange being in there as a button at all *shrug*.

As for the aside -- afaik we haven't gone around changing every other form in the system to add an accesskey on some of the buttons, so not sure I'd be inclined to do so. :)

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