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

What's New with Firefox 142

mozilla.org

Post reply on HN
Print view View original

131–139 of 139 posts

Re: What's New with Firefox 142

#131

Post by 1vuio0pswjnm7 »

everdrive wrote: post #53

I'm genuinely perplexed why people find link previews useful. The page image is too small to really see, and it's not as if rapidly opening and closing a tab actually takes effort. It may be faster than the long click depending how comfortable you are with keyboard controls. I have other questions as well -- does the link preview ignore your plugins? So if you loaded the web page, would uBlock Origin prevent tracking…

It seems like Firefox (Mozilla) looks for any excuse to make an HTTP request

I can't think of another software program I have ever seen that makes so many non-user-initiated, i.e., automatic, HTTP requests by default; some of this behaviour cannot be disabled

Of course the default telemetry is infamous

Re: What's New with Firefox 142

#132

Post by captainepoch »

samtheDamned wrote: post #122
captainepoch wrote: post #120

So... Nothing really useful or what users are asking for a long time... And we then ask why people aren't using Firefox...

Tab groups is pretty useful. My partner refused to try firefox in the past because it didn't have tab groups and now they're able to use it as their main browser.

It's useful, but it's a meaningless feature.

We've been asking for a good JS and HTML engine, faster than what Firefox uses, and for better compatibility with websites (there are webs that don't work properly with Firefox). And to not put the Manifest V3 into Firefox (which it's done already, besides we still have uBlock Origin working as intended, for now, because nobody knows what's going to happen with that in the future).

And I think that's way more important that being able to group tabs.

Re: What's New with Firefox 142

#133

Post by saagarjha »

Y_Y wrote: post #102
saagarjha wrote: post #18

Earlier quoted context omitted.

It's that Safari implemented support for it. Firefox added their own version and chose to give it a different affordance

> You keep using that word, I do not think it means what you think it means. - Inigo Montoya This is no affordance. There's nothing the design of either browser that suggests you can obtain a link preview by those actions, you just have to be told what action to take beforehand.

What part of long pressing a link is discoverable to you

Re: What's New with Firefox 142

#134

Post by tripletpeaks »

dydkgbufxuf wrote: post #101
beng-nl wrote: post #88

Earlier quoted context omitted.

I remember the original reasoning for creating Firefox (first Phoenix) was to create a more lightweight and faster version of the Mozilla browser, which initially was true.

a big part of making it lightweight wasn't stripping away browser bits, but stripping away non-browser bits. mail, newsgroups, irc. mozilla (the suite) was a lot more than a browser.

The browser bit was also much, much snappier than anything else in common use, except maybe Opera. Including the Mozilla browser.

Performance took a giant hit some time in the 1.x series and never recovered, but before that, it was remarkably lightweight and snappy, so much so that normal people would notice.

Re: What's New with Firefox 142

#135

Post by TheNewsIsHere »

mantra2 wrote: post #69
someone4874726 wrote: post #31

Earlier quoted context omitted.

Have been using FireFox Relay for a couple of years now and can coun't the amount of sites which have denied my signup on a single hand.

I'd say that's lucky. I'm using "Masked Email" on Fastmail with a personal domain and I still find that I get blocked from signups from time to time. I assume they're looking for some sort of pattern?

In the alternative, you can configure Fastmail to allow sending and receiving to/from a wildcard address (which for sending allows you to specify the sending address at send time). In my experience this works far more reliably, and is one of the features that pushed me to move to Fastmail many years ago.

Re: What's New with Firefox 142

#136

Post by TheNewsIsHere »

mdaniel wrote: post #100
mantra2 wrote: post #71

Does Firefox still block clipboard history apps from accessing private windows with no way to turn it off? Haven't used Firefox since that change.

Friend, do I understand that you're mad that private windows don't allow the system to introspect what content you're viewing in a private window? BTW, in the spirit of being helpful: if you're using private windows just for 'fresh session' behavior, Firefox offers two other knobs for that outcome: Profiles and Containers. In Chrome I'm with you that Incognito can be a very cheap way to login to a site multiple times…

Firefox Profiles are useful, but not nearly as useful as their analogue in other browsers. Same with containers.

I use both, but I try to use profiles very sparingly because you have to relaunch Firefox, which is at times unrealistic.

Re: What's New with Firefox 142

#137

Post by TheNewsIsHere »

mdaniel wrote: post #129
mantra2 wrote: post #128

Earlier quoted context omitted.

I am, yes. It worked as I described up until I think October of last year. I’m logging in and out of client accounts - often for services that don’t do delegate access - so private windows work nice for me to make sure that I’m always cleared out of what I was working on before changing to a different project. Often I copy things in private windows that aren’t secrets, it just happens to be how I used the feature. Co…

If you haven't seen it, there's also https://addons.mozilla.org/en-US/firefox/addon/temporary-con... ( https://github.com/stoically/temporary-containers MIT ) when you don't care about the containers but do care that their browsing context is isolated. The screenshot even shows the handy "delete temporary container 15 minutes after the last tab closes") Actually, sorry, it seems to be https://addons.mozilla.org/en-US…

That’s fantastic, thank you.

I have a very useful plugin that automatically deletes website data (other than history and downloads) after a configured interval once you’ve closed the tab or window. You can define an exception list. I cannot recall its name, I’ll post back when I’m back at my computer.

Re: What's New with Firefox 142

#138

Post by jffry »

zveyaeyv3sfye wrote: post #112
jffry wrote: post #24

Earlier quoted context omitted.

If you select a chunk of text in the page and right click there should be a context-menu option to translate the text. It's a popup with a textarea and not in-situ, but it's the same local model as far as I can tell

> in-situ I believe you mean ex situ: > By contrast, ex situ methods involve the removal or displacement of materials, specimens, or processes for study, preservation, or modification in a controlled setting, often at the cost of contextual integrity. Might as well use the correct words if you want to talk above people's heads.

First: No need to be rude, "in situ" is a very commonly used phrase among English speakers, as should be evident from the Wikipedia article [1] you yourself cited

Second: The normal Firefox translate feature replaces the text in the page with the translated text - retaining its styling, position, context w/ images, etc. The right click menu, does not. I described the right click menu as "not in situ" which is correct.

[1] https://en.wikipedia.org/wiki/In_situ

Re: What's New with Firefox 142

#139

Post by zveyaeyv3sfye »

jffry wrote: post #138
zveyaeyv3sfye wrote: post #112

Earlier quoted context omitted.

> in-situ I believe you mean ex situ: > By contrast, ex situ methods involve the removal or displacement of materials, specimens, or processes for study, preservation, or modification in a controlled setting, often at the cost of contextual integrity. Might as well use the correct words if you want to talk above people's heads.

First: No need to be rude, "in situ" is a very commonly used phrase among English speakers, as should be evident from the Wikipedia article [1] you yourself cited Second: The normal Firefox translate feature replaces the text in the page with the translated text - retaining its styling, position, context w/ images, etc. The right click menu, does not. I described the right click menu as "not in situ" which is correct…

> "in situ" is a very commonly used phrase among English speakers

I would challenge the "very common" claim.

But sure, the phrase is in use. Mostly not in tech, though.

And you are using it wrong.

If you wanted to express "in-place translation", you could have done so using your native tongue.

You're welcome.

Post reply on HN