| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
This change replaces the use of contains to check for attachment
by isAttached function
Closes gh-3977
Ref gh-3504
|
|
|
|
|
|
|
| |
for both simple and complex selectors
Fixes gh-3272
Closes gh-3910
|
| |
|
|
|
|
|
| |
Fixes gh-3871
Close gh-3869
|
|
|
|
|
| |
Fixes gh-3605
Close gh-3895
|
|
|
|
|
| |
Fixes gh-2960
Closes gh-3888
|
|
|
|
|
| |
Fixes gh-3438
Closes gh-3781
|
|
|
|
| |
Fixes gh-3214
|
|
|
|
| |
Fixes gh-3609
|
|
|
|
|
|
|
|
|
| |
+30 bytes instead of +182
Thanks to @faisaliyk for the first pass on this feature.
Fixes gh-3532
Close gh-3917
|
|
|
|
|
| |
- selectors beginning with a child combinator are not valid natively.
This fixes the tests when using selector-native.js
|
|
|
|
|
| |
Fixes gh-2958
Close gh-3885
|
|
|
|
|
| |
Fixes gh-2959
Close gh-3884
|
|
|
|
|
| |
- Add back camelCase to the public object (deprecate not remove)
Ref #3384
|
|
|
|
|
| |
Close gh-3604
Fixes gh-3384
|
|
|
|
| |
Fixes gh-3808
Closes gh-3872
|
|
|
| |
Closes gh-3851
|
|
|
|
|
| |
Ref 692f9d4db30c9c6c4f6bc76005cf153586202fa6
Fixes gh-3777
Closes gh-3778
|
|
|
|
| |
Fixes gh-2144
Closes gh-3745
|
|
|
|
| |
Fixes gh-3611
Closes gh-3741
|
|
|
|
|
| |
Fixes gh-3698
Fixes gh-3602
Closes gh-3738
|
|
|
|
|
| |
Fixes gh-3586
Close gh-3590
|
|
|
|
|
|
| |
Ref gh-3589
Fixes gh-3699
Fixes gh-3730
Closes gh-3729
|
|
|
|
| |
Fixes gh-3699
Closes gh-3700
|
| |
|
|
|
|
| |
This reverts commit 3befe5911af0cf516896482bb9ddf197c8cb8a8e.
|
|
|
|
|
| |
Fixes gh-3629
Close gh-3702
|
|
|
|
|
| |
Fixes gh-3693
Close gh-3694
|
|
|
|
| |
Fixes gh-3606
Closes gh-3657
|
|
|
|
| |
Fixes gh-3589
Closes gh-3656
|
|
|
| |
Closes gh-3661
|
|
|
|
|
| |
Firefox 35 and newer support style.float directly.
Closes #3569
|
|
|
|
|
|
| |
Ref gh-3597
Fixes gh-3600
Fixes gh-3596
Closes gh-3617
|
|
|
|
|
|
|
|
| |
Thanks @anseki
Fixes gh-3080
Fixes gh-3107
Closes gh-3096
Closes gh-3487
|
| |
|
|
|
|
| |
- Fixes an issue with getting computed style on detached elements
|
|
|
|
| |
This reverts commit b442abacbb8464f0165059e8da734e3143d0721f.
|
|
|
|
|
| |
Close gh-3577
Fixes gh-3571
|
|
|
|
|
| |
Close gh-3576
Fixes gh-3573
|
|
|
|
|
|
| |
- getCSS already falls back to inline styles
Ref gh-3561
|
|
|
|
|
| |
Close gh-3561
Fixes gh-3193
|
|
|
|
|
|
| |
Fixes gh-3144
Closes gh-3199
Closes gh-3557
|
|
|
|
|
| |
Ref ac9e3016
Close gh-3560
|
|
|
|
| |
- nodeName was included at the wrong spot in dependency lists
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
Fixes gh-3475
Closes gh-3505
|
|
|
|
|
| |
Fixes gh-3288
Close gh-3306
|
|
|
|
|
| |
Fixes gh-3436
Closes gh-3462
|
|
|
|
|
| |
Fixes gh-3423
Closes gh-3494
|
|
|
|
|
|
|
|
|
|
| |
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
|