Joey Arhar

> Thanks! Given that rationale I think it's good to couple the changes, but that should be in the commit message as well. Done. > This doesn't define optional tags...

> * Need to check that a `select` element is in scope so that parsing of option/optgroup tags outside of `select` doesn't change. Example `123` I thought that this is...

> High-level of what I think should happen: when parsing option or optgroup start tag: check that select is in scope, check that option or optgroup is in scope, generate...

@zcorpan how does the latest text look?

> This doesn't define optional tags for `` and `` correctly. I was talking to @mfreed7 about the changes we've made in the PR so far, and I feel like...

> I expect we can't allow nesting of `optgroup`, but I haven't researched it. If that is allowed, it would be reasonable to expect that the native dropdown can support...

> hr in select was added just last year, so we shouldn't flip-flop on that. But it could be allowed only as a sibling to an option element in the...

> If we envision allowing more HTML elements later, then we should at least generate implied end tags, so that HTML authoring rules are somewhat consistent. For example, it should...

Thanks! I implemented your suggestion

Generating all implied end tags with no exceptions in the optgroup case disallows nested optgroups, but I guess I'm ok with that since we can make additional changes to allow...