Spotfire Web Player 7.0 does not work in iframe under SharePoint 2010

Products	Versions
Spotfire Web Player	7.0 and higher

Description

Description:
Support for Internet Explorer 8 and 9 has been dropped, because Web Player 7.0 depends on functionality that is only available in Internet Explorer 10 and above. Internet Explorer can run in several different modes, emulating older browsers for backward compatibility. SharePoint is one such example: SharePoint 2010 by default makes Internet Explorer run in IE8 mode, and SharePoint 2013 uses IE10 mode. Running the Web Player inside a SharePoint 2010 website, typically by inclusion using an iframe element, can make the Web Player render incorrectly if the Internet Explorer version itself adheres to the system requirements, because it runs in a mode that is not supported. Note: for a complete list of Spotfire Web Player system requirements, see the link in the reference section below.

Symptoms:
The two most common symptoms follow.

1). Text labels / links / buttons are replaced with curly brackets {} containing text.

Example: The "About" button will be visible as "{{labels.startPageAbout}}" instead of as a normal button.

2). The page is completely blank / white.

The symptoms also include various Javascript related errors that can only be seen in Internet Explorer's "Developer Tools." To start Developer Tools, press the "F12" key or go to the menu and select "F12 Develop tools". From here you can also find out what "Browser Mode" and "Document Mode" the browser renders the page in. It must not use IE8, IE9, or compatibility mode.

Cause:
SharePoint 2010 places a in its <head> by default. This tells Internet Explorer to render the page in a mode that is not supported by the Web Player.

Resolution

Make SharePoint 2010 place a different X-UA-Compatible tag on the page (IE=10 or IE=Edge) where you place an <iframe> with Web Player 7.0.x in it. See the reference section, for links to two different web pages that explain how it can be done. This can break some SharePoint functionality, so each use case will need individual design, development, and testing. Changing the master page in SharePoint is generally not recommended, because the problem only needs to be solved on the page that embeds the Web Player.