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

Set parent container's data focus #44

Merged
merged 8 commits into from
Jun 5, 2024
Merged

Set parent container's data focus #44

merged 8 commits into from
Jun 5, 2024

Conversation

Murreey
Copy link
Contributor

@Murreey Murreey commented Jun 5, 2024

Description

Refactor how we set data focus, so that when you move into a focusable container it sets the data-focus of that focusable container to also point to the same item your focus eventually landed on.

Rewrote the README a bit for clarity too

Motivation and Context

When moving between multiple nested containers, you previously could end up with lots of different data-focuses at each level that you move through. This'd sometimes mean if you moved your focus out of a focusable container then back in via the same thing, you'd lose the focus history because it hadn't been stored on the parent.

How Has This Been Tested?

New unit tests, and has been running in test for a while now.

Checklist:

  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

Murreey and others added 7 commits February 21, 2024 14:54
Co-authored-by: Abbi Grundy <abbigrundy@users.noreply.github.com>
Co-authored-by: Abbi Grundy <abbigrundy@users.noreply.github.com>
Co-authored-by: Murray Coghill <Murreey@users.noreply.github.com>
@Murreey Murreey requested a review from a team as a code owner June 5, 2024 08:32
@Murreey Murreey merged commit f6502f1 into master Jun 5, 2024
1 check passed
@Murreey Murreey deleted the set-parent-data-focus branch June 5, 2024 11:01
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.

None yet

5 participants