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

Re: [css3-images] Using SVG Paint Servers as <image>

From: Robert O'Callahan <robert@ocallahan.org>
Date: Fri, 15 Jul 2011 16:36:03 +1200
Message-ID: <CAOp6jLbo8iGK7USWaWjW99jtcS-9tAeuQXOX0Ls9VYPsHB+JmA@mail.gmail.com>
To: Alan Gresley <alan@css-class.com>
Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, www-style list <www-style@w3.org>
On Fri, Jul 15, 2011 at 12:15 AM, Alan Gresley <alan@css-class.com> wrote:

>  Also, would this then mean that you could reference
>>> arbitrary elements from external pages (presumably same-origin
>>> restricted)?
>> Yes, you can in Firefox at the moment.
>> I've come full circle on this, in a way.
> Can you clarify what you mean by coming full circle? Is this for or against
> your recent suggestion regarding element() also taking a url?

The rest of the paragraph clarifies that. If url() can be used like
element(), then element() need not take a URL.

I don't quite follow Roc. What behavior is the same when an element(id) and
> url(#id) are referring to the same element. To my understanding, this can
> only happen in a xmlns:svg document like in your example on your weblog [1].

I don't understand the question.

As I follow (I have little knowledge of <canvas>), we can have this.
> <style>
>  h1 { background-image: element(two); }
>  p { background-image: url(http://external.com/**bucket.svg#bar<http://external.com/bucket.svg#bar>);
> }
> </style>
> <h1 id="one">Heading</h1>
> <p id="two">Paragraph</p>
> Does this cross same-origin restrictions?


"If we claim to be without sin, we deceive ourselves and the truth is not in
us. If we confess our sins, he is faithful and just and will forgive us our
sins and purify us from all unrighteousness. If we claim we have not sinned,
we make him out to be a liar and his word is not in us." [1 John 1:8-10]
Received on Friday, 15 July 2011 04:36:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:02 UTC