Chrome Key Sequence not working since update

tom_hutchinson · June 12, 2019, 3:11pm

I agree in that I no longer see the context menu being selected in the Chrome plugin in version 5.0.61429.

stefan_koell · June 12, 2019, 3:52pm

Let me summarize what I’m reading here:

It seems that the issue is not always present. It seems random/sporadic. For some users it’s not working at all, some users can make it work sometimes.
Older versions of the Chrome plugin does not seem to be affected by this issue.
There’s no reliable repro steps for me to or a known trigger how to reliably force the issue on my side.

I think if I can get this reproduced on my machine, I can better investigate if there’s a workaround or something.

I can try to make a beta release ready next week with the latest version of the chromium engine for you to test to see if this has already been addressed.

Also, one information would be interesting as well: when you see this issue, are there other connections open/active? Is this happening with all web sites or just specific ones?

To forward this to the vendor, we definitely need reliable repro steps in order to get them to have a close look what’s going on.

So any information (trigger, pattern, repro steps) which helps me to reproduce the issue would be very helpful.

Thanks!

arthur_rowell · June 12, 2019, 4:05pm

For me, it is not sporadic. Once I upgraded, a key sequence in Chrome could not use {ENTER}. I have even tried uninstalling and downgrading Royal TS, and that did not fix the issue. I don’t know how to change the Chrome plugin version alone. It also appears that clicking buttons with auto fill is broken in the Chrome plugin. I have been talking with Patrik who is with Royal TS support, and he has reproduced the issue. It has also happened to my co-worker who uses Royal TS.

arthur_rowell · June 12, 2019, 4:09pm

"when you see this issue, are there other connections open/active? "

Fails either way.

“Is this happening with all web sites or just specific ones?”

All websites using the Chrome plugin. IE Works fine.

stefan_koell · June 12, 2019, 7:29pm

I just did some more digging and suddenly I could repro the same issue! So I investigated and found a potential code snippet which could cause this issue. The focus handling of the web browser changed dramatically as I read on the vendor’s forum, so maybe it’s a weird race condition when the message pump is not quite ready when the key sequence kicks in.

Anyhow, I quickly compiled a version based on the 5.1 beta code base for you to try:

https://download.royalapplications.com/RoyalTS/RoyalTSInstaller_5.01.10613.0.msi

Please note, this release has not been fully tested and it may not be as stable as 5.0 right now. Please keep that in mind. It would just be interesting if my little fix worked.

Thanks!

tom_hutchinson · June 12, 2019, 7:31pm

Thanks, Stefan!!! I’ll give it a shot once I can get a little free time.

arthur_rowell · June 12, 2019, 8:02pm

I have installed and tested the beta, and that appears to correct the issue.

patrick_leber · June 13, 2019, 9:50am

Tried the new version, it works better but its not like it was before

Something changed with the {TAB} Placeholder

{WAIT:2500}{TAB}$EffectiveUsername${WAIT:500}{TAB}{WAIT:500}$EffectivePassword${WAIT:500}{TAB}{WAIT:500}{WAIT:500}{TAB}{WAIT:500}{ENTER}

The username gets entered correctly but after the tab one character gets entered in the password field before the actual password, hard to explain.

Its like this:

*Key sequence starts with a wait*

*Tab to focus Username Field*

*Username gets entered correctly*

*short wait*

*tab to focus password field*

*one character gets entered in the password field ???*

*short wait*

*password gets entered in the password field (but is now wrong because of the one character)*

*tab two times to the submit button ends on the username field… so this is also wrong*

// Was on break while writing this message, after the break royal ts was unstable (could be because of the beta) so I restarted the app and now its like before… nothing gets entered and the context menu pops up in the top left corner again…

stefan_koell · June 13, 2019, 9:57am

Hi Patrick,

the initial wait is quite short. Can you try to increase the first wait time? Maybe it’s related to a specific web page? Do you see the same issue on other pages?

Anyone else has feedback on the beta release? For Artur it seems the issue has been resolved, correct?

patrick_leber · June 13, 2019, 10:19am

I’ve increased the wait but it did not change anything.

But I noticed something.

If a key sequence starts there is a notification in the bottom left corner.

So I can see that the key sequence is already starting while the page shows up as loading on the bottom of royal ts.

Since I’m using a secure gateway the page takes some time to load.

I think the key sequence starts to soon and without focus on the chrome tab… the initial wait does not change the start of the key sequence itself

patrick_leber · June 13, 2019, 10:53am

I made a Video of the current behavior:

https://streamable.com/ovu4b

stefan_koell · June 14, 2019, 2:55pm

Thank you for the video, Patrick. Can you increase the first wait in the key sequence task to {WAIT:5000} - just for testing?

patrick_leber · June 26, 2019, 11:54am

It did still not work like it was before the patches… but I was able to change the Key Sequence so that it now works…

{WAIT:3000}{TAB}$EffectiveUsername${TAB}{BACKSPACE}$EffectivePassword${TAB}{TAB}{SPACE}

{ENTER} had some strange behaviour… so I now Submit the form with SPACE on the Submit Button

Also I had the problem with one extra random Keystroke in front of the $EffectivePassword$ so I added the {BACKSPACE}… very strange but at least its now working…

stefan_koell · June 26, 2019, 11:57am

That is weird. Anyone else is seeing this?

christian_lammert · August 29, 2019, 1:03pm

Any update on this? Build 61330 is the last working version - containing different bugs. The most annoying failure (non-working key sequences inside the Chrome plugin) are still part of all newer versions up to build 61707.

stefan_koell · August 29, 2019, 4:35pm

Hi Christian,

as mentioned here, I’m not able to repro the issue anymore. I’ve also published a new beta release just now here: https://www.royalapps.com/go/kb-ts-win-downloadbeta

It ships with the most recent Chromium engine. Can you check if you are able to repro the issue with this version?

Regards,
Stefan

patrick_leber · September 9, 2019, 11:31am

I still have the problem with the new Beta… sometimes it works sometimes it doesn’t… but I found a workaround with the autofill plugin which works for our case… so i don’t use key sequences anymore.

adam_blanken · September 25, 2019, 1:12pm

I’m using Royal TS v5.0.61707 on Windows 10 1903 (18362.356) and can reproduce this issue.

Key sequence tasks work fine with IE based connections but not with Chrome.

When attempting to connect using Chrome with the exact same key sequence task, the first letter of the username is not put into the login form, and tabs and enter doesn’t work inside the web page. To finish off with, the ‘Restore/Move/Size/Minimize/Maximise/Close’ menu opens up (the same as if you left click the application icon at the top left of the title bar).

The key sequence task is: {WAIT:5000}$EffectiveUsername${TAB}$EffectivePassword${ENTER}

stefan_koell · September 25, 2019, 1:16pm

Hi everyone!

Can one of you confirm the issue is still occurring with the latest beta release:

A new chromium version has been included in the beta.

Regards,

Stefan

adam_blanken · September 26, 2019, 8:27am

I can confirm that the issue is still occurring with the latest v5 beta