Resizing a window that's been snapped?

After recently moving to KDE Neon - I’ve discovered that windows that have been snapped have had their drag-to-resize disabled until you pull that window out of the snap and place it back.

Is there a setting to disable this somewhere? I don’t know how to search for this issue because I don’t know the proper terminology to search.

My usual workflow for arranging desktop windows is to drag them to the left or right so they snap to half of my ultra widescreen monitor. Often, after snapping I need to resize the windows a little as I don’t want a perfect half for every window - but snapping gets me 99% of the way there.

What you’re running into is caused by KDE Plasma’s newer Quick Tile behavior introduced around Plasma 5.27 and continued into Plasma 6.x.

Older Plasma versions behaved more like classic Windows Aero Snap: snapping a window to the left or right edge was mostly just a temporary positioning shortcut. After snapping, the window still behaved like a normal floating window and could be resized independently without affecting future snaps.

Modern Plasma changed this behavior.

Quick-tiled windows now participate in a persistent split-layout system managed by KWin. Once two windows are snapped side-by-side, KWin treats them as connected tiled regions rather than completely independent floating windows.

Because of that:

  • resizing one snapped window also resizes the adjacent snapped window,
  • shared borders become linked or “magnetic,”
  • modified split ratios are remembered,
  • future quick-snapped windows reuse the modified ratio instead of resetting to exact 50/50,
  • and snapped windows no longer behave like freely floating windows until detached from the tiled state.

This is exactly why your workflow feels awkward.

Your workflow is:

1. snap a window,

2. get roughly the right placement,

3. manually fine-tune the width afterward.

Modern Plasma instead assumes:

1. snap a window,

2. maintain a persistent tiled relationship afterward.

That design difference is the root of the issue.

A particularly important KWin regression report documented this exact behavior:

after resizing a quick-tiled window once, all future quick-tiled windows inherit the modified split ratio instead of returning to equal halves.

Other users also repeatedly reported:

  • windows becoming “glued together,”
  • inability to independently resize snapped windows,
  • persistent asymmetric layouts,
  • quick-tile layouts affecting other desktops/workspaces,
  • and ultrawide monitor workflows becoming significantly less practical.

Current workarounds people commonly use include:

  • dragging the window slightly away from the edge first to detach it from the tiled state,
  • resetting tile layouts manually,
  • deleting custom tiles from the Meta+T tiling editor,
  • disabling edge tiling behavior,
  • using Meta+drag or Meta+right-click resizing,
  • or avoiding persistent tiling workflows entirely.

However, none of these fully restore the older “snap first, freely resize afterward” behavior from pre-5.27 Plasma.

The issue is fundamentally tied to KWin’s newer tiling-oriented design philosophy rather than a simple resize bug.

(post deleted by author)

Upon further investigation, I’ve discovered I was wrong in what I thought it does.

When I snap dolphin into a tile, I can resize it at will. But when I snap firefox into a tile, I cannot resize it.

Is this fixable?

I think the behavior is actually application-specific rather than a general KWin tiling limitation.

Dolphin, Konsole, and most KDE/Qt applications resize correctly while tiled because they properly expose resize regions and cooperate with KWin’s tiled-window handling.

Firefox is different.

This appears to be related to Firefox’s client-side decorations (CSD) implementation on KDE Plasma, especially under Wayland. Multiple upstream reports describe the exact same symptoms:

  • tiled Firefox windows refusing normal edge resizing,
  • resize handles detaching or untile-ing the window,
  • incorrect detection of KDE tiled states,
  • and inconsistent behavior compared to native KDE applications.

Mozilla and KDE bug reports suggest Firefox does not fully detect or integrate with KWin’s quick-tile state correctly yet, particularly when CSD/titlebar modifications are involved. This also explains why Dolphin behaves normally while Firefox does not.

Things that commonly affect the issue:

  • Firefox running under Wayland vs X11,
  • “Hide title bar” / custom Firefox titlebar,
  • GTK client-side decorations,
  • Plasma version (5.27+ and 6.x changed tiling behavior significantly).

The easiest thing to test is:

Firefox → Menu → More Tools → Customize Toolbar → enable “Title Bar”.

Several users reported that immediately restores normal resize behavior on KDE. There are also upstream Mozilla bugs specifically tracking KDE tiling/CSD problems.

So the original assumption about Plasma’s persistent tiling behavior was only partially correct — Plasma’s newer tiling system does change resize semantics, but Firefox additionally has its own compositor/CSD integration problems on KDE that make the behavior much worse than with native KDE apps.

At this point, I’d classify it as: Firefox + KDE integration issue exposed by Plasma’s newer tiling model, not purely a KWin design issue.