You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apologies if this is documented somewhere (and I know some things just changed in v0.9), but I'd like to be able to write declarative shadow DOM templates inside of .webc files and still get the ability to expand additional components in the template. From what I can tell, the WebC processing "magic" doesn't dive into the <template shadowrootmode="open"> tag, which might be reasonable as a default but I'd definitely like to be able to switch it back on (maybe with another webc: directive of some kind)? TIA 😃
The text was updated successfully, but these errors were encountered:
HMMMMMMMMMMMMM yeah, I think you’re absolutely right here. WebC uses an implied webc:raw on declarative shadow DOM templates which hampers their power.
What we really want is an opt-out for asset bundling, I think? webc:nobundle so that stylesheets and scripts aren’t bundled.
Removing implicit webc:raw on Declarative Shadow DOM nodes and adding an implicit webc:nobundle here—this shouldn’t require app code changes to keep current behavior.
Apologies if this is documented somewhere (and I know some things just changed in v0.9), but I'd like to be able to write declarative shadow DOM templates inside of
.webc
files and still get the ability to expand additional components in the template. From what I can tell, the WebC processing "magic" doesn't dive into the<template shadowrootmode="open">
tag, which might be reasonable as a default but I'd definitely like to be able to switch it back on (maybe with anotherwebc:
directive of some kind)? TIA 😃The text was updated successfully, but these errors were encountered: