-
Notifications
You must be signed in to change notification settings - Fork 370
Fix top-left resizing - account for new position when calling back onResize #136
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
Changes from all commits
Commits
Show all changes
22 commits
Select commit
Hold shift + click to select a range
fb7beb4
Adjust deltas based on updated handle positions
83f180e
Reduce type check to any html el
91c4d3e
Persist reference to element, always measure by it
b5f6961
Add standalone omnidirectional resize
1f9ca80
Position my example in line with others
8c7cf5c
Extra padding at bottom for absolute example
d7c3313
Adjust positioning adjustment by transformScale
74bf0cb
Adjust deltas based on updated handle positions
0c0f27f
Reduce type check to any html el
28c7b48
Persist reference to element, always measure by it
3e77e57
Add standalone omnidirectional resize
c80a3b7
Position my example in line with others
30836ec
Extra padding at bottom for absolute example
d20d90b
Adjust positioning adjustment by transformScale
8fc13f4
More declarative axis checks
08dc429
Replace individual handle values with one object
831db21
Replace individual handle values with one object
6ff4329
Merge branch 'master' of github.com:conor-kelleher/react-resizable
7f9f4b3
Update webpack entry file + exact ClientRect
8485a87
Adding full absolute-positioning layout example
82591b8
Set up test case to verify modified position
eb8d342
Test callback modifications with delta position
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is saving this ref necessary (rather than simply using
e.target)?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I originally had it just using
,
e.targeton each callback but because the listener is calling back to any movement in the document body,e.targetwill not always be the same value during a drag. It will be whatever element the mouse is currently over. As you can see, using this value directly causes jumpy behaviour when the mouse enters different elements:Hence the need to persist a reference to the same element through multiple callbacks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or an even worse demo:
