[#20371] - [4.0] Password strength meter states "Password accepted" when Joomla validation would fail password
- Closed
- 13 May 2018
- Medium
- Build: staging
- # 20371
Steps to reproduce the issue
I have said it before and Ill say it again, the Password strength meter should be removed - it gives a false reading - here is ANOTHER concrete example of a bug that makes it useless.
Now lets try a password that STARTS and ENDS with SPACE char...
SPACEabcSPACE
where SPACE is an actual space! duh!
this gives:
So SPACEabcSPACE gives 100% green - hmmm well ok then, BUT - it also states "Password accepted" which a user assumes means that Joomla accepts the password (not that some idiotic JS Password strength meter thinks its ok, so now he thinks it does meet the requirements!
SAVE......
Oh... haha now you get a big warning of:
Warning
Password must not contain spaces at the beginning or end
So it was not "accepted"
A concrete example of a bug to fix, and expectation that is not managed.
joomla-cms-bot
- | Labels |
Added:
?
|
||
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2018-05-13 01:16:19 |
| Closed_By | ⇒ | brianteeman |
Pathetic response to what it a VALID issue to be fixed!
I bet you did not even bother reading what I wrote
Sent from my iPhone
On 13 May 2018, at 02:16, Brian Teeman notifications@github.com wrote:
Closed #20371.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
I did not realise that was still open - and ignored for a whole year :-(
Sent from my iPhone
On 13 May 2018, at 04:04, Michael Babker notifications@github.com wrote:
Other than having some more detail/opinion on the matter this is no different to #15582 which you opened last year.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
| Title |
|
||||||
Updated title and narrative to highlight the issue. For the record. I see this is already closed and so will never be addressed, but at least I have documented the issue for the one that comes after me.
You've said this before. No need to open another issue