Live data from Hacker News

Firefox 66.0 Aims to Reduce Online Annoyances

blog.mozilla.org

61–70 of 574 posts

Re: Firefox 66.0 Aims to Reduce Online Annoyances

#61
post #37

Earlier quoted context omitted.

Wouldn't it be nice if browsers or servers could reserve that space even if it's not loaded? Like "this is going to be a 500x200 image so let's load 500x200 pixels worth of empty space until it's fully loaded" and avoid jumping.

I think you're being sarcastic, but if not and for anyone who isn't aware, setting the width and height on an tag (or it's associated style) will do this.

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

Re: Firefox 66.0 Aims to Reduce Online Annoyances

#62
post #42

Whenever Firefox is automatically updated through my package manager, any open instances refuse to load any new pages or tabs until I restart Firefox . Needless to say, this is absolutely infuriating when I'm in the middle of something important. Does anyone know how to disable this feature?

Couple things. 1. Why update an app when you're in the middle of using the app? I dunno, I use Fedora, so I don't execute 'dnf update' until I'm ready to reboot the system, usually because I'm anticipating a kernel update. 2. Firefox has a pretty reliable "Restore Previous Session" feature that works well. I have also been known to throw a SIGTERM at Firefox and just let it prompt me when I start it again for the "So…

Some people prefer automatic updates. It didn't used to criple the running browser process after an update, that change is very recent.

Restore session doesn't help if you're in a private session.

Also you may be in the middle of actually using your browser for thing that you don't want to interrupt, a game, an online application, anything really..

Re: Firefox 66.0 Aims to Reduce Online Annoyances

#63
post #42

Whenever Firefox is automatically updated through my package manager, any open instances refuse to load any new pages or tabs until I restart Firefox . Needless to say, this is absolutely infuriating when I'm in the middle of something important. Does anyone know how to disable this feature?

Finally I find another person getting annoyed at this. It baffles me how this is acceptable...

My browser is open when my computer is running. I do updates at random times through-out the day, for example before installing new packages. Having to close my browser leads to dead sessions and text being lost from input fields and whatever other state there might be.

My guess is that this is some per-tab isolation/process stuff that would result in a mismatch between tabs from before the update and tabs after the update.

Re: Firefox 66.0 Aims to Reduce Online Annoyances

#64
post #37

Earlier quoted context omitted.

Wouldn't it be nice if browsers or servers could reserve that space even if it's not loaded? Like "this is going to be a 500x200 image so let's load 500x200 pixels worth of empty space until it's fully loaded" and avoid jumping.

I think you're being sarcastic, but if not and for anyone who isn't aware, setting the width and height on an tag (or it's associated style) will do this.

I think you're also being sarcastic :) Websites did this 15 years ago (miss the HTMLX compliant button at the bottom of the page), and now in large part do not.

Re: Firefox 66.0 Aims to Reduce Online Annoyances

#65

Earlier quoted context omitted.

Couple things. 1. Why update an app when you're in the middle of using the app? I dunno, I use Fedora, so I don't execute 'dnf update' until I'm ready to reboot the system, usually because I'm anticipating a kernel update. 2. Firefox has a pretty reliable "Restore Previous Session" feature that works well. I have also been known to throw a SIGTERM at Firefox and just let it prompt me when I start it again for the "So…

Some people prefer automatic updates. It didn't used to criple the running browser process after an update, that change is very recent. Restore session doesn't help if you're in a private session. Also you may be in the middle of actually using your browser for thing that you don't want to interrupt, a game, an online application, anything really..

It's only in parts recent. Updating Firefox did not have this enforcing message telling you to restart, but before Firefox would just randomly break when updated via the package manager. Preventing that is better now.

Don't do automatic updates if you do not want automatic updates. Automatic updates just absolutely can cause you to have to restart stuff, depending on what got updated exactly.

Re: Firefox 66.0 Aims to Reduce Online Annoyances

#66
post #61
post #37

Earlier quoted context omitted.

I think you're being sarcastic, but if not and for anyone who isn't aware, setting the width and height on an tag (or it's associated style) will do this.

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. "width: 100vw; height: auto;" will fill the viewport horizontally and scale the image vertically as per it's aspect ratio. And so on. Generally that'll look bad though because browsers scale things fast rather than well.

And then there's the options for background images. "background-size: cover" is quite useful.

CSS is fun.

Re: Firefox 66.0 Aims to Reduce Online Annoyances

#67
post #61
post #37

Earlier quoted context omitted.

I think you're being sarcastic, but if not and for anyone who isn't aware, setting the width and height on an tag (or it's associated style) will do this.

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

Not sure why you're downvoted. It's a real problem. It would help if it would be possible to set an aspect ratio on the img tag, so that when it's scaled via CSS or whatever, it would maintain the aspect ratio of the loaded image despite it not being loaded yet.

Re: Firefox 66.0 Aims to Reduce Online Annoyances

#68
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...

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

Re: Firefox 66.0 Aims to Reduce Online Annoyances

#69
post #61
post #37

Earlier quoted context omitted.

I think you're being sarcastic, but if not and for anyone who isn't aware, setting the width and height on an tag (or it's associated style) will do this.

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: Or maybe it would be better to just have the ability to lock the ratio, such as:

    ratio: fixed;

Re: Firefox 66.0 Aims to Reduce Online Annoyances

#70

"System title bar is hidden by default to match Gnome guideline for Linux users" - which part of the UI does this refer to exactly? Does this mean that Firefox will now be hiding the page title?

Odd, Firefox 65 already appears to do this under Gnome, unless I'm misunderstanding. Could be that Ubuntu were already doing this and it has now made it upstream, I suppose.

I think it was behind a flag before.
Post reply on HN