-
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(ripple): use element coordinates instead of page coordinates #7446
Conversation
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.
Tried it locally. Works perfect.
@@ -10,7 +10,6 @@ import {Directionality} from '@angular/cdk/bidi'; | |||
import {coerceBooleanProperty} from '@angular/cdk/coercion'; | |||
import {Platform} from '@angular/cdk/platform'; | |||
import {auditTime, takeUntil} from '@angular/cdk/rxjs'; | |||
import {ViewportRuler} from '@angular/cdk/scrolling'; |
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.
We should also remove the VIEWPORT_RULER_PROVIDER
in the ripple module actually.
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.
Good call. Done.
b2e1ab5
to
a48670e
Compare
Uses the `clientX` and `clientY` coordinates when creating a ripple, instead of taking `pageX`/`pageY` and subtracting the scroll position since the result is exactly the same. Using the client coordinates has the advantage of being simpler and not having to read the scroll position. Fixes angular#7436.
a48670e
to
8620ebd
Compare
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. |
Uses the
clientX
andclientY
coordinates when creating a ripple, instead of takingpageX
/pageY
and subtracting the scroll position since the result is exactly the same. Using the client coordinates has the advantage of being simpler and not having to read the scroll position.Fixes #7436.