Open fogoat opened 1 year ago
@sunk818, thank you for creating this issue. We will troubleshoot it as soon as we can.
Triage this issue by using labels.
If information is missing, add a helpful comment and then I-issue-template
label.
If the issue is a question, add the I-question
label.
If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted
label.
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable G-*
label, and it will provide the correct link and auto-close the
issue.
After troubleshooting the issue, please add the R-awaiting answer
label.
Thank you!
@sunk818 - I'm sorry, fixing issues like this in v3 really isn't a priority for me anymore. If you encounter something like this in v4, I'd be happy to fix. But stabilization and getting a mainline release out there is my top priority.
Understood. When v4 comes out (is it out? I just saw 3.1.72 in the Chrome store), I will be happy to test it out. Thanks again for all your hard work and making Selenium IDE accessible to non-programmers. For years, I tried to use stuff like iMacros or other "web macro" programs and this one is the best and free.
I publish the alpha here if you'd like to try it :)
https://github.com/SeleniumHQ/selenium-ide/releases/tag/latest
It needs documentation, some stabilizations, and code signing certificates. I should probably announce it to be in beta by now tbh.
I was looking for an updated Chrome extension. The IDE runs an internal browser and I prefer to use my external Chrome browser
Yeah, but the problem is that Chrome is deprecating manifest v2. And manifest v3 disables arbitrary code execution. By design, that means functions like 'execute script', 'store', or 'assert' basically can't work. So the only choice for the existing web extension model is either this or to slash half of the commands, many of them extremely essential.
Additionally, this was never doing a very good job of testing your browser. For example, the local playback actually used emulated JS instead of driver directives. The reproducability of everything shoots up immensely here. In addition to that, I'm working on making the underlying driver configurable, so you will be able to drive a chrome / firefox / whatever browser with it as long as you have the driver. It's on the six month roadmap for this project. Check back in October if that's the main blocker for you.
What happened?
I place echo statements in my side script to display loop counters or the progress of my script. The log does not always scroll to the very end. I am unable to reproduce consistently or can not explain why it works sometimes, but not other times.
How can we reproduce the issue?
Relevant log output
Operating System
Windows 10 Pro Version 22H2 Installed on 2/17/2021 OS build 19045.3391 Experience Windows Feature Experience Pack 120.2212.3920.0
Selenium version
Selenium IDE Chrome Version 3.17.2
What are the browser(s) and version(s) where you see this issue?
Currently using Chrome Version 116.0.5845.96 (Official Build) (64-bit)
What are the browser driver(s) and version(s) where you see this issue?
?
Are you using Selenium Grid?
?