react-components
react-components copied to clipboard
canonical
A set of components based on Vanilla Framework
## Overview After upgrading from @types/react 18.2.21 to 18.2.22, we are getting build errors of the type `is not a valid JSX element type` for Canonical's React components. For example:...
Tooltips tests fail from time to time. It's hard to reproduce as it doesn't happen in deterministic way. The error when it happens is: ``` ● Tooltip › updates the...
### Issue There are instances where we would like to limit the `max-width` of `Tooltip` without setting a fixed width for it (e.g. the generated content is dynamic and can...
The confirmation modal does not have a min width so it can become very narrow if there isn't a lot of content.
These are probably 2 unrelated issues but I noticed that recently Percy stopped rendering Ubuntu font (maybe when we moved to variable font?) and doesn't render logo image in the...
To build a component library around Vanilla we really care about the class names, visual elements, node order etc. not just the accessible labels and roles To do this we...
Field component should allow custom label id to allow more complex relationships, like `aria-describedby={fieldLabelId}`
Segmented Controls are available in Vanilla but React component for it is not available. It has been implemented in maas-ui but full accessibility functionalities are not available: https://github.com/canonical/maas-ui/tree/main/src/app/base/components/SegmentedControl
The column width for labels in the `Input` component in a stacked form is `4`. On Snapcraft listing forms we use a column width of `2` meaning this component won't...
## What We should have a common way of translating base/modifier classes that exist in vanilla to props in `react-components`. For example, the `help` prop in `Input` could be named...