Live data from Hacker News

Firefox 66.0 Aims to Reduce Online Annoyances

blog.mozilla.org

71–80 of 574 posts

Re: Firefox 66.0 Aims to Reduce Online Annoyances

#71
post #48

This bit is also somewhat surprising/interesting: > Improved performance and reduced crash rates by [doubling web content loading processes from 4 to 8 [1] From personal experience, I believe that things usually get more buggy, not less, as you add more parallelism/concurrency. I think there's supposed to be a link to more explanation or the relevant ticket, but it looks like they forgot to actually add the link. Can…

http://www.erahm.org/2019/03/13/doubling-the-number-of-conte...

Thanks!

While that post addresses the reason why we can double the number of processes, I think I'm still missing the reason why we should double the number of processes (aside from performance reasons).

I mean, the release notes made it sound like more processes is more stable than fewer processes (unless I'm misreading it). How does doubling the number of processes result in fewer crashes? If we manually force FF 66 to use 4 processes only, would it result in more crashes than using 8 processes?

Re: Firefox 66.0 Aims to Reduce Online Annoyances

#72
post #61

Earlier quoted context omitted.

This would be a great solution, if everybody used the same screen size.

It would be nice if we could have a ratio rule in CSS for all block elements, so adjusting one dimension would automatically alter the other, preserving the ratio at all screen sizes. e.g.: width: 2000px; max-width: 100%; ratio: 16/9; Of course this gets tricky when width and height are both specified and they don't match the given ratio, but that just means that one needs to always override the other. Edit to add: O…

Aspect Ratio is coming in CSS4. https://www.smashingmagazine.com/2019/03/aspect-ratio-unit-c...

Re: Firefox 66.0 Aims to Reduce Online Annoyances

#73
post #68

Earlier quoted context omitted.

http://www.erahm.org/2019/03/13/doubling-the-number-of-conte...

That does not really explain why it would be more stable, or did I miss it?

Increasing the number of processes decreases the number of tabs sharing each process. So if a process crashes it will bring down fewer tabs.

Re: Firefox 66.0 Aims to Reduce Online Annoyances

#75
post #28

> Scroll anchoring keeps content from jumping as images and ads load at the top of the page That's a nice little quality-of-life improvement. It's a little annoyance that you don't really consciously notice because you're so used to it, but I recall reading about Chrome adding a similar feature and suddenly realising how annoying it is when you're reading something, and then suddenly it jumps out of your view due to…

On mobile I feel this constantly, mostly due to the lack of adblock. Somehow like 70% of any news site I get linked to by hn feature constantly loading ads that stop me from being able to read anything...

Re: Firefox 66.0 Aims to Reduce Online Annoyances

#76
post #66
post #61

Earlier quoted context omitted.

This would be a great solution, if everybody used the same screen size.

The width and height of an image set in a CSS file can be in any valid CSS unit. That's pixels, or em, or a percentage, or viewport units (vw and vh for 1% of the width or height, vmin or vmax for 1% of the shortest or longest side), or real world units like mm (only works on high DPI screens). Support varies. Eg setting an image to be "width: 100vw; height: 100vh;" means it'll be squished to fill the user's viewport…

In many cases you want to set one size and let the other calculate itself based on the aspect ratio of an image. And this is not know prior to loading and can't be specified in any other way. So you get jumpy behavior during load on most responsive websites and slow connections. It's hard to fix in JS too.

Re: Firefox 66.0 Aims to Reduce Online Annoyances

#77
post #68

Earlier quoted context omitted.

That does not really explain why it would be more stable, or did I miss it?

Increasing the number of processes decreases the number of tabs sharing each process. So if a process crashes it will bring down fewer tabs.

That would mean smaller impact per crash, not fewer crashes though.

Re: Firefox 66.0 Aims to Reduce Online Annoyances

#78
post #76
post #66

Earlier quoted context omitted.

The width and height of an image set in a CSS file can be in any valid CSS unit. That's pixels, or em, or a percentage, or viewport units (vw and vh for 1% of the width or height, vmin or vmax for 1% of the shortest or longest side), or real world units like mm (only works on high DPI screens). Support varies. Eg setting an image to be "width: 100vw; height: 100vh;" means it'll be squished to fill the user's viewport…

In many cases you want to set one size and let the other calculate itself based on the aspect ratio of an image. And this is not know prior to loading and can't be specified in any other way. So you get jumpy behavior during load on most responsive websites and slow connections. It's hard to fix in JS too.

Yes, and that's exactly what Firefox's new scrolling anchoring tries to fix.

Re: Firefox 66.0 Aims to Reduce Online Annoyances

#79

Does anyone else have the problem that firefox denies acces to `navigator.geolocation.getCurrentPosition` even if the user clicks "allow"? I hoped it was fixed in the release but seems to be not the case.

I tried https://developer.mozilla.org/en-US/docs/Web/API/Geolocation... in Firefox 66 on macOS and Windows. I got "Unable to retrieve your location" on macOS (though it worked in Chrome on macOS). It worked on Windows, though.

Re: Firefox 66.0 Aims to Reduce Online Annoyances

#80
post #61

Earlier quoted context omitted.

This would be a great solution, if everybody used the same screen size.

It would be nice if we could have a ratio rule in CSS for all block elements, so adjusting one dimension would automatically alter the other, preserving the ratio at all screen sizes. e.g.: width: 2000px; max-width: 100%; ratio: 16/9; Of course this gets tricky when width and height are both specified and they don't match the given ratio, but that just means that one needs to always override the other. Edit to add: O…

To be honest, if you know one dimension and the aspect ratio, you're more likely to know both dimensions.
Post reply on HN