[wp-trac] [WordPress Trac] #24324: Placeholder support to login form
WordPress Trac
noreply at wordpress.org
Fri Feb 12 11:30:49 UTC 2016
#24324: Placeholder support to login form
---------------------------+----------------------
Reporter: m_uysl | Owner:
Type: enhancement | Status: closed
Priority: normal | Milestone:
Component: Accessibility | Version:
Severity: minor | Resolution: wontfix
Keywords: has-patch | Focuses:
---------------------------+----------------------
Comment (by dpik):
Replying to [comment:7 Caspie]:
> Replying to [comment:6 helen]:
> > Replying to [comment:5 m_uysl]:
> > > Why it need to solve problem? Is there any requirement for it?
> >
> > Yes, we should be solving problems rather than creating them.
Placeholders are not to be used as substitutes for labels. Don't see what
helper text you need for a username and password. So, no, I don't think
core needs to add placeholder support to the login form.
>
> Well it is not a big enhancement, indeed, but I cannot agree with you
that this is something that is not needed at all.
>
> For example, I have a case with a custom login template where email is
the username and I'd like to use wp_login_form instead of building custom
function for it. That's because I have the placeholder texts designed but
cannot filter the form to add it or have to use javascript to inject the
input attributes.
>
> I don't think it is such a big deal to add 2 more arguments with empty
default values (not to match the label texts, like in the patch) to the
wp_login_form.
I'm also really surprised those arguments are not implemented.
Placeholders are very often asked and i don't think that adding this would
break anything.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/24324#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list