New issue
Advanced search Search tips

Issue 747750 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows , All
Pri: 2
Type: Bug



Sign in to add a comment

hterm: AltGr+2 does not work with pt_PT layout if open as window

Project Member Reported by pasc@google.com, Jul 24 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

Steps to reproduce the problem:
1. Open hterm as window, change the keyboard layout to pt_PT and press AltGr+2

What is the expected behavior?
Should write the @ sign.

What went wrong?
Didn't write anything

WebStore page:  https://chrome.google.com/webstore/detail/secure-shell/pnhechapfaindjhompbnflcldabbghjo

Did this work before? N/A 

Chrome version: 59.0.3071.115  Channel: stable
OS Version: 10.0
Flash Version: 

Initially reported as  issue 727906 , which was closed as duplicate of  issue 211925 . However, in version 0.8.36.8 this still happens.
 

Comment 1 Deleted

Comment 2 Deleted

Comment 3 by vapier@chromium.org, Dec 19 2017

what OS are you using exactly ?  this seems to work just fine for me in CrOS.

when you say "pt_PT", i'm guessing you mean "the Portuguese QWERTY keyboard layout as used in Portugal":
  https://en.wikipedia.org/wiki/QWERTY#Portugal

this is working fine for me in CrOS.  i select the "Portuguese keyboard" there (which lines up with the layout listed in wikipedia above), open a new Secure Shell window, and then press AltGr+2 and i get back @.

Comment 4 by pasc@google.com, Dec 19 2017

Windows 10, Chrome Version 63.0.3239.84 (Official Build) (64-bit), Secure Shell version 0.8.40.1.

Keyboad is that one. This is 100% reproducible. In fact, just tried now the Alt-Gr combinations don't produce the expected output, if they produce output at all. For example:

AltGr+ | Standard  | Shell-in-Tab | Shell-in-window
1      | (nothing) | (nothing)    | 1
2      | @         | @            | ^@
3      | £         | £            | ^[
4      | §         | §            | ^\
5      | €         | €            | ^]
6      | (nothing) | (nothing)    | ^^
7      | {         | {            | ^_
8      | [         | [            | ^H (backspace)
9      | ]         | ]            | 9
0      | }         | (nothing)    | (nothing)

Comment 5 by pasc@google.com, Dec 19 2017

When I wrote ^H, I meant ^?. It seems hterm is sending control characters.

Comment 6 by vapier@chromium.org, Dec 19 2017

Labels: OS-Windows
this looks like a bug in Chrome's handling of AltGr keys inside of "apps", and might be outside the control of Secure Shell.  on the other hand, apps are deprecated/dead on Windows, so no one cares how well they work.

this might "fix" itself when the Secure Shell Extension variant launches.

Comment 7 by pasc@google.com, Dec 19 2017

Except for the fact that this is the only way we can SSH in corp from a gWindows machine... are you sure that this is a no one cares scenario?

Comment 8 by pasc@google.com, Dec 19 2017

BTW, AltGr+0 also doesn't work even in in-tab mode.

Comment 9 by vapier@chromium.org, Dec 19 2017

from Chrome's pov, yes, no one cares about Chrome Apps on Windows.  that's why we're launching an Extension version of Secure Shell in 2018Q1.

also, i'm fairly certain the Chrome Secure Shell app is not the only way you can do corp ssh.  http://go/corpssh-faq talks about putty/cmdline ssh too.

Comment 10 by pasc@google.com, Dec 19 2017

I can wait 2018 Q1 with in-tab shells. Putty is way worse...
you can star b/31225897 for updates and then redo your tests when it's ready and let me know how it goes.  i tried getting a windows vm in the past and it didn't really work out, so maybe i'll have to request a windows laptop or something :/.
Project Member

Comment 12 by sheriffbot@chromium.org, Dec 20

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment