Joey Arhar

For options: If we used system colors instead of color-mix() like my last comment, we could use SelectedItem/SelectedItemText or AccentColor/AccentColorText

@tabatkins left some feedback about colors here, which I think would still fit within the resolution: https://github.com/w3c/csswg-drafts/issues/10857#issuecomment-2492230947

> `label`: right now this overrides the displayed text of the `` if defined. Repurposing this to no longer override the text could be considered breaking (maybe?), although otherwise this...

I think we still need to figure out how we are going to incorproate the option label attribute for accessibility mappings, but Proposed resolution: Use the option's label attribute for...

The tone about standardizing keyboard behavior makes me believe that getting interoperable typeahead isn't going to be possible: https://github.com/openui/open-ui/issues/1087 I think this means that we can't add a new attribute...

A similar topic came up for comobox (and filterable select?) where you might want to specify the text to match filtering apis against for each option element, such as alternate...

Thanks luke! I put your links in the description

I found the same issue that keith mentioned, here is a chromium patch that addresses it. I can make a spec PR for it soon: https://chromium-review.googlesource.com/c/chromium/src/+/6526266

The current getter retargets against currentTarget if currentTarget is present, and otherwise just returns the original element. After event dispatch, currentTarget becomes null, so it just returns the original element....

Here is a PR for improved retargeting: https://github.com/whatwg/html/pull/11345 I looked at relatedTarget a bunch while implementing this, and I believe that relatedTarget's retargeting is very complex and should not be...