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

Trouble with find in FF Quantum #2962

Closed
Niroday opened this issue Feb 20, 2018 · 11 comments
Closed

Trouble with find in FF Quantum #2962

Niroday opened this issue Feb 20, 2018 · 11 comments

Comments

@Niroday
Copy link

Niroday commented Feb 20, 2018

Hello.
FF Quantum 58.0.2 (64-bit)
Vimium 1.63.1
From time to time text that i typing in / becomes allocated and the next symbol replaces everything in the / field. Looks like this: https://s13.postimg.org/5a6vwxmfb/vim.gif

@smblott-github
Copy link
Collaborator

Can you reliably reproduce this at all, @Niroday? In the gif, is it going to "0 Matches" or "1 Match" at the end?

@Niroday
Copy link
Author

Niroday commented Feb 20, 2018

@smblott-github
"No matches" after "conn" and 400 after replacing "conn" with "e".
Yes, i can reproduce.

@Niroday
Copy link
Author

Niroday commented Feb 20, 2018

The first thing i thought was it's for quick deleting, but replacing with the next symbol displelled my doubts.

@smblott-github
Copy link
Collaborator

Well, it's something related to inputElement here. But nothing there looks suspicious, to me.

@JohnVonNeumann
Copy link

JohnVonNeumann commented Feb 21, 2018

Probably redundant but came here to submit the issue, also having problems with find, pretty much straight after the most recent update.

It's reliably unreliable, sometimes you can type 2 chars before it highlights the last char input and then you'll just start erasing characters as you type.

@txomon
Copy link

txomon commented Feb 22, 2018

I have seen this in some pages, I have no idea on what could be causing it. This is one of them http://docs.sqlalchemy.org/en/latest/dialects/postgresql.html

@redblade7
Copy link

Having this exact same problem as of recently with Waterfox 56.0.4.1.

@smblott-github
Copy link
Collaborator

Tried this myself.

It looks like, when there is no match, window.find() is finding the only match on the page, the one in the HUD. Once the text in the HUD is selected, then next key clears the input.

There seem to be other changes to the behaviour of window.find(); for example, search no longer seems to wrap.

@gdh1995
Copy link
Contributor

gdh1995 commented Feb 23, 2018

@smblott-github I suggest that we change https://github.com/philc/vimium/blob/master/content_scripts/mode_find.coffee#L180 's second true into false (arg "aSearchInFrames"), which should be useful. In my tests, Chrome does not support this argument and always returns false if a query is not in current frame.

Refer: https://developer.mozilla.org/en-US/docs/Web/API/Window/find

@smblott-github
Copy link
Collaborator

Great suggestion, @gdh1995. That seems to fix it.

@smblott-github
Copy link
Collaborator

smblott-github commented Feb 23, 2018

Fixed in 1bfe474.

I'm minded to publish this for FF as v1.63.1, v.1.63.2.

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

No branches or pull requests

6 participants