====================================

Good Build:

44.0.2366.0    Base Position: 324746


Bad Build:

44.0.2381.0    Base Position: 326628

=====================================

Able to repro this issue on Windows 7, MAC (10.11.3) & Ubuntu Trusty (14.04) for the Google Chrome Stable Version - 49.0.2623.87

This is a regression issue broken in M44, below mentioned is the bisect info:

CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/091a9e14ae9716f30ebb17cee80db13a5dd0261d..b3ee51643703386144a3e6eca2558e72077d5fae

https://chromium.googlesource.com/chromium/blink/+log/21fff74..bb7e4b1

Suspecting Commit: a9ce0ce28c5d2f9b029fcb209358260141e2f41a

Review URL: https://codereview.chromium.org/1088613002

@fmalita: Could you please look into the issue, and if it has nothing to do with your changes and if possible please do assign it to the concerned owner.

Thank you.

This is actually correct as per the current specs. I'm not sure why other browsers haven't implemented this yet :/

This was agreed upon in 2012. https://lists.w3.org/Archives/Public/www-style/2012May/0541.html

https://drafts.csswg.org/css-color/#currentcolor-color
"The keyword currentcolor takes its value from the value of the color property on the same element. This happens at used-value time, which means that if the value is inherited, it’s inherited as currentcolor, not as the value of the color property, so descendants will use their own color property to resolve it."

Not related to a9ce0ce28c5d2f9b029fcb209358260141e2f41a.

The change in behavior was most likely introduced in https://chromium.googlesource.com/chromium/blink/+/78db1a65a9b86eeb89885cda984a1684d50ed450.

Punting to timloh@, but it does sound like this is intended/correct behavior.

@timloh: Your comment is really interesting, I didn't think about searching into CSS4 yet :)

I understand that is the way described in the CSS Color Module Level 4, but it's still an editor's draft version and Blink is the only one which has chosen to take this way :(

We don't know if the W3C will choose an other way soon. Meanwhile, it would be good to follow the behaviour of other browsers while the CSS Color Module Level 4 is not a W3C candidate recommendation.

What do you think about that ?

Thank you for your attention on this issue.

This is also in css-color-3 as an errata. I think you should be filing bugs on other browsers :)

+tabatkins: Other browser vendors agreed on this and it's going to stay in the specs, right?

Yes.