- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 27 May 2022 18:05:22 +0000
- To: public-webrtc-logs@w3.org
> Consider too that this is going to look different between different implementations ... pixels from background content will poke through. This seems like a red herring, because exposure of implementation-specific rendering is inherent with screen-capture and seems mostly orthogonal to cropping. I.e. we'd need to shut down screen capture entirely if this were an issue. > the special thing with HTMLAudioElement is that non-rectangularity and/or transparency is different between user agents, which means an application misguidedly trying to use it as a crop-target would yield non-uniform results. It's a footgun. No more so than screen capture already is. We're not capturing the "element", we're capturing whatever CSS determines is rendered top-most at the pixel coordinates determined by the element's bounding rectangle, which may be pixels that have nothing to do with the element. So to speak of other rendering showing through behind round corners and calling that a "footgun" frankly has me worried about whether this API has received the scrutiny and vetting it deserves. I also don't think it's accurate to say this is somehow unique to HTMLAudioElement. HTMLVideoElement with controls look different in different browsers as well, and corner shapes are like the wind, they change with the seasons. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/51#issuecomment-1139903549 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:05:24 UTC