Comment 2 for bug 1615001

I'm not sure the designed behaviour of keeping the screen on for as long as the snap decision is on screen is correct. I'm not sure respecting MAX_INT as timeout value (-1 would make more sense for "never" anyway) is right either.

The (ab)use case of SIM dialog for this makes it so we want the dialog to remain on screen until it completes, is dismissed, or the backend decides to put it away. That makes some sense, but I don't think that should mean the screen should stay on forever. I agree with the bug description that it should shut down after the idle timeout. So the difference would be between how long the different notifications cause the screen to be on, not that one of them "decides" how long it is on.