Clipping renders object invisible in browsers

Bug #1019159 reported by Erik Nigro on 2012-06-29
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
High
Unassigned

Bug Description

Eye clip is rendered invisible when viewed in a browser: https://dl.dropboxusercontent.com/u/64054017/New%20folder%20%282%29/PetiteFleur.svg *Link updated due to issue being addressed.

Issue line highlighted by a more tech savy friend: http://i.imm.io/uovE.png , apparently " path3071 shouldn't be within a clippath"

OS is Windows 7 x64, being viewed in the latest Chrome, Firefox, and IE browsers. Created on Inkscape 0.48.2

Erik Nigro (eriknigro) on 2012-06-29
description: updated
su_v (suv-lp) on 2012-06-29
tags: added: clipping
su_v (suv-lp) wrote :

Attaching reduced test case: possible trigger seems to be a disagreement about the clip-path itself (a group of 4 paths).

Reproduced with Firefox 12.0 Safari 5.1.4, Opera 12 and Chromium 22.0.1189.0 on OS X 10.7.4
Only Squiggle (Batik 1.7) agrees with Inkscape (0.48.x, current trunk).

tags: added: svg
su_v (suv-lp) wrote :

> (…) a disagreement about the clip-path itself (a group of 4 paths).

Setting bug status to "Confirmed" for now -> needs further investigation (which renderers are correctly interpreting the current SVG specification).

Changed in inkscape:
status: New → Confirmed
su_v (suv-lp) wrote :
su_v (suv-lp) wrote :

Another variation of the reduced test case: Clipping also works in browsers if the four paths describing the clip-path are not nested inside a group inside the <clipPath> definition (they don't have to be unioned into a single path).

su_v (suv-lp) wrote :

See also:
* Bug #1441152 “Create Clip Group generates invalid SVG”
  https://bugs.launchpad.net/inkscape/+bug/1441152

su_v (suv-lp) wrote :

As discussed on irc in the context of bug #1441152, the SVG specification does not allow <g> as child element(s) of a <clipPath> element:
«A ‘clipPath’ element can contain ‘path’ elements, ‘text’ elements, basic shapes (such as ‘circle’) or a ‘use’ element. If a ‘use’ element is a child of a ‘clipPath’ element, it must directly reference ‘path’, ‘text’ or basic shape elements. Indirect references are an error (see Error processing).»

Inkscape OTOH does create <clipPath> elements which may contain groups (<g>) - such clippings do not conform to the SVG specification and AFAIU other SVG renderer seem correct in not rendering the clipped elements at all.

Changing Importance to 'High' (inkscape creates non-conforming SVG when clipping with a group of paths).

su_v (suv-lp) on 2015-05-09
Changed in inkscape:
importance: Undecided → High
Erik Nigro (eriknigro) on 2015-05-10
description: updated
Erik Nigro (eriknigro) wrote :

Should be noted viewing through IE now renders the original SVG properly.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers