-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ShadyCSS] Mixins applied inconsistently #35
Labels
Comments
Thanks for the test case. I think I have a simpler method that moves the |
dfreedm
referenced
this issue
in webcomponents/shadycss
Nov 16, 2016
dfreedm
referenced
this issue
in webcomponents/shadycss
Nov 17, 2016
dfreedm
referenced
this issue
in webcomponents/shadycss
Dec 5, 2016
@azakus any updates on this issue please? |
dfreedm
changed the title
Mixins applied inconsistently
[ShadyCSS] Mixins applied inconsistently
Jun 12, 2019
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
REF Polymer/polymer#4115
Distributed nodes appear to be styled with mixins defined in the host, providing they are applied after the host has been defined.
Please note the following demo: http://codepen.io/oridan/pen/edqMPO?editors=1000
Item B simply extends Item A with no other changes. Therefore they should both display exactly the same. The expected result as I understand it should be per as the following image:
RFC:
I have resolved this where
nativeCssVariables == true
by applying the following two diffs:webcomponents/shadycss@master...TomK:apply-host-descendants - quite inefficient
webcomponents/shadycss@master...TomK:refresh-invalid-shim
I understand this is not a complete resolution, and possibly this implementation is not feasible. So I am hoping for comments/suggestions to steer towards a viable solution.
The text was updated successfully, but these errors were encountered: