Last modified: 2006-10-25 12:43: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 7686 - Allow delete button to have an access key
Allow delete button to have an access key
Product: MediaWiki
Classification: Unclassified
Page editing (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-10-24 21:58 UTC by Platonides
Modified: 2006-10-25 12:43 UTC (History)
0 users

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

Give an Id for Accesskey to 'confirm delete' button (405 bytes, patch)
2006-10-24 21:59 UTC, Platonides

Description Platonides 2006-10-24 21:58:44 UTC
Currently you can go to the delete page of an article with keyboard, but there
you need to agree the deletion with the mouse (or long tabbing) as the
confirmation button doesn't have an id to add it an accesskey.

The patch below adds it the id wpConfirmB (its field name) though as it's not
used anywhere on the code both could be changed to a more descriptive name
(wpConfirmDeletion ?) I wonder what does the B mean...
Comment 1 Platonides 2006-10-24 21:59:42 UTC
Created attachment 2548 [details]
Give an Id for Accesskey to 'confirm delete' button
Comment 2 Brion Vibber 2006-10-25 12:39:10 UTC
Confirmation is normally done with the enter key from the reason/comment field.
Comment 3 Brion Vibber 2006-10-25 12:43:36 UTC
Patch applied on trunk in r17249.

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