- cross-posted to:
- firefox
- cross-posted to:
- firefox
You must log in or register to comment.
Long live Firefox and high praises to all those who develop, maintain and package it.
Release notes: “Firefox now defaults to the Wayland compositor […] It is also a known issue that windows are not correctly placed when restoring a previous session on launch.” I had been led to believe that one of Wayland’s strengths was solving the correct window coordinates save-and-restore problem. Does someone know what happened here?
I had been led to believe that one of Wayland’s strength was solving the correct window coordinates save-and-restore problem. Does someone know what happened here?
It’s literally the opposite. Windows aren’t allowed to position themselves on Wayland (because it’s unsafe or something). Window state save restoration must implemented by the compositor itself. Not sure about GNOME, but KDE doesn’t have that.
because it’s unsafe or something
It’s one of those bits that haven’t been done yet. The protocol extension is being discussed as there are a lot more different use-cases than one would think and a number of ways to do it. Wayland is great but nothing is perfect and this is one of its weaknesses: evolving it takes time as we’re afraid of getting it wrong.
Better this way honestly
Sure, it’s hard to craft a perfect solution. However the status quo for a long time was that applications were doing it themselves. And Wayland took it away without providing a replacement.
Window state save restoration must implemented by the compositor itself. Not sure about GNOME, but KDE doesn’t have that.
Actually KDE has a feature where you can set which display any app shows on, and if it should be maximized horizontally or vertically or both.
I use that for Firefox specifically, as I always like it on my secondary monitor.
Just right click on the title bar of any application to get to those settings.
(I’m using KDE on Fedora.)
Long live Firefox!
don’t forget to get ublock origin along with it!
Been using it forever. It’s the best browser despite Google sabotaging it and making it slower on their sites.
waiting for Firefox 127.0.0.1 release…
my dad has always been using firefox, and he was right. at first i used chrome, then firefox for a bit, then opera gx. and i still came back. sometimes sticking with ol’ reliable is best.
Recently it’s become even better and more stable. I don’t ever find a need to open another browser at this point.
It’s been years since I am trying to use Firefox on my Android phone but I always get the error “This website requires a secure connection” when surfing the Internet, even major websites. I have tried many times to understand why this keeps happening and it’s so frustrating that I always end up deleting the app. Can anyone help? I would love to use Firefox on my phone.
I know that is something with the certificate validation you should check what it says. I mean I know what can cause this but those cases are weird, like having the time/date wrong or having a mitm attack and you are getting not the real cert. But I don’t expect that to be it.
You might want to open settings and then turn “HTTPS-Only Mode” off. Though if it has been a couple of years since you last tried, it’s also not unlikely that most sites will just work now, if that was indeed the culprit.
(Also, if you’re the type of person who dials all the privacy protections up to eleven, you might want to hold off on doing that until you’ve seen everything working just fine, so you know whether those options were the problem.)
Oh, and another thing you could try is going into the app settings in Android, then under Storage and cache tap “Clear storage” and “Clear cache” (or similar options in another place if you’re on a different version of Android). This to ensure you didn’t have old settings that were interfering.
@sachamato @hal_5700X I have used Firefox on my Android phone for years. Never had that issue and everything is on default. Do you use a VPN? Of so, could you disable it and see if that fixes it?
Thanks for all the suggestions. Turns out that it was an ad blocker issue colliding with filtering HTTPS. After disabling it and making some configurations, mozilla is up and running on my Android device. Today is a happy day!
I’ve had problems with this version of Firefox. Whenever I open a new window, it always opens my old tabs that I’ve previously closed, even though the option is disabled in the settings. Anyone else have that problem?
Where are they up to in the cycle of “gradually patching the UI so it’s usable/throwing out the entire UI for a piss poor redesign” these days?
