Skip to content

Fix(UI): Removed canvas' blur filter clipping by expanding image bounds#8773

Merged
lstein merged 6 commits intoinvoke-ai:mainfrom
DustyShoe:Fix(UI)/canvas/expand_image_bbox_on_blur
Jan 30, 2026
Merged

Fix(UI): Removed canvas' blur filter clipping by expanding image bounds#8773
lstein merged 6 commits intoinvoke-ai:mainfrom
DustyShoe:Fix(UI)/canvas/expand_image_bbox_on_blur

Conversation

@DustyShoe
Copy link
Copy Markdown
Collaborator

@DustyShoe DustyShoe commented Jan 18, 2026

Summary

This PR improves Blur filter behavior by adding padding to applied filter. It removes sharp edges caused by clipping with image/layer bounds if blur value is greater than 4.
image
image

Related Issues / Discussions

QA Instructions

  • Extract a region of raster layer or pant a stroke on the empty layer.
  • By accessing filter menu create and apply blur with value 8 or greater.
  • Verify there's no rectangular sharp edges on blurred image.
  • Verify there's no image shifting upon applying the filter.

Merge Plan

Should be safe to merge. The changes are scoped to the canvas filter path and only affect blur behavior: padding is applied in the blur graph and placement/bbox handling is stabilized. Other filters keep the existing flow. The only notable change is the new optional usePixelBbox on image objects, but it defaults to current behavior unless explicitly set (only blur uses it).

Checklist

  • The PR has a short but descriptive title, suitable for a changelog
  • Tests added / updated (if applicable)
  • ❗Changes to a redux slice have a corresponding migration
  • Documentation added / updated (if applicable)
  • Updated What's New copy (if doing a release after this PR)

@github-actions github-actions bot added the frontend PRs that change frontend files label Jan 18, 2026
@lstein
Copy link
Copy Markdown
Collaborator

lstein commented Jan 20, 2026

@Pfannkuchensack Could you take on primary reviewer role for this one?

@lstein lstein assigned lstein and Pfannkuchensack and unassigned lstein Jan 20, 2026
@lstein lstein added the v6.12.0 Intended for 6.12.0 release label Jan 29, 2026
@Pfannkuchensack
Copy link
Copy Markdown
Collaborator

https://push.jetzt/Alex/5f194609-9e66-426e-ad4c-a71cccefb8ad.mp4
Is that something, thats needs to be fixed?

Copy link
Copy Markdown
Collaborator

@Pfannkuchensack Pfannkuchensack left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Works good.

@lstein lstein added v6.11.0 Intended for release 6.11.0 and removed v6.12.0 Intended for 6.12.0 release labels Jan 30, 2026
@lstein lstein enabled auto-merge (squash) January 30, 2026 20:54
@lstein lstein merged commit 0716b2f into invoke-ai:main Jan 30, 2026
13 checks passed
@lstein lstein moved this from 6.12.x to 6.11.x in Invoke - Community Roadmap Jan 30, 2026
dunkeroni pushed a commit to dunkeroni/InvokeAI that referenced this pull request Feb 2, 2026
Co-authored-by: Alexander Eichhorn <alex@eichhorn.dev>
Co-authored-by: Lincoln Stein <lincoln.stein@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

frontend PRs that change frontend files v6.11.0 Intended for release 6.11.0

Projects

Status: 6.11.x

Development

Successfully merging this pull request may close these issues.

3 participants