Skip to content

fix: include page blur in end events for drag #507

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

Merged
merged 5 commits into from
May 19, 2025

Conversation

Akxe
Copy link
Contributor

@Akxe Akxe commented May 16, 2025

Adding a blur event handler when dragging is in progress will prevent the user from switching from the app, letting go of the mouse and coming back with the ability to start a new secondary drag, or performing similar actions that were not expected to be possible.

@SanderElias
Copy link
Contributor

@Akxe Can you update your PR description with some text explaining what problem is fixed by this?

@Akxe
Copy link
Contributor Author

Akxe commented May 19, 2025

@SanderElias like this?

@SanderElias
Copy link
Contributor

SanderElias commented May 19, 2025

@Harpush @Jefiozie I'm fine with this, we can merge it!

@Jefiozie Jefiozie enabled auto-merge (squash) May 19, 2025 11:02
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR addresses an issue in drag handling by ensuring that a blur event cancels dragging when the user switches away from the app.

  • Updated the rxjs import to include the merge operator.
  • Modified the drag termination logic to also cancel on a document blur event.

@Jefiozie Jefiozie merged commit f7af815 into angular-split:main May 19, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants