- From: guest271314 via GitHub <sysbot+gh@w3.org>
- Date: Fri, 09 Oct 2020 13:21:41 +0000
- To: public-webrtc-logs@w3.org
@henbos The screen lock theory fails when then user specifically configures the OS to not suspend or lock the screen due to inactivity; see https://github.com/w3c/mediacapture-main/issues/670#issuecomment-604785660, https://github.com/w3c/mediacapture-main/issues/668#issuecomment-623018135. Even if the theory of default settings of a machine suspending or locking the screen without user activity were to be seriously explored we would need to test all devices to determine what really occurs, which is not practical and ecludes the very real possibility that the user has changed default settings that this specification has no way of observing all of the possible OS and hardware configuration. I could have several cameras connected to a machine using `motion` or a different program to capture still life, perform experiments, or general security; for that I need no screen open or user action, perhaps for hours or days or weeks, yet I still expect my code that runs through the browser to capture what I tell it to without an absentee specification authors trying to insert their defensive coding criteria into my projects. If I want the `MediaStreamTrack` turned off I set `enabled` to false or call `stop()` or define my own mechanism to turn off the stream. Trying to state what should happen when a machine suspends or screen is locked is beyond the scope of what the specification can actually evaluate or control - and I do not want a specification trying to control that anyway. -- GitHub Notification of comment by guest271314 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/141#issuecomment-706177129 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 9 October 2020 13:21:44 UTC