191–200 of 328 posts
Earlier quoted context omitted.
Wait... GNOME only?
Yep. We've seen bugs with different window managers so WebRender is only enabled in Gnome in 84 to minimize the risk of breakage. This restriction will be removed in subsequent releases.
And for developers: https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Rel... The biggest change from my perspective is "Firefox now ensures that localhost URLs — such as http://localhost/ and http://dev.localhost/ — refer to the local host's loopback interface (e.g. http://127.0.0.1 ). As a result, resources loaded from localhost are now assumed to have been delivered securely (see Secure contexts), and also w…
Earlier quoted context omitted.
Do you have an example url for this?
Here is a bug report that shows the issue on Chrome. It is roughly 7 times slower with hardware rasterization enabled: https://bugs.chromium.org/p/chromium/issues/detail?id=114367... This particular example is only slow on Chrome. Even if you move the edge of the shape into the viewport Firefox is much faster than Chrome. But I know from real life examples that Firefox becomes slow if handling large SVGs. I will have…
Earlier quoted context omitted.
It's a fresh install and that's enabled. Let's be clear here: there is pinch to zoom. But it's an extremely half-assed implementation that is most certainly NOT native and feels terrible. I like Firefox but this has been a deal breaker for me for literally years. I don't understand why their zooming and scrolling can be so good on Android but so awful in Windows.
When you pinch does it jump between zoom levels in large increments or is it smooth? The large jumping was the old behavior – check about:config's browser.gesture.pinch settings are all empty and not mapped to ctrl+ or anything. I haven't tried on Windows but on macOS the native zoom is smooth and pretty good As a last ditch attempt you could try https://addons.mozilla.org/en-GB/firefox/addon/multi-touch-z... But if…
Huge update for users on new Apple Silicon Macs: > Native support for macOS devices built with Apple Silicon CPUs brings dramatic performance improvements over the non-native build that was shipped in Firefox 83: Firefox launches over 2.5 times faster and web apps are now twice as responsive You will need to do a browser reboot after updating to get the ARM64 version instead of the Rosetta version[1] [1] https://supp…
Earlier quoted context omitted.
The reason it's disturbing is exactly why it's good that it went away. It was a proprietary plugin supported by a single vendor, so when that vendor chooses to stop supporting it, it's gone. We've been lucky that it's been supported for so long, in that regard. Although in practice it is still hard for independent parties to implement support for all relevant open web standards, at least they are open and already hav…
Allow me to rephrase what you wrote: It's good that Flash will abruptly stop working because that will force people to stop relying on software supported by a single vendor, the problem with which is that it might abruptly stop working, which would be bad.
The "new mozillians" link in the changelog is broken, just so that if someone works at Mozilla and wish to report https://blog.mozilla.org/community/2020/12/11/the-new-faces-...
Earlier quoted context omitted.
It's not native, it's a poor, buggy implementation.
What do you mean by not native? What bugs do you see?
Bugs from a quick play-around (comparing with Microsoft Edge):
* The zoom with touch pad has a weird latency not present in Edge.
* Zoom on touchscreen is janky and jumps around.
* Zooming in and then out often (but not consistently) stops working half way through the gesture.
* Scrolling behaviour while zoomed is wildly different to native apps like Edge. Scrolling is extremely fast and has some kind of acceleration.
* Pinching while scrolling on the touchscreen lags badly.
It just feels shitty. Firefox devs don't care about a polished experience on Windows touchscreen laptops and it's a dealbreaker for me.
Earlier quoted context omitted.
Firefox is way too valuable as a hedge against Google hegemony to let die. If they ever lose the Google search money hose and become threatened I do expect a Google competitor to realize that and step in with some funding. Microsoft basing Edge on Chromium was a really stupid move on their part for this reason, and I suspect they are starting to realize it. That being said, I only expect it to be maintained at a hedg…
>Microsoft basing Edge on Chromium was a really stupid move on their part for this reason, It is not true at all. After a long time Microsoft's browser share in increasing. They probably are quite happy about it,.