NumberInput: background color can not be overridden
See original GitHub issueCodeSandbox: https://codesandbox.io/s/chakra-js-starter-iwy4d
I like to style my inputs with grey backgrounds when they are on white backgrounds.
It seems to work for Input
, but it doesn’t work for NumberInput
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
HTML input CSS background color not applied - Stack Overflow
The color style is being applied to the input's text properly and Chrome's dev tools shows the background-color as being active on the...
Read more >lightning-input - documentation - Salesforce Developers
Use SLDS styling hooks to customize the component's styles. For example, change the checkmark color and background color when an option is selected....
Read more >CSS !important Property - W3Schools
The !important rule overrides the background-color property in both cases. Important About !important. The only way to override an ...
Read more >appearance - CSS: Cascading Style Sheets - MDN Web Docs
The appearance CSS property is used to control native appearance of UI controls, that are based on operating system's theme.
Read more >Widgets - Django documentation
You may also implement or override the render() method on custom widgets. attrs ¶. A dictionary containing HTML attributes to be set on...
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
Thanks for that feedback.
NumberInputStepper
sounds like a better name. I’ll rename it.@segunadebayo That looks great! I think
NumberInputStepper
might be a better name thanNumberInputSpinner
though. Just thinking it might conflict with the loading activitySpinner
component we already have