We detected an issue when using wrapper with multiple screens and the new version of Spotfire 12. This resulted in the wrong screen (div element) responding in an open page request. The reason for this is that the _doc element in the spotfire-webplayer class did not bind to the correct SpotfireAPI object.
I have added a test to check the id of the Spotfire API element before the binding, so the correct SpotfireAPI object binds to the _doc element, which makes the correct screen react again.
We detected an issue when using wrapper with multiple screens and the new version of Spotfire 12. This resulted in the wrong screen (div element) responding in an open page request. The reason for this is that the _doc element in the spotfire-webplayer class did not bind to the correct SpotfireAPI object.
I have added a test to check the id of the Spotfire API element before the binding, so the correct SpotfireAPI object binds to the _doc element, which makes the correct screen react again.