- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Mon, 28 Mar 2022 18:22:18 +0000
- To: public-webrtc-logs@w3.org
> For instance, if we want in the future to allow cropping of a screen or a window, would we reuse CropTarget or something else? I don't think we have a robust way of cropping windows wrt changes to window-internal layout. But should we find something in the future, that future mechanism could rely on a token that is marked as a sub-class of CropTarget. Or CropTarget could be extended to support that. I don't think the name will be an issue. > or according what it represents (an element reference). > ... > hence why a name focused on what the object is (ElementReference, ElementProxy...) seems more appropriate at the moment. * I don't think it's good to think of the token as a reference/proxy to the Element - see [here](https://github.com/w3c/mediacapture-region/pull/24#issuecomment-1080970113). * I don't see another use-case for a "weak reference" to an Element in another document. What, other than cropping, could we do? Why do we need a name that fits hypothetical future uses too? > Of course, who knows the future. But in any case, these are the kind of discussion I'd like to have to validate the name selection. Please let me know if I have failed to address any of your points, or if you have new naming ideas that you feel should still be discussed. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/18#issuecomment-1080991648 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 28 March 2022 18:22:22 UTC