Posted on Updated on

Image result for JQUERYJQUERY .NET

Run this code in a program and check the reassure. In jQuery 3, this will log “parent settled” before summoning any callback, every tyke callback will then log “satisfied youngster”, and the grandchildren will be rejected with Error “grandchild”. In past jQuery forms, this would log “rejected kid” (the kid Deferred having been dismisses rather than satisfied) once and after that instantly end with uncaught Error “grandchild” (“parent settled” not being logged and the grandchildren staying uncertain). JQuery. When has been upgraded too so as to acknowledge any protest that can be utilized as a part of then callback, which incorporates local Promise objects. On the off chance that for reasons unknown you can’t acknowledge or change your code to take after this new, and a more exact approach to handle guarantees, you can reestablish the past conduct by supplanting any utilization of .then() with the deplored .pipe() technique (which has an indistinguishable mark). Included catch () to conceded. The catch () technique was added to guarantee questions as a nom de plume for .then (null, FN).

Other improvement in jQuery 3

Removed deprecated event register

Finally the deprecated load, unload and error, deprecated since jQuery 1.8; are now removed. Remember that the correct method to register an event handler in jQuery is on, and the opposite off.

Error cases exception

Previous jQuery versions always return “something” instead of throwing errors. This can be frustrating because an obvious logical error returns an empty result, which is difficult to handle appropriately.

JQuery 3 in similar scenarios now throws an exception, which can be handled accordingly.

Animation now use request Animation Frame

JQuery 3.0, if the browser supports it, uses requestAnimationFrame API to perform animations. The API uses GPU to perform animations. This method is powerful because it’s faster and smoother while performing animations, and on mobile devices, it’s a battery saver.

It is not the first time that jQuery developers have tried to use requestAnimationFrame for animations, but in order to apply it correctly, some code assumptions need to be refactored. The main problem is that requestAnimationFrame is not performed when the browser tab is not active, so jQuery must handle the animation stack correctly.

JQuery custom selector’s speedup

JQuery offers some custom selectors (like: visible and: hidden) that apparently look like a CSS selector, but are resolved by jQuery selector engine.

The developers found that with these selectors, some extra work can be skipped if used multiple times in the same document. After they optimized it in jQuery 3, the result is now ~17 times faster.

: Visible and: hidden custom selectors can still be expensive because they are based on how each browser implements the DOM flow rendering. This means that sometimes these selectors ask a complete flow recalculation of the whole page, so they must be used with responsibility.

JQuery 3.0 changes the meaning of: visible (and therefore of: hidden) selectors. Starting with jQuery 3.0, elements will be considered: visible if they have any layout boxes, including those of zero width and/or height. For example, elements and inline elements with no content will be selected by the: visible selector.


For more details and queries please feel free to email, visit or call us. Wishing you the very best for all your future endeavors.
Helpline: 9814666333, 8699444666
Email: info@technocampus.co.in

Please fill the form and we shall contact you soon.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s