This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html Multipage: http://www.whatwg.org/C#the-style-attribute Complete: http://www.whatwg.org/c#the-style-attribute Comment: The spec should define whether <base> affects the SVG 'fill' attribute of value url(xxx). Posted from: 58.100.161.178 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/534.52.7 (KHTML, like Gecko) Version/5.1.2 Safari/534.52.7
There is a case indicates that the value of a SVG fill attribute does not follow the <base> href: <base href="http://www.w3cgroup.com"> <svg version="1.1" xmlns="http://www.w3.org/2000/svg"> <defs> <radialGradient id="myGradient" fx="0.5" fy="0.5"> <stop offset="0" stop-color="red" stop-opacity="1"/> <stop offset="1" stop-color="blue" stop-opacity="0"/> </radialGradient> </defs> <circle cx="100" cy="100" r="35" fill="url(#myGradient)" stroke="none"/> </svg> It could be duplicated on Mac OS X 10.6.8 / Safari 5.1.2 http://www.jslab.org.cn/?tag=inconsistentBetweenFillAndBase
(In reply to comment #1) > It could be duplicated on Mac OS X 10.6.8 / Safari 5.1.2 On the other hand, Chromium nightly and Firefox nightly do honor <base> here and render this example as a black circle, which was described as "abnormal" by the original reporter. Also, I couldn't find the section where how <base> affects examples like <div style="background: url(xxx)"> is defined in the spec. ([CSSATTR] doesn't seem to mention this either.)
That is up to the SVG and CSS specifications to define. And they should take it into account. <base> simply sets the base URL for the document.
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: <http://dev.w3.org/html5/decision-policy/decision-policy.html>. Status: Rejected Change Description: no spec change Rationale: Out of scope.