ISSUE-2287

empty_clippath

Consider clarifying empty clipPath behaviour

State:

CLOSED

Product:

SVG Full 1.1

Raised by:

Erik Dahlström

Opened on:

2009-06-30

Description:

We might want to consider clarifying the behaviour for how empty clipPaths affect what they're applied on. And also how display and visibility affect children of <clipPath> when generating the clippath.

Some cases to consider (all tested by [1]):
a) <clipPath> with no children
b) <clipPath> with children that have display="none"
c) <clipPath> with children that have visibility="hidden"
d) does clip-path="url(#brokenlink)" mean everything is clipped, or nothing is clipped?

Testresults for [1] in order a,b,c,d:
Safari 4:    x, y*, x, y
Opera 10:    x, x,  x, y
Firefox 3.5: x, x,  x, x
Batik 1.7:   y, y,  y, f

x) clips all
y) clips nothing
f) error dialog
*) visibilty=hidden children contribute to clippath

[1] http://dev.w3.org/SVG/profiles/1.1F2/ua-tests/clippath-empty.svg

Related Actions Items:

• ACTION-2628 on Erik Dahlström to Add these decisions to the 1.1SE spec, and make the clippath example into a test case - due 2009-07-08, closed

Related emails:

1. SVG/profiles/1.1F2/master changes.html,1.40,1.41 masking.html,1.10,1.11 (from cvsmail@w3.org on 2009-07-02)
2. Minutes, 01 July 2009 SVG WG telcon (from cam@mcc.id.au on 2009-07-01)
3. Minutes, 01 July 2009 SVG WG telcon (from cam@mcc.id.au on 2009-07-01)
4. Agenda, July 1 2009 SVG WG telcon (from ed@opera.com on 2009-06-30)
5. Agenda, July 1 2009 SVG WG telcon (from ed@opera.com on 2009-06-30)
6. ISSUE-2287 (empty_clippath): Consider clarifying empty clipPath behaviour [SVG Full 1.1] (from sysbot+tracker@w3.org on 2009-06-30)

Related notes:

No additional notes.

Display change log