youennf has just created a new issue for https://github.com/w3c/mediacapture-region: == Should we support strings in addition or in lieu of opaque identifiers? == CropTarget current proposal is basically an opaque wrapper around some kind of element identifier. @eladalon1983 original proposal was to expose a string, with some use cases in mind that could take benefit of the identifier being a string. The WG decided to move to an opaque identifier. Since then, @eladalon1983 mentioned several times the string use cases with the potential idea to allow CropTarget stringification. This raises a few questions: - Should we reconsider our position and directly use string identifiers? - In that case, should we go with web app provided identifiers or user agent generated identifiers (stringification would mean the latter). - Should we instead look to support these usecases without stringification? for instance by allowing MessagePort communication in CaptureHandle? Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/46 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-configReceived on Monday, 16 May 2022 07:52:48 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:57 UTC