Applying Theme Variant Class in the <html>
#61
Replies: 1 comment 1 reply
-
|
That is a good feature request. Being able to configure how themes get applied is a common request. It is on my list of things to add when I prioritize the time. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
I released this in the most recent version of the plugin :) |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm porting a theme created with Bootstrap to Tailwind, and I came across an issue regarding coloured scrollbars.
The general idea is to set
scrollbar-colorand their WebKit vendor prefixes to the overflowing content, and that works nicely with the current implementation described by this Plugin's docs. However, it seems that the only way to colourize the main scrollbars on Firefox is by setting the said rules to the<html>while for Chrome — and possibly other WebKit browsers — setting on<body>is enough.Problem is, blocks like this:
Would create rules like this:
Which, as much as I know, — and accordingly to Tailwind's docs about manual Dark Mode — includes an incorrectly parsed directive
.theme1 htmlwhile it should behtml.theme1.I could have made an Issue of this, but I thought the best to discuss it first. If it's like I'm thinking, perhaps you could condition the variant expression based on the name/type of the tag if the selector is
htmlor*(both are affected).Thank you for your time
Beta Was this translation helpful? Give feedback.
All reactions