[hugs]

It sounds like their approach is the same one we took with the first version of Selenium. The approach is JavaScript injection through an HTTP proxy. Because of the same origin policy and JavaScript security model, we abandoned this approach when moving to Selenium 2. Selenium 2 goes for the most native approach for clicks and key events. (Continuing in that native-is-better approach, I'm now experimenting with robots, but that's another story.) I'm amazed they think their approach is better.

I'm surprised they think the Selenium 1 JavaScipt proxy-injection model is a better approach. But hey, I'm getting old... Get off my lawn, yadda, yadda, yadda. But I'm stunned they think it's better and trying to patent it. I really hope I'm missing some new key insight here. Please enlighten me, people.

[jolt]

Thank you. From what i have gathered here in the comments, it seems that I need to look into Selenium.