Opened 12 years ago
Last modified 11 years ago
#190 closed defect (FIXED)
In-field labels
Reported by: | Jan-Christoph Borchardt | Owned by: | Jef van Schendel |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | ui | Keywords: | |
Cc: | Parent Tickets: |
Description
For the log in and registration forms, the labels should go in the fields to make it more quickly recognizable. Check this jQuery plugin: `http://fuelyourcoding.com/scripts/infield/ <http://fuelyourcoding.com/scripts/infield/>`_
Subtickets
Change History (5)
comment:2 Changed 12 years ago by
WHOA. We should totally placeholder= it up :) Wonder how hard that is to do with wtforms...?
comment:3 Changed 12 years ago by
Actually, the HTML5 spec says: »The placeholder attribute should not be used as an alternative to a label.« `http://dev.w3.org/html5/spec/Overview.html#the-placeholder-attribute <http://dev.w3.org/html5/spec/Overview.html#the-placeholder-attribute>`_ So the jQuery plugin is still the best way to do that. I don't know about its non-JS compatibility though. An issue for us was Chromium's autofill feature colliding with it - having the info filled in but the labels still displayed. We didn't look into a solution yet as we still use the placeholder attribute for ownCloud's log in form.
comment:4 Changed 11 years ago by
Owner: | set to Jef van Schendel |
---|---|
Status: | New → Closed |
I'm closing this bug, since it seems that the placeholder attribute is not the right way to do this and I think that including and using a jQuery plugin just for this is not necessary.
comment:5 Changed 11 years ago by
The original url for this bug was http://bugs.foocorp.net/issues/484 .
Note: See
TracTickets for help on using
tickets.