Open nolanlawson opened 3 years ago
This issue has been linked to a new work item: W-9667229
Other at-rules we could potentially open bugs for:
@counter-style
@font-feature-values
@property
(experimental)@color-profile
(experimental)@viewport
(deprecated)Probably some more stuff I forgot.
Worth noting:
@font-face
(although it does @keyframes
)styled-components
also does @keyframes
but not @font-face
So this might not be a high-value feature.
This bug affects me too. Is it possible to change the priority? - it is open for almost a year.
Synthetic shadow DOM is in maintenance mode. We are working to move to native shadow DOM instead.
This particular bug is also complicated by the fact that (as discussed above) Chrome and Firefox do not support the specced behavior yet. Your best bet is probably to manually scope your font-family
names for now.
Follow-up to https://github.com/salesforce/lwc/issues/1536#issuecomment-535518329
@font-face
in CSS is currently global. It should be scoped to the component that declares it.