Linked-Offset displayed incorrectly

Bug #167278 reported by Tavmjong
2
Affects Status Importance Assigned to Milestone
Inkscape
Invalid
Medium
Unassigned

Bug Description

Linked-Offsets that have been modified are displayed
incorrectly by Firefox and Squiggle.

0.43+svn

Draw a star. Create a linked offset. Distort star.
In Inkscape, the offset will change with the distorted
star. Firefox and Squiggle show offset with original shape.

Revision history for this message
Tavmjong (tavmjong) wrote :
Revision history for this message
Rwst (rwst) wrote :

I confirm this bug report. the output from the batik-based
editor GLIPSGraffiti-1.3 and from firefox is apparently
identical, and both are different from the inkscape one.

Revision history for this message
Tavmjong (tavmjong) wrote :

Originator: YES

Problem still present with 0.45+SVN.

Revision history for this message
ScislaC (scislac) wrote :

Tested with fresh SVN copy (0.45+svn 12/20/07) on Linux. Same result.

Changed in inkscape:
status: New → Confirmed
Revision history for this message
ScislaC (scislac) wrote :

Is the issue originally reported where it says it's displayed incorrectly by Firefox and Squiggle accurate or is Inkscape doing something incorrect? Chrome and rsvg agree with Firefox as well.

Revision history for this message
Tavmjong Bah (tavmjong-free) wrote :

Wow, action on an eight year old bug report!

Inkscape is not updating the calculated path data correctly ('d'). This bug still exists in trunk (0.91).

I've just tested Opera (Presto), Chrome, Firefox, Squiggle, and rsvg. All render the test image the same way and correctly according to the path data ('d' attribute).

The file contains three paths. One path is an offset linked to another path that itself is an offset of a path that is a star. I've tested that the problem exists even with one level of linked offset.

Inkscape 0.48 is generating a crazy path for the outer-linked path while trunk (0.91) is doing something more reasonable.

A copy of the original path data is being saved. This should not be necessary as the data is available from the linked path. Perhaps this was to allow reuse of the code from 'Dynamic Offset'.

Each path is linked via 'xlink:href' and 'inkscape:href'. 'xlink:href" is being misused; it has a definite meaning in SVG however, removing it breaks the linking in 0.48 and trunk. 'inkscape:href' does not appear to be used in either 0.48 and trunk but this is the correct way the paths should be linked. The test file dates back to 0.43. As it contains 'inkscape:href', we should be able to delete the 'xlink:href' and only use the 'inkscape:href' without breaking content.

Revision history for this message
mray (mrayyyy) wrote :

Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new
bug tracker on GitLab, and closed it here.

Please feel free to file new bugs about the issues you're seeing at
http://inkscape.org/report.

Moved to: https://gitlab.com/inkscape/inbox/issues/322
Closed by: https://gitlab.com/mray

tags: added: bug-migration
Changed in inkscape:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.