Keyboard shortcuts

[RickCogley]

Hitting / puts the cursor in search, and I thought it would also be cool to have something mapped to those automatically generated previous and next links.

[geoffreymcgill]

Agreed. Excellent idea.

I will investigate and try to figure out what keys would work best. My initial thought would be [ and ] keys.

[DannyBen]

although just landing on good solution that most everyone can agree on would be preferred.

Well, this is a hard thing to do in software design. Personally, I tend to choose the intuitive approach for things like this, and in this case, the choice is even clearer since there are keys designed specifically for this purpose in the keyboard.

I think that if you allow configuration (or disabling at least) of these keys, then there is no other key pair with a stronger argument than arrow keys. Even without configuration, I feel arrow keys have more advantages than disadvantages.

[geoffreymcgill]

Left and right arrows it is. We will try and get this feature into the v1.12 release.

[RickCogley]

cool, that will be a nice UX win

[geoffreymcgill]

We are reviewing this feature request and are now undecided on whether this is a good idea or not, especially if using the left-arrow and right-arrow keys as navigation. Those keys are assigned to horizontal scrolling in basically all browsers and operating systems.

Overriding the native functionality may have unintended consequences that we just cannot foresee at the moment. I would be most concerned with impacting accessibility browsers and/or users that need to zoom their content for visual impairment.

Thoughts?

[DannyBen]

Thoughts?

I for one am happy with any of the below:

1. No implementation at all. Reason: I do not expect web pages to have any "built in" navigation.
2. Have just hotkeys provided by the native accesskey functionality, so on Windows+Chrome it would be the ALT key + whatever keys are configured (ALT+n for next maybe, and ALT+bfor back?)
3. Have arrow keys, but in a way that a) they can be disabled in config and b) they are not hijacking any normal functionality (Vertical scroll, if exists, search field etc).
4. How do you feel about ALT+→ and ALT+←? I have seen these used in some web interfaces, and logically, it makes sense: ALTernative use for the arrow keys.

[spencercap]

[ meta + K ] is also a common key command for focusing the search input

[spencercap]

how do you specify a key modifier for the hot keys config in yaml?

[geoffreymcgill]

how do you specify a key modifier for the hot keys config in yaml?

Retype does not include configurable keyboard shortcut options.

[spencercap]

dang.

i got so close manually inserting some javascript for the keydown event listener but it seems you have setup a more complex isFocussed state using vue reactivity. any chance you can expose these reactive state models to a global variable off of window.searchState or similar?