This chapter is for reference only since the user environment will vary. It describes issues you may encounter while using the Nexacro and presents possible solutions..

Web Browser Option

Changing web browser options may impact how an app runs as described in this section.

JavaScript Activation

Issue

Setting the web browser to not use JavaScript causes the app to not function normally.

Description

Even though basic options are set to activate JavaScript in general, you need to check the relevant option first when the apps cannot be found on the screen since you can choose other options.

Possible Solution

Depending on the web browser, activate the JavaScript usage option. (The option can vary depending on brower version.) Refer to the following link or each web browser's help for details.

http://www.enable-javascript.com

For Internet Explorer, you can change the option using the following menu:

Tools > Internet options > Security > Custom level > Internet Zone > Scripting > Active scripting

File Download Activation

Issue

Even though you restrict to download files from web browsers, files can be downloaded using File download component.

Possible Solution

Even though basic options are set to activate file download, you need to check the relevant option first when the files are not downloaded since you can choose other options.

Depending on the browser, activate the file download option. (The option can vary depending on browser version.) Refer to the web browser's help for details.

In case of Internet Explorer, you can change the option using the following menu.

Tools > Internet options > Security > Custom level > Internet Zone > Downloads > File Download

HTTP 1.1 Activation

Issue

If you restrict the use of HTTP 1.1 on the web browser, apps might work slowly or might not work at all.

Possible Solution

Even though basic options are set to activate HTTP 1.1, you need to check the relevant option first when the applications do not work, since you can choose other options.

This option is provided in Internet Explorer only, and can be changed using the following menu.

Tools > Internet options > Advanced > HTTP settings > Use HTTP 1.1 through proxy connections
Tools > Internet options > Advanced > HTTP settings > Use HTTP 1.1

XMLHTTP Activation

Issue

If you restrict the use of XMLHTTP on a web browser, apps may not be able to process dynamic scripts.

Possible Solution

Even though basic options are set to activate XMLHTTP, you need to check the relevant option first when the application does nt work since you can choose other options.

In Internet Explorer you can change the option using the following menu.

Tools > Internet options > Advanced > Security > Enable native XMLHTTP support

Internet Explorer Compatibility View

Issue

If you add a domain serviced on Internet Explorer as a target for compatibility view mode, the screen might not be displayed normally.

Possible Solution

An HTML file to be used when developing Nexacro-based apps is set in rendering mode by the Meta tag, so it can work in Internet Explorer's standard mode (IE=Edge) to utilize improved features of later versions. Consequently, the compatibility view icon is not shown in the address window in the corresponding mode.

For this reason, a guide for standard mode operation can be provided after checking the user's browser settings, or the user can be informed of the compatibility view mode with a separate script.

var agentStr = navigator.userAgent;

var mode;

if(agentStr.indexOf("rv:11.0") >= 0) {
	mode = "IE11";
}
else if (agentStr.indexOf("Trident/6.0") > -1) {
	if (agentStr.indexOf("MSIE 7.0") > -1) {
		mode = "IE10 Compatibility View";
	} else {
		mode = "IE10";
	}
}
else if (agentStr.indexOf("Trident/5.0") > -1) {
	if (agentStr.indexOf("MSIE 7.0") > -1) {
		mode = "IE9 Compatibility View";
	} else {
		mode = "IE9";
	}
}
else if (agentStr.indexOf("Trident/4.0") > -1) {
	if (agentStr.indexOf("MSIE 7.0") > -1) {
		mode = "IE8 Compatibility View";
	} else {
		mode = "IE8";
	}
}
else {
	mode = "IE7";
}

document.title = "Browser Mode:\t" + mode;

Adding Web Content Using Iframe

Issue

If Nexacro contents are added in the form of iframe on the existing web screen which is already developed and operated, the screen might not be displayed on Internet Explorer.

Possible Solution

An HTML file to be used when developing Nexacro-based apps is configured to work in Edge mode. If the HTML file used on the existing screen is not set as DTD (Document Type Definition), it works in Quirks mode. In this process, the screen might not be displayed normally.

In this case, add the Meta tag as shown below.

<head>
  <meta http-equiv="X-UA-Compatible" content="IE=Edge"/>
</head>