- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Mon, 16 May 2022 19:41:24 +0000
- To: public-webrtc-logs@w3.org
> Should we reconsider our position and directly use string identifiers? I think that'd be for the best. Modulo the next points. > In that case, should we go with web app provided identifiers or user agent generated identifiers I don't like the idea of an app-assigned string, as it means we have to consider collisions (both in spec and in implementation). If the user agent assigns, it can trivially guarantee no collisions by randomizing a UUID. Less to worry about. Simple. > Lifetime of a CropTarget is well defined. Lifetime of a string value is potentially endless. So long as we never assign the same string value to a new Element, what's the problem? And if we randomize a UUID, that's easy to guarantee. > If there is some clean-up being made when a CropTarget is GCed As the identifier will be attached to the Element, we can GC when the Element is GCed. Am I missing some complication? -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/46#issuecomment-1128064124 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 16 May 2022 19:41:26 UTC