Forum Discussion
aw, no not really. I believe that there are some browsers that don't allow access to cross-access framesets. It is possible that chrome considers https to cause a cross-access frameset. If the frame content itself an http frame ? Can you see any content/html text in the object browser for the panel ? In other words does chrome allow TC to read the contents of the frame or doesn't it allow it in in the first place ? Do you get different results in other browsers ?
Even the inner text is empty when I checked it. It seems this is a limitation introduced by how Chrome handles security for iframed pages.
It works fine in FFox. IE on the other hand is not an option for us as our application started using Web Components which gets converted by IE.
I was just hoping that there was a way to make Chrome work to imrpove test coverage.
- RUDOLF_BOTHMA5 years agoCommunity Hero
Perhaps this is then something that will have to be taken up with Smartbear support. I didn't find anything in their support documentation regarding this myself, but I would expect that they should be able to think of something. It's not full coverage if you can't test in all browsers :smileyhappy:
Related Content
Recent Discussions
- 2 days agovladd1