Philip Jägenstedt

I've tried to summarize everything I could find about document interfaces here: https://gist.github.com/foolip/103963a1ae8598d2baedd296f4a1bf4c I think it would be very good if representatives from all implementers, including from Edge, could get...

> ctor for Document is already shipping This was made very clear in the doc, but I've now also added that to the timeline, although I couldn't find the impl...

See also thread in https://lists.w3.org/Archives/Public/www-dom/2016JulSep/thread.html

This is an initial translation of https://open-ui.org/components/interest-invokers.explainer/ to spec language, with a lot of things incomplete. @mfreed7 I think the two biggest points of uncertainty I have now are the...

Thanks @lukewarlow, I've pushed those changes! (Couldn't apply the suggestions directly as they were line-by-line.)

Thanks for the review @mfreed7! I've addressed your comments now.

I have now pushed definitions of when `:interest-source` and `:interest-target` should match. Those pseudo-classes are now defined in https://drafts.csswg.org/selectors/#interest-source.

For anyone following only this PR and not the tracking issue, see https://github.com/whatwg/html/issues/10309#issuecomment-3252590058 about today's WHATNOT discussion and request to advance to stage 2.

https://github.com/whatwg/html/pull/11006/commits/fa121b61ee7bc1b96ee80e0f32b9d52f625ac895 is intended to align with https://chromium-review.googlesource.com/c/chromium/src/+/6970966. @mfreed7 can you carefully review it? It's now closer to the Chromium implementation in that it doesn't depend on a recursive call to...

Adding the interop label, because in https://github.com/w3c/web-platform-tests/issues/4884 this was the cause of some confusion, as a harness error only happened in Firefox where a error event was fired on window,...