-
-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Propose an alternative method to use Twind with Web components and Lit for Firefox and Safari #181
Comments
Hi, I also really like the project. But as @gawlk mentioned, the implementation from the example is unusable in production due to the limitations in Firefox and Safari. I would suggest some kind of hook/event that could be listened for to re-trigger the creation of the style. Anyways, cool project! Keep up the good work! |
I'm not that familiar with web components and their frameworks. Would it be possible to use a style element (maybe using the dom sheet) for each web component which is updated per web component instance? |
I gotta +1 this as well. I had a FANTASTIC time using this library over the last week on a project (super easy to use and super easy to tell what's a tailwind class and what's my class) until I noticed that my font sizes weren't right on Firefox and had to rip it all out and replace it with using PostCSS + Tailwind (using lit-element as well). |
This has been implemented in a new integration: You can view a preview of the docs here: https://next.twind-style.pages.dev/with-web-components. I have added a Lit example as well in case you are using that: https://next.twind-style.pages.dev/with-lit This will be released soon (#417). Until is released you can use the pre-release version (for example If you have any issues or questions please re-open this issue. |
Hi,
Love this project, it works great, ton of great ideas but I have one small issue with it: it's with
adoptedStyleSheets
. It works great with Chrome but as you know it doesn't with Firefox or Safari. As it's the only way to use both twind with web components it's not at all usable in production.I was wondering if you guys had any idea for an alternative method that would work on more browsers.
If not I fully understand, just thought to point the need for such functionality.
Anyway,
Thanks for you work
The text was updated successfully, but these errors were encountered: