```suggestion
- Design teams must use page spinners to track the progress of operations that affect the entire page, ensuring users understand that the page is temporarily unavailable.
```
```suggestion
A [spinner](https://clarity.design/documentation/spinner) component visually indicates an ongoing, user-initiated process, signaling to users that the system is working and they shou...
```suggestion
- **Must** add an asterisk after the label for required fields and **must** include a legend at the top of the form to inform users that the asterisk denotes a required field unless ...
```suggestion
- Design teams may use a password field when the user needs to mask the input content to protect sensitive information, even if it is not a password.
```
```suggestion
- Design teams **should** not hide password requirements in a signpost or reveal them only after the user fails the first attempt. Providing them upfront helps prevent frustration an...
```suggestion
### Usage
```
I don't think we need to repeat the component name. It's in the level-one heading. This is also consistent with the website. Please update all three level-three hea...
```suggestion
- Design teams **should** show password requirements in the helper text to guide the user, helping them create valid passwords without confusion.
```
```suggestion
- An editable stack view **must** open a modal on clicking the edit button.
```
extra word here, sorry if I introduced this with my previous suggestion.
```suggestion
- Design teams **must not** use an asterisk (*) in the password field. Instead, use dots or bullets to mask the password for consistency and clarity.
```
```suggestion
- Design teams **must** use a password field when the user needs to set or input a password. This ensures security and consistency across the interface.
```
```suggestion
A [password](https://clarity.design/documentation/password) component is an input field that allows users to toggle between hiding or showing the password in plain text.
```