I tried katalon is very similar to kantu, it it based on Selenium IDE.
On katalon there is not the bug of “Error #101: Kantu is not connected to a browser tab” It’s possible to run a macro from internal page of firefox without any problem (I tested this).
I runned macro from about:config or about:blank of firefox and the macro run perfectly from any page.
Why kantu do not allow to run macro from a non web page of firefox ?
it is very annoying not to be able to start a macro from any firefox page I hope you can understand how to solve this problem Katalon and apply it to Kantu.
Hmm… I checked with Katalon but it seems they do not support selectWindow | tab=open | http://google.com/, or?
=> Can you please post a macro that does what you need in Katalon? Because currently I think it is technically impossible (no extension can run on a special page… but maybe I am wrong).
Or you said it used to work in Kantu? If yes, what version? you find all old ones here:
The title of the post is old, in the past Kantu did not start macros from a non-web page (inside firefox) while katalon succeeded
Today ui vision with the open command starts macros even from non-web pages (internal from the browser) but it is the old title remained in this post.
Unfortunately I have not found a way to start macros from the browser’s internal page by opening a new tab and not even katalon.
The title is old and refers to the period in which Kantu even with the open command could not start macros starting from non-web pages (internal browser pages).
I use the command to open on a new tab so that at the end of the work the macro closes the used tabs and sends me back to the initial tab. at the end of the work the macro closes the new tabs that opened and the browser remains at the initial state with the last tabs used before starting the macro.
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.
This bug is solved with open command.
With the command selectWindow | tab=open | the problem remain but probably the base of Selenium do not allow to use selectWindow | tab=open | in an intenal page of firefox.