Live data from Hacker News

Firefox 67.0 Released

mozilla.org

101–110 of 264 posts

Re: Firefox 67.0 Released

#101

When I upgraded from 66.0.5 it created a new profile, rather than keeping my existing passwords/histories/extensions. I'm not going to use firefox sync, so it seems like there will be a painful migration ahead.

We're defaulting to profile-per-install to make it easier to run different versions side-by-side, but you can still manually specify your original profile.

Docs on the profile manager are at https://support.mozilla.org/en-US/kb/profile-manager-create-...

...or, as a super weird hack, you can set the envvar SNAP_NAME=firefox to get the old behavior (see https://github.com/mozilla/nixpkgs-mozilla/issues/163 for context)

Re: Firefox 67.0 Released

#102

Earlier quoted context omitted.

As someone who codes dark mode first thanks for the lazy “OMG, my eyes...” mode ;-)

I used to code with black themes for a long time but not anymore: Why not simply lower your screen brightness ? I feel it better for my eyes because the text which i'm looking at is actually dark and not bright. Most people with dark themes have high brightness levels on their screens. I think this can be bad on the long term. Especially that many screen elements are not as dark as their code, which makes them ultra…

I mean that when I build out an application / site, I build the Dark Mode first then convert the dark mode into the light mode. (Most of my users choose to use dark mode over light mode if the option is given to them)

Re: Firefox 67.0 Released

#103
post #49
post #18

Earlier quoted context omitted.

It would be better if they offered a way to really turn it off. Firefox has got very crashy in environments that have no access to a GPU.

Could you set set gfx.webrender.enabled to false?

Already did. It is not enough.

Re: Firefox 67.0 Released

#104
That means that one of the most obscure performance regression bugs I've ever found in Firefox is also fixed: property lookups on numbers being slower for values recognized and optimized as integers by the JavaScript engine than for regular doubles.

https://bugzilla.mozilla.org/show_bug.cgi?id=1523633

Re: Firefox 67.0 Released

#105
post #28

Earlier quoted context omitted.

You must mean OLED. And no, there are almost no desktop OLED monitors in the wild.

"LED display" term is commonly used for LCD displays where backlight is also actively controlled to increase dynamic range.

Thus the distinction "pure LED" in my previous post.

That there are plenty of deceptively labeled LCDs does not mean there are no actual LED displays.

Re: Firefox 67.0 Released

#106
post #71
post #41

Earlier quoted context omitted.

No. The extensions that are already installed will still work in private windows. It’s only newly installed extensions that are disabled in private windows by default

That still doesn't solve a problem of a user installing the browser for the first time, installing adblock, then going to a porn site in private mode and getting a faceful of malware-ridden ads. Who thought this is a good idea?

It's not perfect, but there are prominent prompts about this when you install an add-on for the first time and when you open a private window. Screenshots at https://imgur.com/a/d4ZnAHI

Re: Firefox 67.0 Released

#107
post #55

Earlier quoted context omitted.

That was also the case with CRT displays. If a pixel is to stay black, no electron must be emitted to light up its phosphor. This Google search frontend has been around long enough to claim it helped save considerable amount of energy on that principle: http://www.blackle.com/about/ What they report about LEDs and CCFL isn't entirely correct, however. It may become in the future. Technicalities aside, what once could…

CRTs consume so much power that the beam current is negligible. The comparison is with backlit LCD screens, which have to have the backlight on regardless of how many black pixels you have.

Not the case for LCDs with variable brightness backlight regions.

Re: Firefox 67.0 Released

#108

When I upgraded from 66.0.5 it created a new profile, rather than keeping my existing passwords/histories/extensions. I'm not going to use firefox sync, so it seems like there will be a painful migration ahead.

Go to "about:profiles" and make your old profile ("default" by default) the default profile again, then restart Firefox.

This was indeed a fucking terrible way of doing this: "Hey, we've just hidden all your profile data from you and to get it back you need to sign up to our web service!"

Re: Firefox 67.0 Released

#109

When I upgraded from 66.0.5 it created a new profile, rather than keeping my existing passwords/histories/extensions. I'm not going to use firefox sync, so it seems like there will be a painful migration ahead.

It looks like that may be related to FF now creating a separate profile for every installation. That was apparently targeted for FF65 originally, then bumped to FF67:

https://groups.google.com/d/topic/mozilla.dev.platform/hVeJS...

Re: Firefox 67.0 Released

#110

When I upgraded from 66.0.5 it created a new profile, rather than keeping my existing passwords/histories/extensions. I'm not going to use firefox sync, so it seems like there will be a painful migration ahead.

That's really odd. Had you used that profile with a post-67 nightly at some point or something?

Some more information about the profiles involved here would be really useful. Are you willing to file a bug at https://bugzilla.mozilla.org/ ? If you do and give me the link to it, I'll get people who know the right questions to ask involved...

Post reply on HN