-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Using var in a css mixin breaks the scoped style of the element #3461
Comments
Confirmed. Thanks for the report. This is a bug introduced as a result of an optimization we applied in 1.3.0. Unfortunately, we did not have a test to catch this. The fix is clear and we'll work on addressing this and making a quick release asap. |
Here's a temporary workaround Add a style like this in the affected element:
For example: http://jsbin.com/cerepig/edit?html,output. |
…properties are consumed in an element, properly excluding properties produced as a result of consumption.
Thanks for the quick fix and workaround! |
I have a similar issue but with a custom property and the workaround doesn't seem to work for me... we cannot update to 1.3.0 due to this and are waiting for the next fix release. |
We also saw this issue with 1.3.0 and had to rollback to 1.2.4. I just checked the fix branch and it appears to solve all styling issues except one, which might be unrelated. If it's a different bug we'll post something. In the mean time, thanks for making this a priority to release! |
Per @MeTaNoV, here's another repro that just uses a
http://jsbin.com/xajayo/1/edit?html,output When I first tried this, it appeared that the workaround rules needed |
+1 for this |
…ty stylesheet relies on the same info.
Fixes #3461: Only avoid creating a statically scoped stylesheet when …
Description
Using
var
in a css mixin rule causes the element to not define its scoped style. This works fine for Polymer 1.2.4. Did something change or is this no longer allowed?Live Demo
http://jsbin.com/nulepeveku/edit?html,output
Steps to Reproduce
my-element
my-element
to document.bodyvar
onmy-element
Expected Results
Actual Results
Versions
The text was updated successfully, but these errors were encountered: