惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Jina AI
Jina AI
大猫的无限游戏
大猫的无限游戏
T
Tailwind CSS Blog
酷 壳 – CoolShell
酷 壳 – CoolShell
WordPress大学
WordPress大学
Last Week in AI
Last Week in AI
Hugging Face - Blog
Hugging Face - Blog
阮一峰的网络日志
阮一峰的网络日志
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
人人都是产品经理
人人都是产品经理
V
V2EX
博客园 - 叶小钗
雷峰网
雷峰网
小众软件
小众软件
量子位
V
Visual Studio Blog
H
Hackread – Cybersecurity News, Data Breaches, AI and More
The GitHub Blog
The GitHub Blog
Martin Fowler
Martin Fowler
G
Google Developers Blog
博客园_首页
博客园 - Franky
有赞技术团队
有赞技术团队
宝玉的分享
宝玉的分享

no.heger

The struggle of resizing windows on macOS Tahoe – no.heger
Resizing windows on macOS Tahoe – the saga continues – no...
norbert · 2026-02-13 · via no.heger

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”.