Philip Jägenstedt

@fred-wang `.asis` files is indeed what I meant. That's not used in loading/early-hints/ however, so I guess there's another way?

@sadym-chromium did you see this error in infastructure/ tests? ``` Unexpected Results ------------------ /infrastructure/expected-fail/user-prompt.html?type=confirm UNEXPECTED-OK /infrastructure/expected-fail/user-prompt.html?type=confirm ERROR BiDi event processing failed: unexpected alert open (500): unexpected alert open: {Alert text...

From skimming features in https://wpt.fyi/interop-2024 I think all the big features are already covered. What stands out is `@starting-style` and `transition-behavior`, as new features but which I suspect don't make...

@una thanks for the correction, I don't understand all the pieces and how they fit together. Do you think there's something worth asking about here in the 2024 survey?

@josepharhar before I take another look, can you resolve conflicts and ensure the build runs without errors? (Otherwise the preview might not be updated.)

Just to make it explicit, is the idea to keep this PR open until there's multi-vendor support, or also until the change is proven web compatible by shipping it? @annevk,...

Oops, I spoke to soon in my aside. The proposal says > "focus-without-user-activation", which has a default allowlist of *. That doesn't match the behavior of the `autofocus` attribute. Shouldn't...

Yep, also decide which spec gets to define "default object size" for , and the default "default object size" for replaced content for that matter.

Oh, also, consider if "default object size" is actually needed. At least for <video>, current Firefox, Chromium and Blink are already (mostly) interoperable in having a default intrinsic size 300x150,...

OK, so then I suppose it's just a matter of figuring out what values for intrinsic size and default object size are Web compatible for <img> and <video>. Make it...