56

Noting that the core feature of Vimium, finding and clicking links, does not work in 0.99.121-beta.
To reproduce:

  1. Install Vimium from the Chrome Web Store.
  2. Open a new tab.
  3. Click f on your keyboard.
  4. Observe no highlighted links.
    a month later

    using f to generate the link labels works until I go back with H. after that it is always stuck on collecting labels... in the bottom right corner.

      I am going to prioritize it but someone needs to summarize the top three things we should fix, there is too much here.

        16 days later

        For me I think f to generate link labels is the most important feature for vimium. It works probably ⅔ of time for me right now, when it fails to work it gets stuck on collecting labels... as uloco said above. I haven't been able to figure out if its going back with H that always precedes the failure or not, but I know at least sometimes I can use hints after going back.

        Refreshing the page usually fixes it.

          a month later
          2 months later

          Vimium remains unable to open a new tab with shift+F, on Orion 0.99.123.3-beta.

            18 days later

            +1.

            I myself don't use too many features of Vimium, just a few of them, so I think these are the most problematic two things, as they affect the main feature the most:

            • shift+F not opening in a new tab
            • after navigating back (either using vimium or in the standard browser way - just going back in history), F doesn't work at all and is stuck at "collecting hints"
            15 days later

            +1 to displaying link hints correctly as the most important broken Vimium feature to prioritize for Orion. It basically never works correctly and this is essentially the single thing preventing me from switching to Orion as my primary browser fulltime.

            9 days later
            3 months later

            Steps to reproduce:
            Vimium seems to randomly be focused on a wrong tab and pressing "x" or "yt" closes or copies the wrong tab unexpectedly.
            n
            Expected behavior:

            That it will be in sync iwth the current focused page of the browser. There is also this issue on firefox as well.
            Orion, OS version; hardware type:

            Orion 0.99-125RC
            Image/Video:
            <Copy/paste or drag and drop to upload images or videos (up to 20MB)>

              7 days later

              Vlad You have to install vimium.
              Then after that cycle between many tabs and perss x. Now it will close a random tab and not the tab that you are currently in. And also, gt and gT do not work. THey are shortcuts ot to the next tab and the preivous tab.

                Merged 3 posts from Errant miscommunication between Vimium Chrome and current tab focus.

                  I'm an avid Vimium user so I'd love if it got some attention, probably my biggest pain point in switching from Firefox to Orion. I could even sponsor this issue; I'd happily pay to be able to use it since I use it for accessibility reasons.

                  One bug that hasn't been mentioned is that it seems like some options simply don't get applied even though they do get saved, but this is a bit inconsistent and sometimes the options do get applied for a while only to stop working later. Eg. changing "Characters used for link hints" mainly doesn't do anything for me, and no matter what I put in there it uses the defaults. Also changing "CSS for Vimium UI" doesn't seem to do anything most of the time (except sometimes it does, so one of my test profiles has massive red link hint boxes which I haven't been able to change back to the default yet. I'm not sure what I did differently.) It seems like often even if eg. the link hint setting actually does get applied when I change it, if I reload the page it'll go back to the defaults again.

                  In general saving settings usually takes at least two presses of the "Save Changes" button before it indicates the changes were saved by changing the text to "Saved" and greying out. The Vimium logging URL (moz-extension://d7742d87-e61d-4b78-b8a1-b469842139fa/pages/logging.html for me but I have no idea if that UUID is just local or not) unfortunately shows no output, and the javascript console on that page has Failed to load resource: The operation couldn’t be completed. (Orion_RC.SchemeHandlerError error 2.) (same error in the main Orion version, just without the _RC) .

                  This was tested with the Firefox Vimium-FF plugin (I'm relatively sure the Chrome version has the same issues, or at least I remember testing it out a while ago and finding no real difference at least at that point) and the latest Orion RC (Orion 0.99.125-rc (WebKit 616.1.22)) and latest main version (0.99.125-beta (WebKit 616.1.22)).

                    subintercessor What makes this difficult for us is

                    a) we are not vimium users so we do not understand the extension
                    b) there are so many different things highighted in this thread so we do not know where to start.

                    Can you summarize top three asks with clear steps to reproduce them?

                      5 days later

                      subintercessor I'm not much of an avid user, I just use the basic commands because I just want to hover the keyboard most of the time.
                      I don't reallly relegate tons of time towards learning every niche of the things I use.
                      But I do agree. I use the Chrome version and it's mostly broken except for scrolling up and down the rest of the functions break randomly so I don't use it much.

                        Just tried vimium, vimium-c, and tridactyl. Unfortunately none of them currently work correctly on Orion.

                        Install any of them, press f to highlight links, and observe that Orion cannot navigate to a highlighted link when the keys are pressed.

                        I realize these are probably about the most complex extensions possible so it makes sense that they might not work while Orion's extension support grows.

                        Vlad You should be able to pinpoint the issues by installing any of these extensions then attempting to follow their tutorials or use basic commands from their ? menu. I hope we can eventually get to a point where at least one of the vim extensions functions well. At least for me this is the last big thing missing from Orion.

                        Just a guess but I think the type technical of people who want a vim mode extension are also probably some of the best potential contributors, so getting a vim extension working might attract more developers to Orion and increase contributions.

                        • Vlad replied to this.

                          evelant

                          You should be able to pinpoint the issues by installing any of these extensions then attempting to follow their tutorials or use basic commands from their ? menu

                          Respectfully, we do not have time to do this. There are over 300,000 extensions out there, imagine us debugging each like that with a team of three people, while building a web browser.

                          What we need from the community is top three features of the extensions that you want fixed, with steps to reproduce each of them.