Start a new topic

Chrome Key Sequence not working since update

Hi,


since Update 5.0.61428 Key Sequences are not working anymore on Web Page Connections (Chrome)


image


I think the web page does not get the focus since the key sequence will run outside of the web page and is changing stuff in the royal ts interface


3 people have this problem

I think its hard to reproduce because sometime it works, and sometime it doesn't... so I think it could also be some problem with other apps running, ssh tunnel speed, or something else...

The strange thing is - it's mostly started working all of a sudden, apart from the enter key which I can work around as you've mentioned above. I can't think of anything on the machine that has changed... I'll keep an eye on it.

Thanks for looking into this. I'm available to do a screen share if needed. Cheers

I've spent a couple of hours doing tests and research. While I still can't reliably reproduce what you are seeing, I sometimes get that the ENTER key is always not recognized from the key sequence task. I was able to workaround the issue using TABs to focus the log in button and then send a SPACE to hit the button.


During my research I also noticed a SO post here:

https://stackoverflow.com/questions/55068873/selenium-chrome-mobileemulation-not-allowing-sending-key-enter-or-key-return


Selenium is used for web app testing and also allows to create test cases and send keyboard input. I'm more and more convinced that this is an issue deep down in Google's Chromium engine. I will do some more research. Maybe I find a workaround or a solution...


1 person likes this

I was able to reproduce this with the first public site I tried:

https://www.trademe.co.nz/Members/Login.aspx?url=%2fdefault.aspx

 

I also tried Spotify which works fine with the IE plugin.

 

With Chrome, the focus is lost before the key sequence begins. If I help it along by clicking inside the login box before the key sequence begins, the first two characters of the username are cut off. Tabs and Enter don't work, and the application menu opens

https://accounts.spotify.com/en/login/?_locale=en-NZ&continue=https:%2F%2Fwww.spotify.com%2Fnz%2Faccount%2Foverview%2F

As far as I can tell, this seems to be an issue which only affects a subset of users (I also can't really reproduce the issue). Can you share the URLs of public pages you are seeing the autofill issues? Maybe I get some reliable repro case there. (If you want to share those URLs privately, feel free to open a support ticket).


Thanks,
Stefan

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


1 person likes this

Hi everyone!


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

https://support.royalapps.com/support/solutions/articles/17000075446--royal-ts-v5-beta-version


A new chromium version has been included in the beta.


Regards,

Stefan

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}

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.

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

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.

That is weird. Anyone else is seeing this?

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...

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

Login or Signup to post a comment