Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vim mode experimental #264

Open
wants to merge 58 commits into
base: vim-mode-experimental
Choose a base branch
from

Conversation

ed2k
Copy link

@ed2k ed2k commented Jun 16, 2019

test to see how this travis works

tobimensch and others added 30 commits October 7, 2018 14:45
The keybindings are hardcoded for now, but this is going to change.
Added moveTabLeft and moveTabRight functions, which take
a tab ID and try to move the tab as far right or left
in the tabOrder as possible.
Added previouslyVisitedTab function that switches to the
previously selected tab.
with activating input boxes using link hinting.
In Firefox 63 an old syntax for Marionette commands was deprecated.
Updating mostly just meant prepending `WebDriver` to existing commands.

This should fix most problems in browsh-org#232
Vim mode still needs a lot more tests
…to key combinations only working after a certain number of key strokes.
@tombh
Copy link
Member

tombh commented Jun 17, 2019

Tests! Wow, this is so great to see you doing this :) If you can get all the main functionality of Vim Mode tested then we can merge it into master.

@ed2k
Copy link
Author

ed2k commented Jun 17, 2019 via email

@tombh
Copy link
Member

tombh commented Jun 17, 2019

Exactly. That's why we have the flake retries set to 3, I think that could actually be set higher. I actually recently spent a lot of time looking into it. I'm fairly confident that most of the failures are real, as in those are actual real bugs in Browsh being surfaced by the tests. This means that the test runner itself is actually probably pretty reliable. So the best thing would be to actually fix the bugs in Browsh (or just increase the flake retry attempts to 6! haha). For example one of the most annoying bugs is where text doesn't get rendered, that's been a problem for months that you sometimes see when using Browsh yourself. So once bugs like that get fixed the tests will become much more reliable.

@@ -210,15 +212,32 @@ export default class extends utils.mixins(CommonMixin, CommandsMixin) {
let target = document.querySelector("body");
let observer = new MutationObserver(mutations => {
mutations.forEach(mutation => {
if (!target) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting! Can you tell me more about this bit?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see type error from logs, makes me believe the body node some times doesn't exist at that time.

@tombh
Copy link
Member

tombh commented Jun 24, 2019

Could you rebase the vim-mode-experimental branch into this branch. I just updated it with all the recent changes from master. I think that should help clean the commits up here so I can better see what you've specifically added.

@ed2k
Copy link
Author

ed2k commented Jun 25, 2019

Could you rebase the vim-mode-experimental branch into this branch. I just updated it with all the recent changes from master. I think that should help clean the commits up here so I can better see what you've specifically added.

my changes,

  1. more clean logging to catch some error from extention, such as disable keyboard and mouse event logs, log frame_text text content.
  2. merge two vim PR,
  3. merge vim_test into tty_test, seems to be if not these two suite will have some kind of race condition (i.e not executing one after another)
  4. adjust code/test here and there trying to get reliable pass in my local ubuntu with statup_url set to localhost:4444 (instead of browsh.com)

@dvd42
Copy link

dvd42 commented Sep 12, 2019

I started to use browsh and I love the idea. But this is the key feaure missing for me since the default mappings wont all work inside my Tmux. So, any news on when this will be released? Or is there a way I can try this version (with the Vim mappins) by compiling from source?

P.S: Thanks for creating and mantaining this great project 😃

@tombh
Copy link
Member

tombh commented Sep 12, 2019

@dvd42 You can always just try installing Vim Vixen yourself with Browsh's Firefox in GUI mode (so you can actually install normal Firefox extensions): https://www.brow.sh/docs/extensions/

@ed2k Again apologies for the delay. I just don't have the mental bandwidth at the moment to digest the significance of this work :'(

@dvd42
Copy link

dvd42 commented Sep 12, 2019

@tombh, thanks for the swift reply. I tried this approach and it doesnt seem to work. The new keybindings dont do anything. I tried it both with Vim vixen and Vimium-ff. Any ideas?

@tombh tombh mentioned this pull request Jul 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants