https://github.com/pixelscommander/requestidlecallback-polyfill

Polyfill for request idle callback. Determines is user interacting with document and fires when it is not or after interaction is finished.
https://github.com/pixelscommander/requestidlecallback-polyfill

Last synced: 2 months ago
JSON representation

Polyfill for request idle callback. Determines is user interacting with document and fires when it is not or after interaction is finished.

• Host: GitHub
• URL: https://github.com/pixelscommander/requestidlecallback-polyfill
• Owner: PixelsCommander
• Created: 2015-09-05T08:48:34.000Z (over 9 years ago)
• Default Branch: master
• Last Pushed: 2019-07-11T14:08:26.000Z (over 5 years ago)
• Last Synced: 2024-10-05T12:04:11.303Z (3 months ago)
• Language: JavaScript
• Homepage:
• Size: 11.7 KB
• Stars: 54
• Watchers: 4
• Forks: 4
• Open Issues: 3
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
requestIdleCallback polyfill

============================

requestIdleCallback is a new browser API which allows to execute code when browser is idle.

This is crucial for creating smooth animations and user experiences allowing to avoid janks which basically happens when CPU become too overloaded to fit into frame budget which is 16 msec.

Article about RIC https://developers.google.com/web/updates/2015/08/27/using-requestidlecallback?hl=en by Paul Lewis

How polyfill works

------------------

Polyfill is built on principe that janks are most harmful to UX and have highest chance to happen when user is continously interacting with UI. Polyfill basically prevents operation from being executed while user performing some actions on interface. Currently this implies scrolls, taps, clicks, mouse and touch movements. The condition is pretty simple - if there were no interactions for 100 msec there is a huge chance that we are in idle.

Differnce between requestUserIdle and requestIdleCallback

---------------------------------------------------------

The difference is that requestUserIdle is always relying on polyfill logic even if requestIdleCallback is implemented natively in browser. This is handy if you just need to wait for UI idle since native requestIdleCallback have different behaviour and fires when main thread becomes idle, not UI.

NPM

---

Available via `npm install ric`

TO DO

-----

- Consider touchend, touchcancel, mouseup, touchleave for faster idle recognition

- Consider CSS transitions as blockers via listening to transitionstart, transitionend