Re: [w3ctag/design-reviews] User Idle Detection (#336)

@tomayac wrt

> If we think of idle detection use cases, a chat app should probably report "idle" if a screen lock is active (even if it's not the right word) in that case.

I think that's the original [intent/model](https://github.com/samuelgoto/idle-detection/blob/master/README.md#model) and the [implementation](https://chromium-review.googlesource.com/c/chromium/src/+/1446402).

The state is reported in two orthogonal/different dimensions, the `user` state (idle/active) and the `screen` state (locked/unlocked).

We [debated a bit](https://chromium-review.googlesource.com/c/chromium/src/+/1446402/20#message-8b9ad0937907d025e34d2ddac9b983ade73c8eb7) whether it would be useful to decouple in different APIs the `user` state from the `screen` state, and arrived at [bundling](https://chromium-review.googlesource.com/c/chromium/src/+/1446402/20#message-0748dcf10712e064944661e4515704d529157bdc) but [weekly held](https://chromium-review.googlesource.com/c/chromium/src/+/1446402/20#message-0f082aaf3523c4bab633f85c80c587832d77c44c).

Does that make sense and address your point?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/336#issuecomment-470729123