Royal Apps

Hi,

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

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

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

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.

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.

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

I made a Video of the current behavior:

https://streamable.com/ovu4b

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

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

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