Meeting minutes
<scotto_> https://
<Zakim> jamesn, you wanted to ask about remaining use cases that may need support and to talk about the redundancy case
<Zakim> jamesn, you wanted to drill into details of a deprecation
"The aria-haspopup property is a token type. User agents MUST treat any value of aria-haspopup that is not included in the list of allowed values, including an empty string, as if the value false had been provided."
Proposal: Keep aria-haspopup on combobox as is. Comboboxes just re-done don't want to touch it right now
Otherwise potentially deprecate the token values on other elements. Would be fine with true/false - potentially could make mapping changes
if we were to deprecate the values - eventually we would need a menubutton role - need legacy support for true - could make this more generic if we could fix the underlying menubutton problem
jcraig: techincally could deprecate the values with the way the spec is written (and moving more towards interop testing) would make it really difficult to do that to create a test. Other major downside to deprecation - in scenarios where it helps would discourage use. Deprecation is too much in this case. Would rather put notes in the spec.
Matt_King: menubutton - i hear you say that and then thing do we need a togglebutton role. We need to think down the road a bit and think how we want to best serve screen reader users here.
scotto_: Fine with no menubutton role
scotto_: if not going to add more token values - understand there is value in those other things