This repository was archived by the owner on Sep 5, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Performance issue: <md-autocomplete> fires $digest cycles on window resize #10680
Copy link
Copy link
Open
Labels
P3: importantImportant issues that really should be fixed when possible.Important issues that really should be fixed when possible.needs: investigationThe cause of this issue is not well understood and needs to be investigated by the team or communityThe cause of this issue is not well understood and needs to be investigated by the team or communityseverity: performanceThis issue causes a significant performance degradationThis issue causes a significant performance degradationtype: performanceThis issue is related to performanceThis issue is related to performance
Milestone
Description
Actual Behavior:
What is the issue? *
$digest cycles on window resizeWhat is the expected behavior?
If model wasn't changed why should we recalculate all watchers per app? Expected behavior - no $digest cycles on window resize
CodePen (or steps to reproduce the issue): *
CodePen Demo which shows your issue:
https://codepen.io/anon/pen/LyMMNQ?editors=1010Details:
Open browser-console, resize the window, you'll see a lot of '$digest cycle was fired' messages in console
AngularJS Versions: *
AngularJS Version:
1.6.4AngularJS Material Version:
1.1.4
Additional Information:
Browser Type: *
Chrome (seems any)Browser Version: *
OS: *
Windows (seems any)Stack Traces:
Shortcut to create a new CodePen Demo.
Note: *
indicates required information. Without this information, your issue may be auto-closed.
Do not modify the titles or questions. Simply add your responses to the ends of the questions.
Add more lines if needed.
Metadata
Metadata
Assignees
Labels
P3: importantImportant issues that really should be fixed when possible.Important issues that really should be fixed when possible.needs: investigationThe cause of this issue is not well understood and needs to be investigated by the team or communityThe cause of this issue is not well understood and needs to be investigated by the team or communityseverity: performanceThis issue causes a significant performance degradationThis issue causes a significant performance degradationtype: performanceThis issue is related to performanceThis issue is related to performance