Adobe captivate 2019 popup blocker message

Hm, the OP debbie.griffin might have left the conversation, but for everyone else and in particular WSDB9 I'll be a bit picky now:

The two CPM.js methods to open up an URL are very different and that is not because they are distinguished through the use of openURL respectively window.top.location.href - it it the use of _parent as opposed to _top that makes them so different.

cp.openURL(\'https://www.mycustomer.com/directory/subdirectory/file.xxx?module=I1\',\'_parent\')

'window.top.location.href = \'https://mycustomer.com/directory/subdirectory/file.xxx?module=LH5\'

According to W3 Schools there are four HTML link target attributes:

1. _self - Default. Opens the document in the same window/tab as it was clicked (Cp interface: Current)
2. _blank - Opens the document in a new window or tab (Cp interface: New)
3. _parent - Opens the document in the parent frame (Cp interface: Parent)
4. _top - Opens the document in the full body of the window (cp interface: Top)

_parent or _top makes a big difference. Supposed there is no _parent window, because there is no subordinate window (i.e. iFrame) in which the link is clicked, then the browser with activated popup-blocker might be triggered into an attempt to create such a _parent window on the fly which somewhat comes close to a window.open() method. That of course triggers the popup-blocker. On the contrary with _top this problem doesn't arise.

Just saying

Klaus

My suggestion would be to talk to your IT department and make them aware of the issue. This is a security setting in either the deployment of browsers or perhaps a setting that is imposed by your LMS.