May 19, 2020, 7:17 PM
Hi Fabricio,
Hoping to catch you before end of day.
I set some console.log on the beforeshow and activate events. Something is causing them to fire twice, once with the correct tab to show (on closing another tab), and then both events fire a second time with the next tab higher in the ordinal count. (This only happens when closing a tab, not when switching tabs.)
So I decided to work on a workaround until we can figure out why this is happening. I have tried adding a sessionStorage value that basically says "skip me" and then a timeout that destroys that sessionStorage item a second later.
This is working to return false on beforeshow and activate but then the tabpanel crashes on setactivetab. The documentation seems to indicate that returning false on beforeshow cancels the event, but this doesn't seem to work in practice.
Is there a simple way to stop the tabpanel from processing the setactivetab? Overriding it looks scary, as it is a complex event that is probably part of a chain of events.
I have not successfuly located the reason why beforeshow and activate are getting called a second time. In fact, these are just symptoms of the tabPanel setting active tab twice, right?
I know I'm still asking you to work blindfolded, but I sure do appreciate your help!
Bob Graham
Hoping to catch you before end of day.
I set some console.log on the beforeshow and activate events. Something is causing them to fire twice, once with the correct tab to show (on closing another tab), and then both events fire a second time with the next tab higher in the ordinal count. (This only happens when closing a tab, not when switching tabs.)
So I decided to work on a workaround until we can figure out why this is happening. I have tried adding a sessionStorage value that basically says "skip me" and then a timeout that destroys that sessionStorage item a second later.
This is working to return false on beforeshow and activate but then the tabpanel crashes on setactivetab. The documentation seems to indicate that returning false on beforeshow cancels the event, but this doesn't seem to work in practice.
Is there a simple way to stop the tabpanel from processing the setactivetab? Overriding it looks scary, as it is a complex event that is probably part of a chain of events.
I have not successfuly located the reason why beforeshow and activate are getting called a second time. In fact, these are just symptoms of the tabPanel setting active tab twice, right?
I know I'm still asking you to work blindfolded, but I sure do appreciate your help!
Bob Graham