andreastt

geckodriver has two TCP sockets it operates on: one for the client-facing HTTPD, and another for communicating with Marionette which Firefox binds. You are concerned with the HTTPD here, yes?...

Thanks for running that test! Instead of hardcoding the HTTPD default to `::1`, I think the right option would be to let the system decide. If the system defaults (e.g....

Maybe we should add these prefs to the recommended prefs? Or would that be an overstep?

`file://` protocol URLs are a known problem with geckodriver. This is in part tracked by https://bugzilla.mozilla.org/show_bug.cgi?id=1366035, although there may be separate problems with the `file:` protocol because of content browser...

Supporting the `file:` protocol is not currently a priority because it is not web content and doesn’t block WebDriver conformance.

Yes! We have the intention to also separate out the Marionette client to a separate crate. As you know, we recently [moved from rustc_serialize to serde](https://bugzilla.mozilla.org/show_bug.cgi?id=1396821) which was a major...

I started looking at this over the weekend for a bit of fun, and it turns out that this is not a particularly hard bug to solve but it requires...

Can you help me understand what the circumstances are on your system that necessitates a 60 second connect time to Firefox? I’m struggling to picture why it would take Firefox...

I don’t think I’m opposed to this idea, but it would be a fairly low priority since we already have `POST /session/{session id}/addon/install`.

For the record, we have a similar problem with the command to take a regular screenshot: https://bugzilla.mozilla.org/show_bug.cgi?id=1434313 I couldn’t find a bug on file for element screenshots.