- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 31 Jan 2025 16:12:45 +0000
- To: public-webrtc-logs@w3.org
I'm glad we agree there's a preview tile. Can we also agree that in all use cases presented for scrolling, end-users will essentially perceive themselves as interacting with said preview tile? Would you agree it's reasonable for the user agent to know where it is, so it can do a better job and produce more predictable behavior? We've already moved away from requiring web developer to figure out and scale coordinates themselves (`sendWheel`), to one where the user agent figures this out for them. Except, it appears, for web developers who wish to put an interactive overlay over the preview. Then they're thrust back into hacking around the user agent which no longer knows where the preview tile is? Seems like two different APIs. Your remaining arguments move the goal posts of use cases. They seem to boil down to this being too complicated for user agents to figure out in various use cases you haven't disclosed, so the user agent should stay out of it, and let web developers hack around its efforts to produce the results it needs. I think this feature lives and dies by its use case. If the preview is so twisted and contorted by mal-rendering and transforms that a user agent cannot determine its source or location, then the user probably can't either, and it would be better for forwarding to not work in those cases. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-surface-control/issues/69#issuecomment-2627714276 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 31 January 2025 16:12:46 UTC