91–100 of 574 posts
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.
Earlier quoted context omitted.
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.
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?
It's not a feature and you can't disable it, previously it'd just crash. I think it's to do with the content workers being `exec`d from disk each time instead of forking from a master.
Earlier quoted context omitted.
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.
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.
Looking at the news cycle, it seems like the amount of changes is pretty low for this new version. Are they using version numbers for marketing purposes now?
So what's the list of browsers now that have autoplaying blocked or have that feature planned?
Generally this is good. But I wonder, lets say you want to allow autoplay on Netflix. Do you need to enable it on all subdomains and CDNs - that could be tedious. (I don't know if Netflix has subdomains, CDN, just an example)
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…
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.
Then the page won't be responsive. The image width and height changes depending on your viewport size.
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?