Closed angelofan closed 3 weeks ago
One of the solutions is to consider using Shadow DOM.
An important aspect of custom elements is encapsulation, because a custom element, by definition, is a piece of reusable functionality: it might be dropped into any web page and be expected to work. So it's important that code running in the page should not be able to accidentally break a custom element by modifying its internal implementation. Shadow DOM enables you to attach a DOM tree to an element, and have the internals of this tree hidden from JavaScript and CSS running in the page.
Hey @angelofan, I'm curious how you fixed it or which workaround you took.
thanks!
@euhm Now I use @khmyznikov/pwa-install. Everything works well.
@angelofan @euhm apologies for the delay. This Tailwind issue is fixed in https://github.com/philfung/add-to-homescreen/commit/ba1c2e517cf392ed67928daddcaea7c5cfa8c576 Please update CDN link to use release 2.5 and all should render correctly with Tailwind.
CSS is polluted when used with Tailwind CSS.
Screenshot
Code