And what features and/or technologies you’d rather not see in a web browser
Lets make this interesting: you can imagine features ( there’s no wrong answers ) , its not just about features that you already saw in other browsers
And what features and/or technologies you’d rather not see in a web browser
Lets make this interesting: you can imagine features ( there’s no wrong answers ) , its not just about features that you already saw in other browsers
background/defocused tabs are ‘paused’ by default.
paused meaning no runtime execution of scripts or anything else.
firstly, there’s always some security and plenty of privacy mischief around focus.
secondly, it’s almost always wasting cycles, so its just wasteful of resources and energy.
ofc with some option for you to eg. right-click on a tab and mark it as ‘runtime in background’ or something, for webmail or messengers etc which you do want runtime.
but it should essentially be whitelisted.
i’ve actually played with this in the firefox debugger and it essentially appears feasible so really hope this feature comes oneday - or i finally get some time to look into making an addon for it.
Oh, how so?
that’s cool, yes a browser should stop using resources when you stop using it ( minimize it ), or using that particular tab by making it inactive, chromium based browsers behave like that if I’m not mistaken
check (here)[https://cheatsheetseries.owasp.org/cheatsheets/XS_Leaks_Cheat_Sheet.html] for some basic examples. eg. it can be used to leak info from one context to another.
there’s ofc legit uses for it too, which is why i argue for user intervention.
i may be wrong? but my understanding is they’ll currently limit resources, but execution still takes place? that’s definitely useful, but my argument is for for an option where CPU resources be limited to 0 in background (without user intervention).