Kantu is not connected to a browser tab

I am receiving this error when I do not include an Open command and target URL. When I attempt to target an existing window or open tab, I receive the error:

Error #101: Kantu is not connected to a browser tab

Is it possible to not hard bake a URL into the open command target?

This works:
{
“Name”: “P3”,
“CreationDate”: “2019-1-4”,
“Commands”: [
{
“Command”: “open”,
“Target”: “https://urlexample.com/page”,
“Value”: “”
},
{
“Command”: “click”,
“Target”: “id=text-add”,
“Value”: “”
},

This does not work and receive the above error:
{
“Name”: “P3”,
“CreationDate”: “2019-1-4”,
“Commands”: [
{
“Command”: “selectWindow”,
“Target”: “tab=0”,
“Value”: “”
},
{
“Command”: “click”,
“Target”: “id=text-add”,
“Value”: “”
},

I assume when you start the macro an empty browser tab is open. Kantu - or any other chrome extension - can not work on this special page. The only thing kantu can do there is to load a website. That is why your first macro works, but the second works.

newtab

If you have a normal website open, the second macro will work fine, too. So if you use

selectWindow | TAB=OPEN | https://newwebsiteURL.com

then the 2nd macro works on the empty home page, too.

I am starting the macro on a specific page/URL. It is not blank.

I am trying to use the same macro regardless of the URL I am on.

Can you attach a screenshot or even screencast?

Macros without OPEN usually work just fine. They run on the current, active tab then. We use many of them.

I was expecting it to work this way too. Here is a screenshot. I cannot record a screencast, but the error is visible at the first command.

Strange… => Does the same happen “only” with this website or also if you have another website open? E. g. https://forum.a9t9.com/ ?

This is exactly the same issue I keep getting (sorry to hijack thread)

You can use the selectWindow command with tab=0 as the target

{
“Command”: “selectWindow”,
“Target”: “tab=0”,
“Value”: “”
}

Source → https://a9t9.com/kantu/docs/selenium-ide/selectwindow

I mark this issue as resolved as we can not recreate it.

If anyone still sees the issue, please post a test case that we can run here with the latest Firefox and UI.Vision version. We can only fix bugs that we can recreate.

You can also contact us directly at team AT ui.vision and we can give you access to our test system (e. g. Windows 10 + Firefox 71 or Ubuntu plus Firefox 71) via RDP, Teamviewer or Anydesk, so you can directly recreate the issue on one of our test systems.