Earlier quoted context omitted.
As a Mac/iPhone user the only thing that sort of breaks seamless is that Apple doesn't allow you to define a custom default browser on iPhone. I have Firefox in the dock on iPhone and it's really great but random links, e.g. via messaging, get opened by Safari first.
On iOS/iPadOS _all_ browsers are using Safari's webkit engine to render. That goes for FF on iOS, that goes for Chrome on iOS - it's all webkit.
Firefox 72.0
101–110 of 543 posts
Re: Firefox 72.0
#102My favorite browser since 2017. I don't miss Chrome for anything.
Re: Firefox 72.0
#103Re: picture in picture - anyone else here think that this feature doesn't belong to a browser? It just seems so... erm... random, basically. Looks like something that was cloned from some other product and rather crudely shoehorned in. At the very least it should have been introduced after an update and given an option to opt-in to using it, rather than automatically enabling it without any notice.
A native media player with youtube-dl is still king for power users.
Re: Firefox 72.0
#104Okay, so I don't really post to HN and this may seem like a silly complaint but Firefox's management of theming just seems off to me. I use macOS, I don't fiddle about with my wallpaper very much and so this stains Firefox's top bar with an ugly brown tint. I could switch to the light theme, however when I do so Firefox no longer respects my system change to dark mode. Does anyone else get bothered by this? Is there…
If I'm reading your correctly you'd like to set FF to the light theme (or any theme) but continue to have dark mode pages? about:config browser.in-content.dark-mode true should do that.
Re: Firefox 72.0
#105Interestingly the beta for 73.0 [1] includes NextDNS as a second choice for DNS over HTTPS providers as well as Cloudflare. [1] https://www.mozilla.org/en-US/firefox/73.0beta/releasenotes/
How do I make sure that Mozilla is respecting my OS DNS settings and not using DNS over HTTPS at all?
If you just want to know how to toggle it normally in case something goes weird with one of the changes it's in the network settings part of the settings page.
Re: Firefox 72.0
#106Earlier quoted context omitted.
Are you a devtools user? How do the Firefox ones compare? I speak as someone who originally switched to Chrome (having been a Firefox user since the Phoenix days!) specifically for the devtools — it's pretty much the biggest factor in my browser choice.
Sadly, the performance inspector is still pretty useless compared to what Chromium is offering.
Re: Firefox 72.0
#107For a moment I thought they had done this for the cookie and privacy notices. Oh how that would be amazing to move that functionality into the browser.
Re: Firefox 72.0
#108Can anyone advise how far away hardware accelerated video on Linux might be?
https://security.stackexchange.com/questions/13799/is-webgl-...
TLDR: if js gets direct control of GPU, it can read/modify present and past screens.
Maybe after Wayland implementations get good enough, distributions will make hw acceleration work securely with wayland compositors, probably years? Just guessing.
Playing video on youtube is easy, but performance sucks due to bloated youtube website. Performance of the same video URL in empty page with video player is much better, close to that in video player with CPU only.
If you need GPU acceleration, you can use something like youtube-dl or mpv to play videos on a URL in a video player.
Re: Firefox 72.0
#109Too much trouble to debug it so I opted to switch instead.
Re: Firefox 72.0
#110My biggest gripe with Firefox is how it opens tabs. If I open a new tab in Chrome, it opens just to the right of the current one which is nice because it keeps related tabs together. In Firefox it opens to the far right which is annoying. I tried installing an extension to fix this but it was buggy. Only recently did I discover that I could dig into about:config to enable the behavior I consider expected (and I'm sur…
I already updated to v.72 so I don't know if they changed the default, never really noticed before. But now browser.tabs.insertRelatedAfterCurrent defaults to 'true'. I agree this is expected behavior :)
Edit - default for this config variable could be platform specific; the above is based on Windows 10. I'll check on my MacBook tonight.