- From: guest271314 via GitHub <sysbot+gh@w3.org>
- Date: Fri, 09 Oct 2020 14:10:28 +0000
- To: public-webrtc-logs@w3.org
> I haven't had time to follow all your links Readin Yes, mutes in 1 second by itself when no mouse move (or as pointed out, without activity on the browser rendering thread), which amounts to observing user action, or some superfluous animation just to not mute the track. While I may be verbose that is necessary to place all of the evidence on the record. Reading the entire document is required in primary research. The point is if you miss details you miss critical realities. For example, Taney was legally correct, yet historically incorrect as to all of those supposed "Negroes" or "Africans" being "brought" to the Colonies and later U.S. and sold as "slaves" (prisoners of war), as evinced by the fact that Virginia Colony did not take the vote of "Free Blacks" until 1724. In this case Chromium has not documented at all their muting and unmuting behaviour for tab and screen capture. We cannot find any such language in the actual primary source here, the specification. Still need to test to determine if can record the entire 4 page document to its completion and YouTube does not trim the result based on no frames captured at the end. Even after the change I know mute and unmute are still fired, so I am not sure why Chromium authors want to keep the undocumented behaviour around at all. Have to head of the -- GitHub Notification of comment by guest271314 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/141#issuecomment-706205124 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 14:10:31 UTC