Opened 6 years ago

Closed 6 years ago

Last modified 5 years ago

#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:

Change History (12)

comment:1 Changed 6 years ago by bill

The suggested fix was to switch the order of these two lines in RichText.js:

ifr.setAttribute('src', s);
this.editingArea.appendChild(ifr);

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.

comment:2 Changed 6 years ago by bill

Owner: set to bill
Resolution: fixed
Status: newclosed

In [30495]:

Workaround IE9 problem when "Active Scripting" is disabled for the "Internet" zone in IE9's settings. Fixes #16633 on trunk, !strict. Also removing some legacy support for Safari 4.

comment:3 Changed 6 years ago by bill

In [30496]:

Workaround IE9 problem when "Active Scripting" is disabled for the "Internet" zone in IE9's settings. Fixes #16633 on 1.8 branch, !strict.

comment:4 Changed 6 years ago by bill

Milestone: tbd1.8.4

comment:5 Changed 6 years ago by Ed Chatelain

In [30500]:

Backport workaround IE9 problem when "Active Scripting" is disabled for the "Internet" zone in IE9's settings. Fixes #16633 on 1.7 branch, !strict.

comment:6 Changed 6 years ago by Ed Chatelain

Milestone: 1.8.41.7.5

comment:7 Changed 6 years ago by Colin Snover

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 6 years ago by bill

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.)

comment:9 Changed 6 years ago by Colin Snover <github.com@…>

In 31782ca326dc6ced92ff7d78db30f64474fe35a9/dijit:

Error: Processor CommitTicketReference failed
Unsupported version control system "git": Can't find an appropriate component, maybe the corresponding plugin was not enabled? 

comment:10 Changed 6 years ago by Colin Snover <github.com@…>

In 50f40acbc9fbe814a030fe844f8d8ff32cfb3c8a/dijit:

Error: Processor CommitTicketReference failed
Unsupported version control system "git": Can't find an appropriate component, maybe the corresponding plugin was not enabled? 

comment:11 Changed 6 years ago by mahays0 <mahays0@…>

In 4697d231e7ec444685cc2cb0d796db7897d9f6bf/dijit:

Error: Processor CommitTicketReference failed
Unsupported version control system "git": Can't find an appropriate component, maybe the corresponding plugin was not enabled? 

comment:12 Changed 5 years ago by Colin Snover <github.com@…>

In 7ac4dc7fe1503c9548a12a4a5ef52feca46b2355/dijit:

Error: Processor CommitTicketReference failed
Unsupported version control system "git": Can't find an appropriate component, maybe the corresponding plugin was not enabled? 
Note: See TracTickets for help on using tickets.