5

Additional note about the layout.

  • QWERTY is as you probably know the layout most people use
  • Dvorak is a different layout
  • Dvorak - QWERTY cmd is a hybrid layout. it always behaves as Dvorak except for when cmd is pressed. In that case it becomes QWERTY
  • the comma , in qwerty is the same key as the w in Dvorak and while most shortcuts work, some don't like the example i provided earlier

    Doesn't happen with the straight Dvorak layout. I'm using regular Dvorak, not Dvorak - QWERTY and it doesn't happen for me.

      15 days later
      11 days later

      @Vlad In safari it works as expected meaning: that (using Dvorak-QWERTY) clicking cmd-, does open the preferences panel instead of closing the current tab

        18 days later
        2 years later

        I'm still seeing this issue in sites installed as apps – in regular Orion windows ⌘, is opening preferences correctly but in an installed app it closes the current window (and if that is the only window quits the app completely).

          13 days later

          I still havet the original bug in regular orion, that is: if you have more than one tab open ⌘, couses the tab to be closed

            when only one tab is open then I do see preferences

              25 days later

              Originally when starting the app - it works correctly if only one tab is open, but if you open any extrension window, it starts failing even with only one tab open. I verified it with both 1password and bitwarden extensions separately.

                8 months later

                the issue is still there unfortunately

                  3 months later

                  Really looking forward to this being fixed, every time I give another attempt to switch to orion it's bugging me a lot, would buying a subscription move the task up in priority?

                    3 months later
                    6 days later

                    @Vlad I just downloaded the latest build with the fix, and the bug is only partially fixed:

                    the bug is only fixed if an input is in focus (for example go to google.com)
                    the bug is still present if no input is in focus (eg: youtube.com)

                      The complete issue remains for me in standalone installed web apps.

                        No one is typing