Hacker News Reader

Hacker News

Comment by vonklaus | Hacker News Reader

Full thread

vonklaus

Major Changes:

.load, .unload, and .error, deprecated since jQuery 1.8, are no more. Use .on() to register listeners.

jQuery.Deferred is now Promises/A+ compatible

Error cases don’t silently fail

Animations now use requestAnimationFrame

Massive speedups for some jQuery custom selectors

View on HN

> jQuery.Deferred is now Promises/A+ compatible

Finally. Our old codebase is using quite a lot of jQuery deferreds and, well, Promises/A+ clearly improved a lot of things API-wise.

jQuery.Deferred was such a convoluted api for me. I polyfilled a Promises lib and felt bad having multiple libraries that on the cover said they did the same things.

Is anyone using custom selectors? quick googling only returns 5+ years old results

I use :input (https://api.jquery.com/input-selector/) occasionally

I use :visible. The notes say it can increase speed 17x in certain cases.

The notes say it is computationally expensive and bad for performance.

    Using this selector heavily can have performance implications, as it may force the browser to re-render the page before it can determine visibility. Tracking the visibility of elements via other methods, using a class for example, can provide better performance.

To be clear, it is 17x faster than it was.

I did at one point in time for flagging links to show a "leaving site" prompt. Now the JS simply checks any link when you click it (no more custom selector for flagging).

Reply on news.ycombinator.com