Todd Tarsi

@rafealarcanjo - Oh, I see what you mean from the logs. Thanks for all the screencaps and info there, perhaps I should have looked closer at those at first. Hm....

How are you calling this? Can I see an example CLI command?

So, please help me understand. Is it basically that it doesn't handle filepaths on Windows with spaces well?

@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....

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...

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...

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...

@therealianc - Is this on v3 or v4?

@therealianc - Ah, sorry. I'm not really doing fixes in v3. I think it's just existing for as long as manifest v2 is still allowed.

@Mohammed-Fayaz - Absolutely not. This would force the most unrecommended selector types to the top. I understand this is good for your use case. To better serve that, we need...