On Wed, Dec 9, 2015 at 3:48 PM, Gareth Aye <[email protected]> wrote:
> 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!

I have some questions:
What od you mean with crashing Gecko? If Gecko is really crashing
here, then we should file a bug about this, no? Because crashing is
really bad. Or do you mean that the test is failing here?
Why is accessibility tied into the Marionette code at all?
I noticed also when I was trying to fix
https://bugzilla.mozilla.org/show_bug.cgi?id=1200197 (see comment 22)
For me it seems that accessibility has often different needs on which
elements are clickable then what we need for regular UI testing.

What I also encountered with in Marionette was
https://bugzilla.mozilla.org/show_bug.cgi?id=1203966 where we have an
unminified atoms.js file, which currently stuck at a version and can't
be updated.

Regards,
Martijn


> 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
>
_______________________________________________
dev-fxos mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-fxos

Reply via email to