macOS Tahoe 窗口调整大小 – 故事仍在继续
Resizing windows on macOS Tahoe – the saga continues

原始链接: https://noheger.at/blog/2026/02/12/resizing-windows-on-macos-tahoe-the-saga-continues/

最近的macOS 26.3更新最初似乎修复了一个博文中强调的窗口调整大小问题。测试应用程序证实了候选发布版中的修复,显示调整大小区域现在正确地遵循了窗口圆角半径——这是对先前方形区域的改进。然而,这项改进也带来了一个缺点:仅垂直/水平调整大小的区域明显变薄,增加了错过点击的机会。 令人惊讶的是,最终的macOS 26版本*移除了*这个修复,恢复到了最初的、存在问题的方形调整大小区域。苹果也更新了发布说明,将该问题状态从“已解决”更改为“已知问题”。 基本上,虽然最初承认了这个问题,但苹果最终发布了一个没有预期解决方案的版本。

Hacker News 的讨论强调了 macOS 窗口调整大小的 frustation。一位被分配使用 MacBook 的 Windows 用户发现这个过程出乎意料地繁琐——实现简单的屏幕布局(例如在 Slack 和浏览器之间分割屏幕)比在 Windows 上花费的时间更长,因为缺乏自动吸附功能。 用户报告需要手动调整窗口大小,他们觉得这个过程不直观。虽然有一些解决方法,例如使用第三方窗口管理器应用程序(如 Rectangle),但总体而言,macOS 上的窗口体验被描述为“笨拙”且与 Windows 中易用性相比显得奇怪。主要抱怨集中在期望基本的窗口拖动就足以调整大小和定位。
相关文章

原文

macOS 26.3, Release Candidate

In the release notes for macOS 26.3 RC, Apple stated that the window-resizing issue I demonstrated in my recent blog post had been resolved.

I was happy to read that, but also curious about what had actually changed.

So I wrote a little test app.

It performs a pixel-by-pixel scan in the area around the bottom-right corner of the window, hammering it with simulated mouse clicks to detect exactly where it responds to those clicks (red), where it’s about to resize (green), where it’s about to resize vertically or horizontally only (yellow), and where it doesn’t receive any mouse events at all (blue).

And indeed, the window resize areas now follow the corner radius instead of using square regions:

So that’s definitely better!

But unfortunately, as you can see, the thickness of the yellow area – used for resizing the window only vertically or horizontally – also became thinner. The portion that lies inside the window frame is now only 2 pixels instead of 3.

In total the thickness went down from 7 to 6 pixels, which is a 14% decrease, making it 14% more likely to miss it.

macOS 26.3, Final Release

When the final version of macOS 26 was released I was curious if Apple might have further refined the implementation. So I performed the scan once again. But to my big surprise, the fix was not only unrefined – it was completely removed! So we are now back to the previous square regions:

And in fact, the release notes have also been updated: the problem went from a “Resolved Issue” to a “Known Issue”.

联系我们 contact @ memedata.com