(cherry-picked from 04a29696e5b176ac66401120e433d52425222f0f)

Refs gh-2301

Make iterating over jQuery objects possible using ES 2015 for-of:

    for ( node of $( "<div id=narwhal>" ) ) {
        console.log( node.id ); // "narwhal"
    }

(partially cherry-picked from bb026fc12c3c2ad37f47f0919e484bddcdc3d291)

Fixes gh-1693

JSON needed to be added to JSHint globals as it's not implied by the es3
setting and yet all our supported browsers have it implemented.

(cherry-picked from 1556c4661af647e355a9a5c0a814012955e231bc)

(Cherry-picked from 285cfbfccc4c61d50ee8e0fe6e23695dc663e166)
Ref 26eca143c2dd857b9e3d1c446a467fed16e903d2

Ref 3655c4e1908cc3ee49487e7e26e8cfca9fe8146d

IE8 doesn't like named anonymous expressions. Not naming the function
expression reduces the gzipped size by 5 bytes.

In ECMAScript 2015 the function will get the name inferred from the
variable name (here: swap) anyway.

Refs 02a9d9f9

Specifying the type and URL is deprecated:

https://docs.npmjs.com/files/package.json#license
http://npm1k.org/

(cherry-picked from 8e92e1ea3c533f3be82c99bbafaaf74b5bdedecc)

Fixes gh-2331
Closes gh-2330

(cherry-picked from 38a669735d08bcbd28cfb0d77eee82c67aa89eeb)

Refs 0705be475092aede1eddae01319ec931fb9c65fc
Refs gh-2287
Closes gh-2362

This prevents jQuery from caching a prefixed property name if provided
directly by the user, e.g. the following code:

	elem.css( "msTransform", "translate(5px, 2px)" );

should not prevent one from from later setting the transition directly:

	elem.css( "transform", "translate(5px, 2px)" );

on a browser not understanding the unprefixed version which is the case
for Safari 8 & transform.

(cherry-picked from d471842b3e3af83c9a1be06b5d16f75bfa96af8c)

Fixes gh-2015
Closes gh-2298

Ref 6df669f0fb87cd9975a18bf6bbe3c3548afa4fee
Ref gh-2336

(Cherry-picked from 3c9277086742fe3a38a268ef97184be34e294655)
Thanks @elas7

Fixes gh-2359

Fixes gh-2290
Ref a644101ed04d0beacea864ce805e0c4f86ba1cd1

The logic for IE8 has been incorrectly reversed: every non-local request
outside of the whitelist was run via the native XHR. This commit reverses
this logic and adds back a fallback to the ActiveX XHR if the native one
fails even after the regex detection.

Refs 61f812b7

(Cherry-picked from 0705be475092aede1eddae01319ec931fb9c65fc)
Fixes gh-2286
Closes gh-2287
Ref trac-11733

Ref 20aaed367f993f3c2aa204183d82d0d73efa114f

Ref c074006a69db73a116dc04ec78844468a8cea7d3
Ref gh-2312

IE throws an error on cross-domain PATCH requests if issued via the ActiveX
interface. This commit switches the logic to use the native XHR in all
non-local requests.

Fixes gh-1684
Closes gh-2183

Related:
https://github.com/bower/bower.json-spec/commit/a325da3d79baab018c572d75dc1781b12322f6cd

Close gh-2304

Fixes gh-1708
Close gh-1714

Fixes gh-2264
Close gh-2265

- Note: support for SVG is limited in jQuery,
  but this is one area where the cost vs benefit ratio
  was acceptable.

Fixes gh-2199
Close gh-2268

- Reverts behavior from 10399dd, which we never released.
  BR and inline elements are considered visible.
- The possibility of dropping .offsetWidth and .offsetHeight
  was debunked by this perf:
  http://jsperf.com/visible-hidden-and-getclientrects

Fixes gh-2227
Close gh-2281

Since we're testing the factory code from intro.js on master only it's best
to have those two files almost identical.

This commit leaves only one difference between them: "jQuery Compat" vs.
"jQuery" in the second line.

Closes gh-2294

Fixes gh-1767
Fixes gh-2071
Closes gh-2180

(cherry picked from commit 86419b10bfa5e3b71a7d416288ab806d47a31d1f)

Conflicts:
	src/css.js
	src/css/defaultDisplay.js
	src/effects.js
	test/data/testsuite.css
	test/unit/css.js
	test/unit/effects.js

Fixes gh-2269
Close gh-2270

Fixes gh-2225

Fixes gh-2224

Ref gh-2219

Fixes gh-2219
Close gh-2218

Fixes gh-2238
Close gh-2243

Close gh-2254

Fixes gh-2114

Fixes gh-2115

Fixes gh-1784
Close gh-2043

Fixes gh-2228

- This will be tested in migrate

Fixes gh-2101