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.
To be fair, it would be weird for Google NOT to support Linux, as I believe they use Debian Testing internally.
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.
To be fair to Phoronix, I hardly think they’re the worst offender in Linux space; I find their Linux coverage to be the least terrible online. They cover new kernel and software developments pretty well.
Other Linux-focused sites seem to mostly consist of clickbait “Ditch Windows 11 headlines”, fleeting Linux apps, explaining something that there are already vast amounts of quality articles for, and/or thinly-veiled advertisements.
That is not to say Phoronix is perfect; I don’t necessarily enjoy having to run my ad blocker there. However, it’s not like it’s different on other sites. Comparatively, I find Phoronix to be a decent quality Linux outlet.
Chromium can fuck off. FF is king.
Yeah, I want my passwords unencrypted in the browser, where they belong!
Eh?
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.
I don’t understand what is the point of this. Isn’t it the job of the WM to position windows and stuff? Apps have to do it themself now?
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.
How can a window manager position things if the program doesn’t communicate with it correctly?
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.
I kind of think that’s QTs whole deal right? An abstraction layer that allows for devs to not get stuck in the weeds implementing it all manually.
If Qt or Java is doing it, then that’s still your program and not the WM, though?
In those cases, I agree. But for a tiling window manager like w3m, I don’t see the application having a say in position and location. Hence I didn’t think that the app has so much to do with creating windows. Just my thought.
