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

Firefox 67.0 Released

mozilla.org

Post reply on HN
Print view View original

111–120 of 264 posts

Re: Firefox 67.0 Released

#111

Post by callahad »

riskable wrote: post #59
ncmncm wrote: post #27

Running Firefox under Qubes has become increasingly frustrating, as tabs crash whenever (apparently?) they try to use WebGL, or anything that depends on access to a GPU. More and more, Firefox seems to depend on GPU access (or something?) and fails hard when it's not there.

To be fair, that sounds like a bug in the graphics driver or OpenGL ICD/libraries. GPUs are a bit special in that they have the power to hose your entire running OS (force a reboot due to a hard hang) no matter what OS you're running. It's just the nature of GPUs and how their drivers work... With direct access to memory and allowing user space applications access to their hardware features. In other words: Probably…

> if your driver has issues with any of those calls (e.g. bad application auto-detection) it can cause things to crash or have undefined behavior.

If I understand it correctly, that's one of the perks of WebRender: by using the GPU more like a game engine would, we're relying on code paths that tend to be better tested / more reliable.

Re: Firefox 67.0 Released

#112

Post by nominated1 »

sdsdsdsds wrote: post #81
Crosseye_Jack wrote: post #20

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've also read that it takes more power (battery) to render black than it does white. Combined with the need for more brightness it doesn't seem like a good solution.

Calibrating my monitors took them from having piercing bluish whites to more softer pinkish whites and reduced daytime eye strain significantly.

I then use Redshift at night with the undocumented "preserve" switch to combine my icc profile with the Redshift changes.

Re: Firefox 67.0 Released

#114

Post by iforgotpassword »

ncmncm wrote: post #55
noisem4ker wrote: post #33

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.

Actually traditional tft displays need to apply a current to turn a pixel black, so if you don't use adaptive brightness that would dim the backlight if the display is mostly black, you actually consume more power with a black theme. I have a low power Pentium notebook with 15" led backlit screen and the difference between a terminal with black or white background is significant.

Re: Firefox 67.0 Released

#115

Post by cweagans »

acdha wrote: post #63
jdlyga wrote: post #22

I've tried to switch to Firefox, but I keep running into rendering engine issues with certain sites. It's like it's 2005 again.

Which sites? They actively pursue compatibility issues but it's pretty rare to see non-Google sites which only work in Chrome.

coda.io goes out of their way to only work in Chrome for some strange reason

Re: Firefox 67.0 Released

#116

Post by amluto »

lholden wrote: post #43
akavel wrote: post #39

> "Enable FIDO U2F API, and permit registrations for Google Accounts" Oh! Didn't expect that! Does this mean YubiKeys will now be working in GMail on Firefox? Together with all the other stuff, this starts to look like a really important and major release of Firefox.

Yep, though technically one could enable this before now by tweaking the about:config security.webauth.u2f setting. (Which is something I've been having to do for a while now). As a side note... the way Google handles U2F is somewhat out of spec. For example, you haven't been able to register a u2f device with Firefox on google. I wonder if that's been worked around with this release? That would be great! Otherwise,…

> the way Google handles U2F is somewhat out of spec.

Somewhat? As I understand it, it doesn’t even pretend to be fully specified. Chrome shipped it without going through the normal intent to ship process.

Re: Firefox 67.0 Released

#117

Post by dredmorbius »

noisem4ker wrote: post #33
ncmncm wrote: post #17

Earlier quoted context omitted.

Dark mode, for the first time ever, has legitimate, objective reasons to want, now that we have pure LED displays: a black LED pixel consumes no energy.

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…

https://duckduckgo.com/tty/

https://duckduckgo.com/settings#theme

Re: Firefox 67.0 Released

#118

Post by viraptor »

nominated1 wrote: post #112
sdsdsdsds wrote: post #81

Earlier quoted context omitted.

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've also read that it takes more power (battery) to render black than it does white. Combined with the need for more brightness it doesn't seem like a good solution. Calibrating my monitors took them from having piercing bluish whites to more softer pinkish whites and reduced daytime eye strain significantly. I then use Redshift at night with the undocumented "preserve" switch to combine my icc profile with the Reds…

> I've also read that it takes more power (battery) to render black than it does white

This really depends on the display technology and for more modern monitors, the opposite is true.

Re: Firefox 67.0 Released

#119

Post by will4274 »

akavel wrote: post #39

> "Enable FIDO U2F API, and permit registrations for Google Accounts" Oh! Didn't expect that! Does this mean YubiKeys will now be working in GMail on Firefox? Together with all the other stuff, this starts to look like a really important and major release of Firefox.

This is an anti-feature. Firefox enabled a deprecated standard because Google couldn't be bothered to move to the current standard. Classic catering to the big players.

Re: Firefox 67.0 Released

#120

Post by Silhouette »

acdha wrote: post #63
jdlyga wrote: post #22

I've tried to switch to Firefox, but I keep running into rendering engine issues with certain sites. It's like it's 2005 again.

Which sites? They actively pursue compatibility issues but it's pretty rare to see non-Google sites which only work in Chrome.

it's pretty rare to see non-Google sites which only work in Chrome.

Unfortunately that hasn't been my experience in recent months. A noticeable number of random sites I come across, sometimes including quite important ones, Just Don't Work in Firefox.

Is there a quick way to send a link to such sites/pages, if someone at Mozilla is interested in investigating why?

I think it's important to note that this behaviour isn't necessarily due to anything wrong with Firefox. It could simply be because Firefox is better at blocking unwanted content than certain other browsers and that feature is working as intended, but the kinds of sites that rely on hostile content also tend to break if those scripts are forcibly blocked by the browser.

Post reply on HN