Simon Pieters
Simon Pieters
No, still need to pop the `option` or `optgroup` if that is the current node. Actually, using the `ruby` model is maybe best, however the parse error condition needs to...
Great. `hr` no longer closing `option` and `optgroup` is a behavior change from what the parser currently does, which I'm somewhat uncomfortable with. It makes currently valid HTML invalid. @hsivonen...
cc @whatwg/forms
The spec says for autocomplete=off: > The "off" keyword indicates either that the control's input data is particularly sensitive (for example the activation code for a nuclear weapon); or that...
> google.com falls into the third category, but wants to clear the value on history navigation. However, for pages in general, I think it doesn't makes sense to clear the...
A new attribute to control restoration SGTM, with the default being to restore (regardless of `autocomplete` or bfcache/non-bfcache).
@whatwg/a11y are there any issues with AT with allowing headings in `summary`?
I think the issue is that `summary` is exposed as a button in the a11y tree, and buttons can only have plain text. So long as that is the case...
@domenic Once it has landed in the spec it's fine to need engineering and review from Mozilla to land in Gecko, as it's a trivial change to add a new...
I'm warming up to the idea of switching to a blocklist. Disallowing anything not in the IANA registry means there's at least some friction to start using a new scheme,...