selectTab(tab) also fires the event. This will make it so any tab selection behavior sends an event (rather than just the pointer down).
The event was also modified to include the selected tab in the event detail.
This is also a useful external API to have.
I found that relying on the select event wasn't super reliable as it only fired in one circumstance. The other times where the tab could be selected weren't able to be captured through events.
Calling a DOM method should not trigger an UI event, this is a common pattern in HTML DOM. Those events are meant to be triggered only when user interacts with the UI.
selectTab(tab) also fires the event. This will make it so any tab selection behavior sends an event (rather than just the pointer down).
The event was also modified to include the selected tab in the event detail.
This is also a useful external API to have.
I found that relying on the select event wasn't super reliable as it only fired in one circumstance. The other times where the tab could be selected weren't able to be captured through events.