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

Re: Applying SVG properties to non-SVG content

From: Robin Berjon <robin@berjon.com>
Date: Mon, 14 Jul 2008 22:56:59 +0200
Cc: www-style@w3.org, www-svg <www-svg@w3.org>
Message-Id: <B999C199-DFD5-4AB4-8E6C-56DD5DAE856A@berjon.com>
To: robert@ocallahan.org

On Jul 14, 2008, at 04:38 , Robert O'Callahan wrote:
> 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  
> (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.

AFAIK that limitation is only applicable to SVG Tiny, which doesn't  
support CSS. I can't find the same limitation in the full SVG so I  
wouldn't expect conflict (but I might have missed it).

-- 
Robin Berjon - http://berjon.com/
Received on Tuesday, 15 July 2008 07:56:35 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:39 GMT