| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Without this change animating properties from jQuery.cssNumber on non-elements
throws an error.
Ref gh-4055
Closes gh-4061
|
|
|
|
| |
Fixes gh-3609
|
|
|
|
|
| |
Fixes gh-2959
Close gh-3884
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Update QUnit to 1.23.1
- Remove unused dl#dl from test/index.html
- Remove unused map#imgmap from test/index.html
- Ensure all urls to data use baseURI
- Add the 'grunt karma:main' task
- customContextFile & customDebugFile
- Add 'npm run jenkins' script
Close gh-3744
Fixes gh-1999
|
|
|
|
| |
Fixes gh-2144
Closes gh-3745
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
rAF logic was introduced almost three years ago relative to this commit,
as a primary method for scheduling animation (see gh-1578 pull).
With it there was two substantial changes - one was explicitly mentioned
and the other was not.
First, if browser window was hidden aka `document.hidden === true`
it would immediately execute all scheduled animation without waiting
for time pass i.e. tick time become `0` instead of 13 ms of a default value.
Which created possibility for circular executions in case if `complete`
method executed the same animation (see gh-3434 issue).
And the second one - since then there was two ways of scheduling animation:
with `setInterval` and `requestAnimationFrame`, but there was a
difference in their execution.
In case of `setInterval` it waited default `jQuery.fx.interval` value before
actually starting the new tick, not counting the first step which wasn't
set to be executed through tick method (aka `jQuery.fx.tick`).
Whereas `requestAnimationFrame` first scheduled the call and executed
the `step` method right after that, counting the first call of
`jQuery.fx.timer`, `tick` was happening twice in one frame.
But since tests explicitly disabled rAF method i.e.
`requestAnimationFrame = null` and checking only `setInterval` logic,
since it's impossible to do it otherwise - we missed that change.
Faulty logic also was presented with `cancelAnimationFrame`, which couldn't
clear any timers since `raf` scheduler didn't define new `timerId` value.
Because that change was so subtle, apparently no user noticed it proving
that both `cancelAnimationFrame` and `clearInterval` code paths are redundant.
Since `cancelAnimationFrame` didn't work properly and rAF is and was a primary
used code path, plus the same approach is used in other popular animation libs.
Therefore those code paths were removed.
These changes also replace two different functions which schedule the animation
with one, which checks what type of logic should be used and executes it
appropriatley, but for secondary path it now uses `setTimeout` making it more
consistent with rAF path.
Since ticks are happening globally we also don't require to listen
`visibilitychange` event.
It also changes the way how first call is scheduled so execution of
animation will not happen twice in one frame.
No new tests were not introduced, since now `setTimeout` logic should be
equivalent to the rAF one, but one test was changed since now we actually
execute animation at the first tick.
Fixes gh-3434
Closes gh-3559
|
|
|
|
|
|
|
|
|
|
| |
Notify full progress before resolving empty animations
Register animation callbacks before their ticker
Remove the right timer when immediately-done animations spawn more
Ref 9d822bc1c13dd3393b418210a99537c22c06f2c3
Fixes gh-3502
Fixes gh-3503
Closes gh-3496
|
|
|
|
|
|
| |
Use eslint pragmas, fix new errors, etc
Closes gh-3148
|
|
|
|
|
|
|
|
| |
Single- and no-argument calls act like Promise.resolve.
Multi-argument calls act like Promise.all.
Fixes gh-3029
Closes gh-3059
|
|
|
|
|
| |
Fixes gh-2863
Closes gh-3037
|
|
|
|
|
|
|
|
| |
That test doesn't work properly in such environment
Ref e04e246552c27e872bbf4ae00b55def02b197189
Fixes gh-2888
Closes gh-3034
|
|
|
|
|
|
|
|
| |
This commits backports some changes done in the patch to the then-existing
compat branch that removed support for old browsers and added some support
comments.
Refs 90d7cc1d8b2ea7ac75f0eacb42439349c9c73278
|
|
|
|
|
|
|
|
|
|
| |
Support comments that were lacking the final IE/Edge version that exhibits
the bug were checked & updated. Links to the Chromium bug tracker were updated.
Code in tests related to unsupported browsers (like Android 2.3 in non-basic
tests) has been removed.
Fixes gh-2868
Closes gh-2949
|
|
|
|
|
|
|
| |
Fixes gh-2654
Fixes gh-2308
Close gh-2810
Ref 86419b10bfa5e3b71a7d416288ab806d47a31d1f
|
|
|
|
|
| |
Fixes gh-2716
Close gh-2724
|
|
|
|
|
|
|
|
|
| |
- Ignore certain tests that obviously are not supported
- Beefed up the sortOrder, uniqueSort, isXMLDoc, and attr functions
Fixes gh-1742
Fixes gh-2048
Close gh-2703
|
|
|
|
|
|
|
|
| |
* Remove QUnit jshint globals
* Extend QUnit.assert methods
* Use assert.async instead of start/stop/done
Ref b930d14ce64937e9478405eee2828d4da091d2cb
|
|
|
|
|
| |
Fixes gh-2283
Closes gh-2292
|
|
|
|
| |
Fixes gh-2056
|
|
|
|
|
|
|
|
|
|
|
|
| |
http://qunitjs.com/upgrade-guide-2.x/
For most of the boring work was used
https://github.com/apsdehal/qunit-migrate package
However, it can't update local qunit helpers, plus in some places
old QUnit.asyncTest signature is still used
Fixes gh-2540
|
|
|
|
| |
Closes gh-2507
|
|
|
|
|
|
|
|
|
|
|
| |
Android 2.3 chokes on unquoted reserved words being used as property names
which was making Deferred tests not run.
Acknowledge the sad fact that Android 2.3 is not ES5-compliant browser
and enable the "es3" option in JSHint config.
Fixes gh-2478
Closes gh-2481
|
| |
|
| |
|
|
|
|
|
|
| |
Fixes gh-1767
Fixes gh-2071
Closes gh-2180
|
|
|
|
| |
Ref gh-2219
|
|
|
|
|
| |
Fixes gh-2219
Close gh-2218
|
|
|
|
|
|
| |
More to come later.
(cherry picked from commit f6f8848fbe477fa93fd27ac7f10885dd6e97f633)
|
|
|
|
|
| |
The #dl element has 0 height so it's now considered hidden regardless
of its width.
|
|
|
|
|
|
|
|
| |
* Make animation behave as if jQuery.fx.off = true if document is hidden
* Use cancelAnimationFrame in jQuery.fx.stop
Closes gh-1578
|
|
|
|
|
|
|
|
|
|
| |
Same as before, just use don't use prefixes, since they pretty match useless now
and use page visibility API to determine if animation should start.
Also null the requestAnimationFrame attribute in window for tests since
sinon does not provide fake method for it.
Fixes #15147
|
| |
|
|
|
|
|
|
|
|
| |
Take "olddisplay" value into the account
Fixes #14824
Closes gh-1566
Ref 73fe17299a840a8a7f3ffffcac15e32a88bd3d66
|
|
|
|
|
| |
Fixes #14848
Closes gh-1548
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Chrome 31 reports incorrect offsetWidth on a table cell with fixed width.
This is fixed in Chrome 32 so let’s just skip the failing test in Chrome 31.
See https://code.google.com/p/chromium/issues/detail?id=290399
|
|
|
|
|
| |
Fixes #14623
Closes gh-1473
|
|
|
|
|
| |
Fix #14040
Close gh-1457
|
| |
|
| |
|
| |
|
|
|
|
| |
Fixes #14344.
|
|
|
|
| |
ea5c22ec12e6a548b1ec2d7b0dcd9f71bea8d5dd
|
|
|
|
| |
(cherry picked from commit 2b6a7b1caf5f95034e0324a44ca9e3f27956ff64)
|
| |
|
| |
|
| |
|
| |
|