Skip to content
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

Add TreeView.LeadingAction sub-component #4546

Merged
merged 20 commits into from
May 15, 2024
Merged

Conversation

ayy-bc
Copy link
Contributor

@ayy-bc ayy-bc commented Apr 30, 2024

Closes #4542

Changelog

This PR adds TreeView.LeadingAction sub component (like the leading visual, trailing visual) to create a slot for elements that go before the toggle and can be used for various use cases such as a drag handle.

Rollout strategy

  • Patch release
  • Minor release
  • Major release; if selected, include a written rollout or migration plan
  • None; if selected, include a brief description as to why

Testing & Reviewing

Merge checklist

Copy link

changeset-bot bot commented Apr 30, 2024

🦋 Changeset detected

Latest commit: 29348d6

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@primer/react Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link
Contributor

github-actions bot commented Apr 30, 2024

size-limit report 📦

Path Size
packages/react/dist/browser.esm.js 88.45 KB (+0.12% 🔺)
packages/react/dist/browser.umd.js 88.77 KB (+0.14% 🔺)

@github-actions github-actions bot temporarily deployed to storybook-preview-4546 April 30, 2024 18:53 Inactive
@github-actions github-actions bot temporarily deployed to storybook-preview-4546 April 30, 2024 19:45 Inactive
@github-actions github-actions bot temporarily deployed to storybook-preview-4546 April 30, 2024 22:18 Inactive
@github-actions github-actions bot temporarily deployed to storybook-preview-4546 April 30, 2024 23:23 Inactive
@ayy-bc ayy-bc self-assigned this Apr 30, 2024
@ayy-bc ayy-bc marked this pull request as ready for review April 30, 2024 23:37
@ayy-bc ayy-bc requested a review from a team as a code owner April 30, 2024 23:37
@ayy-bc ayy-bc requested a review from camertron April 30, 2024 23:37
@ayy-bc ayy-bc requested a review from a team as a code owner April 30, 2024 23:42
@ayy-bc ayy-bc requested a review from langermank April 30, 2024 23:42
@primer primer bot temporarily deployed to github-pages April 30, 2024 23:45 Inactive
@github-actions github-actions bot temporarily deployed to storybook-preview-4546 April 30, 2024 23:46 Inactive
Copy link
Contributor

@mperrotti mperrotti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have some initial feedback, but I really think we need somebody from a11y to take a look. For example, I'm not sure the "right"/accessible way to add interactive controls inside of a role="treeitem".

It also looks like consumers will have to write their own drag-and-drop functionality since there are no props to handle onDragStart/onDragEnd callbacks. Also, we should agree on the right designs/interactions for a tree view when it's actively being dragged. For example:

  • What does the node look like when the user is dragging it? Probably just knock the opacity down to make it look like a "ghost" of the original node.
  • How do we indicate the prospective new position of the node while it's being dragged? Probably a blue line that acts like a cursor to show what position the node will be in after it's dropped.

Comment on lines 704 to 713
const [isLoading, setIsLoading] = React.useState(false)
const [asyncItems, setAsyncItems] = React.useState<string[]>([])

let state: SubTreeState = 'initial'

