Bug 8080 - login and password no longer pre-filled by the browser when creating a new patron
Summary: login and password no longer pre-filled by the browser when creating a new pa...
Status: CLOSED FIXED
Alias: None
Product: Koha
Classification: Unclassified
Component: Patrons (show other bugs)
Version: 3.10
Hardware: All All
: P5 - low new feature (vote)
Assignee: Kyle M Hall
QA Contact:
URL: slsn-koha.informindia.co.in
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-13 16:03 UTC by Gaetan Boisson
Modified: 2019-10-17 09:46 UTC (History)
8 users (show)

See Also:
Change sponsored?: Seeking cosponsors
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments
Bug 8080 - login and password is pre-filled by the browser when creating a new patron (2.44 KB, patch)
2012-05-14 12:23 UTC, Kyle M Hall
Details | Diff | Splinter Review
Bug 8080 - login and password is pre-filled by the browser when creating a new patron (2.59 KB, patch)
2012-05-15 13:36 UTC, Liz Rea
Details | Diff | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Gaetan Boisson 2012-05-13 16:03:29 UTC
When creating a new patron, if you have chosen to let your browser remember your login and password for you, the login and password fields will be pre-filled with them, leading to a systematic error "the passwords entered do not match" since the second password field was not filled.

These fields should be blank.
Comment 1 Kyle M Hall 2012-05-14 12:23:08 UTC Comment hidden (obsolete)
Comment 2 Liz Rea 2012-05-15 13:36:05 UTC
Created attachment 9584 [details] [review]
Bug 8080 - login and password is pre-filled by the browser when creating a new patron

When creating a new patron, if you have chosen to let your browser remember your
login and password for you, the login and password fields will be pre-filled with
them, leading to a systematic error "the passwords entered do not match" since
the second password field was not filled. These fields should be blank.

Add the directive autocomplete="off" to the memberentry form tags.

Signed-off-by: Liz Rea <wizzyrea@gmail.com>
passes t xt
enhances usability of password forms, gets my signoff.
Comment 3 Julian Maurice 2012-05-15 15:18:59 UTC
I think bug status should be "Signed off"
Comment 4 Ian Walls 2012-05-23 14:23:56 UTC
Template only change, just adds autocomplete="off" attribute as appropriate.  Thanks for fixing this one, it's been an annoyance to me on my test installs for a long while.

Passed QA.
Comment 5 Paul Poulain 2012-05-25 15:33:32 UTC
Probably usefull and harmless to backport to 3.8
Comment 6 Chris Cormack 2012-05-28 10:19:44 UTC
Pushed to 3.8.x, will be in 3.8.2