> We should aim at decoupling as much as possible capturer and capturee through a standard API. Capturee can declare regions of interest through an API a la CaptureHandle, with the same origin protection mechanism. Capturer would get and use that information from the MediaStreamTrack object itself. I'd prefer tight coupling here, otherwise sites could exploit this to protect themselves against capture. E.g. a bank site saying: please capture this nice 8x8 pixel gray element I created, instead of the user's full accounts transactions page. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/195#issuecomment-1006031833 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-configReceived on Wednesday, 5 January 2022 19:54:59 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:55 UTC