Open johnhaire89 opened 2 years ago
I'm not sure what exactly might be causing this, but we're getting ready to put out an alpha of a new major version in the next couple weeks. It will be a binary and rest on electron. Once that's out, your issue may be resolved that way, or we'll want to investigate in that version. As it is now, I'm kind of spread thin and I need to get that version out. Once we're all on sync on the next version, I'd be happy to really deep dive this sorta thing.
I'm not sure what exactly might be causing this, but we're getting ready to put out an alpha of a new major version in the next couple weeks. It will be a binary and rest on electron. Once that's out, your issue may be resolved that way, or we'll want to investigate in that version. As it is now, I'm kind of spread thin and I need to get that version out. Once we're all on sync on the next version, I'd be happy to really deep dive this sorta thing.
Thanks for your hard work! I'm not sure how to set a reminder, but if I remember to check for when the alpha is out I'll rerun my test cases to see if the issue is still there.
I have test cases that fail around half the time on a send keys command with the error {"code":-32000,"message":"DOM Error while querying"}. The send keys step references an input using xpath, but there isn't a problem with the xpath since I wait for the exact path in the preceding command.
I've tried added a pause step but it doesn't help.
My problem is exactly what another user reported here https://github.com/chromedp/chromedp/issues/545#issuecomment-774252565 but I can't find a bug report on this repo.
Environment
OS: Windows 10 Selenium IDE Version: v3.17.2 Selenium SIDE Runner Version:
Please note that selenium-side-runner supports Node.js 8 - 10 Browser: Chrome Browser Version: Version 99.0.4844.82 (Official Build) (64-bit)