smaug----

Possible tweak to domenic's proposal - I think I'd prefer something very explicitly, a long the lines Access-Control: public-resource and not change the behavior of existing stuff. But I don't...

I don't pretend to understand the explainer. "eviction is triggered on a change". If a page is in bfcache (from which it can be evicted), how can a cookie change?...

It wouldn't be to far fetched to think of a site which uses no-store explicitly to prevent bfcache. And it uses it so that loading a new page to the...

What is stable Chrome behavior? Propagating click from child elements of a disable button to the ancestor of the button, but not firing on the button itself. That is just...

Have other browsers gotten bug reports about the behavior they have?

Looks like in Chrome disabled button is in the composedPath, but event listeners aren't called on it. So one can't rely on event.composedPath() to return the targets on which listeners...

Another testcase where Chrome's behavior is rather surprising: https://mozilla.pettay.fi/moztests/disabled_button.html One may use a disabled button to trigger default handling but a listener in the button itself isn't triggered.

That seems surprisingly low number for this. Nothing here is of course safe. Leaving Chrome's behavior as it is will likely cause issues later (since it is so [inconsistent](https://docs.google.com/document/d/18OEhfqA7yYJWcvHKlzldkrg7SzseFGqKZNFlL0CBiec/preview)) and...

I guess similar-ish issue might happen with focus/blur. I can't recall how the blur is defined to work in this case ` data:text/html,`

It is partially an implementation detail why I'd prefer to fire event first and only after it change styling. There are cases where JS may spin event loop in Gecko,...