[Backport IE11 fixes to 1.7] fix ENTER key toggle on IE9, fixes #15793

Picked from https://github.com/dojo/dijit/commit/5ef1323383acb6aba0d3c8ab5d283a5feeaec815
[Backport IE11 fixes to 1.7]   Removing parts of !ToggleDir test that fail after switching editor iframe to standards mode.

commit: https://github.com/dojo/dijit/commit/948bf4f763a5688843fac653709774558f755646
[Backport IE11 fixes to 1.7] fix spurious Dialog test failures on IE10 due to async focus(), refs #16926

cherry-picked from: https://github.com/dojo/dijit/commit/db846a232891b365c26d92698a6798bc6f0c59bd

git-svn-id: http://svn.dojotoolkit.org/src/dijit/trunk@31076 560b804f-0ae3-0310-86f3-f6aa0a117693

Conflicts:
	tests/Dialog.html
On IE9+ clicking a Button (with the mouse) to open a Dialog and then closing the Dialog doesn't refocus the Button, due to the async nature of the focus event.   But I don't think we should be guaranteeing refocus except when the Dialog was opened via keyboard (tabbing to the Button and then pressing ENTER/SPACE).   So changing the mouse test to not check for Dialog refocus.   Refs #16926.

git-svn-id: http://svn.dojotoolkit.org/src/dijit/trunk@31089 560b804f-0ae3-0310-86f3-f6aa0a117693
(cherry picked from commit ad8a64b8e9390981c8fae585889b1aefd607cd60)

Conflicts:
	tests/robot/Dialog_mouse.html
fix numerous test case errors, refs #11132.

git-svn-id: http://svn.dojotoolkit.org/src/dijit/trunk@29090 560b804f-0ae3-0310-86f3-f6aa0a117693
(cherry picked from commit 855cef82202c2e2c036de26f058a054374352381)

Conflicts:
	tests/robot/TooltipDialog_mouse.html
[Backport IE fixes to 1.7] more test fixes to avoid spurious failures, refs #7681 on 1.8/ branch

git-svn-id: http://svn.dojotoolkit.org/src/branches/1.8/dijit@29504 560b804f-0ae3-0310-86f3-f6aa0a117693
(cherry picked from commit 1058941e058b68839be402d47d9434da0dcd0072)

Conflicts:
	tests/layout/robot/BorderContainer_complex.html
[Backport IE fixes to 1.7] Fix JS errors occurring during EnterKeyHandling in IE11. Curiously, the tests did not catch them. Fixes #17466.

Note: I am not adding the has("trident") test that was added in other branches because I can't seem to reproduce on IE11...

(cherry picked from commit 8ec9162b32398ed7a2a15272e277532698a6512d)

Conflicts:
	_editor/RichText.js
	_editor/plugins/EnterKeyHandling.js

(cherry picked from commit 1e0d8c0945335796f09fce4d4eeb9105c28b4b69)

Conflicts:
	_editor/RichText.js
[backport IE fixes to 1.7] allow for IE9+ async focus in !ComboBox and !FilteringSelect test, refs #16926

git-svn-id: http://svn.dojotoolkit.org/src/dijit/trunk@31121 560b804f-0ae3-0310-86f3-f6aa0a117693
(cherry picked from commit fbec15cae397b80cec54682cb40858a4e125050b)
(cherry picked from commit 902b314bfcd6a6138781740656c09083e3b01c24)
[Backport IE fixes to 1.7] allow for IE9+'s async focus in Form test, refs #11800

git-svn-id: http://svn.dojotoolkit.org/src/dijit/trunk@31106 560b804f-0ae3-0310-86f3-f6aa0a117693
(cherry picked from commit a63501c383e1fe018aeec952dc490719fb644df5)
(cherry picked from commit 919a3428177c010c010f4bbcc2f897ee2c4b7df7)
[Backport IE fixes to 1.7] Make necessary additions to Editor for modern Trident

Refs #17311.

(cherry picked from commit bb0ae352737b8994419d591c728bf962d1d0759b)

Conflicts:
	_editor/RichText.js

(cherry picked from commit 574fd141dd4ae18cd08174f4d5b892afdf7aa114)

Conflicts:
	_editor/RichText.js

(cherry picked from commit f2c48ad6469eaebff35bc45dd27c0ea05406e9d1)

Conflicts:
	_editor/RichText.js
[backport IE fixes to 1.7] Fix formatblock command in IE9+

Fixes FontChoice plugin test failures

Refs #17311.

(cherry picked from commit 8d884077865c16f9debe62077f8ebb2da07ee29f)
(cherry picked from commit 397c2da26c0fb18da29643ee2e8f1535246d4863)

Conflicts:
	_editor/RichText.js

(cherry picked from commit 58fac915c27e8e28e76dca762d309fcf0da24881)
[Backport IE fixes to 1.7] Make <body> height 100%, so that clicking anywhere on the editor window focuses it on IE8.  As a side effect, the scroll bar needs to go on the <body> rather than on <html>.  Tested on IE8, Chrome, FF (manually), and IE9.  Fixes #16804 !strict.

git-svn-id: http://svn.dojotoolkit.org/src/dijit/trunk@31303 560b804f-0ae3-0310-86f3-f6aa0a117693
(cherry picked from commit b61b56813dc0c922976ca783496c374b81ca3b58)

Conflicts:
	_editor/RichText.js

(cherry picked from commit 162b535bcccb4711e036c7cdf5dfea23f412dc5a)
[Backport IE fixes to 1.7] Set height:100% on #dijitEditorBody in addition to <body>.
Note that usually #dijitEditorBody is actually the <div> inside the <body>.

Setting height:100% on the <div> fixes the Chrome problem where typing ctrl-A
and then some characters locks up the editor.   Doesn't seem to affect IE or FF.
The scrollbar still seems to work (showing up when the editor content overflows).

Refs #16804, fixes #17559.
Fixes regression from b61b56813dc0c922976ca783496c374b81ca3b58.
(cherry picked from commit fbfc0fe89385b8c85f2ae75c27a15ac807b42e71)

(cherry picked from commit d3d7755e7d3d2135dcedcc51cc16f7431a065d5d)

Conflicts:
	_editor/RichText.js

(cherry picked from commit c77d355c71583e6cea314a1d1058bc791407bf27)
Fix auto-expand editor on IE11.

Not backported from a 1.8 commit, but seems necessary otherwise auto-expand editors have resize handles + a horizontal scrollbar on IE11.
[Backport IE fixes from 1.7] Prevent keypresses from triggering onNormalizedDisplayChange

This avoids toolbar buttons from becoming disabled in IE11 when
the editor frame is unfocused by keyboard navigation to the
toolbar. The onNormalizedDisplayChange will occur once the entire
editor is blurred.

The ultimate solution is probably to stop using
queryCommandEnabled (like all other RTEs) but that would require
a significant amount of additional effort for diminishing gain.

Fixes #17595.

(Note on 1.7 backport: I added the hast("trident") test to activate the code path modified by the fix,
plus I had to add the creation of the tabStop div in the !has("ie") case in onLoad.
I tried to just go to the has("ie") path for IE11 too, but it breaks later).

(cherry picked from commit 2b37eebc7284cb83bf7e35e1225a95b1a8d90d46)

Conflicts:
	_editor/RichText.js