Maksym Hevyk - Hello everyone! We’re building a...
Hello everyone! We’re building a feature with the React SDK where we list liveboards in a table. When a user clicks a dashboard name, they’re taken to a details page where we render the liveboard with
Navigation works fine with our custom Back button, but the browser’s back button breaks because ThoughtSpot’s navigation pollutes the browser history.
After debugging (using
- Liveboards without tabs don’t cause this issue (because
- With tabs:
- If no
- Manual tab switches also add entries to history (it works fine).
- Setting
To sum up, the internal redirect to the default tab inside the iframe is polluting browser history, and I can’t intercept or prevent it.
Is there any way to handle or work around this issue?
LiveboardEmbedliveboardIdNavigation works fine with our custom Back button, but the browser’s back button breaks because ThoughtSpot’s navigation pollutes the browser history.
After debugging (using
onALLROUTE_CHANGEKey observations:
- Liveboards without tabs don’t cause this issue (because
ROUTE_CHANGE- With tabs:
- If no
activeTabIdROUTE_CHANGE- Manual tab switches also add entries to history (it works fine).
- Setting
activeTabIdliveboardEmbed.trigger(HostEvent.GetTabs)To sum up, the internal redirect to the default tab inside the iframe is polluting browser history, and I can’t intercept or prevent it.
Is there any way to handle or work around this issue?
