xontab / chrome-virtual-keyboard Goto Github PK

keyboard.html has 2 underscores ("_") signs and missing equals "=" sign, so I suggest you replace one with another.

Offtopic: also google chrome store has an outdated version.
Is it possible for me to fork from you and publish modified version as a private plugin for internal non-commercial use?

The feature list of this extension says the smaller keyboard can be moved. I've been unable to move it using 3 different computers. Is there a trick to getting it to move?

Hello,

I found that current version in the chrome web store does not work correct with React. Please find some details here. It seems that recent version in the master branch has already fixed that issue. Could you please release it and update chrome web store?

Thanks in advance.

Hey there,

this keyboard works really nice in one of our applications but we are missing one thing:

When backspace is hit, there is no keyboard events (keydown, keyup, keypress) or a change event on the input element which makes it hard to detect changes in a underlying model value. We are using AngularJS and this breaks the databinding and forces to check the value of the input field on intervals. I would do the change and submit a pull-request if you welcome contributions.

Hi!
First thank you for your work.
I'm experiencing a strange behavior with this extension when using it with chromedriver.
It causes chrome to open a new blank tab with "about:blank" on the address bar.it doesnt happen if I dont add the extension to chromedriver options.
Being my application a kiosk app it is fullscreen and makes it imposible to close the new tab(need to do it from code but feels like hacky)
Did anyone notice this behavior or has any solution?
Thanks

Very nice keyboard! I'm trying to use it with a Vuejs app, but it seems not to work with Vuejs bound input fields...you can try it here: https://vuejs.org/v2/guide/forms.html#Text

If I dispatch the following event to the element after typing with your keyboard, it seems to work.

var event = new Event('input', {
    'bubbles': true,
    'cancelable': true
});

Is there some way to make this work?

Thanks,
Kevin

When running this keyboard on a portrait screen, using the &123 button has the content overflowing off the page and is unacceptable. The only way to return to normal is to click off the text box and refocus it.

As this is a webextension there should not be any reason to limit it to Chrome, so I went ahead and did a port and built/signed a firefox version based of e2b9adf

https://github.com/MarZab/firefox-virtual-keyboard/releases

Since the addon uses exec everywhere, I'm not going to publish it to the store - it's going to get rejected anyway.

Modification of the number key pad with dashes.

Hello!
It's cool application and works perfect! The only thing that makes me upset, is the fact it doesn't show up when I use document.getElementById('fs').webkitRequestFullscreen() in chrome.

Live example is at:
https://bl.ocks.org/AutomationEngineer/raw/203b24d38ddfd0825ea6c65cdafa6eb2/

It would be great if its possible for you to fix this, or is there a workaround?

Regards,
Vicror

in french layout letter 'n' is defined as a menu but without related menu definition, in some cases it works anyway, in other don't
to fix change this:
td class="kbdH kdbCase kbdClick kMenu" _menu="FrN" _hoverOnly="true" _key="n"...
to this:
td class="kbdH kdbCase kbdClick" _key="n"....

When using the intelligent scroll option, the page is scrolled up for the extra space of the keyboard but after the keyboard is closed this space is not scrolled down again.

The keyboard does not work in Webcomponents. Maybe cause of Shadow dom?
see: https://www.webcomponents.org/element/PolymerElements/paper-input

Hey,

i'm currently thinking about fixing some issues with the keyboard. Will you accept pull requests?

I would add some missing event listeners needed for better usage in client side applications using Angular or React. Sound support is also something that is on my list ..

Best

Georg

It would be great if you could default to the number pad on number type inputs.

Just in brief a report on what I did to make it work with electron 1.8.4 - actually there may be better approaches since I'm not that deep into the matter. At least as a Proof-Of-Concept it works, configuration might be a big issue. But here we go (in brief!):

• electron does not support chrome.extension.sendMessage and chrome.extension.onMessage which are both deprecated by the way. I had to use chrome.runtime instead of chrome.extension as MDN suggests.
• is seems as if electron does not support background pages. Using Process Monitor on Windows 10 I could see that background.js is loaded but it seems to not get executed. So here comes the work-around in hope for better times.
• I removed background.js from the manifest.json (although since it's not working this may not be necessary) and integrated it into script.js. Actually there is some fine tuning and I will give the details if someone needs it. More or less I encapsulated the background.js in a function which is called when the extension starts and replaced chrome.extension(runtime).sendMessage with a delayed (setTimeout(,0)) chrome.runtime.onMessage.emit. This is not really clean but seems to work as expected.
• Two incompatibility corrections for the Chrome version (59) used in electron 1.8.4 (no InputEvent class) and a missing chrome.tabs (could be since my app is running in kiosk mode could be a electron issue but doesn't matter for me) and I got the keyboard running.

If there is any better way I would really like to hear about it!

Jochen

PS: Forked the changes at https://github.com/JMS-1/chrome-virtual-keyboard. Sorry for the script.js mess due to the the reformatting (space/tabs): it's NOT that big of a change!

on the symbols page of the keyboard you have two '}' buttons and no '%' button.

Hey @xontab, without a licence explicitly added to the code it is not open-source. Is it intended to be open-source? If so, could you please add a license? Thanks!

Hi and thanks for this fantastic extension. I was curious about whether you plan on continuing to maintain this extension. I know open source project maintenance can be a real drag so please don't feel pressured, it would just help me and others know what (if anything) to plan for if we plan on using this in production.

Chrome allows not only installing but also configuring extensions using policies. This is very useful when deploying extensions to several machines and performing initial setup.
This would require to declare possible values in the manifest as a schema and then they can be read using the storage.managed API.
My personal use case is setting up kiosk devices to have an on-screen keyboard with the correct layout already set and "Use touch events instead of mouse events" enabled.

This doesn't appear to be working correctly for fields that are added to the page dynamically after load.

I don't see why or how this could be, but the only inputs which aren't working are added in this way.

Using input data-* attributes it would be great to have the ability to handle the state or behavior of the onscreen keyboard like that.

From this file:
https://github.com/xontab/chrome-virtual-keyboard/blob/6ca73d02b418cc940ba073ed2bdb4dcd519e193f/keyboard.html

There is a URL on every page

Something which lets users choose a date field's value.

It would be great if there was some documentation on the purpose of each function in the codebase

For some reason, it's not working with Ionic Framework inputs (ion-input).

Steps to reproduce:

1. Acess ionic website (https://ionicframework.com/docs/components/#floating-labels)
2. click in any input the preview app (on the right side) and type a value
3. When navigate to the next filed, the value from the previous field is cleared

Expected Behaviour:
The value inserted in the input shouldn't be cleared.

I've tried everything in the application side. regular inputs inside a Ionic App work as expected, but ion-input is with this bug.

Thank you for any clarification :-)