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

Unwanted scramble on mouseover #430

Closed
bevrard opened this issue Jan 26, 2016 · 8 comments
Closed

Unwanted scramble on mouseover #430

bevrard opened this issue Jan 26, 2016 · 8 comments
Labels

Comments

@bevrard
Copy link

bevrard commented Jan 26, 2016

Hi,

I have the following configuration:
http://jsfiddle.net/bevrard/94L89hzL/4/

When I move the cursor over the first keyboard, it scrambles once again... Could you tell me why?

I can't find a solution.

Thanks in advance for your aswner.

Kind regards,

bevrard

@Mottie
Copy link
Owner

Mottie commented Jan 26, 2016

Hi @bevrard!

Interesting... I'll try to look at this when I get some time today.

@Mottie Mottie added the Bug label Jan 26, 2016
@bevrard
Copy link
Author

bevrard commented Jan 28, 2016

Hi @Mottie ,

Did you have time to look at this bug?

Thanks,

Benjamin

@Mottie
Copy link
Owner

Mottie commented Jan 28, 2016

Sorry, I'll try to dig into the code soon.

@Mottie Mottie closed this as completed in 0a4b425 Feb 1, 2016
@Mottie
Copy link
Owner

Mottie commented Feb 1, 2016

Please verify that the scramble extension is working as expected... sorry, it took a while to isolate the problem.

@bevrard
Copy link
Author

bevrard commented Feb 1, 2016

Thanks for your answer!
I'm checking this tomorrow morning!

@bevrard
Copy link
Author

bevrard commented Feb 2, 2016

It's working as expected :-) !

Thanks a lot!

@bevrard
Copy link
Author

bevrard commented Feb 24, 2016

Hi,

It seems that there is still a bug on mouseover. If we use the same fiddle:
http://jsfiddle.net/bevrard/94L89hzL/7/

It's pointing on the last version of your keyboard.
Issue:

  • write code in first input
  • same in the second one.
  • put your mouse on the first keyboard => the first input will be empty.
  • do the same for the second keyboard => second input empty.

I've tried with the "noFocus" option, but it doesn't resolve the issue.

Do you have an idea?

Thanks

Benjamin

@Mottie
Copy link
Owner

Mottie commented Feb 24, 2016

Hi Benjamin!

This problem should be all fixed in the latest update. Thanks again for reporting it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants