ALT- <- and ALT -> for navigation in MacOS desktop not working

Steps to reproduce

Hover over the arrows that show back and forward on Mac desktop client: a tip will appear indicating alt and arrow keys are way to do this on keyboard. Try using the keyboard to navigate back and forth.

Expected result

Expect to see the same navigation as clicking on the arrows which works.

Actual result

Nothing happens.

Environment

Using MacOS client on Chrome.


Additional information

Anything else you think would help our investigation, like a screenshot or a log file? You can drag and drop screenshots to this box. For large amount of text, try putting them into something like Pastebin.


Additional comments

Could it be conflicting keyboards mappings? Is there a way to change it?

@erica or @Yatharth_Agarwal can you reproduce this?

Hmā€¦ I donā€™t even see these on-screen arrows.

Hitting Alt/Opt-ā† and Opt-ā†’ on macOS navigates the cursor by words.

@Wayne_Smith If you want to go backwards and forwards in history in Chrome on macOS, you can use Cmd-[ and Cmd-].

1 Like

Hi @Wayne_Smith,

So this shortcut used to be Alt+Left and Alt+Right, but because they conflict with the native way to navigate between words, we changed it, but didnā€™t change the tooltip text.

The correct shortcut should be Control+Left/Right for macOS.

1 Like

Control+Left/Right donā€™t work for me. It has exactly the same effect as CMD, which is to jump to the end or beginning of line in the text.

Thatā€™s weird. If you check the ā€œViewā€ menu, ā€œNavigate back/forwardā€ is using Ctrl+Left/Right and those menu options work for me. Weird that the shortcut doesnā€™t work.

Confused :confused: Here is image of what I see in the menu.

Yeah, I tried clicking on the ā€œNavigate backā€ and ā€œNavigate forwardā€ buttons, and they do work.

I have found that I can only use the ā€œNavigateā€ command if the document is not focussed for editing. So either I have to click on the side pane, or use something like CMD-O ESC to lose the focus. Would be nice if there was way to lose the extra keystrokes.

In that case you can just click on the backward/forward buttons on the top left corner, that sounds faster.

I do, but ideally one should be able work using only keyboard, without the mouse, as that is oftentimes much faster. Would like to see Dynalist as super-efficient solution! :wink:

This is related to the need expressed in Recent file in File Finder as well. Would like to rapidly navigate between recent files using keyboard only, something like CMD-TAB to move around stack of recently visited items.

Neither Ctrl+Left/Right nor Alt+Left/Right work for me and I would love to see this implemented, as I use keyboard shortcuts a lot.

Yes, I definitely agree. The options in the ā€œViewā€ menu does work, but for some reason the macOS system has intercepted the Ctrl+Left/Right shortcut (I think to switch workspaces?). We have to look into how to bypass that or switch to another shortcut if nothing works out.

It would be great if we could customize shortcuts in a future version of Dynalist!

1 Like

As a Pro user you can already do that for most shortcuts in Dynalist! Itā€™s available under settings - keymap. Unfortunately this shortcut is more of a system shortcut and we donā€™t provide customization for it yet.

Hi @Wayne_Smith, sorry for digging this up :grimacing:! Weā€™re cleaning up the bugs and would like to know if the bug is still happening to you? If not weā€™ll close this bug :slight_smile:

Hi Erica,

I downloaded the latest desktop app to be sure, but the alt arrows do nothing :frowning:

Added this to our new tracking system, hopefully weā€™ll get to it soon!

Hi @Wayne_Smith,

Sorry for the super late update. Recently (back around beginning of April), we changed the go back/forward shortcuts on the desktop app to be the consistent with the browsers.

Now you can use Cmd+Left/Right to go back and forward, when thereā€™s nothing focused. If youā€™re focusing on something, you can now use the Esc to remove the focus.

I hope that helps! If you could kindly confirm that, Iā€™ll mark this bug as fixed.