Yura Zenevich [:yzen] (please use "needinfo") Reporter
	Description • 10 years ago

When the screen goes on and off the screen reader used needs to be notified.

	jobara Assignee
	Comment 1 • 9 years ago

I have the screen off/on notifications working, but having trouble with the dimmed notification. What's more, the phone doesn't ever seem to dim when connected to the WebIDE. Is there another way to debug?

	Eitan Isaacson [:eeejay]
	Comment 2 • 9 years ago

I wonder if screen dim is really important..

	Yura Zenevich [:yzen] (please use "needinfo") Reporter
	Comment 3 • 9 years ago

(In reply to Eitan Isaacson [:eeejay] from comment #2)
> I wonder if screen dim is really important..

Well it gives a clue to a sighted user that the screen will shut off shortly because of inactivity. I think without it, there's a chance the screen reader users might fall into a situation where their screen shuts off too much on them?

	Yura Zenevich [:yzen] (please use "needinfo") Reporter
	Comment 4 • 9 years ago

(In reply to jobara from comment #1)
> I have the screen off/on notifications working, but having trouble with the
> dimmed notification. What's more, the phone doesn't ever seem to dim when
> connected to the WebIDE. Is there another way to debug?

If you don't mind, would you post your PR and I can try running it on my device? The only other useful thing could be adb logcat logging, and logging to console in content.

	Eitan Isaacson [:eeejay]
	Comment 5 • 9 years ago

Any news on this? I think the only announcement we need is when the screen turns off (ie. mozPower.screenDisabled == true).

When the screen turns on, the cursor should simply present where it is at.

	jobara Assignee
	Comment 6 • 9 years ago

(In reply to Eitan Isaacson [:eeejay] from comment #5)
> Any news on this? I think the only announcement we need is when the screen
> turns off (ie. mozPower.screenDisabled == true).
> 
> When the screen turns on, the cursor should simply present where it is at.

Gone down the rabbit whole of related/dependent issues. I'm currently working on https://bugzilla.mozilla.org/show_bug.cgi?id=1171184 which is under review.

	Eitan Isaacson [:eeejay]
	Comment 8 • 6 years ago

This bug is for Firefox OS, which we no longer develop or support.