- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Nov 2017 23:20:34 +0000
- To: public-css-archive@w3.org
FYI: Some of the differences you're seeing in browsers may be related to how they handle inheritance of `currentColor` values in general, not specific to the particular inheritance issues of elements broken into separately styled fragments. Most browsers still follow the original draft of CSS Colors 3, and convert `currentColor` to a specific color value _before_ inheritance. Chrome, however, inherits `currentColor` as its own value, only converting it to a specific color at final used value time. This is how the latest drafts of CSS Colors 3 & 4 define it, to be consistent with how it was defined in SVG 1. Which makes it much harder to distinguish from the test how the browsers are interpretting the inheritance rules for the two fragments within the `<span>`. But regardless, the rules for `currentColor` and fragments should be consistent with any other property that depends on inheritance, such as `font-size` with a percent value. So the best place to define that would probably be in the pseudoelements and/or cascade specs, not in Colors. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1510#issuecomment-346498938 using your GitHub account
Received on Wednesday, 22 November 2017 23:20:40 UTC