Live data from Hacker News

Firefox 74

mozilla.org

91–100 of 269 posts

Re: Firefox 74

#91
post #14

The Facebook container is great, but I wish there was an option for the built-in Multi-Account containers to work this way. I've been doing what the Facebook Container extension does, but with built-in containers, and the experience is very clunky. The two biggest issues are that I can't give the container a list of domains beforehand and say "everything under google.com should open here". I have to go to each Google…

Apart from those 2 issues, a smaller annoyance but I really wish 'Reopen in Container' would just reuse the tab. At least I've personally not once felt the need to keep the original tab open.

Re: Firefox 74

#92
post #17

A new Firefox release, a new reminder that Firefox hasn't implemented native context menus in macOS for 20 years.

I reckon it's the only thing I use on macOS that even has a context menu. What's wrong with it? Or is it just that it doesn't look like those in... whatever you're using that also has them (Numbers.app et al. maybe?)?

Re: Firefox 74

#93
post #40
post #14

The Facebook container is great, but I wish there was an option for the built-in Multi-Account containers to work this way. I've been doing what the Facebook Container extension does, but with built-in containers, and the experience is very clunky. The two biggest issues are that I can't give the container a list of domains beforehand and say "everything under google.com should open here". I have to go to each Google…

I use FF, I don't use FB, but I still think this is wrong. Browser is not a place to decide which companies are good and which are bad. As much as I despise Facebook I still don't think it's fair. "I disapprove of what you say, but I will defend to the death your right to say it". All companies should have the same access to the technology in user's browser. Favoring Google by Chrome seems no different than blocking…

Even it were true, which is not, Facebook had been anything but fair to its users (and non users) in case you didn’t get a chance to follow the news. Since Mozilla is all about user’s privacy and safety online and Facebook is such a huge menace than it actually makes sense to offer a targeted solution. But again, it’s just an implementation of a container, nothing specific to Facebook.

Re: Firefox 74

#94
post #68

Eagerly awaiting a Firefox release that improves power consumption on Mac to a point where it is at least close to competitive with Safari. That, plus the rumors that iOS will soon allow 3rd party default browsers and I'm all in Firefox for sure.

restricting all browsers to use safari is the single killer feature that made me stick with ios. If I blacklisted a website in control center it is respected in all browsers even in private mode.

Requiring all third party browsers to honor those settings is something I could see Apple doing.

Re: Firefox 74

#95
The 74 release says "New: Facebook container..."

Do they mean the facebook container addon will come as standard, pre-installed with 74 or do they only mean they updated the addon? Little bit confused, feels a bit strange if they meant the later (under the new firefox release), but a at the same time when I updated 73 to 74 I could not see any traces of the "facebook container" in 74, no added addon. Is it meant fb container should should be like an pre-installed addon?

Re: Firefox 74

#96
post #22

I wish they’d fix Lockwise on iOS. Not really working. In my case takes ages to open when set as default, and never auto suggests login for the active site, either from Firefox or any other app.

Why use lock wise over say. 1password or LastPass ?

Re: Firefox 74

#97
post #54

Earlier quoted context omitted.

How is this tantamount to deciding which companies are good and bad? Mozilla have simply identified an extremely common way people are tracked online and are doing their best to contain it.

Same rules should apply to everybody. You should be able to decide some rules, even heuristics that can catch tracking across multiple sites and suggest user to disable it rather than pointing to entity and applying different rules to it than to everybody else.

No, they shouldnt. Everybody isnt the problem, its large scale privacy destroying services that are the problem.

Singling out facebook and google would absolutely be correct actions, and making it more obvious to users how to do that is a net good.

Re: Firefox 74

#98

It says a lot that there's a new feature bullet for Facebook alone. I wonder if at some point Firefox is going to be so effective at hampering FB's goals that FB decides it needs to be crushed

[deleted]

Re: Firefox 74

#99
post #14

The Facebook container is great, but I wish there was an option for the built-in Multi-Account containers to work this way. I've been doing what the Facebook Container extension does, but with built-in containers, and the experience is very clunky. The two biggest issues are that I can't give the container a list of domains beforehand and say "everything under google.com should open here". I have to go to each Google…

> whenever I click a link on Gmail that goes to Github, Github opens in the Google container Google intercepts clicks and redirects them through a Google Domain to track clickthru. If you're in Gmail and hover over a link it will show the actual destination but onclick your browser opens a mail.google.com URL that redirects to the destination URL.

This is the real problem in my opinion. The URL shown in the status bar should always match the URL which is opened after clicking on the link. Anything else is deception.

I don't know how you'd enforce it at the browser level because obviously there are tons of legit uses for modifying a link on click... but it should be enforced somehow.

Re: Firefox 74

#100
post #28

Earlier quoted context omitted.

I think it's tracked under https://bugzilla.mozilla.org/show_bug.cgi?id=1604492 It's still open, but it seems people haven't been able to hit the bug on the last few nightlies (this is also my experience), so it's possible the bug was quietly fixed as a side effect of some other patch.

Programming can be so easy: "Oh hey, it fixed itself!" Programming can be so hard: "So then what was the bug?"

You can bisect to try and figure out where exactly the bug "fixed" itself. Not easy with a bug that can't be triggered reliably, of course.
Post reply on HN