W3C home > Mailing lists > Public > www-style@w3.org > July 2008

Re: Applying SVG properties to non-SVG content

From: Robert O'Callahan <robert@ocallahan.org>
Date: Mon, 14 Jul 2008 14:38:19 +1200
Message-ID: <11e306600807131938k35ce7312sc8fe14f8f67f0b11@mail.gmail.com>
To: "Robin Berjon" <robin@berjon.com>
Cc: "Bert Bos" <bert@w3.org>, "www-style@w3.org" <www-style@w3.org>, www-svg <www-svg@w3.org>
On Sun, Jul 13, 2008 at 9:39 AM, Robin Berjon <robin@berjon.com> wrote:

> Processing of fragments (especially the parts IMHO of most relevance to
> Robert's spec) can be found by plodding around starting from FuncXMLRI:
> http://www.w3.org/TR/SVGMobile12/types.html#DataTypeFuncXMLRI.
>

By the way there's a significant problem in this spec:
http://www.w3.org/TR/SVGMobile12/linking.html#ReferenceRestrictions

> *A:* Reference a fragment within the current SVG document fragment<http://www.w3.org/TR/SVGMobile12/intro.html#TermSVGDocumentFragment>(e.g. "#someelement").
>

What if the reference is coming from an external CSS stylesheet? URLs should
be interpreted relative to the stylesheet, so normally we'd expect
#someelement to be an element in the stylesheet, which is of course
nonsense, but anyway it conflicts with the SVG spec here. We could
special-case a lone fragment identifier to say it refers to that element of
the styled document, but that seems a little ugly. I don't care myself but
it will need to be addressed.

Rob
-- 
"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
53:5-6]
Received on Monday, 14 July 2008 02:38:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:55:10 GMT