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
According to the spec, rules from outside a shadow tree always win against rules within a shadow tree, when they attempt to style the same element: http://dev.w3.org/csswg/css-scoping/#cascading
It seems that Shady DOM correctly handles this with regular properties, but not with custom properties. Consider the following example:
The result should be blue text with a pink background since document style should win here; instead, I see red text with a pink background.
That means Polymer is correctly determining that the outside background:pink property should win, but incorrectly not doing the same with the outside --color:blue custom property.
The text was updated successfully, but these errors were encountered:
…rties so scope properties override them; also adds '*' as an own scope matcher. Own scope properties are applied last; this gives the element the final say and allows property retargeting.
According to the spec, rules from outside a shadow tree always win against rules within a shadow tree, when they attempt to style the same element:
http://dev.w3.org/csswg/css-scoping/#cascading
It seems that Shady DOM correctly handles this with regular properties, but not with custom properties. Consider the following example:
With the following external styles defined:
The result should be blue text with a pink background since document style should win here; instead, I see red text with a pink background.
That means Polymer is correctly determining that the outside
background:pink
property should win, but incorrectly not doing the same with the outside--color:blue
custom property.The text was updated successfully, but these errors were encountered: