Closed
Bug 306674
Opened 20 years ago
Closed 10 years ago
SVG clipPath in symbol not interpreted
Categories
(Core :: SVG, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 353575
People
(Reporter: domob, Unassigned)
References
Details
(Keywords: testcase)
Attachments
(1 file, 1 obsolete file)
607 bytes,
image/svg+xml
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20050828 SeaMonkey/1.1a
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20050828 SeaMonkey/1.1a
A svg:clipPath element, which is defined inside a symbol-element, can't be
referenced (isn't applied); moving it out of the symbol (into defs), it works.
As clipPath is allowed in the content model of symbol (at least in the SVG 1.1
Recommendation), I suppose it should be allowed there.
Reproducible: Always
Steps to Reproduce:
Open the sample file, which is the same as that of Bug 193825, except that it
uses symbols & references.
Actual Results:
No clipping is done.
Expected Results:
The clipPath should be applied.
Reporter | ||
Comment 1•20 years ago
|
||
This is the same test case as for Bug 193825, except that the rectangle &
clippath are defined inside a symbol which is referenced later. Moving the
clipPath element one level up (making it a child of defs) it works.
Comment 2•20 years ago
|
||
I CONFIRM this bug.
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20050912
Firefox/1.6a1
![]() |
||
Comment 3•18 years ago
|
||
This is still present on trunk, but I'm not sure how valid/useful it is to have a <clipPath> _inside_ a <symbol>, or whether we really care to use up time allowing that.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 4•18 years ago
|
||
Is this too time expensive?
I work as gr. designer and I can imagine using such construction...
![]() |
||
Comment 5•18 years ago
|
||
What stops you putting the <clipPath> outside of the <symbol> instead of inside?
Comment 6•18 years ago
|
||
Nothing :)
But, I think if this is not prohibited by the SVG standard
http://www.w3.org/TR/SVG11/masking.html#ClipPathElement
we should allow designers create such construction...
otherwise we will cause compatility problems... by my opinion.
Updated•16 years ago
|
Assignee: general → nobody
QA Contact: ian → general
Comment 7•16 years ago
|
||
Seems to work now both in trunk and in Firefox 3.6.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
Comment 8•16 years ago
|
||
Actually it doesn't work. Previous releases didn't clip at all. 3.6 and above now clip everything regardless of what the clip path should clip.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
The attached .zip contains a .svg that contains 2 implementations of a clip-path use, both should render the same way. A PNG of how it should look after the 2 intersections are done is also included.
Comment 10•15 years ago
|
||
Comment 9 is unrelated it is bug 534612 which is fixed on the trunk.
Updated•15 years ago
|
Attachment #440115 -
Attachment is obsolete: true
Updated•10 years ago
|
Status: REOPENED → RESOLVED
Closed: 16 years ago → 10 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•