Tab actions test case could be improved.

[cookiecrook]

The Tab Actions APG test case here:
https://www.w3.org/WAI/ARIA/apg/patterns/tabs/examples/tabs-actions/

…is unexpected in my opinion. Yes, it's fine to have a single ~"show menu" action on the tab, and then follow on actions in the sub-menu once the menu trigger is focused, but people don't use actions this way in my experience. And that "popup-button spawning a menu" pattern already exists and is achievable in a more predictable way.

I would suggest instead that the APG example use simple, menu-less tabs, that have s few actions that can be performed in other mainstream ways.

• a "close tab" action that can be triggered with cmd/ctrl+W or a mouse click on the intra-button "x" button, with similar behavior here to browser tabs
• Perhaps some "move tab left" and "move tab right" actions that are equivalent to a mouse drag operation or some custom key combo

IMO, this would be a more representative of how I'd expect people to use aria-actions on Tabs, rather than as an alternative to the pre-existing pattern for menu popup button. Thanks for considering.

[cookiecrook]

If you feel strongly about keeping the existing example, then my change suggetion could be a new test case in addition to the existing one.