Page MenuHomePhabricator

in Special:MovePage the "Move page" button should be disabled until a new name was entered
Closed, DeclinedPublic

Description

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.


Version: unspecified
Severity: enhancement

Details

Reference
bz28739

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 11:28 PM
bzimport set Reference to bz28739.
  • 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, if empty, disable.

Will do soon.

EN.WP.ST47 wrote:

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.

Clearly not being done "soon"; this bug hasn't been touched in over three years.

I agree. While it seems wrong to allow submission for a null action that results in an error. I think disabling the button would be even more counter-intuitive as it isn't obvious the button will enable once you start typing. It might lead the user to believe the page can't be moved for an unknown reason. This is imho not an established UX concept on the web and certainly not within MediaWiki at this time.