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

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)

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.

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.

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.

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.

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.