Skip to content
Branch: master
Commits on Mar 7, 2018
  1. Build: remove artefact from previous commit

    markelog committed Mar 7, 2018
    Follow-up for 09684ba
Commits on Mar 5, 2018
  1. Build: Seasonal update of uglify and its options

    markelog committed Mar 2, 2018
    raw     gz Compared to last run
     =      = dist/jquery.js
    -294    -88 dist/jquery.min.js
    Closes gh-3994
Commits on Mar 6, 2017
  1. Effects: stabilize rAF logic & align timeout logic with it

    markelog committed Mar 6, 2017
    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
Commits on Aug 2, 2016
  1. Build: .eslintrc -> .eslintrc.json

    markelog committed Jul 29, 2016
Commits on Jul 15, 2016
  1. Build: Update eslint config and fix associated errors

    markelog committed Jul 15, 2016
Commits on Jul 8, 2016
  1. Build: Don't use ESLint 3.x

    markelog committed Jul 8, 2016
    Since it is not supported by older node versions :/
  2. Build: More ESLint related changes

    markelog committed Jul 8, 2016
Commits on Jun 22, 2016
  1. Build: Improve ESLint configuration (#3188)

    markelog committed Jun 22, 2016
    * Bump eslint-config-jquery package to 0.1.4 version
    * Add subtask "dist" to "eslint" task and add it to the build task list
    * Make gitignore globs more flexible for the "dist" folder
    Fixes gh-3169
Commits on Jun 11, 2016
  1. Build: ESLint details

    markelog committed May 10, 2016
    Use eslint pragmas, fix new errors, etc
    Closes gh-3148
Commits on May 19, 2016
  1. Events: don't execute native stop(Immediate)Propagation from simulation

    markelog committed May 19, 2016
    In Firefox, called `stop(Immediate)Propagation` methods,
    in capturing phase prevents receiving focus
    Fixes gh-3111
Commits on Apr 27, 2016
  1. Revert "Effects: Remove additional parameters of easings"

    markelog committed Apr 27, 2016
    This reverts commit b7a7dea.
    Fixes #3064
Commits on Apr 8, 2016
  1. Core: add test for `jQuery.isPlainObject(localStorage)`

    markelog committed Apr 8, 2016
Commits on Apr 4, 2016
  1. Ajax: execute jQuery#load callback with correct context

    markelog authored and timmywil committed Apr 4, 2016
    Thanks @blq (Fredrik Blomqvist)
    Fixes gh-3035
    Close gh-3039
  2. Tests: do not run IE9 effect tests if inside testswarm

    markelog committed Apr 3, 2016
    That test doesn't work properly in such environment
    Ref e04e246
    Fixes gh-2888
    Closes gh-3034
Commits on Mar 28, 2016
  1. Support: improve support properties computation

    markelog committed Mar 28, 2016
    * Remove div from the memory if it is not needed anymore
    * Make `computeStyleTests` method a singleton
    Fixes gh-3018
    Closes gh-3021
Commits on Mar 14, 2016
  1. Build: try insight package to get info about custom builds

    markelog committed Mar 12, 2016
    Fixes gh-2890
    Closes gh-2988
Commits on Mar 12, 2016
  1. Tests: add additional test for jQuery.isPlainObject

    markelog committed Mar 12, 2016
    Ref 00575d4
    Also see discussion in
    #2970 (comment)
Commits on Mar 4, 2016
  1. Build: update husky dependency

    markelog committed Mar 4, 2016
    Fixes gh-2915
Commits on Mar 3, 2016
  1. Build: update grunt-contrib-jshint and grunt-jscs while we at it

    markelog committed Mar 3, 2016
Commits on Feb 13, 2016
  1. Build: add `npm-debug.log` to `.gitignore`

    markelog committed Feb 13, 2016
  2. Build: remove npm-debug file

    markelog committed Feb 13, 2016
  3. Tests: use `jQuery` variable instead of `$`

    markelog committed Feb 13, 2016
    For some reason that works with `amd` but not with builded version
    Fixes gh-2909
Commits on Feb 11, 2016
  1. Build: simplify and correct .editorconfig

    markelog committed Feb 11, 2016
Commits on Feb 8, 2016
  1. Tests: account for new offset tests

    markelog committed Feb 8, 2016
  2. Revert "Offset: account for scroll when calculating position"

    markelog committed Feb 8, 2016
    This reverts commit 2d71594.
    This commit provoked new issues: gh-2836, gh-2828.
    At the meeting, we decided to revert offending commit
    (in all three branches - 2.2-stable, 1.12-stable and master)
    and tackle this issue in 3.x.
    Fixes gh-2828
Commits on Jan 31, 2016
  1. Tests: fix another traverse test

    markelog committed Jan 31, 2016
    Tricky test - if isolated, was executed fine, but falling
    if runned with other tests
    Ref b97c8d3
Commits on Jan 29, 2016
  1. Tests:Build: update qunit and fix incorrect test

    markelog committed Jan 29, 2016
    * Update QUnit to the latest version (1.20.0)
    * Corrected test was dependent on QUnit UI, which is always a bad idea
Commits on Jan 28, 2016
  1. Build: add scripts.precommit script

    markelog committed Jan 28, 2016
    It was losted while merging gh-2881
Commits on Dec 2, 2015
  1. Core: do not expose second argument of the `jQuery.globalEval`

    markelog committed Nov 13, 2015
Commits on Oct 17, 2015
  1. Build: update Sizzle to 2.2.1

    markelog committed Oct 17, 2015
    Ref #2644 - `selector` module in Edge - Waiting for Sizzle update
    Fixes #2390
You can’t perform that action at this time.