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
This would not work for all cases (namely selectors that cross shadow boundaries), but it could be a good ~95% solution with minimal perf impact (since it wouldn't include all of SLDS, just the minimal rules needed).
Another downside is that this would not keep pace with SLDS updates, but maybe this is okay since this is intended as a one-time operation. Perhaps another option here would be to transform from classes to styling hooks (i.e. CSS custom properties, which pierce native shadow roots).
The text was updated successfully, but these errors were encountered:
One of the biggest blockers of moving from synthetic shadow to native shadow is HTML templates containing SLDS utility classes, e.g.:
As part of
synthetic-to-native
, we could inject the minimal SLDS style rules into thecomponent.css
file, e.g.:This would not work for all cases (namely selectors that cross shadow boundaries), but it could be a good ~95% solution with minimal perf impact (since it wouldn't include all of SLDS, just the minimal rules needed).
Another downside is that this would not keep pace with SLDS updates, but maybe this is okay since this is intended as a one-time operation. Perhaps another option here would be to transform from classes to styling hooks (i.e. CSS custom properties, which pierce native shadow roots).
The text was updated successfully, but these errors were encountered: