#532 closed defect (invalid)
Editor not working with IE / High Security Level (ActiveX disabled)
Reported by: | Owned by: | alex | |
---|---|---|---|
Priority: | blocker | Milestone: | |
Component: | Widgets | Version: | 0.2 |
Keywords: | IE XMLHTTP Editor | Cc: | |
Blocked By: | Blocking: |
Description
Our customers are mainly big corporate IT companies, use Internet Explorer with high security settings and don't let the users change those settings. No Admin rights, IE settings are locked. No chance to install Firefox.
Is there something that could be done?
The Editor Widget doesn't work with High Security level in Internet Explorer. It looks like it fails when trying to init XMLHTTP. I read there is a IFrame transport implemented (Ticket #34)? How can this transport be enabled, so that the Editor works?
It's easy to reproduce the problem: disable ActiveX, enable JavaScript?.
Settings: Windows XP Internet Explorer Version 6.0.2900.2180.xpsp_sp2_gdr.050301-1519 Tools / Internet Options / Security Default Level / High Custom Level... Scripting / Active scripting: Enable
Test pages and errors:
http://archive.dojotoolkit.org/nightly/tests/widget/test_Editor_from_textarea.html
FATAL: XMLHTTP not available: Automation server can't create object DEBUG: failed loading ../../src/widget/Editor.js with error: [Error: XMLHTTP not available: Automation server can't create object] FATAL: XMLHTTP not available: Automation server can't create object DEBUG: failed loading ../../src/widget.js with error: [Error: XMLHTTP not available: Automation server can't create object] FATAL: XMLHTTP not available: Automation server can't create object DEBUG: failed loading ../../src/package.js with error: [Error: XMLHTTP not available: Automation server can't create object] FATAL: XMLHTTP not available: Automation server can't create object DEBUG: failed loading ../../src.js with error: [Error: XMLHTTP not available: Automation server can't create object] FATAL: XMLHTTP not available: Automation server can't create object DEBUG: failed loading ../../package.js with error: [Error: XMLHTTP not available: Automation server can't create object] FATAL: Could not load 'dojo.widget.Editor'; last tried 'package.js'
http://archive.dojotoolkit.org/nightly/tests/widget/test_Editor.html FATAL: XMLHTTP not available: Automation server can't create object DEBUG: failed loading ../../src/event/package.js with error: [Error: XMLHTTP not available: Automation server can't create object] FATAL: XMLHTTP not available: Automation server can't create object DEBUG: failed loading ../../src/package.js with error: [Error: XMLHTTP not available: Automation server can't create object] FATAL: XMLHTTP not available: Automation server can't create object DEBUG: failed loading ../../package.js with error: [Error: XMLHTTP not available: Automation server can't create object] FATAL: symbol 'dojo.event' is not defined after loading 'package.js'
Change History (6)
comment:1 Changed 16 years ago by
Milestone: | → 0.4 |
---|---|
Owner: | changed from anonymous to alex |
comment:2 Changed 16 years ago by
Hi,
Some more information: ActiveXObject are not allowed at that security level. As far as I know Dojo supports an alternative transport (IFRAME transport) if XMLHTTP is not available, but in some situations currently still tries to use XMLHTTP (maybe those places are actually unrelated to the editor, but I'm not sure). I'm not familiar with the Dojo code, so I might be wrong.
Thomas
comment:3 Changed 16 years ago by
Milestone: | 0.4 → 0.4.1 |
---|
comment:4 Changed 16 years ago by
Summary: | Editor not working with IE / High Security Level → Editor not working with IE / High Security Level (ActiveX disabled) |
---|
Alex, schedule as 0.4.1 or 0.5 (or wontfix) as you see fit.
comment:5 Changed 16 years ago by
Resolution: | → invalid |
---|---|
Status: | new → closed |
the iframe transport doesn't handle package loading, although you may be able to use a cross-domain build to handle this situation. Alternately, make a build that interns all the resources for this widget.
Marking "invalid".
I'm not sure there's much we can do here... alex?