Squish mostly hooks itself into the browser/web page at the JavaScript level and is thus compatible with most web pages.
But this JavaScript-based approach means that whatever security restrictions the browser imposes on JavaScript code in the page also applies to Squish.
So if a web page has frames or iframes that load content from a different domain than the website itself, Squish for Web will not be able to hook into it. This is because, for the sake of security, the browser prevents accessing the internals of the iframe if the domain is different: but as a consequence, this also prevents Squish from accessing the frame or iframe.
By different domains, we mean if the part between the protocol (http:// or https://) and the first slash is different, for example:
https://www.qt.io/product/quality-assurance/squish
https://www.qt.io/blog
These have the same domain.
https://www.qt.io/product/quality-assurance/squish
https://doc.qt.io/
These have different domains ("www" vs. "doc").
We are not aware of any ways to disable this particular security feature in Microsoft Internet Explorer.
We are not aware of any ways to disable this particular security feature in Firefox.
For Google Chrome you can register a .bat file/shell script (
Edit>Server Settings>Browser...) for Google Chrome with approximately this content (Windows .bat file example):
start /wait "" "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --disable-web-security %*(Also see Disable same origin policy in Chrome .)