replied on August 23, 2016
Hi Karim,
This is a known issue in Web Access 9 and 10. The problem is that the code Web Access uses to detect the chrome extension fails when Web Access is accessed through an iframe. We plan on addressing the issue in a future release.
Note that we believe the root cause is in Web Access proper, not the Chrome extension. This means the customer will need to upgrade to the latest version of Web Access to get the fix (as opposed to pushing out a new version of the Chrome extension).
For your reference, the id number for the change request TFS6972.