[Bug]: When holding Shift to enable multi-selection, mouse:over and mouse:out do not behave as expected.

[zhe-he]

CheckList

• I agree to follow this project's Code of Conduct
• I have read and followed the Contributing Guide
• I have read and followed the Issue Tracker Guide
• I have searched and referenced existing issues and discussions
• I am filing a BUG report.
• I have managed to reproduce the bug after upgrading to the latest version
• I have created an accurate and minimal reproduction

Version

6.0.2

In What environments are you experiencing the problem?

No response

Node Version (if applicable)

None

Link To Reproduction

https://codepen.io/zhe-he-the-vuer/pen/ByBKXQN?editors=0010

Steps To Reproduce

1. Create 3 rectangles: A, B, and C.
2. Drag a selection box over rectangles B and C, ensuring the selection area just covers the right half of A.
3. Hold Shift to prepare for selecting A

Expected Behavior

When the mouse enters the right half of A, hold Shift to trigger A's mouse:over. Release Shift to trigger A's mouse:out

2024-12-12.18.27.43.mov

Actual Behavior

When the mouse enters A's right area, holding Shift allows multi-selection of A but fails to trigger A's mouse:over event, which is a clear bug.

2024-12-12.18.14.27.mov

Error Message & Stack Trace

No response

[asturur]

I kind of agree is a bug, i could change idea when looking at the code to fix it.
I sincerly do not remember if there was a specific reason why it couldn't be that way

[asturur]

One of the reason why this could not be a bug is that you are hovering the active selection.
What you hovering is not what you are going to select
But AT LEAST the mouse:over event should tell you that you have both objects in sight.

[zhe-he]

One of the reason why this could not be a bug is that you are hovering the active selection. What you hovering is not what you are going to select But AT LEAST the mouse:over event should tell you that you have both objects in sight.

I made a minimal change to address this issue, ensuring it(mouse:over) will always return only one element to guarantee that the selected element being pressed and the element triggering the active border are the same.

[asturur]

I have seen that. I ll check it asap.

[asturur]

I have been staring at this issue hours, no joking.
I understand that this seems a good quick fix but there are issues with the api.

What is the role of findTarget?

findTarget is finding the target you are over with the cursor, exception made for that strange functionality of altSelectionKey that was made to avoid loosing the ability to reach the active object when preserveObjectStacking is true.

The logic of finding the object behind the activeSelection is already available inside handleMultiSelection.

I would rather run that logic every time there is an active selection, with or without selection key pressed, and return the information in the event, then the developer uses it as it may prefer. Let me make a counter proposal pr

[asturur]

#10365

this is an alternate solution