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[2]. This still an out-of-process, from a client/server perspective,
way to drive the browser, like WebDriver, but it means that we can
automate things like Fennec and B2G just by sending data to the browser.
Let me know if you have any further questions and if you have any
suggestions please let us know!
David
[1] https://developer.mozilla.org/en-US/docs/Marionette
[2] http://dvcs.w3.org/hg/webdriver/raw-file/tip/webdriver-spec.html
On 03/12/2012 16:22, Clint Talbert wrote:
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 mechanism called Marionette that uses the
WebDriver protocol to drive Firefox. (Marionette is wired inside Gecko
in order to make this kind of automation easier).
https://developer.mozilla.org/en-US/docs/Marionette
Hope that helps,
Clint
On 11/30/2012 10:04 PM, mozz wrote:
i've been using selenium firefox driver to automate firefox and it's
too slow as communications between firefox and driver happens
out-of-process.
possible to embed gecko in a process and drive it/interact with its
DOM directly via xpcom?
thanks.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
