W3C home > Mailing lists > Public > www-svg@w3.org > February 2012

Re: Allowing <mask>, <clipPath> etc. to target their parents

From: Brian Birtles <birtles@gmail.com>
Date: Wed, 22 Feb 2012 11:32:25 +0900
Message-ID: <4F4453B9.4070402@gmail.com>
To: www-svg@w3.org
Hi Erik,

Thanks for your feedback.

(2012/02/21 20:24), Erik Dahlstrom wrote:
>> font -> <font> ?
>
> The font property shorthand? It uses font-family names, not id's.

Yes, the use case I had in mind was:

   <g font="child">
     <font>
       ... font def ...
     </font>
     <text/>
     <text/>
   </g>

But I think it's not very useful, especially given the state of SVG 
fonts. So I propose not touching the font property.

>> <font-face-uri xlink:href> -> <font>
>
> The font-face-uri element is how to reference external font content
> sure, but you can already put svg font content directly in <font-face>
> without using the <font-face-uri> element.

Yeah, this one doesn't make much sense. Sorry about that.

>> For properties we could have:
>>
>> clip-path: <funciri> | none | inherit | child
>> If it's 'child', it means "find the first child element that is a
>> <clipPath> and use that."
>
> For the case where there is more than one child <clipPath> element what
> you are proposing is different from how e.g feComponentTransfer [1]
> handles the same case (rationale in [3]). It is however similar to how
> <title> is chosen, and I think it's better to align with <title> here.

Ok, I agree. It sounds like the only reason feComponentTransfer differs 
is because it followed what implementations were doing at the time.

> I quite like the proposed syntax.

Thanks! Actually, I think the credit goes to both you and Cameron anyway :)

> The foreignObject element in SVG Tiny 1.2 is actually already using the
> scheme you are proposing, where if xlink:href is missing you render the
> children[3]. Note that invalid values in xlink (a broken link etc) do
> not affect the choice, it's only whether the attribute was specified or
> not, same as for the animation elements.

Yes, if we add xlink:href to foreignObject in SVG 2[1] it should follow 
this scheme.

I also agree that it's the presence of the attribute that matters.

Thanks Erik!

Brian

[1] 
http://www.w3.org/Graphics/SVG/WG/wiki/SVG2_Requirements_Input#the_xlink:href_attribute_on_.3CforeignObject.3E
Received on Wednesday, 22 February 2012 02:32:57 GMT

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