-
Notifications
You must be signed in to change notification settings - Fork 29.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
Pointer capture when moving sashes or scrollbars #21675
Labels
Milestone
Comments
Note that this issue arises when dragging other elements as well, like the scrollbar or the minimap. |
mquandalle
changed the title
Pointer capture when moving sashes
Pointer capture when moving sashes or scrollbars
Mar 2, 2017
joaomoreno
added
bug
Issue identified by VS Code Team member as probable bug
ux
User experience issues
labels
Mar 2, 2017
bpasero
added
the
help wanted
Issues identified as good community contribution opportunities
label
Mar 2, 2017
bpasero
added
layout
General VS Code workbench layout issues
and removed
help wanted
Issues identified as good community contribution opportunities
ux
User experience issues
workbench
labels
Nov 15, 2017
This was caused by e0b601e. |
fyi @bpasero seems to be your commit |
@isidorn we can return that ugly CSS rule (that seems to be the only way) conditionally, e.g. |
@bpasero I would prefer no action for now. It is a minor issue. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
While dragging the sash, the mouse cursor changes when going over different UI elements:
In the above gif, I'm maintaining my mouse button pressed during the entire sash drag, but the cursor change from the vertical double arrow to the pointer and then insert variants. The expected behavior is that the cursor should be “captured” by the element being dragged and shouldn't change even if it hover different elements.
Since Electron/Chrome doesn't support the setCapture API which would be the canonical solution to this problem, we have to rely on workarounds using JavaScript events and CSS. I changed the implementation when implementing #4702 and at that time it was working—at least on my machine, but the implementation has changed since then. The following blog post describe an approach that seems more robust than what I had implemented: http://code.fitness/post/2016/06/capture-mouse-events.html.
The text was updated successfully, but these errors were encountered: