- From: Dan Jenkins via GitHub <sysbot+gh@w3.org>
- Date: Mon, 04 Jul 2022 14:41:58 +0000
- To: public-webrtc-logs@w3.org
I really like the idea of not needing to use post message at all and relying on other constructs we've already got access to. While discussing this with @steely-glint the other day I started thinking what those could be ranging from "let any page listening for a "createdCropTarget" event know about an available crop target" to "have a list of crop targets on a media stream track and also allow events to tell tab A that's already sharing tab B that tab B has a new crop target available" and then we get away from needing to talk about strings/opaque identifiers etc... when creating a crop target you could limit a crop target to a certain origin if you wanted your crop to only be available to your set of domains.... you'd also need to be able to set a description against crop targets so that an end user could select "I want to share the presentation and not the notes" - there would be no in-between server or post message for you to add any meta data - you'd be reliant on the browser to have that information in a crop target and give that information to the other tab etc. I'd kinda like to offer crop targets direct to a end user visually too - think about selecting a tab from the share your tab gui...... you select a tab that has active crop targets..... and it asks if you want to share the whole tab or a crop taget - giving the nice visual representation of that crop target just like they get for a tab.... this kind of media stream track wouldnt be allowed to remove that crop target as it had been explicitly shared. (but that's getting side tracked) Getting back to this topic.... how would this work? No access to crop targets until you have access to the media stream track that has corresponding crop targets associated with it.... see a list of available crop targets (and their descriptions etc) on the media stream track with a new event telling you about any new crop targets that have been made since the media stream track was initialised..... Maybe we could allow a crop target to have a user generated ID associated with it.... just like a description. that way Meet could still be told that google slides has a list of crop targets and one of them has a user generated ID of X so that Meet can auto crop to X..... Sorry for the brain dump.... -- GitHub Notification of comment by danjenkins Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/46#issuecomment-1173898235 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 4 July 2022 14:41:59 UTC