Ecosyste.ms: Timeline
Browse the timeline of events for every public repo on GitHub. Data updated hourly from GH Archive.
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Accordions **must not** be nested more than 2 levels. ``` Alternative. Thoughts: @jbusta5
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion # Accordion Design Guidance ```
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion A [radio](https://clarity.design/documentation/radio) control is a form element that allow the user to select one of the options in the list. ```
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion # Radio Design Guidance ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **should** provide a brief description of the process, such as “Loading…”, to give users context about what is happening. ```
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Should not** use checkbox for binary choices outside a form. Use a [toggle-switch](https://clarity.design/documentation/toggle-switch) instead. ```
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion # Checkbox Design Guidance ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must** place the spinner where the user’s attention should be directed once the process is complete, ensuring a smooth transition and clear feedback. ```
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Inputs with sensitive field value lengths (such as tweets). - When users return to an error field and successfully edit the error field. - For password fields with visible ...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams must use inline spinners to track the progress of operations related to specific components, ensuring users know which part of the interface is being processed. ```
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Should** choose this layout for narrow or mobile screens. ```
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Should** choose horizontal layout if the screen has limited vertical place. ```
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion ### Validation Guidelines ``` missing blank line after heading
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion ### Vertical Layout ``` missing blank line after heading
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion ### Horizontal Layout ``` missing blank line after heading
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Should** use [radio button](https://clarity.design/documentation/radio) or [checkbox](https://clarity.design/documentation/checkbox) to compare options within the context of the ...