Simon Pieters

cc @DimiDL @galich @masayuki-nakano

Autocomplete works differently on different form controls, see https://html.spec.whatwg.org/#inappropriate-for-the-control Editing hosts don't have a way to signal what kind of input is accepted (e.g. single line vs multiline). Which "groups"...

I don't like adding an easy mechanism to disable incremental rendering. Incremental rendering is done because it is generally better for users. Would it be possible for the browser to...

A new element would require some parser changes (to make it close `p` elements). ARIA has a `note` role, which might be close enough? https://w3c.github.io/aria/#note

> * It seems like we have already talked about notes, tips, warnings, and maybe other things. We should check out ARIA WG's past discussions on this (which I'm sure...

Thanks @aardrian! So if I understand correctly, only JAWS does something interesting for unlabelled `role=note`: > Announces "note" when entering and exiting. Is this useful? What is ideal? OP says...

IIRC, this comes from Hixie trying to spec the behavior of Gecko. I don't know if Gecko has since changed or if the spec was wrong to begin with. But...

Should CSS features that fetch things use HTML-parse also? Consider ```html ``` It's slightly harder to pull off since the `style` attribute needs to be closed on the next line...

Missing: - media element ``: https://whatpr.org/html/10022/055a678...6e9e98e/media.html#loading-the-media-resource:encoding-parsing-a-url - `cite` on [blockquote](https://whatpr.org/html/10022/055a678...6e9e98e/grouping-content.html#attr-blockquote-cite); [del](https://whatpr.org/html/10022/055a678...6e9e98e/edits.html#attr-mod-cite); [ins](https://whatpr.org/html/10022/055a678...6e9e98e/edits.html#attr-mod-cite); [q](https://whatpr.org/html/10022/055a678...6e9e98e/text-level-semantics.html#attr-q-cite) - `itemid` (it shouldn't be fetched, so maybe this one is ok?) https://whatpr.org/html/10022/055a678...6e9e98e/microdata.html#attr-itemid - microdata processing of...

> I would still expect more test coverage though, in particular that `XMLHttpRequest`, `EventSource`, `importScripts()`, `fetch()`, `new URL()`, etc. are not impacted by this. I'm not entirely sold that the...