I render these tabs within onFirstInteractive callback and its working great.
We then started running into some serious performance issues - very slow loading viz- and we started exploring ways to improve performance and make better use of caching (given our specific business use case).
We discovered that by appending #1 to our viz url the caching improvement is tremendous.
for eg...instead of
BUT - doing so breaks all our above custom tab code.
- OnFirstInteractive no longer fires!!
- Trying to call methods on the viz throw an excetion - for eg calling viz.getWorkbook() throws Cannot read property 'get_workbook' of null
- even specifying options on the viz like hideTabs and hideToolbar have NO impact, ie nothing changes. (height and width do change)
It almost seems like using this cached viz (#1) does not create a full viz object and does not allow any manipulation of the viz!
This is a big problem for us and I cant find any support/help on this.
Has anyone experienced anything like this ? Any suggested fixes or workarounds?
I have a feeling you're right about the viz object. It could also be an order of operations issue because it's calling a cached version prior to enacting the rest of the parameters. I won't if there's a JS parameter for calling the cached version. I'll do a bit more digging. Have you found a solution yet?