Hopefully the author only means to bring relative shares in from cgroups - absolute limits seem like they would only serve to throttle the browser for no good r

Hopefully the author only means to bring relative shares in from cgroups - absolute limits seem like they would only serve to throttle the browser for no good reason. If you do want to throttle a browser tab, let the user do this in the browser. No reason for that to come from the page markup. Also, is it realistic that web publishers will have to intentionally deprioritize ads and tracking etc relative to the main site/application? I imagine some people (ad networks) might not be too impressed with this. Maybe a cool PoC of this would be an "adblocker" type browser extension/feature that automatically deprioritizes known ad/tracking content, but still displays it eventually. Then again, forced "async" or "defer" might be able to achieve this too without a complicated framework.