Univention Bugzilla – Bug 38567
Show virtual keyboard in setup wizard for special characters
Last modified: 2016-03-17 11:28:30 CET
See Ticket#2015051321000257 and Ticket#2013013021001323. During the setup of UCS via a virtual appliance, it is possible that particular keys are not routed through to the virtual system (e.g., the apple key on a Macintosh). We received feedback that the users could not type a "@" character for an email address.
(In reply to Alexander Kläser from comment #0) > See Ticket#2015051321000257 and Ticket#2013013021001323. Sorry, I meant Ticket#2015052021000047 and Ticket#2013013021001323 instead.
Reported again at Ticket#2015060421000825. It is not possible to type a "@" character via RDP and a VSphere client.
Once again: Ticket #2015091521000648. It looks like the @ character is the problem. Maybe we could add a simple solution which solves the @ issue?
Reported again, Ticket#2015113021000641. The user reported that the @ did only work with GB keyboard layout both in Hyper-V and UCS.
It seems that a virtual keyboard just containing the "@" key would be helpful in 99% of the problematic cases.
I added a new input field widget (VirtualKeyboardBox.js) that offers a virtual keyboard containing arbitrary characters. e.g. see system setup / Account information r66579 univention-system-setup (9.0.2-22) * Bug #38567: Show virtual keyboard in setup wizard for special characters r66581 / 66582 yaml file Successful build Package: univention-system-setup Version: 9.0.2-22.938.201601051309 Branch: ucs_4.1-0 Scope: errata4.1-0
I like the solution, it looks very nice! One draw is that the current implementation does not work properly with touch devices. For this, I created Bug 40572 explicitly. AFAIS, the problem here is that you are using the native onclick event via put() as well as the onMouseLeave event which does not seem to work on touch devices. Changes: OK otherwise :) YAML: OK This bug can be VERIFIED.
<http://errata.software-univention.de/ucs/4.1/97.html>
Also occurred at Ticket#2016020221000611.
Also occured at Ticket#2016031121000299.