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

On Mon, Oct 29, 2012 at 2:40 AM, Tab Atkins Jr. <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.

> 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.

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]