2 IE9 questions

[senordhuff]

Hi,

I've been looking at the forums regarding IE9 because I am seeing an issue with file uploads using SmartClient 6.5.1. So, I have 2 questions.

1. Is there a formal recommendation to not use DOCTYPE and/or use meta tags like the one below so that SmartClient (6.5.1,7, or 8) works with IE9?
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />


2. We are seeing "Access is denied" error messages when trying to do file uploads in our https environment with SmartClient 6.5.1 on IE9. With Smartclient 8.0, this is not happening. Don't suppose you have any idea if there is a way to fix this in Smartcliient 6.5.1? It is only impacting IE9 and no other browsers or versions.

[senordhuff]

On question #2, it appears that it is happening both http and https environments with 6.5.1. Let me know if you have any insight.

[Isomorphic]

1. Yes: use those meta tags, do not set a DOCTYPE at all.

2. Are you able to reproduce this with a sample? Do you have a stack trace or any further information other than "Access denied"?

[senordhuff]

on #2, yes it can be reproduced with a sample. Look here:

http://www.smartclient.com/docs/6.5.1/a/b/c/go.html#class..UploadItem


Clicking in the box produces the following error visible in the dev console

 10:23:20.560:XRP6:WARN:DynamicForm:isc_DynamicForm_27:[Class UploadItem] form item defined with no 'name' property - Value will not be saved. To explicitly exclude a form item from the set of values to be saved, set 'shouldSaveValue' to false for this item.
10:23:38.247:selectionchange1:WARN:Log:Error:
	'Access is denied.
'
	in http://www.smartclient.com/docs/6.5.1/a/b/development/ISC_Core.js?isc_version=6.5.1.js
	at line 1559
    anonymous(_1=>"Access is denied.
", _2=>"http://www.smartclient.com/docs/6.5.1/a/..."[86], _3=>1559)

[senordhuff]

Hi, any feedback on this issue? I was able to recreate for you as requested from the Feature Explorer.

[Isomorphic]

We've looked at these warnings - they are basically spurious exceptions. At the moment, due to the age of 6.5.1, we don't plan to patch it - I think in your case this is OK.

[senordhuff]

Thanks,

I've patched our environment to ignore this exception when thrown for IE9 and not report it to the user.