This repository was archived by the owner on Apr 12, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 27.4k
$$rAF performance issue in Angular Material #12280
Comments
Thx @Narretz |
Any movement on this? We have to resort to using 1.3.15... |
Same as @AdriVanHoudt , any movement? |
matsko
added a commit
to matsko/angular.js
that referenced
this issue
Jul 14, 2015
…or animations Prior to this patch ngAnimate buffered all repeated calls to requestAnimationFrame into a task queue that is flushed once the next animation frame has passed. While this works it causes a random lag to jump out when any CPU intensive rAF requests are processed. This patch sets a configurable task range which then offsets followup rAF requests into the next available frame. Closes angular#12280
matsko
added a commit
to matsko/angular.js
that referenced
this issue
Jul 14, 2015
…or animations Prior to this patch ngAnimate buffered all repeated calls to requestAnimationFrame into a task queue that is flushed once the next animation frame has passed. While this works it causes a random lag to jump out when any CPU intensive rAF requests are processed. This patch sets a configurable task range which then offsets followup rAF requests into the next available frame. Closes angular#12280
matsko
added a commit
to matsko/angular.js
that referenced
this issue
Jul 14, 2015
…or animations Prior to this patch ngAnimate buffered all repeated calls to requestAnimationFrame into a task queue that is flushed once the next animation frame has passed. While this works it causes a random lag to jump out when any CPU intensive rAF requests are processed. This patch sets a configurable task range which then offsets followup rAF requests into the next available frame. Closes angular#12280
The commit is there why wasn't this included in 1.4.4? |
@AdriVanHoudt the commit wasn't guaranteed to fix it. We're testing to see if we can use setTimeout in IE to make this work better. |
@matsko cool, let me know if I can help and of you know an ETA that would be helpfull |
It's set as the main fix for 1.4 this week. So it should be done for the next release. |
Cool, thanks for all the work! |
Thanks guys! |
matsko
added a commit
to matsko/angular.js
that referenced
this issue
Aug 19, 2015
matsko
added a commit
to matsko/angular.js
that referenced
this issue
Aug 19, 2015
1.4.5 will have the fix. |
matsko
added a commit
that referenced
this issue
Aug 19, 2015
🎉 🙏 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When scrolling sticky md-subheader, recent changes in $$rAF seem to create excessive CPU usages.
See angular/material#3531 for details and CodePen demos.
The text was updated successfully, but these errors were encountered: