Text isn't using default variant without passing a variant prop.
See original GitHub issueDescription
According to the docs the <Text/>
component should use the text.default
variant automatically, when implemented with next
it does not inherit the default value.
Screens
In the bottom section, the card on the left is explicitly declaring variant: default
and the card next to it isn’t. Both are using the <Text/>
component from theme-ui
Issue Analytics
- State:
- Created 3 years ago
- Reactions:7
- Comments:5 (1 by maintainers)
Top Results From Across the Web
How can I us a theme to style all material-ui inputs as if they ...
Using my own OutlinedTextField component (where I override the default variant and pass all other props to TextField isn't an option, since I ......
Read more >Create and use variants - Figma Help Center
A variant property allows you to define attributes of your variants, such as state, color, or size. In the example below, we have...
Read more >Global Styling with Material-UI Theme Overrides and Props
Learn how to use global CSS overrides and default props in a theme to customize all instances of a Material-UI component in a...
Read more >API - React Select
A flexible and beautiful Select Input control for ReactJS with multiselect, ... These base props are those available to be passed to all...
Read more >lightning-input - documentation - Salesforce Developers
If you don't want to display a label, specify the variant="label-hidden" ... The component uses date-style="medium" by default to display the date in...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@cameronwlewis and whomever else finds this until close. You can solve the issue by upgrading your package to
theme-ui@next
It’s because the update to the Text component hasn’t landed in a stable release yet.
The docs probably shouldn’t dictate something that isn’t in the default branch.