Resolves yui#1411.

Conflicts:
	build/loader-yui3/loader-yui3-coverage.js
	build/loader-yui3/loader-yui3-debug.js
	build/loader-yui3/loader-yui3-min.js
	build/loader-yui3/loader-yui3.js
	build/loader/loader-debug.js
	build/loader/loader-min.js
	build/loader/loader.js
	build/yui-nodejs/yui-nodejs-debug.js
	build/yui-nodejs/yui-nodejs-min.js
	build/yui-nodejs/yui-nodejs.js
	build/yui/yui-debug.js
	build/yui/yui-min.js
	build/yui/yui.js
	src/loader/js/yui3.js

Currently, running Calendar tests containing the focus process will
fail in Firefox. The cause of this problem seems to be a problem that
test case is not bad, what happens if you are running Yeti while running
Firefox in the background. This problem does not occur in a browser
other than Firefox. In addition, there is a test that includes a focusing
process in the same way the Widget Button module [1], but it has to
ignore Yeti is here. Therefore, I would like to ignore running some tests
by Yeti in the same way in Calendar. Fix yui#1363.

[1]: src/widget-buttons/tests/unit/assets/widget-buttons-test.js

Conflicts:
	src/event/js/tap.js

IO clears the form content on end, but if the caller removed the form soon
after it was called, this fails at a removeAttribute on part of the, now
non-existent form content.

We should check that the form exists before attempting to reset it.

This problem occurs when you try to set an opacity to 1 using node.setStyle()
method on IE. It has adapted to change an opacity only if less than 1, but we
should change an opacity, even if it passed 1. Fix yui#1469.

yui#1376

This was originally overwritten when merging in v3.14.1.

Even though the attribute's effect gets activated for any value of the
attribute, this way it's easier for anyone looking at the DOM to figure
out what the visibility of the node is.

…indow.getSelection`.

This is no longer necessary as using `xdr: native` will remove
all custom headers for you by default.

IE11 changed the `type` of pointer event objects from 'MSPointerDown' to
'pointerdown' to comply with their proposed W3C standard. Firefox
Nightly also supports W3C Pointer events with a
dom.w3c_pointer_events.enabled flag

As recommended by Microsoft in
http://msdn.microsoft.com/en-us/library/ie/dn304886(v=vs.85).aspx