So if you're writing a simple test and crashing gecko in the near future, check the gecko logs and also make sure that you have the correct accessibility stuff!
On Wed, Dec 9, 2015 at 3:39 PM, Gareth Aye <[email protected]> wrote: > I just debugged what was going on and found that > > 1449692934326 Marionette DEBUG conn2 <- Response {id: 33, error: > {"error":"element not accessible","message":"Element is not currently > visible via the accessibility API and may not be manipulated by it -> id: > light, tagName: DIV, className: red\n","stacktrace":null}, body: null} > > was being thrown by the marionette server and crashing gecko. The reason > for that was that my traffic light app didn't have the appropriate > accessibility designations. Calling marionette.client() with the options > > { desiredCapabilities: { raisesAccessibilityExceptions: false } } > > prevents that from happening. Getting marionette server logs from > marionette-js-runner was the key to debugging that fwiw. > > Cheers, > Gareth >
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
