Revert "Fix dijit Editor in cross-domain pages with document.domain set"
It breaks a number of Editor tests on IE10, like Editor_a11y.html and Editor_mouse.html.

This reverts commit 730d18d0e52b8a4c6b483bd25210763905c03528.
Prefer dojo.position() over dojo.marginBox(), fixes #11444 on 1.7 branh.
Fixes dijit/place test failures and maybe others on IE10.

git-svn-id: http://svn.dojotoolkit.org/src/dijit/trunk@28029 560b804f-0ae3-0310-86f3-f6aa0a117693
(cherry picked from commit fdf06fc9ed6de55df92e10a46c587c993e0a7630)
IE10 fixes to dijit/place tests.
Backported from 948cda25a51f8f065a99c1d018beb6889cb3a380, refs #16121
fix spurious Dialog test failures on IE10 due to async focus(), refs #16926

(cherry pick of db846a232891b365c26d92698a6798bc6f0c59bd)
fix IE10 rounding problem, fixes #16128, refs #17969

(cherry picked from commit f469394c20265f5dbfdaeec2c233a61efffd2fbb)
(cherry picked from commit 1059aeb7c47da5d679ff85372f9ae3490ff58f2e)
For dijit/tests/helpers::onFocus(), if focus changes multiple times during the specified delay,
return the latest focus to the callback.

Prerequisite to fix to #16961: fixes a failure in the cancel test in Dialog_mouse.html:
due to that change, focus first goes to the close icon and then goes back to the button.

Refs #8285, #16961.

(cherry picked from commit 21cb189911489e2ec9a42ced8d7913a401999296)
Workaround IE10 problem where Dialog's close icon doesn't get focus.
Not sure why tabindex="-1" isn't working but in this case we can just set it to tabindex="0".
Fixes #16961.

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

Also backports delay added in 21cb189911489e2ec9a42ced8d7913a401999296,
to avoid spurious failure on Dialog_mouse.html on IE8, refs #8285
Use opacity :0 rather than opacity: 0.01.
Opacity: 0.01 was a workaround to a firefox or webkit bug that's been fixed,
and using opacity:0 allegedly fixes a rendering problem on IE on certain hardware/drivers.

Fixes #17200.

(cherry picked from commit 4068c904425890334d5face9cb692815ae4db7bb)
(cherry picked from commit b343c470b3d41f0fd9eec94060377bd334e0c2b0)
Don't call preventDefault() on MSPointerDown/pointerdown event.
Likewise for MSPointerUp/pointerup.
It prevents the mousedown / mouseup events from being emitted.

Fixes #17709.

(cherry picked from commit d4334c3d206c01ad28d6f030560445c2866dd496)

Conflicts:
	tests/tree/robot/Tree_mouse.html
	tests/tree/test_Tree.html

(cherry picked from commit e71b4bc67606488b4f18966192a36f0422b7bf6f)

Conflicts:
	tests/tree/test_Tree.html
	tree/_dndSelector.js
[Backport IE11 fixes to 1.7] fix ENTER key toggle on IE9, fixes #15793

Picked from https://github.com/dojo/dijit/commit/5ef1323383acb6aba0d3c8ab5d283a5feeaec815
Fix ENTER key click on IE9 (for _HasDropDown).

Switched from synthetic dojo/_base/connect keypress event to native keydown event.   In practical terms, that means that the dropDownWidget.handleKey() callback from _HasDropDown now gets passed an event where keyCode is set rather than charOrCode, and you check for a space character as evt.keyCode == keys.SPACE rather than evt.charOrCode == " ".

Fixes #15709 on 1.7 branch.

Also needed to change _AutoCompleterMixin.js since _onKey() is now called on keydown instead of the synthetic keypress event.

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

Conflicts:
	_HasDropDown.js
	a11yclick.js
Revert "Fix bad has(ie) check in IE11 with older versions of focus.js, which invoked attachEvent. Refs #17311."

This reverts commit 50a5a1747a6d69afc5e2c19fe3401eb885a0b3ee.

It was breaking Menu_a11y.html, specifically that when using ENTER to select a menu item,
the menu would close but the parent MenuBarItem would remain selected (i.e. blue).
Either this needs to be rolled back, or replaced with the change to focus.js to
use dojo/on consistently (e2b992b720df9936af690e08de1a76c299f38613).
Give popup time to display before calling mouseMoveAt().
Otherwise mouse moves to top left of screen.
Fixes BgIframe.html test on IE10.

TODO: change may not be necessary with upgraded DOH robot, so test again.
Tooltip placement fixes.
Refs #4282 and fixes #14122 on 1.7 branch.

Squash commit of:

----
Rewrite Tooltip-placement.html, removing unnecessary dependency on dijit.form.ValidationTextBox etc.
Calling dijit.Tooltip.show() should be sufficient for testing tooltip placement, and will hopefully
have less intermittent failures than the old test.   Refs #4282 !strict.

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

---

Fix calculations in Tooltip.orient() for when Tooltip is above/below rather than to the left or the right.
It's suspicious though why we need to measure the size of the connector at all, rather than just measuring
the size of the whole tooltip.

Fixes #14122 !strict.

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

Conflicts:
	Tooltip.js

----

Remove code from [23065] to "Adjust width for tooltips that have a really long word or a nowrap setting".
It doesn't work, as shown by "test14" failure in Tooltip-placement.html.   It will make any tooltip with
a sufficient amount of text expand to fill the width of the viewport, even if the tooltip content has
neither large words nor a nowrap setting.   Refs #4282 !strict.

git-svn-id: http://svn.dojotoolkit.org/src/dijit/trunk@26939 560b804f-0ae3-0310-86f3-f6aa0a117693
(cherry picked from commit aec9bfd24f694faae2f3e4af8ac386b46265be2f)
avoid spurious failure on chrome where italic button is checked,
and stop using internal editor method to position caret, refs #9460
(cherry picked from commit f130c59e937bf9e71e4fe10f161972d9c1bb3dfd)

(cherry picked from commit 513200647599abb14740c5faa912737cc3192fc4)
(cherry picked from commit 5526335ca754a1c6b251eefd09ab99503af191db)
[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