Re: Clip & shaped borders + error/ambiguity in spec

Matthew Brealey wrote:
> 
> There is definitely a need for more shapes. However,
> rather than defining clip: hexagon/triangle or
> whatever, it seems that the logical solution is to
> define clip: polygon{Xa, Ya, Xb, Yb, Xc, Yc ...},

Which still restricts you to closed polygons, requires you to deal with
self intersection, and rules out smooth curves (Beziers, NURBS, and so
on).

> Having dealt with polygons, it remains only to deal
> with ovals.

I wouldn't say "only"

My proposal:

clip: url(url-for-some-shape.svg)