-
|
Hi all, I'm not sure if this is a bug or intended, but, having followed the Replicate Algolia docs search guide I've discovered the preview data only updates when selected via mouse hover or via the arrow keys. Tabbing through the results/suggestions fails to update the preview. This is also the case in the example CodeSandbox. Tabbing is a key mode of navigation with forms for various reasons. Though having just checked Google Search tabbing with the autocomplete open closes it and focusses the search button. In the linked Algolia demo tabbing takes you via the submit button to the results. Another potential wonk to this is once a result has been focussed/selected via tabbing any arrow key interaction fails to work. As I say, not sure how much of this is intended, or just how things are, but thought I'd mention it as I'd love to be able to get tabbing to update the preview pane content. Thanks for such an epic product! Mark |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
In this pattern it's intended, the WCAG guide for a combobox recommend that tabbing is for navigating between different controls, of which the combobox is a single unit. If you follow the guide on "making your own autocomplete renderer", you can use that to add tab handlers yourself, but the default autocomplete doesn't allow for that as far as I can tell |
Beta Was this translation helpful? Give feedback.
-
|
Perfect, thanks for clearing that up for me. Will check the guide you reference and make a call from there. Cheers mate! |
Beta Was this translation helpful? Give feedback.
In this pattern it's intended, the WCAG guide for a combobox recommend that tabbing is for navigating between different controls, of which the combobox is a single unit.
If you follow the guide on "making your own autocomplete renderer", you can use that to add tab handlers yourself, but the default autocomplete doesn't allow for that as far as I can tell