aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* CSS: Support custom propertiesConnor Atherton2017-03-073-9/+99
| | | | | | Fixes gh-3144 Closes gh-3199 Closes gh-3557
* Core: move jQuery.fn.nodeName to jQuery.nodeName, add testsMichał Gołębiowski2017-03-062-2/+50
| | | | | Ref ac9e3016 Close gh-3560
* Build: fix tests in AMD modeTimmy Willison2017-03-066-10/+14
| | | | - nodeName was included at the wrong spot in dependency lists
* Effects: stabilize rAF logic & align timeout logic with itOleg Gaidarenko2017-03-062-37/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Core: Deprecate jQuery.nodeNamekaran-962017-03-0112-36/+56
| | | | | Fixes gh-3475 Closes gh-3505
* Core: Move holdReady to deprecatedManoj Kumar2017-02-133-18/+7
| | | | | Fixes gh-3288 Close gh-3306
* Build: Keep deprecated module in slimTimmy Willison2017-02-131-1/+1
| | | | | Fixes gh-3237 Close gh-3533
* Traversing: $.fn.contents() supports HTMLTemplateElement南漂一卒2017-01-292-1/+64
| | | | | Fixes gh-3436 Closes gh-3462
* Event: Add radio click triggering testsAlex Padilla2017-01-191-11/+26
| | | | | Ref b442abacbb8464f0165059e8da734e3143d0721f Ref gh-3423
* Event: Trigger checkbox and radio click events identicallyAlex Padilla2017-01-194-8/+10
| | | | | Fixes gh-3423 Closes gh-3494
* Effects: Resolve issues revealed by recent Callbacks fixRichard Gibson2017-01-162-20/+36
| | | | | | | | | | 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
* Manipulation: Restrict the tbody search to child nodesRichard Gibson2017-01-092-1/+22
| | | | | | | For performance, use a querySelectorAll path instead of Javascript iteration. http://codepen.io/anon/pen/vywJjx?editors=1010 Fixes gh-3439 Closes gh-3463
* Callbacks: Prevent add() from unlocking with-memory listsRichard Gibson2017-01-092-1/+22
| | | | Fixes gh-3469 Closes gh-3470
* Tests: Update the loader so test pages always get jQueryRichard Gibson2017-01-091-33/+34
| | | | | | Pages used for iframe tests will now successfully load jQuery, even when opened directly in the browser. Closes gh-3489
* Build: fix markerPattern and ticketPattern regexes in package.jsonAlexander Lisianoi2017-01-091-2/+2
| | | | | | | Commit messages used to fail the style check if they contained a word starting with "ref", like reformat or reference, in their message body. Close gh-3437 Ref jzaefferer/commitplease#91
* Docs: Correct typo in issue templateAlex Louden2017-01-051-1/+1
|
* Build: Drop support for building on Node.js 0.12Michał Gołębiowski2016-12-302-29/+11
| | | | | | | | | | | Node.js 0.12 is no longer supported by upstream. So far we had to keep a workaround that would skip running ESLint there (or even load its task) as it no longer supports Node.js <4; the same applied to Node smoke tests as jsdom has also dropped support for those old Node versions. Those workarounds have been removed now. Ref 030191ae32dfcb7ecb2efb61d17a4964a3633e44 Closes gh-3478
* Tests: Added tests for symbol-separated tag namesDavid Broder-Rodgers2016-12-291-9/+18
| | | | | Fixes gh-2006 Closes gh-3473
* Offset: Eliminate little-used internal functionRichard Gibson2016-12-191-10/+10
| | | | Fixes gh-3449 Closes gh-3456
* Build: Use valid ecmaVersionRichard Gibson2016-12-191-1/+1
| | | | | | Fixes Node smoke tests Ref gh-3385 Closes gh-3460
* Build: Add most of the dist folder to .eslintignoreMichał Gołębiowski2016-12-191-0/+2
| | | | | | | This way `eslint .` run from the terminal will work regardless of ignored files present in the repository. Closes gh-3385
* Build: Drop jscs.json from .npmignoreMichał Gołębiowski2016-12-191-1/+0
| | | | The file doesn't exist anymore.
* Build: ESLint setup improvementsMichał Gołębiowski2016-12-199-36/+88
| | | | | | | 1. Use the short name of the preset in the config. 2. Run ESLint first on non-minified files. 3. Explicitly specify environments in every config file (those settings cascade which means we've been assuming a Node.js environment where we shouldn't have).
* Deferred: Stop inventing jQuery.when() resolution valuesRichard Gibson2016-12-162-8/+10
| | | | Fixes gh-3442 Closes gh-3445
* Offset: report offset for 0 sized elementsJason Bedard2016-12-122-15/+38
| | | | Fixes gh-3267 Closes gh-3367
* Build: Make the @CODE-replacing regex more robustMichał Gołębiowski2016-12-051-1/+5
| | | | | | | | | | | | | The code replacing @CODE in wrapper.js was written so that it expected both the code and the next line to start in the first column. This commit adjusts the regex so to get rid of that assumption and to work properly regardless of number of lines with comments after this block. While this is technically not necessary for our code, contributors sometimes re-format the wrapper file in their pull requests and the error messages they get don't tell them what's the real problem with their code. Closes gh-3429
* Build: jQuery Foundation -> JS FoundationTimmy Willison2016-12-055-6/+6
| | | | Close gh-3414
* Core: Deprecate jQuery.isArrayManoj Kumar2016-11-3013-18/+23
| | | | | Fixes gh-2961 Closes gh-3278
* Build: Stop testing on Node.js 0.10Michał Gołębiowski2016-10-312-3/+2
| | | | | Node.js 0.10 loses upstream support today (see https://github.com/nodejs/LTS/) so let's stop testing against it as well.
* Docs: Remove supported jQuery versions from ISSUE_TEMPLATE.mdMichał Gołębiowski2016-10-311-1/+1
| | | | | | | | We no longer support jQuery 1.x/2.x and mentioning 3.x would just mean the text gets out of date once we release jQuery 4. We only really support the latest jQuery version so let's make that clear. Closes gh-3372
* Build: Run tests on Node.js 7Michał Gołębiowski2016-10-261-0/+1
|
* Build: Updating the master version to 3.1.2-pre.Timmy Willison2016-09-221-1/+1
|
* Release: fix quotes for releasing on WindowsTimmy Willison2016-09-221-3/+4
|
* Release: add email to .mailmap, update AUTHORSTimmy Willison2016-09-222-1/+2
| | | | | - Not sure how that got there. I did check the privacy box at one point, but can't find any commits with that email
* Core: remove precautionary variable `readyFiring`Steve Mao2016-09-191-10/+4
| | | | Close gh-3284
* Build: Make sourcemap updates in two .replace() passesDave Methvin2016-09-191-4/+5
| | | | | Fixes gh-3260 Closes gh-3321
* Tests: Add test results for Safari 10/iOS 10, remove for Safari 8Michał Gołębiowski2016-09-191-19/+2
|
* Core: Compress stripAndCollapseRichard Gibson2016-09-191-5/+7
| | | | Close gh-3318
* Core: rnotwhite -> rhtmlnotwhite and jQuery.trim -> stripAndCollapseTimmy Willison2016-09-1515-51/+121
| | | | | | | | | | | | - Renames and changes rnotwhite to focus on HTML whitespace chars - Change internal use of jQuery.trim to more accurate strip and collapse - Adds tests to ensure HTML space characters are retained where valid - Doesn't add tests where the difference is inconsequential and existing tests are adequate. Fixes gh-3003 Fixes gh-3072 Close gh-3316
* Build: Update promises-aplus-tests for compat with Node 7Michał Gołębiowski2016-09-121-1/+1
| | | | | | The older promises-aplus-tests was relying on old Mocha that, in turn, used an obsolete graceful-fs version that is not guaranteed to work fine with the upcoming Node 7 and later.
* Tests: Disable a whitespace-setting test in Edge 14Michał Gołębiowski2016-09-121-1/+10
| | | | | | | | | | | | | | Working around this problem would require us to skip setting whitespace-only values except when they're valid which would be very fragile. Another option would be to set the value and see if it succeeded and then react to that. We've tried something like that in the past to be able to overwrite !important styles (see 24e5879) but it broke the CSS cascade (see https://bugs.jquery.com/ticket/14836#comment:5) and was triggering MutationObserver callbacks too often so it was reverted in PR gh-1532. Ref gh-3204 Ref gh-1532
* Core: expose noConflict in AMD modeTimmy Willison2016-08-155-32/+24
| | | | | | | | - For compability reasons, we had already added the global in AMD mode, but without noConflict. This adds back noConflict to AMD (which fixes noConflict mode in the tests). Fixes gh-2930
* Traversing: Let .not(arraylike) pass non-element nodesDave Methvin2016-08-102-7/+26
| | | | | Fixes gh-3226 Closes gh-3261
* Build: Update Sizzle to 2.3.3Richard Gibson2016-08-084-6/+6
| | | | Fixes gh-3263
* Build: Update Sizzle to 2.3.2Richard Gibson2016-08-083-3/+3
|
* Ajax: Don't mangle the URL when removing the anti-cache paramDave Methvin2016-08-082-12/+22
| | | | | Fixes gh-3229 Closes gh-3253
* Build: Update Sizzle to 2.3.1Richard Gibson2016-08-084-36/+91
| | | | Fixes gh-3224
* Event: Optimize delegated event processingRichard Gibson2016-08-041-17/+24
| | | | Closes gh-3255
* Build: .eslintrc -> .eslintrc.jsonOleg Gaidarenko2016-08-028-7/+7
| | | | | | | | `.eslintrc` format is deprecated - http://eslint.org/docs/user-guide/configuring#configuration-file-formats Fixes gh-3248 Closes gh-3247
* Build: Simplify Gruntfile constructionsOleg Gaidarenko2016-08-025-31/+41
| | | | Fixes gh-3246