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

[DataTable]: Expansion clickable area is not up to specification #6589

Closed
2 tasks done
janhassel opened this issue Jul 30, 2020 · 2 comments · Fixed by #7392
Closed
2 tasks done

[DataTable]: Expansion clickable area is not up to specification #6589

janhassel opened this issue Jul 30, 2020 · 2 comments · Fixed by #7392

Comments

@janhassel
Copy link
Member

What package(s) are you using?

  • carbon-components
  • carbon-components-react

Detailed description

Describe in detail the issue you're having.

According to the DataTable guidance on the Carbon website, the clickable / interactive area to expand a row is a square filling the entire height of the row, meaning with the default row height of 48px, the clickable area is 48px by 48px.

Currently in react implementation, this interactive area is 16px by 16px.

Is this issue related to a specific component?

DataTable.TableExpandRow

What browser are you working in?

Chrome 84

What version of the Carbon Design System are you using?

carbon-components@10.16.0
carbon-components-react@7.16.0

Steps to reproduce the issue

  1. Visit react storybook (https://react.carbondesignsystem.com/?path=/story/datatable--with-expansion)
  2. Try to click "around" the chevron

Additional information

Click targets according to Carbon website:
image

Screen recording of react storybook:
Screen Recording 2020-07-30 at 14 44 03

@tw15egan
Copy link
Collaborator

@emyarod are you still working on this?

@emyarod
Copy link
Member

emyarod commented Aug 31, 2020

yes still WIP after getting updated spec

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants