Technical Restrictions

There are several technical restrictions that may prevent AppNavi from working properly in a system. These limitations are mostly technological or due to security settings. This article describes the most common stumbling blocks.

Content Security Policy

The Content Security Policy is a problem that often occurs during the integration of AppNavi, but can usually be solved by settings on the web server or the web application itself. This [article] (doc:issues-with-content-security-policy-csp) gives a good guide to the problem.


Embedding AppNavi in iFrames is not a problem. However, there are several security mechanisms that prohibit embedding content into an iFrame. These security mechanisms usually take effect when it is a foreign domain. You can find more information on how to use iFrames in this [article] (doc:working-with-iframes-frames).

Shadow Roots (Shadow DOM)

An important aspect of web components is encapsulation — being able to keep the markup structure, style, and behavior hidden and separate from other code on the page so that different parts do not clash, and the code can be kept nice and clean. The Shadow DOM API is a key part of this, providing a way to attach a hidden separated DOM to an element. This article covers the basics of using the Shadow DOM. In the Shadow Dom, a distinction is made between open and closed modules. Recording and playback of content is only possible in open DOM nodes.