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
I am using Angular 4 and Polymer 2. The problem is that Polymer 2 supports css-mixins but Angular doesn't. So I need to parse css-mixins and @apply rules in Angular component-level styles. When I tried to use <custom-style> feature from Polymer 2, the css-mixins worked fine but the styles were messed up. :not(.style-scope) was appended to all style selectors and elements were decorated with style-scope class. I know that's how ShadeCSS emulates ShadowDOM v1 spec. But as I know, Angular also applies different scoping with ShadeCSS, so I only need to handle what Angular missed - css-mixins and @apply rules. So I am asking if there is any way to parse them only from the styles inside a certain element which can be retrieved like as document.querySelector()?
The text was updated successfully, but these errors were encountered:
…mposition
Set the root to "clean" before composition. Fixes#38
dfreedm
changed the title
Parse css-mixins and @apply rules in Angular component-level styles
[ShadyCSS] Parse css-mixins and @apply rules in Angular component-level styles
Jun 12, 2019
I am using Angular 4 and Polymer 2. The problem is that Polymer 2 supports
css-mixins
but Angular doesn't. So I need to parsecss-mixins
and@apply
rules in Angular component-level styles. When I tried to use<custom-style>
feature from Polymer 2, thecss-mixins
worked fine but the styles were messed up.:not(.style-scope)
was appended to all style selectors and elements were decorated withstyle-scope
class. I know that's how ShadeCSS emulates ShadowDOM v1 spec. But as I know, Angular also applies different scoping with ShadeCSS, so I only need to handle what Angular missed -css-mixins
and@apply
rules. So I am asking if there is any way to parse them only from the styles inside a certain element which can be retrieved like asdocument.querySelector()
?The text was updated successfully, but these errors were encountered: