Bug 70434 – Fill color not applied inside visited links

• Status: RESOLVED
• Resolution: FIXED
• Component: SVG

[Richard Cyganiak]

Created attachment 111662 [details]
Test case: filling of elements inside visited versus unvisited links

There's a problem with the filling of descendants of an <a> element whose xlink:href URL has been visited.

They are always filled black; the actual specified fill is ignored.

See attached test case. I expect both circles to be filled green, but the one whose xlink:href is visited (it's the current document) is filled black instead.

[Philip Rogers]

I suspect this is a regression caused by http://trac.webkit.org/changeset/97638

[Philip Rogers]

Created attachment 116864 [details]
Fix for fill color not being applied inside visited links

[Antti Koivisto]

Comment on attachment 116864 [details]
Fix for fill color not being applied inside visited links

Good catch!

[WebKit Review Bot]

Comment on attachment 116864 [details]
Fix for fill color not being applied inside visited links

Clearing flags on attachment: 116864

Committed r101452: <http://trac.webkit.org/changeset/101452>

[WebKit Review Bot]

All reviewed patches have been landed.  Closing bug.

[Itsy Bitsy]

Hey y'all!

I'm a bit of a n00b when it comes to implementing bug fixes. I am a front-end web developer and was curious as to how i implement the patch for my site. I am having the black svg issues on a circle within an <a> tag. I tried putting the source file in my root folder for the site (still local on my desktop for further development). It just started doing this today - please help!

[Philip Rogers]

(In reply to comment #6)
> Hey y'all!
> 
> I'm a bit of a n00b when it comes to implementing bug fixes. I am a front-end web developer and was curious as to how i implement the patch for my site. I am having the black svg issues on a circle within an <a> tag. I tried putting the source file in my root folder for the site (still local on my desktop for further development). It just started doing this today - please help!

This is already in Chrome dev channel and will hit Chrome beta channel soon (and Chrome stable shortly after that). If you'd like to test with the patch in, just grab Chrome dev channel. It's not something end users can really do themselves but it will automatically roll out as your favorite WebKit implementation updates (Chrome, Safari, etc)--usually on the order of months.