Xpra: Ticket #859: Remote browser commands don't work in Chrome HTML 5 viewer

I suspect the wording will get a bit confusing.

Using the HTML 5 Viewer with Firefox on Windows and Ubuntu against a Fedora 21 server running trunk r9357:

Issuing commands to Firefox running remotely such as ctrl + t and ctrl + w work in Windows and Ubuntu, but do not work with Google Chrome in Windows and Ubuntu. If I attempt to use these commands then they are directed to Google Chrome running locally, rather than Firefox on the remove machine.

However, OSX isn't an issue at the moment as the Control and Command keys haven't been swapped yet(those pesky OSX users...) so ctrl + t will open a tab on the remote Firefox and cmd + t will open a tab locally in Safari and Google Chrome. Firefox, however indicates that you gave it a command(cmd + t) to open or close a tab but doesn't actually open or close a tab.

I have a feeling it may be an issue on other platforms(Fedora, Debian, Arch, etc), but my Cent6.4 machine is too old to run Google Chrome, and I haven't gotten Fedora working with our new test-bench environment.

As an aside, I'm not sure if there is a way around it depending on how Google Chrome handles the Control key.

Sun, 10 Apr 2016 06:09:48 GMT - Antoine Martin: owner changed

owner changed from Josh to J. Max Mena

@maxmylyn: is this still a problem?

Sun, 10 Apr 2016 06:11:22 GMT - Antoine Martin: milestone changed

milestone changed from 0.16 to 0.17

Tue, 12 Apr 2016 20:38:01 GMT - J. Max Mena: owner changed

owner changed from J. Max Mena to Antoine Martin

Just accidentally tested it trying to get to this ticket. Yes, it is still a problem, at least as of r12379 (trunk, Fedora 23 server).

Of note: Still works as expected with Firefox. (both browsers in Windows)

Thu, 14 Apr 2016 04:10:24 GMT - Antoine Martin: status, milestone changed

status changed from new to assigned
milestone changed from 0.17 to 0.18

Re-scheduling.

Sat, 11 Jun 2016 13:29:51 GMT - Antoine Martin:

For some key combinations we can use preventDefault() to ensure the browser doesn't intercept the key event (but we still have to inject it into our key event handling code I think), but for some others it's just not possible: javascript capture browser shortcuts (ctrl+t/n/w): These combinations cannot get captured by Javascript, but embed plugins can capture these. So for these, we would need a plugin.

Sat, 11 Jun 2016 13:35:21 GMT - Antoine Martin: owner, status changed

owner changed from Antoine Martin to J. Max Mena
status changed from assigned to new

See comment:5, as of r12793 we now intercept as much as we can so things like control-S will save the file in gedit rather than triggering the save page action of the browser.

Doing more than that would require a browser plugin...

Mon, 13 Jun 2016 18:47:57 GMT - J. Max Mena: status changed; resolution set

status changed from new to closed
resolution set to fixed

Excellent! Firefox is now usable....within Firefox.

Closing.

Fri, 24 Jun 2016 22:45:41 GMT - J. Max Mena:

Quick note to anyone who didn't read the links in comment:5

These shortcuts will not work in Chrome due to a Google design decision

However they will work in OSX because the cmd and ctrl keys haven't been swapped. Not sure if that's a bug or not, just noting it.

Tue, 12 Jul 2016 16:52:22 GMT - Antoine Martin: milestone changed

milestone changed from 0.18 to 1.0

Milestone renamed

Sat, 23 Jan 2021 05:08:05 GMT - migration script:

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/859