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.
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
[EuiDataGrid] Fix keyboard navigation not fully scrolling cells into view #5515
[EuiDataGrid] Fix keyboard navigation not fully scrolling cells into view #5515
Changes from 12 commits
4068925
961677c
99b370f
e72953e
51e405d
1e5999b
e3db4f8
bbd7587
b1cd532
2c307ed
91b0e00
9d950a9
d218634
f444d56
a410c56
d4f5293
b7d4cee
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
@chandlerprall This is possibly the dicey change in this approach (but unfortunately is necessary, as my entire approach requires being able to obtain the outermost cell DOM node).
I changed the order because it's confusingly the opposite of
setFocusedCell
which is[colIndex, rowIndex]
, and I thought thex,y
coordinates made a bit more sense.I also changed this from
rowIndex
tovisibleRowIndex
because that's what the focused cell behavior uses for indices, and it feels somewhat more accurate to howreact-window
behaves - that is to say, on pagination it doesn't actually destroy the cells that exist but instead replaces its contents.That being said, if that's too big of a change for this PR, maybe we should add a new data attr instead like
data-gridcell-location
? Thoughts?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.
We can swap to x,y , but it would be a breaking change (+ Kibana has two affected unit tests) which is okay, and I agree that the x,y pattern fits better.
Instead of changing this attribute to be the visible row index, let's use that second
data-gridcell-location
idea and provide both.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.
f444d56
Per our sync call:
data-gridcell-column-id
,data-gridcell-column-index
,data-gridcell-row-index
, anddata-gridcell-visible-row-index
(with code comments for each prop to help indicate their use-cases).data-gridcell-id
will be deprecated in 3 months in favor of using each 4 separated data attrs