Opened 15 years ago
Last modified 15 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/
Change History (5)
comment:1 by , 15 years ago
comment:2 by , 15 years ago
WHOA. We should totally placeholder= it up :)
Wonder how hard that is to do with wtforms...?
comment:3 by , 15 years ago
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
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 by , 15 years ago
| Owner: | set to |
|---|---|
| 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.
And in HTML5 of course you would use the placeholder="Username" attribute. :)