Blur: Crop rectangle (Filter effects region) wrong when using stroke

Bug #1412035 reported by Frank
84
This bug affects 15 people
Affects Status Importance Assigned to Milestone
Inkscape
Invalid
Medium
Unassigned

Bug Description

1. Create line (or rect)
2. Set solid stroke with a width of 5mm
3. Set blur to 0.5%
4. Rotate by 45% to make cropping more visible

It looks like cropping doesn't take the stroke into account.
I.e. toggle stroke on/off and notice that crop rectangle doesn't change.

This seems to be a regresssion over 0.48
Tried on
Inkscape 0.91pre3 r13670 Win8 VM

Tags: filters-svg
Revision history for this message
su_v (suv-lp) wrote :

Probably related to bug #1229971 (reported earlier as bug #1188336).

tags: added: filters-svg
Revision history for this message
jazzynico (jazzynico) wrote :

Reproduced on Windows XP, Inkscape trunk rev. 13867.
Not reproduced with 0.48.5.

Test file attached.

Changed in inkscape:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
jazzynico (jazzynico) wrote :
su_v (suv-lp)
summary: - Crop rectangle wrong when using stroke
+ Blur: Crop rectangle (Filter effects region) wrong when using stroke
Revision history for this message
qubodup (qubodup) wrote :

Reproducable in Linux Inkscape 0.91 r13725 (Dec 17 2016)

Demonstration video:
https://www.youtube.com/watch?v=CuRnH1LHa94

Revision history for this message
jazzynico (jazzynico) wrote :

Confirmed on Windows XP (32-bit), lp:inkscape/0.92.x rev. 15302.

Changed in inkscape:
status: Confirmed → Triaged
Revision history for this message
vaifrax (vaifrax) wrote :

I confirm this on Windows 7 with 0.91 and 0.92.
A blur on a stroke does not seem to have the correct region for the blur filter.

Workaround: Path -> Stroke to Path

The attached file contains blurred strokes (left column, wrongly displayed) and the same objects converted to paths (right column, correctly displayed).

Revision history for this message
vaifrax (vaifrax) wrote :

PS: From playing with the XML I assume the problem is not the rendering but the incorrect computation of the filter region (as the bug title already says).

Revision history for this message
Will Pittenger (will-pittenger1) wrote :

Unfortunately, the workaround specified by vaifrax only works on paths, not clones of paths like I have. :(

In my case, the path specifies the outline, but leaves the stroke unset. I then create two clones. The first has a thin black stroke. The second, in the the background, has the blur and a wider white stroke. This effectively creates a complex stroke that SVG itself doesn't (yet) support.

Also, stroking the path makes it harder to edit down the line. You have to keep a hidden copy of the original path, locate it when it's time to edit, and restroke it.

Revision history for this message
Nathan Lee (nathan.lee) wrote :

Closing as no longer replicated in Inkscape 1.1.2 (ccedf6bf22, 2022-02-24) and Inkscape 1.3-dev (7108662a0e, 2022-04-25) with the attached example files, while it still is replicated in 0.92.5

I'm not going to dig deeper to see when the fix was introduced, but it was likely the introduction of the Automatic Region feature.

If you're concerned about editing a SVG file, Inkscape should be able to choose a filter region that displays the entire filter in Inkscape. We may consider https://gitlab.com/inkscape/inkscape/-/issues/1321 as tracking that, but as it's no longer replicated, I've closed it too.

However, if you consider this a bug about following the specs, then this is not fixed. That issue is still being tracked in https://gitlab.com/inkscape/inkscape/-/issues/2589 - filter region doesn't account for object rotations (affects fast crop filter)

Thanks for reporting this bug!

Please feel free to file new bugs about the issues you're seeing at
http://inkscape.org/report (we've more our bugtracker from launchpad to Gitlab, inkscape.org/report should redirect to the current bugtracker)

Changed in inkscape:
status: Triaged → 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.