Skip to content

Conversation

@adamviktora
Copy link
Contributor

@adamviktora adamviktora commented Nov 20, 2024

Closes #11131 for V5

V6 PR: #11132

  • also updated MenuContainer to reflect changes that has been done in V6 (added the shouldFocusFirstItemOnOpen)
  • general question: now that moving focus to menu is handled by arrow keys, towards V7 is there any chance we would be removing the shouldFocusFirstItemOnOpen prop?

@patternfly-build
Copy link
Collaborator

patternfly-build commented Nov 20, 2024

@adamviktora adamviktora requested review from kmcfaul, thatblindgeye and tlabaj and removed request for kmcfaul and thatblindgeye November 20, 2024 11:58
@tlabaj tlabaj merged commit 623da5e into patternfly:v5 Dec 3, 2024
10 checks passed
@patternfly-build
Copy link
Collaborator

Your changes have been released in:

  • @patternfly/react-code-editor@5.4.14
  • @patternfly/react-core@5.4.11
  • @patternfly/react-docs@6.4.19
  • @patternfly/react-drag-drop@5.4.11
  • demo-app-ts@5.4.16
  • @patternfly/react-table@5.4.12
  • @patternfly/react-templates@1.1.12

Thanks for your contribution! 🎉

mvollmer added a commit to cockpit-project/cockpit that referenced this pull request Dec 9, 2024
… changes

The new PF version will move the keyboard focus into the SelectList of
a opened Select when the user presses ArrowUp or ArrowDown
keys. Further keyboard navigation then happens by moving the focus
around in that list.

However, TypeaheadSelect and MultiTypeaheadSelect templated implement
their own custom keyboard navigation based on the (now broken)
assumption that the text input stays in focus all the time.

To restore the assumption, Select has a new "typeahead" variant that
switches off its new key handling, letting the Typeahead templates
live in the past for a little while longer.

See patternfly/patternfly-react#11249
mvollmer added a commit to cockpit-project/cockpit that referenced this pull request Dec 9, 2024
… changes

The new PF version will move the keyboard focus into the SelectList of
a opened Select when the user presses ArrowUp or ArrowDown
keys. Further keyboard navigation then happens by moving the focus
around in that list.

However, TypeaheadSelect and MultiTypeaheadSelect templated implement
their own custom keyboard navigation based on the (now broken)
assumption that the text input stays in focus all the time.

To restore the assumption, Select has a new "typeahead" variant that
switches off its new key handling, letting the Typeahead templates
live in the past for a little while longer.

See patternfly/patternfly-react#11249
allisonkarlitskaya pushed a commit to cockpit-project/cockpit that referenced this pull request Dec 9, 2024
… changes

The new PF version will move the keyboard focus into the SelectList of
a opened Select when the user presses ArrowUp or ArrowDown
keys. Further keyboard navigation then happens by moving the focus
around in that list.

However, TypeaheadSelect and MultiTypeaheadSelect templated implement
their own custom keyboard navigation based on the (now broken)
assumption that the text input stays in focus all the time.

To restore the assumption, Select has a new "typeahead" variant that
switches off its new key handling, letting the Typeahead templates
live in the past for a little while longer.

See patternfly/patternfly-react#11249
martinpitt pushed a commit to cockpit-project/cockpit that referenced this pull request Dec 10, 2024
… changes

The new PF version will move the keyboard focus into the SelectList of
a opened Select when the user presses ArrowUp or ArrowDown
keys. Further keyboard navigation then happens by moving the focus
around in that list.

However, TypeaheadSelect and MultiTypeaheadSelect templated implement
their own custom keyboard navigation based on the (now broken)
assumption that the text input stays in focus all the time.

To restore the assumption, Select has a new "typeahead" variant that
switches off its new key handling, letting the Typeahead templates
live in the past for a little while longer.

See patternfly/patternfly-react#11249
martinpitt pushed a commit to cockpit-project/cockpit that referenced this pull request Dec 10, 2024
… changes

The new PF version will move the keyboard focus into the SelectList of
a opened Select when the user presses ArrowUp or ArrowDown
keys. Further keyboard navigation then happens by moving the focus
around in that list.

However, TypeaheadSelect and MultiTypeaheadSelect templated implement
their own custom keyboard navigation based on the (now broken)
assumption that the text input stays in focus all the time.

To restore the assumption, Select has a new "typeahead" variant that
switches off its new key handling, letting the Typeahead templates
live in the past for a little while longer.

See patternfly/patternfly-react#11249
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.

4 participants