#16633 closed defect (fixed)
dijit/Editor on IE9 can't enter text if "Active Scripting" is disabled for the "Internet" zone in IE
Reported by: | Ed Chatelain | Owned by: | bill |
---|---|---|---|
Priority: | undecided | Milestone: | 1.7.5 |
Component: | Editor | Version: | 1.8.3 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
See the discussion and suggested fix here: http://dojo-toolkit.33424.n3.nabble.com/IE-9-1-7-2-can-t-enter-text-into-dijit-Editor-td3854747.html
Change History (12)
comment:1 Changed 8 years ago by
comment:2 Changed 8 years ago by
Owner: | set to bill |
---|---|
Resolution: | → fixed |
Status: | new → closed |
In [30495]:
comment:4 Changed 8 years ago by
Milestone: | tbd → 1.8.4 |
---|
comment:6 Changed 8 years ago by
Milestone: | 1.8.4 → 1.7.5 |
---|
comment:7 Changed 7 years ago by
The applied fix, which assumes that every browser after IE9 will have the same bug until the end of time, causes dijit/tests/_base/robot/focus_mouse.html to never load on IE10.
comment:8 Changed 7 years ago by
Thanks for tracking that down. Do you have any idea on the other editor problem on IE11, #17595? It's easy to fix for IE9 and IE10 but I'm not sure what to do for IE11. (Taking the optimistic approach that IE11 works like other browsers does not work.)
Note: See
TracTickets for help on using
tickets.
The suggested fix was to switch the order of these two lines in RichText.js:
However, then on IE9 the onload event for the iframe never fires, so the editor initialization never finishes (and the real content of the editor never gets set).
Also, a cautionary comment from Christopher Morrissey (about switching the order):
this might cause a problem in IE when using https because I've seen in the past that having an empty src tag causes a warning that the page is trying to load unsecure content. I haven't seen this happen on IE 8 or IE 9 when I made sure the setting was on to warn when loading both secure and insecure content. I think it may be because instead of there being an empty src attribute, there is none at all and maybe that makes a difference? Or maybe it only shows up on versions of IE prior to IE 8.