55

Bug Report

Steps to reproduce:
Press shift+W, or W.

Expected behavior:
Current tab will simulate a mouse event dragging the tab outside of its current region, shifting the new tab region to another place by a few pixels based on the default that this browser has defined as, as well as have the current tab contents which are loaded into memory, such as scroll position and current website state all the same.

Orion/macOS:
0.99107.8 11.5.2

Image/Video:
too big can't post

    15 days later

    Steps to reproduce:
    Install and activate the said extensions from the Chrome store and have them enabled individually or together.

    The Problem:
    Vimium: Custom key mappings like the following do not work.

    map c removeTab
map z goBack
#map z goBack count=-1
map x goForward
map a previousTab
map s nextTab
map v toggleViewSource
map u copyCurrentUrl
map yy copyCurrentUrl

    Vimium C: Following link hints does not work.

    Related topic: https://github.com/gdh1995/vimium-c/issues/501.

    When both are enabled, Vimium C is taking precedence which means it is not possible to follow link hints.

    Orion and macOS:
    Orion 0.99.107-beta (WebKit 613.1.3)
    macOS Monterey Version 12.0.1

      sridhar What is the reason for having them both enabled together?

          Vlad Explained in that the GitHub link.

          There are several features of Vimium/C.

          The main ones (for me at least) are:

          1. Being able to click links by link hints i.e., press f, then type the letters shown next to the links.
          2. Navigate the browser using single keyboard shortcuts. Ex.: c to close the tab, z to go back.

          Pasting from my notes..

          Following links:
          works in Vimium (Chrome)

          Custom key mappings:
          works in Vimium C

          Saving may not work in Vimium unless you restart Orion.

          When both are active, Vimium C is taking precedence i.e., following link hints feature is not working.

              a month later

              Steps to reproduce:
              Install Vimium C on either the Chrome or Firefox versions

              Expected behavior:
              They should work, but they do not.

              Orion and macOS:
              Orion 109
              MacOS 12.0.1

              Image/Video:

                6 days later

                Steps to reproduce:
                Many Vimium shortcuts don't work. They should take precedence after most browser shortcuts and before website shortcuts. They should also be dormant and take precedence over unused browser shortcuts such as when no text input fields are focused.

                Expected behavior:
                When I press <c-f>, or <c-b>, I expect to go down one full page down or up respectively, but I experience none of those things.

                Orion and macOS:
                Orion 109.1
                MacOS12.0.1

                Image/Video:

                • Vlad replied to this.

                  I thought vimium C does not work at all?

                    Steps to reproduce:

                    1. Install Vimium C from the chrome web store. Right click to see the options in the context menu.

                    Expected behavior:
                    For it to open it's options page.

                    Orion and macOS:
                    Orion 109.1 release
                    MacOS 12.0.1

                    Image/Video:

                      Steps to reproduce:
                      Press the 'O' key.

                      Expected behavior:
                      For the vimium omnibar to show up. This is how it looks like in Chrome.

                      Orion and macOS:
                      Orion 109.1
                      MacOS 12.0.1

                      Image/Video:

                        Fortrikka This is related to the old problem of shortcuts precedence/expectation not being well defined. Somethimes you want to keep native shortcut (cmd-n), sometimes you want to give it to extension and sometimes to web page. It is not clear which and in which circumstances.

                            My feeling is that extension shortcuts should take precedence over native shortcuts (except for maybe "vital" ones such as cmd-q)? Would appreciate if this could be fixed as vimium is a core part of my browser experience!

                            • Vlad replied to this.

                              ti250 Yes, at this time something like this has much bigger chances of going through if we had such a list ready made.

                                sridhar Also, it appears my vimium simply does not allow me to save anything.

                                    Still does not work, nevermind. It just opens a blank page.

                                      Steps to reproduce:
                                      Install Vimium or Vimium C

                                      Expected behavior:
                                      It will fully work, with all of its features inside the chrome version work.

                                      1. The 'O' shortcut does not work. It creates an error within the web inspector. It used to work on older versions, but a recent update changed it. It although works on it's own extension options page, so it has to be a permissions issue, even though I have gave it full permissions.
                                      2. The '/' shortcut should work. It appears a recent update removed Vimium's ability to create elements on the current webpage. Here is a comparison with Chrome. Here is the past when it used to work. https://orionfeedback.org/d/390-vimiums-find-function-is-faster-than-the-native-in-synesthefox
                                      3. The 'shift+T' shortcut should work. It used to work, but now does not work.
                                      4. Shift+F should open a highlighted link in a new tab, not the current tab. Also, pressing 'F' then going back a page simply breaks the web inspector.
                                      5. https://orionfeedback.org/d/310-problems-with-vimium-and-vimium-c/4
                                      6. Pressing 'J' or any scroll-related shortcut while focused on not the webview continuously holds the shortcut down even though it should only be pressed once.

                                      Orion and macOS:
                                      Orion 0.99-109.1
                                      MacOS 12.0.1

                                      Image/Video:

                                        sridhar Also, custom key mappings now work in Vimium (Chrome).

                                        I use these shortcuts, and they work perfectly.

                                            I made a new post, so this should be merged?