Ecosyste.ms: Timeline
Browse the timeline of events for every public repo on GitHub. Data updated hourly from GH Archive.
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```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. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```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...
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```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 ...
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion # Forms Pattern Design Guidance ```
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Must** follow the [password guidance](/1019) for the password input. ``` Let's not repeat guidance when we can just link to it.
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
(edited Jay's comment to bold "may")
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```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. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```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...
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```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...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **should** show password requirements in the helper text to guide the user, helping them create valid passwords without confusion. ```
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```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.
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion # Tree View Design Guidance ``` Please also update the filename to match.
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```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. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```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. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```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. ```