W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > May 2022

Re: [mediacapture-region] Should we support strings in addition or in lieu of opaque identifiers? (#46)

From: Elad Alon via GitHub <sysbot+gh@w3.org>
Date: Mon, 23 May 2022 16:22:03 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1134882125-1653322920-sysbot+gh@w3.org>
> I disagree here, it does not make sense to do stringification on top of CropTarget.
If the WG validates the use cases/support of strings, it seems best to deprecate the CropTarget APIs and go with a single string based API.

Whether we deprecate the token in favor of a string, or add stringification on top, is an issue for future discussion. At the moment, what's important for me is that both options are technically feasible.

> The interesting case is when the element is still present, not when it went away.

What's interesting about that case?

> If you GC `uuid`...
> You cannot recreate a CropTarget like you can with strings.

Recreating the UUID is equivalent to never letting go of the CropTarget. What I'm missing is a scenario where the app would be forced to let go of CropTarget, but could somehow (i) keep hold of the UUID, which is easy, **AND** (ii) have it still be meaningful, which is... impossible, I think...? What am I missing?

GitHub Notification of comment by eladalon1983
Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/46#issuecomment-1134882125 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 23 May 2022 16:22:04 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:57 UTC