Currently, Qwik does not natively support Declarative Shadow DOM, which wesc relies on. Qwik's design philosophy focuses on delaying the execution and download of JavaScript for as long as possible, which is different from traditional SSR frameworks that wesc is designed to work with.
While it's theoretically possible to use wesc to add Shadow DOM boundaries to a Qwik application, it would likely require significant modifications to both wesc and Qwik applications, and may not align with Qwik's design philosophy.
We are very interested in using the selectlist polyfill web component, but the major tradeoff seems to be hydration in polyfill browsers breaking the layout (Qwik does not have hydration, the JavaScript is serialized into the HTML). If anyone has any ideas for how this might work, we would love to hear it. We've been trying to figure out a way to get this to work natively in Qwik without breaking the design philosophy of the framework.
Currently, Qwik does not natively support Declarative Shadow DOM, which
wescrelies on. Qwik's design philosophy focuses on delaying the execution and download of JavaScript for as long as possible, which is different from traditional SSR frameworks that wesc is designed to work with.While it's theoretically possible to use wesc to add Shadow DOM boundaries to a Qwik application, it would likely require significant modifications to both wesc and Qwik applications, and may not align with Qwik's design philosophy.
We are very interested in using the selectlist polyfill web component, but the major tradeoff seems to be hydration in polyfill browsers breaking the layout (Qwik does not have hydration, the JavaScript is serialized into the HTML). If anyone has any ideas for how this might work, we would love to hear it. We've been trying to figure out a way to get this to work natively in Qwik without breaking the design philosophy of the framework.