Firefox 146 Now Available With Native Fractional Scaling On Wayland (phoronix.com) 46
Firefox 146 has been released with native fractional scaling support on Wayland -- finally giving Linux users crisp UI rendering. Other new additions include GPU process improvements on macOS, developer-focused CSS features, and broader access to Firefox Labs. Phoronix reports: Firefox 146 also now makes Firefox Labs available to all users, Firefox on macOS now has a dedicated GPU process by default, dropping Direct2D support on Windows, support for compressed elliptic curve points in WebCrypto, and updated the bundled Skia graphics library. Firefox 146 also has some fun developer enhancements like support for the CSS text-decoration-inset property, the @scope rule now being supported, CSS contrast-color() function being available, and several new experimental web features. The release notes and developer changes can be found at their respective links. Release binaries are available at Mozilla.org.
Reinstate Brendan Eich NOW!!! (Score:1)
Stop the wokeness to end the brokeness.
Re: (Score:2)
That includes scaling and sensitivity.
Nobody is forced to implement their own compositor. There is a reference implementation (wlroots)
The model pairs the compositor with the display server, because it makes more sense.
99.9/100 Wayland beefs are based on ignorance and regurgitation of others' ignorance.
btw- how is HDR support coming on your X11 display?
Re: (Score:1)
Mouse input in Wayland is handled by libinput.
No.WaYlAnD iS jUsT a PrOtOcOl, remember?
"Wayland" doesn't handle the mouse input. Many compositors choose to use libinput for mouse input. This of course means that there's no standard way in Wayland to tweak things for compositors making different choices, because it's not a feature of Wayland.
The model pairs the compositor with the display server, because it makes more sense.
It does not. It's the wrong split.
99.9/100 Wayland beefs are based on ignorance and re
Re: (Score:2)
No.WaYlAnD iS jUsT a PrOtOcOl, remember?
Correct. Have you had a stroke, or is your shift key broken?
"Wayland" doesn't handle the mouse input. Many compositors choose to use libinput for mouse input. This of course means that there's no standard way in Wayland to tweak things for compositors making different choices, because it's not a feature of Wayland.
You're splitting hairs. All compositors do. The reference compositor does.
Since All do, it is sufficient to say, "Wayland does..."
It does not. It's the wrong split.
Wrong. Were I you, I'd leave this to the educated people to sort out. Or at the very least, those with functional control over their shift key.
No. Lack of standardised method for control is a big one. I am not sure if they've fixed screen recording yet. That was a shitshow for the longest time. Also, it's been what 15 years in development, but sitting down at a freshly installed latest version ubuntu machine and I find that things like meshlab don't work out of the box in Wayland.
Screen recorded is sorted as of years ago. The fact that you don't know that shows your hand- you're just here to fling shit. You couldn't give a fuck about being factually accur
Re: (Score:2)
You're splitting hairs.
Wayland's relative lack of portability compared to X is now an advantage of Wayland? No, Wayland does NOT have a standard method of control. Compositors to be ported to non Linux systems have been written using other input mechanisms.
This is not splitting hairs, it's somewhat fundamental.
Wrong.
Yeah your opinions aren't facts, buck-o. And it is indicative of a weakness of thinking that you persist in believing that.
In dB? Why?
Why not? It's perfectly cromulent and used across most of e
Re: (Score:2)
Wayland's relative lack of portability compared to X is now an advantage of Wayland? No, Wayland does NOT have a standard method of control. Compositors to be ported to non Linux systems have been written using other input mechanisms.
What non-linux system does not support libinput? It's supported on BSD, and linux. Wouldn't be surprised if there was a functional Windows port as well.
There's middle ground to be had here-
X.org is likely to have support for more input drivers than any particular Wayland compositor- I agree with that statement.
However, Wayland compositors have absolutely standardized on libinput as their input driver, and it does have very extensive support- to the point of being the only input driver used on most linux
Re: (Score:2)
> 99.9/100 Wayland beefs are based on ignorance and regurgitation of others' ignorance
That's irony right there.
Virtually every criticism of X11, that it's "inefficient" or "insecure" is based upon ignorance and regurgitation of other's ignorance. And it was that ignorance that lead it to be left unmaintained and developed for 15 years while the former devs worked instead on an awful, less efficient, replacement that only has superficial compatibility and still, today, lacks critical features - some of wh
Re:Wayland? Who cares. (Score:4, Insightful)
How well does X.org do with a dual screen system where one is 4K and the other is 1080P? For folks running laptops this sort of scenario is increasingly common, and X11 just doesn't do it very well.
I'm contemplating buying a 4K monitor and my main concern was how well X11 and the various desktop environments do hidpi. Having switched to Wayland, though, and with Firefox natively on Wayland and supporting fractional scaling, it makes the purchase a bit more comfortable.
Re: (Score:2)
How well does X.org do with a dual screen system where one is 4K and the other is 1080P?
What Problem do you have with that scenario? I find xrandr very versatile in configuring me all sorts of display combinations.
And like others wrote already: It was a brilliant idea of the X11 design to separate window managers and applications painting into windows. Really would not want to miss that.
Re: (Score:2)
I had a problem of the screen configuration resetting about a quarter of the time the system went to sleep mode or rebooted. Since upgrading to a newer version of Kubuntu that uses Wayland, I haven't had the issue.
I have a 1440p monitor paired with a weird resolution ultrawide, on a nVidia card. A few months ago I started running 2 GPUs. One monitor I have plugged into the integrated AMD GPU and the other monitor is the the nVidia card.
Wayland handled the weird configuration seamlessly. No problems with dri
Re: (Score:2)
You've tried running screens with very different dpi then? If you have a window running at hidpi on the 4k and drag it over to the 1080p, what happens? Will the app get scaled automatically (hopefully the toolkit redraws instead of everything being blurry). My understanding is X11 cannot deal with that scenario at all, xrandr notwithstanding. But I've never tried it myself. Will have a 4K monitor to test with in the new year.
Re: (Score:2)
At this point, the main problem is that for the last 15 years all development has gone into Wayland client development and X11 has stalled. It's kind of amazing that Wayland has a feature that X11 doesn't. Except...
With that said: xrandr is fine here, and the correct choice (the API, not the command line tool). Programs know which screen their pixels are on they are on and its DPI, and it's easy to query. Clients could choose to render, based on that query, but none of the toolkits implement it.
You'd need s
Re: (Score:3, Informative)
Just fine, thank you. You've just described my desktop setup for probably the last 10 years.
Re: (Score:2)
That's good to know. So you can run hipdi on the 4k with scaling (possibly fractional scaling) and normal dpi on the 1080p then? things don't get all blurry on the 1080p when X11 tries to downscale the screen?
Re: (Score:2)
You say it works just fine, but how it actually works is like shit.
You've got the DPI set to something reasonable for your small screen, and you need a microscope to read it on your 4K screen.
And that's ok- people have a right to like the pile of shit they're daily driving.
Re: (Score:2)
It's real, but I'll never have a problematic setup myself, since my eyesight is getting worse with age, I'm past the point of having use for real high dpi screens. I got a 4k eizo that's 30 inch, becau
Re: (Score:2)
Re: (Score:2)
I have no interest in a giant 4K monitor for my desk. But a 24" 4k monitor would look quite nice. I would want my font sizes to be the same as they are now, just sharper. I find sharper, higher resolution text easier to read as my eyes get older, than blurry text at the same size.
I was just thinking that although my eyes are getting older, I still can see the screen okay. Then I glanced up at the url bar in my browser and noticed I'm browsing the web at 150% zoom. Ha.
Re: (Score:2)
Re:Wayland? Who cares. (Score:4, Interesting)
I have four monitors hooked up to my graphics card. From left to right, an Acer 1920x1080 display, an LG 1920x1080 display, a Samsung 1920x1200 display, and a Dasung PaperLike e-ink display whose native resolution is 3200x1800 but which I'm software-scaling to 1600x900.
No issues whatsoever with this setup and X11.
Re: (Score:2)
Do any of those monitors use hidpi and scaling that's independent of the other monitors?
Re: Wayland? Who cares. (Score:2)
It sounds interesting to have an e-ink display as a monitor What do you use it for? Documentation? Do you find it's really better for reading from?
Re: (Score:3)
No issues whatsoever with this setup and X11.
I call bullshit, you may have no issues with X11, but you definitely had issues with the "setup". I have never managed ever on any distro with any device to get X11 to correctly identify multiple different resolution / refresh monitors correctly.
I've always gotten it to work... except for the refresh issue, but the reality is X11 is very poor at this. Bonus points if you need to scale across one monitor only. That I've never gotten to work.
Last time I used X11 I switched away from it out of frustration and
Re: (Score:2)
That's the exact problem I have. Windows does it without even asking. My second monitor is actually a 4k tv for watching movies. Supposedly you can tweak xrandr and make it work but frankly it's not worth my time.
Re: (Score:2)
Don't use xrandr directly. Use arandr which gives you a nice GUI to configure the monitors. Once you're happy with the layout, you can save it as a shell script (that under the hood does invoke xrandr) so you can replicate the setup each time you log in or each time the system boots.
Re: Wayland? Who cares. (Score:2)
I'm pretty sure both X11 and Wayland are fine with that setup. I use different sizes external monitors all the time.
Re: (Score:1)
X.org will handle the resolution differences well.
X.org won't handle well different scalings.
X.org won't handle well different _refresh rates_.
X.org won't handle HDR
Important: Wayland is not a thing, it's a protocol. Different implementations will have different feature sets.
If you want a Wayland implementation that supports all of the above: use Kwin (from KDE).
Re: (Score:2)
But network transparency- that's what we care about.
Re: (Score:2)
I see the victims of bad tech are, again, out in force and insist the bad tech is actually good tech. How pathetic.
GPU Rendering is Not Good For Battery Life (Score:4, Interesting)
The best place to hide a lie (Score:1)
dropping Direct2D support on Windows, support for compressed elliptic curve points in WebCrypto, and updated the bundled Skia graphics library
As Iâ(TM)ve always said, best place to hide cryptography tech is between two rendering technologies.
Re: (Score:2)
Compressed elliptic curve points is not some crazy secret or complex thing to be making up conspiracy theories about. The nature of elliptic curve cryptography is that knowing the curve and the x coordinate, there are literally only two possible y coordinates, and a single bit signals which of the two possible y coordinates to use, allowing you to reduce, say, 512 bits of key coordinate down to 257 (256 for the x, 1 for the y), at a trivial cost to compute y from x before doing the rest of the math.
The only
Re: (Score:2)
Re: (Score:2)
Final version isn't out yet! (Score:2)
It should be out tomorrow at 6 AM PST (USA) unless last minute issues come up which are rare.
Re: (Score:2)
As of 2025-12-09 at 00:40 UTC, it seems to have been released.
Re: (Score:2)
But not on its official public web site and internal updater. Until those offer v146, then it is not officially out.
Fractional what-now? (Score:2)
Re: (Score:2)
Also Ctrl-MouseWheel works a treat.
Re: (Score:2)
The thing is about desktop DPI. If you have two monitors with slightly different size and want the pixels to have the same size, you probably need to have fractional DPI on one of them.