-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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(cdk/overlay): OverlayRef.outsidePointerEvents() should only emit … #23679
fix(cdk/overlay): OverlayRef.outsidePointerEvents() should only emit … #23679
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.
LGTM
Caretaker note: these changes have the potential of breaking tests. We should trigger an exploratory presubmit to get a feel for how breaking it will be. |
I refactored the PR according to the discussion in #23643. The breaking change has been removed and the PR description updated. The following scenarios are now covered:
I'm open to suggestions for improvement. |
…due to pointerdown outside overlay Currently OverlayRef.outsidePointerEvents() emits when a user starts a click inside the overlay, drags the cursor outside the overlay and releases the click (e.g. selecting text and moving the mouse outside the overlay). In order to only emit when the click originates outside the overlay, we track the target of the preceding pointerdown event and check if it originated from outside the overlay. Fixes #23643
Is there a chance of this landing in v13? |
I can't guarantee when it'll land since it has to follow the process for merging pull requests. |
…due to pointerdown outside overlay (#23679) Currently OverlayRef.outsidePointerEvents() emits when a user starts a click inside the overlay, drags the cursor outside the overlay and releases the click (e.g. selecting text and moving the mouse outside the overlay). In order to only emit when the click originates outside the overlay, we track the target of the preceding pointerdown event and check if it originated from outside the overlay. Fixes #23643 (cherry picked from commit 335a798)
…due to pointerdown outside overlay (#23679) Currently OverlayRef.outsidePointerEvents() emits when a user starts a click inside the overlay, drags the cursor outside the overlay and releases the click (e.g. selecting text and moving the mouse outside the overlay). In order to only emit when the click originates outside the overlay, we track the target of the preceding pointerdown event and check if it originated from outside the overlay. Fixes #23643 (cherry picked from commit 335a798)
…due to pointerdown outside overlay (angular#23679) Currently OverlayRef.outsidePointerEvents() emits when a user starts a click inside the overlay, drags the cursor outside the overlay and releases the click (e.g. selecting text and moving the mouse outside the overlay). In order to only emit when the click originates outside the overlay, we track the target of the preceding pointerdown event and check if it originated from outside the overlay. Fixes angular#23643
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. |
…due to pointerdown outside overlay
Currently OverlayRef.outsidePointerEvents() emits when a user starts a click inside the overlay,
drags the cursor outside the overlay and releases the click (e.g. selecting text and moving the
mouse outside the overlay). In order to only emit when the click originates outside the overlay,
we track the target of the preceding pointerdown event and check if it originated from outside
the overlay.
Fixes #23643