#1990 closed defect (fixed)
Dojo demos appear not to run under IE7
| Reported by: | Owned by: | Jared Jurkiewicz | |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | General | Version: | 0.4 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: |
Description
Opening demoEngine.html in IE7 does not produce any results.
Steps:
- in file explorer right click on demoEnging.html
- IE displays a yellow bar at the top of the IE window warning about a security risk
- Click and select allow script to run.
exp: demo application appears act: nothing is shown in the browser. The tab title is labeled "Dojo Demos", but no contont or errors are produced
true in dojo 0.4.0 true in dojo 0.4.1rc
dojo 0.3.1 reports an error: "FATAL: symbol 'dojo.widget' is not defined after loading 'package.js'"
comment I'm working on a project, Dojo seems pretty nice under Firefox, but too many of my users have IE to ognore it.
Attachments (4)
Change History (14)
comment:1 Changed 14 years ago by
comment:2 Changed 14 years ago by
| Milestone: | → 0.4.1 |
|---|---|
| Resolution: | → invalid |
| Status: | new → closed |
browser issue. Not our bug. Marking as such and closing.
comment:4 Changed 13 years ago by
| Resolution: | invalid |
|---|---|
| Status: | closed → reopened |
Alex,
I'm reopening this as you said you were amenable to the patch suggestion. I had a bit more thought on this last night and think there's even a nicer patch we could do to make this automatic for users when they are on IE 7 and doing local file loads. 'll attach both patches and you can pick which you prefer.
Basically patch files without alternate in the name are the original patch suggestion, allow a djConfig option users can set. Patched with the 'alternate' in the name take it one step further. It does a check that the browser is IE and if the window protocol (how you opened dojo), is file: (local load), then automatically set that flag for you. I've tested this with the demos we have in 0.4.3 and it works nicely. I'll also gen a patch set for 0.9 and append those to this as well.
Changed 13 years ago by
| Attachment: | dojo_0.4.3_xhr_ie7_force.patch added |
|---|
Patch that puts in a flag into 0.4.3 to allow forsing of activeX xhr on IE 7
Changed 13 years ago by
| Attachment: | dojo_0.4.3_xhr_ie7_force_alternate.patch added |
|---|
Patch that allows forcing of activeX xhr on IE 7, *and* auto-enables if the files are being local-loaded to begin with (file:)
Changed 13 years ago by
| Attachment: | dojo_0.9_xhr_ie7_force.patch added |
|---|
Patch that puts in an option to force ActiveX xhr on IE 7
Changed 13 years ago by
| Attachment: | dojo_0.9_xhr_ie7_force_alternate.patch added |
|---|
Patch that puts in an option to force ActiveX xhr on IE 7 and auto-enables on local loads.
comment:5 Changed 13 years ago by
There. I've added the patches. My preference is for the alternate one, as it only engages when it's a local load of dojo and does get local usage of IE 7 working for 0.4.3 and 0.9.
comment:6 Changed 13 years ago by
comment:7 Changed 13 years ago by
| Owner: | changed from anonymous to Jared Jurkiewicz |
|---|---|
| Status: | reopened → new |
comment:8 Changed 13 years ago by
comment:9 Changed 13 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:10 Changed 13 years ago by
I applied the alternate patches I noted in this defect. Tested on IE 6, IE 7, for 0.9 and 0.4.X, seems to work fine now.
This appears to be an issue with opening the file directly in IE7 instead of serving it from a webserver. Deploying Dojo 0.4.1 to tomcat 5.5 results is properly working demos.