W3C home > Mailing lists > Public > www-svg@w3.org > November 2003

RCC question

From: Sigurd Lerstad <sigler@bredband.no>
Date: Tue, 18 Nov 2003 17:09:09 +0100
Message-ID: <009b01c3adee$4cfdd0b0$6e1273d5@mmstudio>
To: <www-svg@w3.org>

Hello,

I have a clarification question on RCC.

When a custom element has a shadow tree element. Does things work as if the
shadow tree element was there instead of the custom element, or as if the
shadow tree element was a child of the custom element?

Does it work like this:

<some_custom_elements shadow tree>
  <children of shadow tree>
</some_custom_elements shadow tree>

or like this:

<some_custom_element>
 <shadow_tree>
     <children of shadow tree>
 </shadow_tree>
</some_custom_element>

The difference is important, let's say the custom element has a transform
attribute, or some style attributes, is it the rcc components responsibility
to copy those attributes onto the shadow element or is that not necessary
since the custom element is still rendered (the second approach).

I noticed that ASV6 has a SVGCustomElement which implements SVGTransformable
and SVGStylable, so it seems they use the second approach.

I think that the first approach should be used, the main reason I think that
is it would allow using rcc not just for rendering. Consider this

<MyNamespace:DropShadow id="drop_shadow".....>

and the shadow tree element of DropShadow is a <filter> with some children.

later on:

<ellipse filter="url(#drop_shadow)" />

This will only work if it were as if the MyNamespace:DropShadow element was
replaced with a filter element (the shadow tree element).

What do you think?

--
Sigurd Lerstad
Received on Tuesday, 18 November 2003 11:08:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 5 November 2012 23:52:55 GMT