"Added settings in about:preferences to stop websites from asking to send notifications" Been waiting for this one.
Sites have been replacing the actual API request with a HTML5 overlay, precisely because of this - only when clicking "notify me" does the actual permission get requested, with the requisite dialog. (The rationale is "once the permission is denied, there's no way to bring it up again; a dismissed HTML5 box can be brought up again an infinite number of times") As for me, I went for WebAPI Manager, which blocks most of…
Firefox 59 released
121–130 of 233 posts
Re: Firefox 59 released
#122Re: Firefox 59 released
#123Earlier quoted context omitted.
That's unfortunate. I finally gave up on Firefox as my main browser when 57 came out, and one of the big reasons was that so many of the useful extensions that had set Firefox above other browsers for me were broken and didn't have good replacements. In some of those cases, my understanding is that you can't currently write a direct replacement because the new API doesn't support the required functionality. I was rea…
> That's unfortunate. I finally gave up on Firefox as my main browser when 57 came out, and one of the big reasons was that so many of the useful extensions that had set Firefox above other browsers for me were broken and didn't have good replacements I never really understood this argument, you gave up Firefox since you could no longer have your XUL/XPCOM extensions in favor of serious browsers who have less WebExt…
And lets not ignore the fact that most sites are designed with Chrome as their intended target. FF simply doesn't work as well on many sites.
Re: Firefox 59 released
#124Earlier quoted context omitted.
> That's unfortunate. I finally gave up on Firefox as my main browser when 57 came out, and one of the big reasons was that so many of the useful extensions that had set Firefox above other browsers for me were broken and didn't have good replacements I never really understood this argument, you gave up Firefox since you could no longer have your XUL/XPCOM extensions in favor of serious browsers who have less WebExt…
Mozilla took away perfectly good functionality and gave existing fans a big middle finger while doing so. Although I am a fan of Mozilla, it is entirely understandable to me why someone wouldn't want to keep using their products. And lets not ignore the fact that most sites are designed with Chrome as their intended target. FF simply doesn't work as well on many sites.
Re: Firefox 59 released
#125Although its a minor thing, I'm personally delighted with drag & drop for the new tab tiles. These are the kind of little usability improvements that can tip the finely balanced scales between major browsers these days.
Re: Firefox 59 released
#126While websites do render fast, the UI is not very responsive, whether its laggy typing into the address bar [1] or the crawling devtools.
Re: Firefox 59 released
#127Sadly, still unusable for me since the Quantum update. A clean install and profile, no add-ons, and google.com/maps (for example) will max out my cpu. There must be some bug related to old hardware and OS (Macbook Pro 2009 + 10.11.x) or more people would be experiencing this.
Re: Firefox 59 released
#128Earlier quoted context omitted.
I don't know why you are being downvoted. I have the same problem. I'm still stuck with Firefox 56 and no upgrade path in sight. I wish Mozilla declared FF 56 a LTS release for those of us who value their addons more than performance benefits of Quantum. Right now I'm still using an out-of-date release that doesn't receive critical security updates, and I have to choose between either downgrading 4 releases down to F…
Which are the addons you're missing? Do they have a GitHub site?
Bug 1318532 had a patch submitted which provided a WebExtensions-compatible API which would allow the original implementation to work, but this was spiked permanently because of :reasons: The developer, DW-dev has been gamely trying to provide similar functionality via implementing a browser-managed tiling window manager, but this seems doomed to failure since it is at the mercy of the display rendering on the target OS. For example, on MacOS, a massive shadow is rendered around an active window, which thus renders over the top of a neighboring tiled window.
Doubt this one will get fixed ... unless Chrome implements it. Right now the objective seems to be full Chrome "compatibility" and Chrome doesn't have it.
Re: Firefox 59 released
#129Is allow client side decorations available yet in about:config? It was in a fedora release about 2 months ago, and it was removed because it wasn't in mainline. I have the title bar disabled for now, but that's broken in it's own way(dragging doesn't work right).
Should be part of Firefox 60.
Re: Firefox 59 released
#130https://www.androidpolice.com/2017/09/26/project-quantum-enh...