Bug 95083 - Setting 'color' CSS property by script doesn't update values using 'currentColor'
Summary: Setting 'color' CSS property by script doesn't update values using 'currentCo...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: SVG (show other bugs)
Version: 528+ (Nightly build)
Hardware: Macintosh OS X 10.8
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2012-08-27 06:58 PDT by Antoine Quint
Modified: 2014-05-12 23:30 PDT (History)
5 users (show)

See Also:


Attachments
test case (664 bytes, image/svg+xml)
2012-08-27 06:58 PDT, Antoine Quint
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Antoine Quint 2012-08-27 06:58:25 PDT
Created attachment 160711 [details]
test case

In the attached testcase, I have a <linearGradient> element and I set its "color" CSS property dynamically in a script ran after the DOMContentLoaded fires. The <stop> elements of the <linearGradient> all have their "stop-color" value set to "currentColor" via a CSS rule, and yet that color doesn't change when the parent element's "color" CSS property is updated via script. The testcase works if either of those is true:

1. "color" on <linearGradient> is set statically
2. the <stop> elements have their "stop-color" property set to "currentColor" via the inline "style" attribute instead of a CSS rule.
Comment 1 Antoine Quint 2012-08-27 07:00:50 PDT
rdar://problem/12179192
Comment 2 Dirk Schulze 2014-05-12 07:27:12 PDT
There was a fix for this issue in Blink lately. pdr, do you know the CL for it still?
Comment 3 Philip Rogers 2014-05-12 23:30:06 PDT
This may have been fixed with https://src.chromium.org/viewvc/blink?view=rev&revision=164726?

In general, "git log -S currentColor" is your friend :)