261–270 of 527 posts
I've tried to find an extension for FF that does this, but so far I was unable to find one.
Earlier quoted context omitted.
Right. Well I'm referring to always turning it off, and the option very specifically is: media.autoplay.default if 0, then it's on. if 1, then it's off. 2, I'm not sure.
pref("media.autoplay.default", 2); // 0=Allowed, 1=Blocked, 2=Prompt https://dxr.mozilla.org/mozilla-central/source/browser/app/p...
What's the status of the cat and mouse game being played with autoplay video being forced on and new options needing to be hunted down? First Chrome forced it on, because EvilCorp's business model is around a forced-open-eyelid philosophy of advertising revenue from unstoppable impressions. Next I moved to Firefox, which in an update a few months ago changed the autoplay option to be on, removed the config attribute…
Some things I've been looking forward to: > Easier performance management: The new Task Manager page found at about:performance lets you see how much energy each open tab consumes and provides access to close tabs to conserve power > Improved performance for Mac and Linux users, by enabling link time optimization (Clang LTO). (Clang LTO was enabled for Windows users in Firefox 63.) Release Notes: https://www.mozilla.…
What's the status of the cat and mouse game being played with autoplay video being forced on and new options needing to be hunted down? First Chrome forced it on, because EvilCorp's business model is around a forced-open-eyelid philosophy of advertising revenue from unstoppable impressions. Next I moved to Firefox, which in an update a few months ago changed the autoplay option to be on, removed the config attribute…
I introduced the change to 0,1,2. Not sure what happened when we first introduced autoplay but the change to 0,1,2 was so we could let users switch between enabled, disabled and ask the user. Original plan was to ask the user by default. We did some user testing with this change and it looks like we will be changing it to block by default based on feedback Not sure what this has to do with any companies ad revenue, o…
I already had to deal w/ increased complaints from users due to scripts no longer being able to start the video in Chrome when the user hasn't interacted with the DOM yet. The only warning was an error in the development console. Users would get incredibly confused because they'd join the room and "lurk", i.e not interact w/ chat or the site, and then they'd be left wondering why everyone is commenting on the video when their's hasn't started playing.
I realize autoplay gets a lot of flak due to large corporations using it to further their aggressive marketing campaigns, but there are legitimate use cases out there which you will be breaking w/ a block-by-default policy. I'd urge you to reconsider ask-by-default, or at least allow scripts to have some sort of API whereby they can ask the user for permission ahead of time.
This just really sucks, because it's hard to communicate these sorts of things to my userbase which has wildly varying degrees of technical competency. It's also unfortunate to, essentially, need relay the message "some organizations (ab|mis)used this useragent functionality, so now nobody gets to use it."
Earlier quoted context omitted.
Likewise. Not aware of any weird issues with performance in relation to Firefox. I use it exclusively. I'm on the beta channel. I can't remember the last time I had a browser crash. I generally restart it to apply new updates every few days or so. If you have performance issues; you might want to check whether you need to blame the browser or some of your extensions.
Seconding your last point — almost every time I've had someone complain about generic Firefox or Chrome performance the problem went away as soon as they restarted it without extensions. There are certainly exceptions but misattribution is common enough that I'm not surprised to see browser vendors adding the UI to make it easier to discover.
This is a known issue, and has been around since at least v57. There are multiple Bugzilla issues on it. The cause is known. It isn't extensions. The fix is just invasive, and apparently ongoing.
I hope multi-accounts containers will land soon on Android. The phone is where I feel the least in control of what's happening on the browser.
Earlier quoted context omitted.
I have never been able to get a tearing-free experience with X11, and I've tried everything to fix it. Meanwhile Wayland is butter smooth out of the box on the same hardware. Security is another obvious advantage of Wayland.
Just another data point: I've never experienced screen tearing in the decades that I've used X. Also, when I run X just for myself on my own laptop, what security issues do I have to worry about with X that I don't have to worry about with Wayland?
With regards to security, the main issue is that X11 provides no isolation between applications, allowing them to listen to keystrokes and the clipboard at all times. With Wayland, only focused applications have this access.
Earlier quoted context omitted.
Time for FF's balance of configurability and reasonable defaults to shine: the about:config properties to edit are `layout.css.scrollbar-color.enabled` and `layout.css.scrollbar-width.enabled`.
I am pretty sure that changing it would be a bad idea if you care about your privacy.
I really wish they would implement tab stacking, that is the feature that I really miss from the old Opera, here is a video of how it looks in case you don't know: https://www.youtube.com/watch?v=VWpJvg8icmM I've tried to find an extension for FF that does this, but so far I was unable to find one.
1. rebuild the UI from scratch
2. rebuild basic tab handling behaviour from scratch
3. build tab stacking on top of that
4. (ideally) hide Firefox's existing tab bar
And there's two issues with the above steps:
(a) 4 hasn't been possible with the new extensions API sofar (it was in progress last I checked, maybe it's possible now)
(b) the dev effort required is big, so results have not been very polished sofar
they're getting there though
On the other hand, if you want to try something resembling that as-yet-unsurpassed 2010 UI today, Vivaldi is working on replicating it natively.
I'm never keen to recommend Vivaldi because it's (a) closed source, which is why we don't have Opera anymore and (b) it's Blink, and we need diversity there. But it's a very good browser otherwise.