*:not(style) ~ *:not(style)
See original GitHub issueCurrently I am having to override most of my useBreakpointvalue
items with an important to remove this random css rule, but this means I cannot use my number based fontSizes, lineHeights etc.
const margin = useBreakpointValue({ base: "0 !important", md: space["0.5"] });
So in this situation I cannot use important on my space
What is this style and how can I find out where it is defined?
Theme
const space = {
"-1": "0rem",
0: "0.5rem",
1: "1rem",
2: "1.5rem",
5: "2.5rem",
8: "4rem",
13: "6.5rem",
21: "10.5rem",
35: "16.5rem",
};
This is adding the styles from the first image, to all child components of .chakra-stack.css-gafkgn
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:11 (2 by maintainers)
Top Results From Across the Web
Margins not working due to *:not(style) - GitHub
An unknown style is being applied to elements, so far I can only narrow this down to when using vStack, but I imagine...
Read more >not() - CSS: Cascading Style Sheets - MDN Web Docs
The :not() CSS pseudo-class represents elements that do not match a list of selectors. Since it prevents specific items from being selected, ...
Read more >javascript - chakra ui - the style does not apply - Stack Overflow
The size is not the same as my expectation. App.js import "./styles.css"; import { HStack, PinInput, PinInputField } from "@chakra-ui/react" ...
Read more >Style Props - Chakra UI
Learn how to use style props in Chakra UI. Style props are a way to alter the style of a component by simply...
Read more >STYLE NOT COM (@stylenotcom) • Instagram photos and ...
140k Followers, 1844 Following, 2009 Posts - See Instagram photos and videos from STYLE NOT COM (@stylenotcom)
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
I am also trying to figure out where this rule is coming from. It is not wanted and now I have use an !important css declaration to get around it.
Unwanted style added by something in Chakra:
An alternative is to use https://emotion.sh/docs/ssr#advanced-approach
When you do not use the default cache it will not issue that warning. The advanced approach also extracts the styles into a single style tag, so this workaround is not required.