Last modified: 2011-12-14 17:37:33 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 28739 - in Special:MovePage the "Move page" button should be disabled until a new name was entered
in Special:MovePage the "Move page" button should be disabled until a new nam...
Status: NEW
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Krinkle
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-04-28 19:01 UTC by Amir E. Aharoni
Modified: 2011-12-14 17:37 UTC (History)
4 users (show)

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


Attachments

Description Amir E. Aharoni 2011-04-28 19:01:23 UTC
If a user attempts to move a page to the same title, he sees the error message selfmove (Source and destination titles are the same; cannot move a page over itself.). This can be avoided by disabling (graying out) the "Move page" button until a different name is entered.
Comment 1 Krinkle 2011-05-02 20:56:28 UTC
* disable on load from JS (not from PHP, to avoid non-JS viewers from being unable to move)
* on key touch if not empty, enable, id empty, disable.

Will do soon.
Comment 2 Dan Collins 2011-07-09 01:43:33 UTC
Do we /ever/ disable buttons in JS? I don't think so, the save page button isn't grayed out if the page hasn't been edited, for example, so why is this a special case? If the user submits invalid input, they get an error message, I don't see what the problem is. Marking as an enhancement, because it is, but I'm not sure whether it makes sense to start disabling buttons.

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


Navigation
Links