-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Fix 6631 DragDrop Tree keyboard navigation #6646
Fix 6631 DragDrop Tree keyboard navigation #6646
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 2 Ignored Deployments
|
I've seen that primang Tree stores nodes and droppoints together in a special p-treenode tag, I don't know if this is the only point of having an additional tag, or if I should study their example deeper and try something similar, or if we are good with this solution ? |
@@ -84,17 +84,41 @@ export const UITreeNode = React.memo((props) => { | |||
} | |||
}; | |||
|
|||
const findNextNonDroppointSibling = (nodeElement) => { |
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.
conditions can be refactored
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 need to study this one...
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.
LGTM and Works Fine @gucal @melloware what do you people say?
Its good for me i was gonna refactor it slightly but i can do it after the PR is merged! |
Defect Fixes
Fix #6631 Skip drag points where needed