This isn't something to complain about, IMO. Chromium is a popular app and it is a good thing to see work on supporting FDO protocols and improving Wayland support. I prefer Firefox myself, but it's nice that Linux support isn't just an afterthought for Google either and more importantly it trickles down to the countless apps on Linux that depend on Chromium in some form (usually through Electron). I personally use several, including but not limited to Slack, Discord, r2modman and VSCodium.
Yeah, I mean Google caring about Linux isn't exactly breaking news. We knew that already. Android and ChromeOS both exist and as web company they kinda have to care about the OS that by and large runs the web. But this is Phoronix and they'll make articles about anything as long as they think as it'll get engagement. "Chromium" and "Wayland" are pretty good buzzwords as far as that goes, thus this article. My point is more so that maybe it isn't productive to have every acknowledgment of Chromium's continued existence be overwhelmingly negative regardless of context.
Cool, while a lot of people are complaining. For those of us that still keep a chromium based browser around for the those few times where you need compatibility. These small improvements are very much welcome.
This is about dragging a tab out of or into a browser window, and letting the compositor know about it, so it can move and place the window accordingly. Apps don't get to place windows themselves.
I used to do apps with QT (as well as with Java) and when creating a window, I only needed to say, "new window of that preferred size please", then the engine would make the window of that size if possible.
Now, maybe QT did things more in depth behind the scene, I don't know.