Simon Pieters
Simon Pieters
Should this be defined in html-aam, similar to https://w3c.github.io/html-aam/#att-inert ?
Pointer and Mouse events was carried over to Interop 2025, so this is still relevant.
I guess we can close this now?
The suggested changes make sense to me and seems in line with what CSS UI expects. Last I checked there was no standardized pseudo-element for `meter`. That seems necessary to...
Does the algorithm match Chrome or Firefox, or neither? cc @nchevobbe
@bmeurer can this be changed in Chromium/V8? See https://github.com/whatwg/console/pull/237#issuecomment-2292207723 above.
I think the idea is that a JS object (that is not an array) would still work (step 4). Hmm, the spec algorithm here operates on Infra value types (list...
@domenic I think the second option is closer to what browsers do today. [Gecko uses `any`](https://searchfox.org/mozilla-central/source/dom/webidl/Console.webidl#37). This doesn't throw in Safari/Chrome/Firefox: ```js let o = {}; Object.defineProperty(o, "x", { get()...
The [button layout magic](https://html.spec.whatwg.org/#button-layout-2) covers more than safe centering, do you intend to keep those as-is or try to remove them also?
There are more APIs that call the focusing steps. For example `showModal()` on `dialog`. See https://html.spec.whatwg.org/multipage/interaction.html#focusing-steps (click on "focusing steps" to see callers).