W3C home > Mailing lists > Public > public-fx@w3.org > July to September 2015

Re: SVG image security restrictions

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 15 Sep 2015 11:27:59 -0700
Message-ID: <CAAWBYDBQ7wDW6Mb55mLW6O3ikmhRpsT5A42QfZ4GOdoyy=Kqdg@mail.gmail.com>
To: "Robert O'Callahan" <robert@ocallahan.org>
Cc: "public-fx@w3.org" <public-fx@w3.org>, www-style <www-style@w3.org>
On Mon, Sep 14, 2015 at 5:42 PM, Robert O'Callahan <robert@ocallahan.org> wrote:
> On Tue, Sep 15, 2015 at 12:26 PM, Tab Atkins Jr. <jackalmage@gmail.com>
> wrote:
>> We've switched url() over to a function, so we can add arguments to it.
>
> Doesn't url(A, B) currently mean "try A, and if that doesn't work try B"?

Nope, it currently means nothing and is invalid.  You're thinking of
the image() function.

On Mon, Sep 14, 2015 at 5:53 PM, Zack Weinberg <zackw@panix.com> wrote:
> I wonder how often what authors *really* want is the ability to pass
> parameters to the SVG (a la this old WD:
> http://www.w3.org/TR/SVGParamPrimer/ )

That's a separate topic; they both mention the word "parameters", but
in totally different contexts.  (But yes, once rebased to be based on
CSS variables, that's also very desirable.)

~TJ
Received on Tuesday, 15 September 2015 18:28:49 UTC

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