Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is my idea of how to fix #886. The drag data keeps track of the start position, and we don't paint the editor tab unless it's 5px away from the initial mouse down event. It would need to be updated to include other draggable items, mainly the file picker tab. Right now it does still paint the stationary tab highlight, which isn't as jarring as seeing the entire tab move a tiny bit when you just meant to click on it. It should be cleaned up a bit.
It now handles the file picker tabs, but the rectangle indicating the drag target still flashes sometimes on small drags.