if (isLoading) {
state = 'loading'
} else if (asyncItems.length > 0) {
state = 'done'
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we need to include the loading functionality for this story. We can just focus on the drag-and-drop behavior.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

{dragHandle ? (
// eslint-disable-next-line jsx-a11y/no-static-element-interactions
<div className="PRIVATE_TreeView-item-drag-handle" onMouseDown={() => setIsExpanded(false)}>
{dragHandle}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we should require folks to style their own drag handles. We should ship with a default recommended style.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 to this idea. The internal consistency will help users understand what the UI does.

@@ -337,6 +358,7 @@ export type TreeViewItemProps = {
onExpandedChange?: (expanded: boolean) => void
onSelect?: (event: React.MouseEvent<HTMLElement> | React.KeyboardEvent<HTMLElement>) => void
className?: string
dragHandle?: ReactElement
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure we need to require folks to pass dragHandle if they're passing dragAndDrop on the parent.

If we have a tree view where some nodes are draggable and others are not, we could assume all nodes are draggable by default. Then, we could add a prop to TreeView.Item that allows people to disable drag-and-drop functionality.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 to this one as well. I don't think we'll have a scenario where individual tree nodes would be prevented from being dragged and dropped?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we'll have a scenario where individual tree nodes would be prevented from being dragged and dropped?

@ericwbailey we could. If the user didn't have access to see an item, they wouldn't be able to drag it.

@@ -488,6 +511,12 @@ const Item = React.forwardRef<HTMLElement, TreeViewItemProps>(
<div style={{gridArea: 'spacer', display: 'flex'}}>
<LevelIndicatorLines level={level} />
</div>
{dragHandle ? (
// eslint-disable-next-line jsx-a11y/no-static-element-interactions
<div className="PRIVATE_TreeView-item-drag-handle" onMouseDown={() => setIsExpanded(false)}>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How would a keyboard user drag and drop?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can resolve this one for now, with this overall approach being understood.

@@ -488,6 +511,12 @@ const Item = React.forwardRef<HTMLElement, TreeViewItemProps>(
<div style={{gridArea: 'spacer', display: 'flex'}}>
<LevelIndicatorLines level={level} />
</div>
{dragHandle ? (
// eslint-disable-next-line jsx-a11y/no-static-element-interactions
<div className="PRIVATE_TreeView-item-drag-handle" onMouseDown={() => setIsExpanded(false)}>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After I interact with the drag handle, I can't get focus to go back into the tree view. Maybe I'm just doing something wrong - so you and other reviewers should check to make sure you can reproduce this bug.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not just you, I can reproduce this as well. The focus shifts to body after interacting with the drag handle

focus.shifts.to.body.mov

Copy link
Contributor

@ericwbailey ericwbailey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

only show dragHandle when user hovers over TreeView.Item

One small thing I'd love to sneak in: can we also show the DragHandle via :focus-visible? That way it will also be shown to keyboard-only user.

I have some initial feedback, but I really think we need somebody from a11y to take a look. For example, I'm not sure the "right"/accessible way to add interactive controls inside of a role="treeitem".

This interaction pattern is really unique to the web, so it's going to take some time to research this. The other thought here is that my understanding of the shape of this work is getting initial functionality in for demo purposes, and then follow up with accessibility tweaks so it does not block the work.

With that context, I think we can consider this merge-able once other things folks reviewing have pointed out have been addressed. I simply don't know what will be needed yet. We have a plan in place for discovering that, but it will take time.

So, I'd consider this an approval from accessibility at a high level with the idea that there may need to be larger structural updates to follow as we learn what they'll be.

@ayy-bc
Copy link
Contributor Author

ayy-bc commented May 2, 2024

@mperrotti @ericwbailey the initial idea was to just have some space before the expand/collapse toggle where users can place any element. I used dragHandle as the example as that is what we were interested in.

If we were to ship with a default recommended style to always have the dragHandle show, I believe the drag and drop logic should also reside within TreeView (at least for onDragStart/onDragEnd). This would complicate things quite a bit for our use-case.

I think the better way to put this is: do you have recommendations on what we could do if we just wanted to place an element before the TreeView.Item toggle? The consumer would handle what that element does (i.e clicking on it, dragging it, etc).

@JoseInTheArena JoseInTheArena removed the request for review from camertron May 3, 2024 16:47
@ayy-bc ayy-bc temporarily deployed to github-pages May 14, 2024 17:00 — with GitHub Actions Inactive
@github-actions github-actions bot temporarily deployed to storybook-preview-4546 May 14, 2024 17:01 Inactive
@@ -45,6 +45,7 @@ const ItemContext = React.createContext<{
setIsExpanded: (isExpanded: boolean) => void
leadingVisualId: string
trailingVisualId: string
leadingActionId: string
Copy link
Member

@siddharthkp siddharthkp May 15, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ayy-bc Don't think we need this anymore either, removed it :)

@github-actions github-actions bot temporarily deployed to storybook-preview-4546 May 15, 2024 11:44 Inactive
@github-actions github-actions bot temporarily deployed to storybook-preview-4546 May 15, 2024 11:49 Inactive
@siddharthkp
Copy link
Member

siddharthkp commented May 15, 2024

@mperrotti Hi 👋 Can I get a review for the snapshots?

@siddharthkp siddharthkp enabled auto-merge May 15, 2024 12:20
@siddharthkp siddharthkp added this pull request to the merge queue May 15, 2024
Merged via the queue into main with commit c81898c May 15, 2024
30 checks passed
@siddharthkp siddharthkp deleted the ayy-bc/addTreeViewDragHandle branch May 15, 2024 13:05
@primer primer bot mentioned this pull request May 15, 2024
JelloBagel pushed a commit that referenced this pull request May 16, 2024
* add grid area for drag handle when data-drag-and-drop is true

* add test to verify dnd attribute

* css updates

* add docs

* test(vrt): update snapshots

* Sid/treeview leading action (#4569)

* wip: leading action slot

* clean up a little

* change from prop to subcomponent

* remove outdated test

* spacer should come before leadingAction

* merge snapshots from main

* merge package-lock from main

* add visual tests

* use IconButton for leadingAction

* add example of drag handle on hover

* Create tame-nails-live.md

* test(vrt): update snapshots

* change LeadingActio type to React.FC<TreeViewVisualProps> and accept children

* change LeadingAction of type React.FC<TreeViewVisualProps>

* typo

* add `variant="invisible"` to icon button in stories

* add leadingActionId and aria-hidden to LeadingAction subcomponent

* remove `leadingActionId` to describe the tree view item

* remove unused leadingActionId

* remove docs from changeset

---------

Co-authored-by: ayy-bc <ayy-bc@users.noreply.github.com>
Co-authored-by: Siddharth Kshetrapal <siddharthkp@github.com>
Co-authored-by: siddharthkp <siddharthkp@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[TreeView] Add area for dragHandle to be shown before the expand/collapse toggle
5 participants