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

**Practically speaking**, I think `CropTarget` with serialization and a possible future-path to stringification are good enough, and I am fine with sticking with them, as the consensus appears to be (WG interim meeting; your messages). I don't think it's necessary to go back to the drawing board over this.

**Theoretically speaking**, I don't yet understand your concerns over ID lifetime; if you have the time to educate me, I'd be happy to hear more. Namely:
```js
  const token = makeToken(document.getElementById('some_id'));
  const uuid = makeUUID(document.getElementById('some_id'));
```
Assume the relevant element is garbage-collected but `token` and `uuid` are still alive. Both `token` and `uuid` now hold "something", but nothing of interest can be done with that "something". What's concerning about this state of affairs? How is `token` less concerning than `uuid`?

-- 
GitHub Notification of comment by eladalon1983
Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/46#issuecomment-1134378163 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 08:51:39 UTC