Adrian Roselli on Nostr: . npub1l3e40…ecrpw shows how to work around broken `<optgroup>` support: ...
. npub1l3e40m56cmez3jlv4afvemmmhvv6xl54d896lgkwh4urg9ppgx8specrpw (npub1l3e…crpw) shows how to work around broken `<optgroup>` support:
https://html5accessibility.com/stuff/2024/01/12/options-for-optgroup-labeling-of-options/
I added to my post (which is really an indictment of WHATWG and Google/Apple):
https://adrianroselli.com/2023/10/splitting-within-selects.html#Update02
My MDN support chart issue for `<optgroup>` is still out there:
https://github.com/mdn/browser-compat-data/issues/21663
But I expect it to be closed since MDN does not track real support (specifically, #accessibility support), just as they did with `<mark>`:
https://github.com/mdn/browser-compat-data/issues/21847#issuecomment-1878757924
The burden is on you to test, dear author.
https://html5accessibility.com/stuff/2024/01/12/options-for-optgroup-labeling-of-options/
I added to my post (which is really an indictment of WHATWG and Google/Apple):
https://adrianroselli.com/2023/10/splitting-within-selects.html#Update02
My MDN support chart issue for `<optgroup>` is still out there:
https://github.com/mdn/browser-compat-data/issues/21663
But I expect it to be closed since MDN does not track real support (specifically, #accessibility support), just as they did with `<mark>`:
https://github.com/mdn/browser-compat-data/issues/21847#issuecomment-1878757924
The burden is on you to test, dear author.