- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Fri, 27 May 2022 18:35:56 +0000
- To: public-webrtc-logs@w3.org
> This seems like a red herring, because exposure of implementation-specific rendering is inherent with screen-capture and seems mostly orthogonal to cropping. That's missing the point. The problem is not that the players look different generally-speaking. I don't mind if one implementation exposes the play button to the left of the scrubbar and other implementation to the right of it. The problem is that the players' opacity and shape is different in substantive ways. This implementation-specific shape is peculiar to HTMLAudioElement and perhaps a handful other Elements. Consider a developer working with Firefox and Safari. They try to cropTo an audio element and they get only the player, which is rectangular and opaque. They're happy. They don't mind that the player is different in both cases. They ship it. Then it turns out that in Chrome, that still captured some background pixels. Oops! That's unfortunate. Sure, the same problem would have been observed with a div-containing-a-player, if the player happened to obscure something. But that case makes it clearer to the developer that they're capturing "what's in the div" and not "the player". It's a lesser issue. > Who's "we" and where are you going with this? [We](https://github.com/w3c/mediacapture-region/issues/13) who participated in the discussion. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/51#issuecomment-1139928924 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 27 May 2022 18:35:57 UTC