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

[mediacapture-handle] Should the handle be an object? (#68)

From: Elad Alon via GitHub <sysbot+gh@w3.org>
Date: Fri, 23 Sep 2022 20:30:27 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-1384270446-1663965025-sysbot+gh@w3.org>
eladalon1983 has just created a new issue for https://github.com/w3c/mediacapture-handle:

== Should the handle be an object? ==
At the moment, the [handle](https://w3c.github.io/mediacapture-handle/identity/index.html#dom-capturehandle-handle) field is a string. This limits it to stringable objects rather than serializable objects. If we change to an object, applications will be able to expose [CropTargets](https://w3c.github.io/mediacapture-region/#dom-croptarget) as well.

  exposeOrigin: true,
  permittedOrigins: ['*'],
  handle: {
    field1: "value1",
    field2: "value2",
    cropTargets: {
      label1: cropTarget1,
      label2: cropTarget2,

@youennf, I think you were amenable to this during TPAC 2022...?
@jan-ivar, your opinion?

Note that I still intend to pursue orthogonal proposals for:
1. **Structured** exposure of CropTargets.
2. **Structured** exposure of a suggested contentHint.
3. Exposing a MessagePort (transferable but not serializeable, btw) for bidirectional **unstructured** messaging. (The `handle` is one way and immediate, which is important [a] for Conditional Focus without exceeding the task-end limit, and [b] for capturers that don't wish to communicate with the capturee and alert it to the existence of a capture session.)

Please view or discuss this issue at https://github.com/w3c/mediacapture-handle/issues/68 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 23 September 2022 20:30:29 UTC

This archive was generated by hypermail 2.4.0 : Friday, 3 March 2023 08:55:24 UTC