remove editor reference to dijit global

[bill]

The editor references the dijit global during initialization as a way to set the <iframe> initial contents:

var iframeSrcRef = 'parent.' + dijit._scopeName + '.byId("'+this.id+'")._iframeSrc';
var s = 'javascript:(function(){try{return ' + iframeSrcRef + '}catch(e){document.open();document.domain="' +
		document.domain + '";document.write(' + iframeSrcRef + ');document.close();}})()';

This indirection of making src point at a variable, rather then just being a string literal, was done due to a limitation of the src attribute length in an old browser. Need to check what that browser was and if we still support it or not.

The current design is stopping dijit from working without globals.

[bill]

My tests (all on Windows) with inlined src:

• IE 6 (test_Editor.html loads)
• FF 3.5.9 (test_Editor.html loads)
• Safari 3.2.3 (test_Editor.html loads)
• IE 8 (passes dijit/tests/editor/runTests.html)
• IE 9 (half passes dijit/tests/editor/runTests.html, IE9 has lots of issues in general)
• Chrome 16 beta (passes dijit/tests/editor/runTests.html except for pre-existing EnterKeyHandling failure)
• FF 8 (passes dijit/tests/editor/runTests.html)

It looks like it's no longer necessary to use that parent.dijit._iframeSrc indirection.

[bill]

In [27128]:

Workaround IE9 bug where iframe is initialized twice, and the first time "parent" points to a phantom window object without dijit defined, and "frameElement" is null, fixes #14323 !strict. Also removes use of dijit global, fixes #14324 !strict.

[bill]

In [30261]:

backport [27128] to 1.7, fixing editor initialization problems on IE9/IE10, fixes #14323, #14324 on 1.7 branch !strict.