Jonathan Griffin (:jgriffin) Reporter
	Description • 10 years ago

The lock screen sometimes interrupts or interferes with the semi-auto tests; I think we should have the harness disable the lock screen before running a test.

	Andreas Tolfsen ❲:ato❳ Assignee
	Comment 1 • 10 years ago

requestWakeLock might be of use here: https://developer.mozilla.org/en-US/docs/Web/API/Navigator.requestWakeLock

	Andreas Tolfsen ❲:ato❳ Assignee
	Comment 2 • 10 years ago

Correction, requestWakeLock makes the screen never dim or switch off.  LockScreen.unlock can be used to unlock the device.  That's available off the window.wrappedJSObject.

	Andreas Tolfsen ❲:ato❳ Assignee
	Comment 3 • 10 years ago

And for actually turning on the screen we can use ScreenManager.turnScreenOn, also available from wrappedJSObject.  It would seem combining the three of these is what we want.

	Andreas Tolfsen ❲:ato❳ Assignee
	Comment 4 • 10 years ago

Code review: https://critic.hoppipolla.co.uk/r/1354

	Robert Wood [:rwood]
	Comment 5 • 10 years ago

Screen unlock and screen wakeup work great, so merged so we can get it into this week's sprint: https://github.com/mozilla-b2g/fxos-certsuite/commit/4fbc1b519dc1987fe40f5178a51905172073ea4f

However disabling dimming doesn't work, so filed bug 1001065 for that.