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

Re: Applying SVG properties to non-SVG content

From: Robert O'Callahan <robert@ocallahan.org>
Date: Sat, 12 Jul 2008 10:30:18 +1200
Message-ID: <11e306600807111530o5791ef15ma4a689f1d92fe4ad@mail.gmail.com>
To: "David Hyatt" <hyatt@apple.com>
Cc: "Bert Bos" <bert@w3.org>, "www-style@w3.org" <www-style@w3.org>, www-svg <www-svg@w3.org>
On Sat, Jul 12, 2008 at 10:14 AM, David Hyatt <hyatt@apple.com> wrote:

> On Jul 11, 2008, at 5:04 PM, Robert O'Callahan wrote:
> If you're talking about the element-as-background extension, I haven't
> written down a proposed spec for that yet. But when I do, it will also
> ignore clip, opacity and other effects on the ancestors of referenced
> elements. Is that surprising? I can't think why you'd want it any other way.
> I believe it might be surprising if you intended to use the feature to do
> say reflections or thumbnails.

I don't think so. Normally a reflection would be drawn in a sibling element,
or at least nearby in the DOM and thus likely to be clipped by the same
ancestor. For thumbnails you usually don't want to see clipping performed by
ancestors; for example you might want to show thumbnails of slides that are
scrolled out of view. If you want clipping to be shown, you would normally
just make the clipping ancestor the element-as-background.

Do you have a specific problematic scenario in mind?

"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
Received on Friday, 11 July 2008 22:30:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:54:19 UTC