Typing "Pause" command into the editor causes a problem

Ui.Vision Bug Reports
1

When I create a new line in my macro and select pause the field stays empty unless I save the macro and select it again:

image

image
image1193×464 23.7 KB

2

Hmm, this works fine for me. Do you see the issue also with other commands?

3

so far just for the pause. I did not see it first but my script acted wired and then I went back and saw the command missing.

So I was able to reproduce it exactly as the pictures show it. It’s on a PC windows 10.

4

Ahh, I just saw Kantu was also updated in my Edge browser to version 3.9.1. Therefore just I lost the last working Kantu IDE. :frowning:

Is there a way to roll back IDE to a previous version in Edge?

5

The Enterprise Edition offers such a feature, it is called “Update Management”. This feature allows you to use older versions and to block the automatic browser extension updates.

6

any update on the “pause” issue?

7

In my tests the PAUSE commands works just fine. But maybe I test it wrong? This is what I do:

  • I type “pa…”
  • “pause” shows up in drop down
  • I select it

All works fine.

8

It does not. Just tried.

  1. Open IDE in side bar
  2. From there open IDE in window
  3. Insert a new line in the code “Empty” Line [Insert new Line]
  4. In Command type “Pause” and DO NOT ENTER
  5. Click into the Target Field
    → Command blanks out

image
image831×581 6.24 KB

9

Any update on this? The pause command selection still does not work. It actually applies to all commands. Not only pause

10

I tested this further:

  • If I enter “pause” and then click into the next box (“target”) without pressing ENTER, then I see the issue. This affects all commands. You need to press ENTER or select the command in the dropdown.

  • Workaround: What I usually do is to type only a few letters of a command and then press ENTER. So to enter “Pause” I type “pau”, the command shows up in the drop down, and then press ENTER. This is faster and it works.

But now that we can recreate it, I added this to our todo list for the next update.

11

Thanks a lot. I just checked version 8.3.9 and this seems not to be an issue with that version. So this issue must have been introduced in a later version.

12

Thanks again for the useful test case => The issue is fixed in V9.1.9