-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(material/form-field): make notch sizing more reliable #26028
Conversation
8bd90f4
to
44c4f85
Compare
Deployed dev-app to: https://ng-dev-previews-comp--pr-angular-components-26028-e02f-qfra092t.web.app Note: As new commits are pushed to this pull request, this link is updated after the preview is rebuilt. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work!! much more future-proof. Nit: can the commit message explain what it is fixing?
Swap out the current logic for determining when to resize the outline gap, for logic based on ResizeObserver. The current logic tries to guess when the size may need to change based on observing the content, checking after fonts load, etc. But using ResizeObserver should catch more cases. Also brings the gap calculation logic outside the NgZone to avoid running unnecessary change detections.
5e81684
to
b4870f9
Compare
This is ready for another look |
ready for review again |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Swap out the current logic for determining when to resize the outline
gap, for logic based on ResizeObserver. The current logic tries to guess
when the size may need to change based on observing the content,
checking after fonts load, etc. But using ResizeObserver should catch
more cases.
Also brings the gap calculation logic outside the NgZone to avoid
running unnecessary change detections.
Fixes #15027
Fixes #14336