Problem with oxy_browser Form Control
Posted: Wed Oct 18, 2023 11:40 pm
Good afternoon!
We are trying to use oxy_browser on Oxygen Web and have had some problems.
We create a .html inside the CSS folder that is calling oxy_browser. We called this html via CSS and the first error we noticed was the message "file protocol is disabled". Then we discovered that the "enable.file.protocol" option should be changed in the Administration tab.
After this configuration, instead of the HTML being plotted on the screen and its javascript activated, Oxygen Web started downloading the HTML. And besides the download, it kept the iframe blank.
We carried out a test via Oxygen Desktop and noticed that it is working correctly.
Are we perhaps doing something wrong or forgetting some configuration?
Our intention is that whenever you open the XML, the system brings information from our CMS and includes it within the tags without having to save the content in the file. And from the description of oxy_browser this would be possible.
Another important detail worth highlighting. If we switch from oxy_browser to oxy_htmlContent, Oxygen renders the content perfectly on the screen, even passing the same HTML as a parameter.
HTML File
Desktop working fine
Oxygen Web downloading HTML Page
Test before protocol option
We are trying to use oxy_browser on Oxygen Web and have had some problems.
We create a .html inside the CSS folder that is calling oxy_browser. We called this html via CSS and the first error we noticed was the message "file protocol is disabled". Then we discovered that the "enable.file.protocol" option should be changed in the Administration tab.
After this configuration, instead of the HTML being plotted on the screen and its javascript activated, Oxygen Web started downloading the HTML. And besides the download, it kept the iframe blank.
We carried out a test via Oxygen Desktop and noticed that it is working correctly.
Are we perhaps doing something wrong or forgetting some configuration?
Our intention is that whenever you open the XML, the system brings information from our CMS and includes it within the tags without having to save the content in the file. And from the description of oxy_browser this would be possible.
Another important detail worth highlighting. If we switch from oxy_browser to oxy_htmlContent, Oxygen renders the content perfectly on the screen, even passing the same HTML as a parameter.
Code: Select all
/* CSS for all CIR Elements */
accessPointRef{
content:
oxy_browser(
href, 'teste.html',
width, 600px,
height, 400px);
-oxy-foldable: true;
}
CSS Code
zoneRef{
content:
oxy_browser(
href, 'teste.html',
width, 600px,
height, 400px);
-oxy-foldable: true;
/*
WORKING!!
content:
oxy_htmlContent(
href, 'teste2.html',
id, "main",
width, 400px);
-oxy-foldable: true;
*/
}
Code: Select all
<!DOCTYPE html>
<html>
<head>
<script type="text/javascript">
function bridgeReady() {
initialize();
}
function initialize() {
var main = document.getElementById("main");
var p = document.createElement('p');
p.style.color = 'black';
p.textContent = 'I was appended to the div';
main.appendChild(p);
console.log("test");
}
</script>
</head>
<body>
<div id="main">
<h3>TESTING HTML CONTENT FROM CSS DIR</h3>
</div>
</body>
</html>