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:
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...
I can confirm that the issue is still occurring with the latest v5 beta
Thanks for confirming! I hope this release is more stable with key sequence tasks.
Still not working... here are some Steps to reproduce:
I've attached an example page to try. (copy of the vmware vCenter login page)
Autofill does not work for this page so I've created a Key Sequence:
{WAIT:2500}$EffectiveUsername${TAB}$EffectivePassword${TAB}{ENTER}
Username + Password is set set to "test"
Engine: Chrome (Dedicated, but non dedicated doesn't work also)
The key sequence enters "estest" in the first textbox and then a context menu pops up on the top left corner of Royal TS. (see screenshot)
Just a small update: I've contacted the vendor (Essential Object) and provided a repro project for them. They blame it on the Chromium Engine but one of their competitor's product works fine with the keyboard input. Essential Objects is working on integrating the V77 engine and since they are aware of the issue now (they are also aware that their competition's product works correctly), I assume they will look into it. If they don't, I can explore integrating the component of the other vendor. Unfortunately the performance and quality of that other component is not as good as Essential Object's. So replacing it wouldn't be an option and shipping the other component side-by-side will increase the download package size by... a lot. I also have to find out if I can even host two different chromium engines in one app.
Anyhow, let's wait for their next release and see what they come up with. I'm really sorry about that and I wish I can do something to fix it...
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
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
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.
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'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
I made a Video of the current behavior:
Thank you for the video, Patrick. Can you increase the first wait in the key sequence task to {WAIT:5000} - just for testing?
Thanks for looking into this. I'm available to do a screen share if needed. Cheers
Patrick Leber
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
3 people have this problem