Bug 2192563 - [RFE] : login-change-password : Confusing green tick for old password field
Summary: [RFE] : login-change-password : Confusing green tick for old password field
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Dashboard
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 7.0
Assignee: Nizamudeen
QA Contact: Sayalee
Anjana Suparna Sriram
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-02 09:49 UTC by Vasishta
Modified: 2023-07-10 06:38 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-6597 0 None None None 2023-05-02 09:50:24 UTC
Red Hat Issue Tracker RHCSDASH-969 0 None None None 2023-05-02 09:50:26 UTC

Description Vasishta 2023-05-02 09:49:59 UTC
Created attachment 1961636 [details]
Dashboard snapshot

Description of problem:
Green tick mark for password fields are used generally for input validation,
we have green tick for old password field in login-change-password page.
(Page just after first login using password created by default at the time of bootstrap).

This particular green tick turns on with more >0 characters of user input.
This creates confusion as generally green tick denotes acceptance and anything other than old password is not acceptable, right ?

IMHO, we don't need green tick for old password, we can use some other way to say that this field is required to submit the form.

Version-Release number of selected component (if applicable):
<Latest>

How reproducible:
Tried twice

Steps to Reproduce:
Bootstrap a cluster and login to dashboard
when it redirects for password change, enter incorrect value to old password field and observe green tick

Actual results: Expected results:
<Explained above>


Additional info:

Comment 1 Veera Raghava Reddy 2023-05-26 11:38:22 UTC
6.2 is now combined with 7.0 as per May 24, 2023 program meeting. Updating target release to 7.0.


Note You need to log in before you can comment on or make changes to this bug.