π V2 Inconsistent Behavior With Angular
HealMah opened this issue Β· comments
@HealMah There are no intermediate values ββfor v2 colors, see https://rc.css.master.co/reference/colors. Additionally, the bg:red
fg:yellow
defaults rely on the light/dark classes on <html class="light">
. https://rc.css.master.co/reference/base-colors
@HealMah There are no intermediate values ββfor v2 colors, see https://rc.css.master.co/reference/colors. Additionally, the
bg:red
fg:yellow
defaults currently rely on the light/dark classes on<html>
. https://rc.css.master.co/reference/base-colors
Ooops, obviously I am not good with this latest version yet. But, "No intermediate values"???.
Anyways, no doubt, this is "Master Css". IT'S GREAT, so kudos to you and your team.
Please may I know why one of the following is working but not the other? And this is with classs 'light' on the html element - please see the screenshots.
Besides, I don't know the real reason behind mandating assigning the theme class ('light', 'black', or otherwise) for colors to work properly, BUT - it seems counter-productive, sorry to say. WHAT IF I DON'T WANT to use this framework for managing themes? Color 'red' should be red, what bg is and isn't shouldn't be a burden on the framework - the developer should know enough about his color system! I think this is how the v1 works.
The moment there is not a theme class on any parent, MOST colors go blank - THAT'S WEIRD! Or am I missing something?
I hope you understand my concerns, PLEASE do help enlighten us SIR!
@HealMah In v2, only red-5
red-10
red-20
red-30
... are available. We value the real experience of developers and have indeed re-evaluated the solution of not driving color through html.light
html.dark
.
π This issue has been resolved in version 2.0.0-rc.42 π
The release is available on:
- GitHub release
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
Your semantic-release bot π¦π