-
Notifications
You must be signed in to change notification settings - Fork 1.4k
fix: focus newly added table row on drop #9873
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
LFDanLu
wants to merge
6
commits into
main
Choose a base branch
from
fix_table_drop_focus
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+162
−4
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
78ffcc1
fix: focus newly added table row on drop
LFDanLu c31f48e
fix test
LFDanLu e2b2e95
fix 16/17 tests
LFDanLu d752135
actually just need to remove the acts?
LFDanLu 9b90f43
fix focus issues when dropping on a collapsed/expanded tree item and …
LFDanLu 00b3a2e
lint
LFDanLu 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -253,10 +253,18 @@ export function useDroppableCollection(props: DroppableCollectionOptions, state: | |
| state.selectionManager.isSelectionEqual(prevSelectedKeys) | ||
| ) { | ||
| let newKeys = new Set<Key>(); | ||
| for (let item of state.collection) { | ||
| if (item.type === 'item' && !prevCollection.getItem(item.key)) { | ||
| let key = state.collection.getFirstKey(); | ||
| while (key != null) { | ||
| let item = state.collection.getItem(key); | ||
| if (item?.type === 'item' && !prevCollection.getItem(item.key)) { | ||
|
Comment on lines
-256
to
+259
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Root issue was that using the collection iterator for TableCollection returns just the column header and the body, not the actual rows. Walking the items should be more accurate I believe |
||
| newKeys.add(item.key); | ||
| } | ||
|
|
||
| if (item?.hasChildNodes && state.collection.getItem(item.lastChildKey!)?.type === 'item') { | ||
| key = item.firstChildKey!; | ||
| } else { | ||
| key = state.collection.getKeyAfter(key); | ||
| } | ||
| } | ||
|
|
||
| state.selectionManager.setSelectedKeys(newKeys); | ||
|
|
@@ -268,10 +276,11 @@ export function useDroppableCollection(props: DroppableCollectionOptions, state: | |
| let first: Key | null | undefined = newKeys.keys().next().value; | ||
| if (first != null) { | ||
| let item = state.collection.getItem(first); | ||
|
|
||
| let dropTarget = droppingState.current.target; | ||
| let isParentRowExpanded = state.collection['expandedKeys'] ? state.collection['expandedKeys'].has(item?.parentKey) : false; | ||
| // If this is a cell, focus the parent row. | ||
| // eslint-disable-next-line max-depth | ||
| if (item?.type === 'cell') { | ||
| if (item && (item?.type === 'cell' || (dropTarget.type === 'item' && dropTarget.dropPosition === 'on' && !isParentRowExpanded))) { | ||
| first = item.parentKey; | ||
| } | ||
|
|
||
|
|
||
Oops, something went wrong.
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.
These two tests actually always pass without the changes in
useDroppableCollection, not quite sure why it differs from the observed browser behavior. Also interesting to note is that having Strict Mode on in the storybook locally also will cause the issue to not appear...Still digging as to why this would be the case