Time | Presenter | Notes |
|---|
5
| Bronwyn Hawkins (Deactivated)
| Chip proposal JW: If it’s interactive it needs a role. If it’s clickable its role is a button. LB: agree it should be different from badge. JW: minimum touch target size is 24 x 24. If the X is smaller than than that we’ll have issues. AB: what if it’s two buttons side by side. TJ: Couldn’t we restrict it: we could say it’s a single button. Do we need to solve it right now? Could we do it later? BH: The immediate need is logistration as selectors. Maybe they only have one function. JW: are they buttons? BH: They are, just smaller. EK: Visual design question: it looks exactly like the badge if there’s no X. Do we think that’s an issue. Maybe change border radius. Should they vary? BH: Yes definitely. TJ: I like David’s idea that it is a superset of the badge from a rendering standpoint. I think taht would work well currently. DJ: Chip is composed of a Badge.
Bronwyn will update design and reshare with this group |
1 | Eugene Kang | Table alignment Would like columns with numeric content to be right aligned. LB: Possible to achieve now, but doing it automatically is hard. AB: Is it a content type on the column? LB: Default cell could handle that. Maybe it should just be a right aligned or not, rather than responding to a type.
- Adam to create a ticket for this work.
|
10 | Jeff Witt (Deactivated) | Coordinating / homogenizing messaging (with accessibility)
Taming the messaging chaos DJ: Has a component like this in frontend-app-learning. It’s a mess. But would like to clean it up. |
10 | Adam Butterworth (Deactivated) | Update on Form components implementation |