Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Firefox 64 Released

hacks.mozilla.org

Post reply on HN
Print view View original

231–240 of 527 posts

Re: Firefox 64 Released

#231

Post by daleharvey »

MrRadar wrote: post #189
mancerayder wrote: post #180

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…

Get uMatrix and block Media requests globally, then whitelist on a per-domain basis. That should "fix" auto-playing videos for you permanently.

This is built in to Firefox now, the change to the preferences the OP is talking about was implementing that feature.

Re: Firefox 64 Released

#232

Post by pmoriarty »

iod wrote: post #117
pmoriarty wrote: post #66

Earlier quoted context omitted.

I'm not. Wayland lacks a lot compared to X.[1] From the linked-to-post, it lacks: * Programmatic output configuration (xrandr, arandr, etc.) * CLI clipboard access (xsel, xclip) * Third party app launcher/window switcher (rofi, dmenu, albert, docky). * Clipboard managers (parcellite, klipper, Gpaste, clipman, etc.) * Third party screen shot/capture/share (shutter, OBS, ffmpeg, import, peek, scrot, VNC, etc.) * Color…

Those things are mostly compositor specific and not specifically a Wayland issue. For example with Sway: ​ * Programmatic output configuration swaymsg -t get_outputs # get displays swaymsg output DP-1 pos 0 0 res 1920x1080 # set displays ​ * CLI clipboard access swaymsg -t get_clipboard ​ * Third party app launcher/window switcher I use gnome-panel with Xwayland, but better than nothing ​ * Third party screen shot/ca…

As OP in the thread I linked to above says:

"GNOME and KDE have dbus APIs for some (but not all) of these things, and sway has its own IPC, and other compositors probably have similar solutions. However, they all use different mechanisms, which means that if you are writing say, screenshot application you either have to write a different backend for every compositor, or choose just one or two to support.

"Something all of these types of applications have in common is they need to be able to inspect and/or modify state from other applications or the compositor itself. Which wayland's security model normally prevents. I think a major gap in wayland, is having a way for an application to run with escalated permissions so it can have access to other applications. Unfortunately, I don't have any great ideas on what that would look like."

and then, later in the thread:

"for simple things using the compositor's screen shot tool is fine. But what if I don't like the screenshot tool for my compositor of choice? My experience with the GNOME screenshot tool (granted this was pre-wayland) was that it wasn't as good as, say, shutter, which has a lot of options, let's you easily crop and edit the screenshot from inside the screenshot tool etc. And then swaygrab doesn't even (currently) have an option to capture a rectangular region."

The entire thread linked to above is worth reading.

My own takeaway is that Wayland is just way too immature to compete with X for my power-user use cases.

It might be ok for users with simple needs.

Re: Firefox 64 Released

#233

Post by nothrabannosir »

daleharvey wrote: post #228
nothrabannosir wrote: post #225

Earlier quoted context omitted.

Even for YouTube?

Yes, we dont have any whitelist / blacklist of sites we treat differently

That's.. big. Congratulations on managing to stay true to the numbers, and out of corporate influence. And thank you.

Re: Firefox 64 Released

#234

Post by yason »

mancerayder wrote: post #180

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…

Autoplay is the last straw, I'm at the verge of migrating to Firefox for my primary browser because it seems Chromium just can't keep those damn videos from playing and more often than not the videos seem to steal keyboard too. When space, shift-space, arrow up and down stop working because of a element that's a good point to decide the browser is broken.

Re: Firefox 64 Released

#235

Post by trulyrandom »

sprash wrote: post #203
mixmastamyk wrote: post #105

Earlier quoted context omitted.

I'm happy someone is using it however, as that will encourage many shortcomings to be addressed.

In my experience X11 has zero shortcomings compared to Wayland. The code might be ancient and arcane at some points but the performance and features (hello "ssh -X") are actually far superior. Why do we need Wayland?

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.

Re: Firefox 64 Released

#236

Post by acdha »

jillesvangurp wrote: post #197
acdha wrote: post #174

Earlier quoted context omitted.

I use only Macs by default. It runs great and has for years. There's probably a real issue somewhere but it's far from as universal as your post implies.

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.

Re: Firefox 64 Released

#238

Post by AnIdiotOnTheNet »

kiriakasis wrote: post #126
dman wrote: post #106

Earlier quoted context omitted.

This is a fascinatingly coercive take on the privacy / observability tradeoff.

No, this is supporting direct feedback. How can mozzila know which features are useful in your opinion? how should they know that you wanted [feature X]? Maybe they are also in the wrong if the telemetry is excessive, but the alternative is to never deprecate any feature ever.

They could ask.

Re: Firefox 64 Released

#239

Post by cpmsmith »

jillesvangurp wrote: post #220
jasin wrote: post #104

Earlier quoted context omitted.

In my case, CPU usage goes to the roof if I use a scaled resolution instead of the default one. If that is the case with all macOS users with non-default resolution, I wouldn't call it low prevalence.

Not an issue for me. I have a imac 5K and a retina mac book pro. Both with image scaling on by default. I think most recent macs have retina now. I use Firefox exclusively and have done so for the last 2 years or so. This sounds like it could be a driver issue for specific macs. Both my macs have AMD Radeon chipsets & quad core i7s. Anyway, I'm sure this issue is real. Bugzilla ticket numbers probably exist for it an…

Anecdotal, but I've found it happens when image scaling by a factor other than 2. Affects my setup of a 4K display at 2650x1440 effective resolution, or 1.5x scaling.

Re: Firefox 64 Released

#240

Post by nine_k »

nine_k wrote: post #127
fao_ wrote: post #33

Earlier quoted context omitted.

> but this addon promises to restore it Mozilla did the same with tab groups, then the addon was abandoned. The replacement that is compatible with the new form of extension isn't able to unload the tabs, just hide them, which undoes most of the performance benefits. [abraham simpson voice] It'll happen to you too! [/abraham simpson voice] /jk

FWIW, Tree Style Tab solved tab groups (and more) for me. I wish tab handling had a first-class API in Firefox, so that different tab managers could interact with the default tab menu, etc.

Also:

Firefox 64 introduces an entirely new API, browser.menus.overrideContext, which allows complete customization of the context menu shown within add-on content like sidebars, popups, etc.

This is illustrated right in the post by my favorite pain point, the Tree Stye Tab custom tab menu mixing with the regular tab menu.

Finally!

Post reply on HN