MarionetteJS enthusiasts,

When running a GIJ test *on-device* that has "focusmanager.testmode"
preffed to `true`:

   - While the test is running, touching the physical device produces no
   response, including on system areas like the software home button.
   - The test inevitably fails, as no input or tap events seem to make it
   through.
      - A test that used "actions.flick(...)" to send touch events, for
      instance, will show logs as though it is forwarding events
      
<https://dxr.mozilla.org/mozilla-central/source/testing/marionette/listener.js#824>,
      but nothing happens.
   - Removing the "focusmanager.testmode" override causes input to work as
   expected.
      - We originally added the pref for B2G-Desktop due to focus-manager
      issues. I'm unable to reproduce the original focus-manager issue
with Mulet
      even with the pref off.

>From what I've seen here, I would think that any test that has this preffed
on would fail on-device, but the tracking list of GIJ_FAILS_ON_DEVICE bugs
<https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20GIJ_FAILS_ON_DEVICE&list_id=12789298>
doesn't show them all. For instance,
"apps/system/test/marionette/update_dialog_confirm_test.js" fails too, but
it's not listed there.

It seems like one of the following is true:

   - We don't need "focusmanager.testmode" any more for running GIJ tests;
   or
   - We do need "focusmanager.testmode" and something's not hooked up right
   in on-device mode; or
   - We do need "focusmanager.testmode", and something I'm doing is causing
   these tests to fail when they should not.

Anyone have insight into which scenario I'm running into here?

:mcav
_______________________________________________
dev-fxos mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-fxos

Reply via email to