Peter,
The FirefoxDriver drive does, as Clint points out, speak via XPCOM to
the browser to get access. Granted there is a lot of JavaScript that
needs to be executed for calls. We are doing rewriting it to put it into
Gecko[1] because it allows us to implement the Browser Automation W3C
Spec
I'm not sure what you mean because as best I understand it, the Selenium
Firefox driver is an extension and thus runs in the same process space
as Firefox itself. If you're looking for a closer binding between your
automation code and Firefox, you can take a look at our new automation
mechanis
2 matches
Mail list logo
