Web client forms need autocomplete and autocapitalize attributes
Bug #1778063 reported by
Jason Boyer
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Confirmed
|
Medium
|
Stephanie Leary | ||
3.2 |
Won't Fix
|
Medium
|
Unassigned | ||
3.3 |
Won't Fix
|
Medium
|
Unassigned | ||
3.4 |
Won't Fix
|
Medium
|
Unassigned | ||
3.5 |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Now that we're using a web app in whatever browser the user chooses there are some things we can do to make the experience of using it better for those users. The staff and opac login forms can be improved by adding autocomplete hints to assist password managers and disabling autocapitalize will help with mobile entry. Both attributes should be disabled in all staff client forms because you don't want your client "helpfully" suggesting barcodes and searches from last week. The good news is that if applied to the <form> element then all input elements within it inherit them.
Changed in evergreen: | |
importance: | Undecided → Wishlist |
Changed in evergreen: | |
importance: | Wishlist → Medium |
Changed in evergreen: | |
status: | New → Confirmed |
milestone: | none → 3.2.3 |
tags: | added: usability |
Changed in evergreen: | |
milestone: | 3.2.3 → 3.3-beta1 |
Changed in evergreen: | |
milestone: | 3.3-beta1 → 3.3-rc |
Changed in evergreen: | |
milestone: | 3.3-rc → 3.3.1 |
Changed in evergreen: | |
milestone: | 3.3.1 → 3.3.2 |
Changed in evergreen: | |
milestone: | 3.3.2 → 3.3.3 |
Changed in evergreen: | |
milestone: | 3.3.3 → 3.3.4 |
Changed in evergreen: | |
milestone: | 3.3.4 → 3.3.5 |
Changed in evergreen: | |
milestone: | 3.3.5 → 3.4.2 |
Changed in evergreen: | |
milestone: | 3.4.2 → 3.4.3 |
Changed in evergreen: | |
milestone: | 3.4.3 → 3.4.4 |
Changed in evergreen: | |
milestone: | 3.4.4 → 3.5.1 |
Changed in evergreen: | |
milestone: | 3.5.1 → 3.5.2 |
Changed in evergreen: | |
milestone: | 3.5.2 → 3.6.1 |
tags: | added: pullrequest |
Changed in evergreen: | |
milestone: | 3.6.1 → 3.6.2 |
Changed in evergreen: | |
milestone: | 3.6.2 → 3.6.3 |
Changed in evergreen: | |
milestone: | 3.6.3 → none |
tags: | removed: webstaffclient |
tags: |
added: needsdiscussion needsrebase removed: needsrepatch |
tags: | added: performance |
tags: | removed: performance |
Changed in evergreen: | |
assignee: | nobody → Stephanie Leary (stephanieleary) |
tags: | added: accessibility ux-forms |
To post a comment you must log in.
I've bumped the importance because I've been getting reports of libraries running into issues with the wrong items being checked in at various locations, and local staff have narrowed it down to autocomplete interference. Here's a branch that does a couple things; in the staff client portions autocomplete is largely disabled everywhere because there's no benefit to a browser trying to guess what you want to do. Where it makes sense in the public facing parts of the opac autocomplete options are specified to make things more reliable and simpler for password managers and browser personal information features to use appropriately.
http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ jboyer/ lp1778063_ autocomplete working/ user/jboyer/ lp1778063_ autocomplete
Testing can be annoying because Chrome doesn't necessarily save every value every time. With this patch installed it should remember next to nothing for staff. The staff and opac login pages are also enhanced for mobile to stop auto-capitalizing the username on the login form.