Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Click between 2 input fields; keyboard toggles on 1 #86

Closed
jkane001 opened this Issue · 8 comments

2 participants

@jkane001

This is an odd one, and I think it's new - but it might be related to other recent bugs. I have 2 fields wired up to use the on-screen keyboard, as below:

$("input:text, textarea")
.not("[readonly]")
.keyboard({
autoAccept: true,
usePreview: false,
maxLength: limit,
layout: "custom",
customLayout: {
'default': layout,
'shift': shiftLayout
},
display: {
"close": "Close",
"dotcom": ".com",
"submit": submitText
},
position: position,
visible: function (e, el) {
$(".ui-keyboard-actionkey.ui-keyboard-close").addClass($(this).getkeyboard().options.css.buttonAction).end();
$(".ui-keyboard-actionkey.ui-keyboard-submit").addClass($(this).getkeyboard().options.css.buttonAction).end();
}
});

All seems well when I click in the top field, then the second field, but when I click back into the first field, the keyboard closes. Now, if I click back and forth between the fields, the top field alternates between showing the keyboard and hiding the keyboard, while the bottom field shows the keyboard on every click into it.

In other words, if I click between top and bottom fields, starting with top, this is what the keyboard does:

Click into top: open
Click into bottom: open
Click into top: close
Click into bottom: open
Click into top: open
Click into bottom: open
Click into top: close
Click into bottom: open

What I did notice is that on first displaying, the classes on the fields are slightly different:

Top:

Bottom:

@Mottie
Owner

Hi jkane001!

Are you using the most recent version? I think (hope) that this bug was fixed in the recent updates.

@jkane001
@Mottie
Owner

Could you please set me up a demo on jsFiddle.net.

@jkane001
@jkane001
@Mottie
Owner

Ok thanks! I see the problem... I'll look into this issue when I get some time.

@Mottie
Owner

Sorry for taking so long, but the problem should be fixed now in version 1.11. Thanks for your patience!

@jkane001

Perfect, it's fixed. Thanks!

@jkane001 jkane001 closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.