Description of problem: Multilple keyboard layouts use 3rd level characters for special symbols. It is impossible to input such characters in these layouts. For example, in the French layout symbols such as "|" do not work Version-Release number of selected component (if applicable): 3.1.0 How reproducible: Always Steps to Reproduce: 1. Enable French layout 2. open a pod console 3. try to type the | (Pipe) symbol Actual results: nothing happens Expected results: symbol appears in the console Additional info: a workaround currently is to input Alt+124 manually which takes a long time Upstream
*** Bug 1473661 has been marked as a duplicate of this bug. ***
This is likely fixed by our switch to xterm.js for the web console terminal. Moving to MODIFIED for QE validation. https://github.com/openshift/origin-web-console/pull/1869
Customer is not accepting any "likely", "might", "probably", etc. He is requesting a clear statement. So, could you please be precise in a statement about whether this issue is really fixed in 3.7 or not.
I can confirm it's really fixed in 3.7. (We would not close the bug without validating.)
This bug has been fixed in the https://trello.com/c/zoxUAO2w, Tested this on all related browsers, could input special symbols in French layouts in the pod terminal. test env: OpenShift Master:v3.6.0-rc.0+01e5a1b-550 Kubernetes Master:v1.7.0+695f48a16f QE could verify when it's changed to ON_QA.
@shahan, it's not just special characters. The problem was specifically with 3rd level characters where you need to hold down multiple modifier keys. I tested the `|` character in the French layout, which on my system was Alt-Shift-l (that's the letter L).
Can you confirm the following is also working/has been tested, as that bug was closed as a duplicate of this one? (1473661) Under Windows and using a Belgium azerty keyboard, AltGr does not function in Container Terminal in the Web Console. Trying to enter the "|" symbol in terminal with "AltGr+1" fails, as do many other "AltGr+Character" combinations. 1. Switch keyboard in Windows to Belgian Azerty keymap 2. Try to enter "|" symbol in terminal with "AltGr+1" OS: Windows 10 Browsers tested that do not send AltGr+Character: Internet Explorer 11 Edge Chrome 59
@Brendan Mchugh Tested some symbol using Belgium azerty keyboard, now the terminal work well. see attachement
Created attachment 1312949 [details] Belgium
Created attachment 1328931 [details] Windows_Edge Read above comments. Checked it again in openshift v3.7.0-0.126.4 As QE guy from Beijing, not familiar with the above keyboard input. Thus to ensure the check correct, first try the check in early version v3.6.173.0.21, then try the same in v3.7.0-0.126.4. If the former reproduces but the latter does not, then the check is correct Brendan, for comment 11 for another bug 1473661: Double got same result as comment 12 in v3.7. Here just give the video record in "Windows Edge gif". And in v3.6, the same check indeed reproduces the issue. so bug 1473661 is fixed Evgheni & Samuel, however, for comment 0 and comment 10, could you clarify in what OS/browser/lang keyboard you reproduced it? Asking this because mine is FF/Chrome on Fedora with one kind of French, but the French "|" works not only in v3.7.0-0.126.4, but also in v3.6.173.0.21 (which, per RH internal https://url.corp.redhat.com/559353b, does not yet include the fix in comment 6)! My check detail is shown in "Fedora Firefox gif". Thus, to validly verify comment 0, need follow the same as your operations
Created attachment 1328932 [details] Fedora Firefox gif
Brendan & Xingxing Xia, thanks for your confirmation. Samuel, according to the above comments, the issues mentioned by comment <0> and comment <11> have been fixed, could you move this bug to ON_QA?
According to above comments, all issues were fixed and move to Verify status.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:3188