W3C home > Mailing lists > Public > www-style@w3.org > October 2012

Re: Ambiguities in fill:url() / stroke:url() syntax

From: Dirk Schulze <dschulze@adobe.com>
Date: Sun, 28 Oct 2012 15:26:41 -0700
To: "robert@ocallahan.org" <robert@ocallahan.org>
CC: "Tab Atkins Jr." <jackalmage@gmail.com>, www-svg <www-svg@w3.org>, www-style <www-style@w3.org>
Message-ID: <2ACB44A6-4486-4AFB-8460-116758773C19@adobe.com>


Sent from my iPhone

On Oct 28, 2012, at 10:06 PM, "Robert O'Callahan" <robert@ocallahan.org<mailto:robert@ocallahan.org>> wrote:

On Mon, Oct 29, 2012 at 2:40 AM, Tab Atkins Jr. <jackalmage@gmail.com<mailto:jackalmage@gmail.com>> wrote:
In that case, as long as we're *able* to head off SVG Stacks at the
pass, I'm cool with your alternate approach, suitably expanded to
disallow all things that *look* like MFs in step a (that is,
everything with an ident followed by an = sign).

Can we simplify it to just exclude =, ( and ) characters from external resource references? That also excludes functional syntax like SVG 1.1 cooked up for svgView(). It also gives SVG Stacks users a workaround: use identifiers such as "=bar" in their images.

How will we know if we're "able to head off SVG Stacks"? I'm not entirely comfortable with just disabling them in Firefox without a commitment from other browser vendors to do the same.

Firefox supports it, opera supports it, won't take to long for WebKit to have fragments either. And there is already use of fragments, which makes it harder to restrict fragments at this time. (Filter Effects use them). It doesn't make sense to restrict them, just because we have a use case in mind where we could use a workaround. After all we mainly have fragments for resources, why would they still be allowed to use any fragment? Unless I did not misunderstand the proposal (may did not get all emails), I don't think this is a good idea at this point.


> By the way, if someone created an document foo.svg with a paint server
> element whose ID is "xywh=0,0,10,10", how would your magical approach treat
> url(foo.svg#xywh=0,0,10,10)? :-)

I think SVG agreed recently (dunno if it's made it into the SVG2
draft) that we'll restrict the syntax of fragment identifiers to
disallow all MF-looking things from referring to elements.

I didn't know that. I don't see anything about it in the SVG2 draft. That is important since it could interact with what we're trying to do here.


It does not, nor were there plans to do so.

Greetings,
Dirk


Rob
--
“You have heard that it was said, ‘Love your neighbor and hate your enemy.’ But I tell you, love your enemies and pray for those who persecute you, that you may be children of your Father in heaven. ... If you love those who love you, what reward will you get? Are not even the tax collectors doing that? And if you greet only your own people, what are you doing more than others?" [Matthew 5:43-47]

Received on Sunday, 28 October 2012 22:27:15 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:21:01 GMT