Simon Pieters

Sorry, I see now CSS seems out of scope here, or is at least currently not covered in this project. Still there are lots of non-fork specs at the W3C.

There has been a change of plans since we need some more time to prepare. The new tentative date is March 28. See w3c/aria-at-automation#17 Apologies for the late change, and...

Next ARIA AT Automation Group Meeting is today: https://github.com/w3c/aria-at-automation/issues/18 If you would like to be added to the calendar invite directly, please reach out to @s3ththompson

The [diff view](https://whatpr.org/html/10286/b3fa80d...e99ff97/dom.html#the-document-object:cereactions-6) shows `document.write` and `writeln` with `HTMLString`. I suppose this needs to be rebased so that #10199 is included, and update those to union type here.

We have "palpable content", but it might not be correct for `option` (for example an `img` with empty alt counts as palpable content). Right now https://html.spec.whatwg.org/#the-option-element has > If the...

cc @whatwg/html-parser

I agree that option 2 seems most workable and easier to understand than option 3. I'm guessing that the content model (i.e. what is allowed for authors to use, not...

Existing sites might have other tags in `option` and expect the current behavior. The parser currently drops most tags but has special handling for ``, ``, ``, ``, and for...

https://ablefast.com/ has ``. If we go with a variant of option 1, this should continue to work. ``` Past Pools Results: Select Date 04-May-2024 ``` Also, https://html.spec.whatwg.org/#parsing-main-inselect:has-an-element-in-select-scope would need to...

top.ge is affected by both option 1 and option 3. But it would still be usable, right? I tested inserting the `a` and `b` elements in devtools and the widget...