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
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).