Sounds good, but I'd move for the total removal and banning of all JS and other scripting.
Otherwise, what's the point?
I've actually taken to using a Javascript toggle extension that defaults to off. Makes the web a far better experience when it comes to venturing into unfamiliar territory (going to a site you haven't been to in a while, if it all, or following some shortened url that leads who knows where, or just clicking through something on a news aggregator for example). And if it breaks the website? 9 times out of 10 that's your "It's not worth it" signal to just close the tab and move on. If they can't even deprecate gracefully, they almost never use javascript competently and unobtrusively.
What about actual apps or games where you want to push the limits?
1.) A subset of modern HTML / CSS, custom Javascript. Remove anything that isn't needed and especially anything that affects rendering negatively for no good reason.
1.1.) Possibly: Provide versioned, vendor neutral versions of js to allow for autocomplete.
2.) Same as 1, but with custom JS. All js must complete in a specified number of cycles. User interaction gives extra cycles.
The point of 1 is to:
- for companies: massively lower the barriers for new browsers (remove lots of backwards compatibility and the huge problem of JS)
- for security conscious users: provide a safer way to browse the web
- for users generally: provide a way to browse the web faster and more comfortably
- the point of 2.) is to provide an approximation of what we have today but in a way that automatically limits developers from abusing JS.