Skip to content

fix(useMouseInElement): fixing the issue where target element updates were not considered. #4782

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

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

Codfisher
Copy link

@Codfisher Codfisher commented May 28, 2025

Before submitting the PR, please make sure you do the following

  • Read the Contributing Guidelines.
  • Read the Pull Request Guidelines.
  • Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
  • Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
  • Ideally, include relevant tests that fail without this PR but pass with it.
⚠️ Slowing down new functions

Warning: Slowing down new functions

As the VueUse audience continues to grow, we have been inundated with an overwhelming number of feature requests and pull requests. As a result, maintaining the project has become increasingly challenging and has stretched our capacity to its limits. As such, in the near future, we may need to slow down our acceptance of new features and prioritize the stability and quality of existing functions. Please note that new features for VueUse may not be accepted at this time. If you have any new ideas, we suggest that you first incorporate them into your own codebase, iterate on them to suit your needs, and assess their generalizability. If you strongly believe that your ideas are beneficial to the community, you may submit a pull request along with your use cases, and we would be happy to review and discuss them. Thank you for your understanding.


Description

This PR enhances the useMouseInElement function to support scenarios where the target element may move or resize. It addresses cases where the element's position or dimensions change dynamically, which could lead to inaccurate mouse position calculations.

To solve this, useMutationObserver and useResizeObserver are used to watch for changes in the element's layout and update the internal state accordingly.

Additional context

No changes were made to the input or output of the function; the update is fully backward compatible.

@dosubot dosubot bot added size:M This PR changes 30-99 lines, ignoring generated files. enhancement New feature or request labels May 28, 2025
@Codfisher Codfisher changed the title feat(useMouseInElement): fixing the issue where target element updates were not considered. fix(useMouseInElement): fixing the issue where target element updates were not considered. May 28, 2025
@@ -1,10 +1,13 @@
import type { MaybeElementRef } from '../unrefElement'
import type { UseMouseOptions } from '../useMouse'
import { shallowRef, watch } from 'vue'
import { tryOnMounted } from '../../shared/tryOnMounted'
Copy link
Member

Choose a reason for hiding this comment

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

This should be imported from @vueuse/shared.

Copy link
Author

@Codfisher Codfisher May 29, 2025

Choose a reason for hiding this comment

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

Got it, thank you, it has been corrected

@dosubot dosubot bot added size:L This PR changes 100-499 lines, ignoring generated files. and removed size:M This PR changes 30-99 lines, ignoring generated files. labels May 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request size:L This PR changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants