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 02a9d9f94b
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 d471842b3e)
Fixes gh-2015
Closes gh-2298
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 61f812b7e7
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
- 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
* Remove third argument from "addEventListener"
* Remove third argument from "removeEventListener"
* Remove second argument from "getComputedStyle"
Ref gh-2047
Ref 85577a348a
(cherry-picked from fac67a9842)
Since we don't have this in off method and its a common perception
that this is a rudiment code
Ref gh-2248
Closes gh-2249
Android 2.3 is very slow & times out a lot in async tests, they have to be
restarted multiple times to settle. Long test execution is not a huge problem
as Android 2.3 is tested only periodically during the night, unstable tests
are a bigger problem. This might mitigate that.
In a regular scenario almost all tests should pass so increasing the timeout
for all browsers shouldn't have a huge impact on overall test time.
(cherry-picked from ff18d8e206)
Closes gh-2232
