- From: Dirk Schulze <dschulze@adobe.com>
- Date: Tue, 23 Oct 2012 08:19:09 -0700
- To: "robert@ocallahan.org" <robert@ocallahan.org>
- CC: "www-style@w3.org list" <www-style@w3.org>
On Oct 23, 2012, at 7:54 AM, Dirk Schulze <dschulze@adobe.com> wrote: > > On Oct 23, 2012, at 5:17 AM, "Robert O'Callahan" <robert@ocallahan.org> wrote: > >> On Sun, Oct 14, 2012 at 2:51 PM, Dirk Schulze <dschulze@adobe.com> wrote: >> As conclusion, I wonder why CSS4 Images can't support SVG fragment identifiers directly: >> >> background-image: url(image.svg#gradient1); >> >> The code paths to load an SVG document as an image and an SVG document to provide an external resource such as a paint server are quite different, in Gecko at least. We need to know when we start loading the document which situation we're in. With your syntax, we can't know until the document is loaded. We use the presence of element() to signal that we're in the external resource situation. > I wonder how you deal with fragments on SVG images then. > > url(test.svg#anyID) works on Firefox. Do you already assume that you may just render the referenced element? And that this element is a graphical element? Btw. you will run into the same problem with the 'fill' and 'stroke' properties. Both will take a paint server reference and a <image> value in SVG 2. (Resolved during the last SVG F2F.) This is why it makes more sense to be consistent IMO. Greetings, Dirk > > Dirk > >> >> Rob >> -- >> “You have heard that it was said, ‘Love your neighbor and hate your enemy.’ But I tell you, love your enemies and pray for those who persecute you, that you may be children of your Father in heaven. ... If you love those who love you, what reward will you get? Are not even the tax collectors doing that? And if you greet only your own people, what are you doing more than others?" [Matthew 5:43-47] >>
Received on Tuesday, 23 October 2012 15:20:09 UTC