- From: Ian Denhardt via GitHub <sysbot+gh@w3.org>
- Date: Sat, 23 Jan 2021 19:36:12 +0000
- To: public-webrtc-logs@w3.org
Getting a track that maps to the actual pixels on the screen within the bounds of a node fits more with what I had in mind anyway. I think being able to make a track based on a cropping and then transfer it would still probably be more ergonomic than having to make a crop_id and then transfer it, then have the other frame have to redeem the id for an actual object -- it's not clear to me what the indirection is buying you vs. having a certain type of track that is transferable, even if not all tracks are. (Since my use case is different I don't want to hijack too much, but since a same-origin restriction was brought up I want to point out that I do actually need cross-origin transfers for what I'm doing). -- GitHub Notification of comment by zenhack Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/158#issuecomment-766167224 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 23 January 2021 19:36:13 UTC