Re: Applying SVG properties to non-SVG content

On Wed, Jul 9, 2008 at 11:24 PM, Ash Searle <> wrote:

> 2008/7/9 Robert O'Callahan <>:
> > The best vendor-prefix option I can see is to introduce a new CSS value
> > -moz-url() which is just like url() except that paint servers specified
> with
> > -moz-url() work on non-SVG content and paint servers specified with url()
> > don't, and -moz-url() clip-paths, masks and filters work on non-SVG
> content
> > but url()s don't. That somehow seems daft, but I could probably be talked
> > into it.
> I don't see the point in a new prefix.  It would be nice if all the
> properties
> that took url() values all followed the 'cursor' specification - but
> I'm not sure
> how much of a problem that would cause this far down the line:
>   <uri>
>   The user agent retrieves the cursor from the resource designated by
> the URI. If the user agent cannot handle the first cursor of a list of
> cursors, it should attempt to handle the second, etc. If the user
> agent cannot handle any user-defined cursor, it must use the generic
> cursor at the end of the list.
> That comment could easily be generalised to background-image and other
> url()-based values.

That can't work with backgrounds since it conflicts with CSS3 multiple

"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 Wednesday, 9 July 2008 18:13:01 UTC