- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Mon, 25 Apr 2022 20:55:30 +0000
- To: public-webrtc-logs@w3.org
> Either we augment CropTarget to expose more of Elements (say its name) and it is better to have a name that clarifies that this is tied to an element. It could for instance be reused in other APIs Consider a Web-developer who today writes and ships code that sends a CropTarget over postMessage(). That developer assumes that CropTarget exposes nothing, and can only be used for cropping (shaving off information). This greatly simplifies how that developer can reason about the safety of posting CropTarget around. If we were to reuse CropTarget in the future, it would run the risk of breaking that developer's reasonable assumption. CropTarget is intentionally crop-specific. Reuse for other APIs is not intended, and so we don't need a name that lends itself to arbitrary reuse. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/18#issuecomment-1109031851 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 25 April 2022 20:55:32 UTC