Why does the BUI fail to load a browser control in a workspace?
Browser User Interface (BUI)
There are several limitations for the use of a browser control in the BUI. Browser contols in BUI are loaded as an iFrame, rather than a separate process used in the .NET console. These are permanent limitations of the BUI and do not reflect a defect or issue with the product. Here are some limitations of the this type of use of a browser control:
The first being that in a browser if we are trying to render a https site inside a http site or http site inside https. This is due to the fact that in modern browsers rendering of such content is treated of security violation. Hence in BUI this is treated as a known limitation of browser control.
Secondly, any site which does not want to be embedded inside iframe will not be rendered. For example, if the response header containing X-FRAME-OPTIONS is set to the same origin or BUI site and is not added to ALLOW-FROM header will not be rendered.
Thirdly, any site trying to navigate top level page will not be rendered by default due to the iFrame being loaded as a sandboxed attribute. For example, BUI site navigating to a different site will not be allowed. If you have external content that needs to be loaded in the sandboxed iFrame in this way, such as flash content, please submit a service request to Oracle Service Cloud Technical Support and that issue can be reviewed.