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
Hi Patrick,
it seems that the 3rd party vendor introduced a bug here. I opened a ticket there and hope to get a fix or workaround soon .
In the meantime, you can either downgrade to the 5.0.61330 release here: https://www.royalapplications.com/go/kb-ts-win-previousversions
Or you increase the delay and click the first text box in time to get the key sequence task working.
Regards,
Stefan
Thanks, I already downgraded to 5.00.61330.0 and told my colleagues to avoid any update for the time beeing.
Thanks for the quick reply.
I have a similar problem with the key sequence broadcaster using the terminal emulators, both RebEx and Putty. I’ve followed the advice to downgrade to v5.00.61330 and the problem isn’t there with that version.
Watch out for the next minor upgrade in the upcoming days. The issue should be fixed then…
Updated to 5.00.61707 and Key Sequences are still not working.
It seems that the chrome window does not get the focus.
If I click into the first text field before the sequence starts it pastes the whole text in one field.
{TAB} and {ENTER} are getting ignored.
In our tests, it works fine. Is it possible that the delay is too short? Can you provide an URL we can test against?
This might be off topic, but is somehow related: you know what would be super helpful? Having a right click option to invoke the sequence when the external window like the Chrome one has focus. Having to switch to RoyalTS, clicking the sequence then hoping it’ll focus back to desired window is finicky.
It’s related to this issue, because this option would be at least a nice workaround when the autotype and focus don’t work well as in newer builds then 5.00.61330.
Confirmed Chrome Web Page key sequence tasks don’t work in v5.0.61429. Changing your plugin to IE works. Key Sequence Broadcaster doesn’t work at all though. I created a separate post, which should be available shortly.
Please download the latest release (5.0.61707) and give it a try. The chromium component was updated in this release which should fix all the focus related issues.
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)
I got the same error with version builds 61428, 61429, 61707. Now, I’m back at 61330 again.
But
with this version I still have problems with VMware vSphere Center and
Hypervisor web interfaces older than v6.7 in combination with key
sequences of Royal TS build 61330 Chrome engine.
Hi Patrick,
I just tried to repro the issue but failed. It seems to work fine for me. Can you create a new web page connection in a new document from scratch and set it up so that it fails. Once you have done that, open a new support ticket with the document attached and your default settings by attaching the file %appdata%\code4ward\code4ward.RoyalTS.UserPreferences.config.
Thanks,
Stefan
Has anyone found a fix for this? I am having the same problem. Even downgrading does not resolve the issue. So far, support has not offered a solution.
No resolution as of now that I’m aware of. I can confirm it appears that key sequence tasks do not type inside the window that should be in focus and that something in the upper left-hand corner of the screen is selected. If I immediately select the window that should be in focus, key-sequence broadcasting executes as expected.
Hi,
I just spend an hour to repro the issue on my side and I’m still not seing the issue. What I did notice is some weird behavior when I use the HTML page, Patrick provided in this thread. I think some javascript may interfere and the key sequence is executed too fast. Can you try to increase the pause between keystrokes in the plugin settings to the max. (500 ms):
Let me know if this changes anything.
The above suggestion did not change anything. The issue is that the enter key does not work, no matter how slow you make it.
Thank you very much for the suggestion. I increased the
keystroke pause interval to 500 for testing. Keystrokes did type much slower as
expected during testing. Although this did not solve the issue at first, you
brought up an excellent point. I added a {WAIT:500} at the beginning of the
sequence, which appears to have resolved the issue in my newly created test web
page connection (with Web Paged based on Internet Explorer). This does
not resolve the issue with Chrome selected as the active plugin as Patrick
Leber has pointed out in the forum.
Ultimately, I believe the Internet Explorer-based page did
not finish loading, which prevented the default text field within the page from
being selected before keystokes began typing. The core issue appears to be isolated
to the Chrome plugin as the default text field is never selected after the page
loads.
Hope that helps! Let me know if I can run any more tests for
you.
It is so strange… I changed the timeout to 500 and it worked “better” for a short time…
“better” means it started typing in the form but somehow the password was always wrong… I’ve added some waits here and there for testing… but the typed password was always longer than it should be (it seemed that {TAB} in a password field was uses as a single character.
After a restart from royalts everything was like before… so no form input at all and a context menu on the top left corner…
also I can’t use IE for testing since I’m using a secure gateway which is not supported with the IE engine 