13.04.2020, 20:24
Hi,
Just to explain, the controller only creates a html page and that is loaded by the client browser, any page loaded in a iframe is happening client side as the controller has added a <iframe> element in the html code and the browser will load the source that is assigned to the element. In the last versions of FW is a extra option to prevent the loading of the iframe source when the plan that is holding the iframe is not active (in the background) to avoid streaming of the source in the background, the checkbox “persistant” is default disabled so you could check that, the rest is happening client side so there is nothing you can do from the controller..
BR,
Erwin
Just to explain, the controller only creates a html page and that is loaded by the client browser, any page loaded in a iframe is happening client side as the controller has added a <iframe> element in the html code and the browser will load the source that is assigned to the element. In the last versions of FW is a extra option to prevent the loading of the iframe source when the plan that is holding the iframe is not active (in the background) to avoid streaming of the source in the background, the checkbox “persistant” is default disabled so you could check that, the rest is happening client side so there is nothing you can do from the controller..
BR,
Erwin