With regards to point 1:: - Fullscreen API is not following this pattern and I do not see any confusion there. - The documentation issue has been solved with partial interfaces/different specs. - There are other Media related locations, why is mediaDevices the right place? For instance a static MediaStreamTrack.produceCropTarget would allow to put consumer/generator API in the same place, and avoid some corner cases related to the mediaDevices object. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/11#issuecomment-1127350855 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-configReceived on Monday, 16 May 2022 07:58:02 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:57 UTC