@@ -180,6 +180,14 @@ <h3>MediaDevices.setCaptureHandleConfig()</h3>
180
180
which accepts a {{CaptureHandleConfig}} object. By calling this method, an application
181
181
informs the user agent which information it permits capturing applications to observe.
182
182
</ p >
183
+ < div class ="note ">
184
+ < p >
185
+ There is no consensus yet on how {{MediaDevices/setCaptureHandleConfig}} should
186
+ behave if called more than once, due to concerns over it being misused as a
187
+ cross-origin messaging channel itself. This is under discussion in
188
+ < a href ="https://github.com/w3c/mediacapture-handle/issues/11 "> issue #11</ a > .
189
+ </ p >
190
+ </ div >
183
191
< pre class ="idl ">
184
192
partial interface MediaDevices {
185
193
undefined setCaptureHandleConfig(optional CaptureHandleConfig config = {});
@@ -285,6 +293,17 @@ <h3>MediaStreamTrack.getCaptureHandle()</h3>
285
293
{{MediaStreamTrack/getCaptureHandle}} returns the latest [=observable=] {{CaptureHandle}}.
286
294
Otherwise it returns < code > null</ code > .
287
295
</ p >
296
+ < div class ="note ">
297
+ < p >
298
+ There is no consensus yet on whether {{MediaStreamTrack/getCaptureHandle}}
299
+ belongs on {{MediaStreamTrack}} or on a dedicated controller object that is
300
+ neither < a data-cite ="GETUSERMEDIA#track-clone "> clonable</ a > nor < a
301
+ href ="https://w3c.github.io/mediacapture-extensions/#transferable-mediastreamtrack "
302
+ > transferable</ a > , to separate messaging affecting all tracks from consumption
303
+ of a single track. This is under discussion in
304
+ < a href ="https://github.com/w3c/mediacapture-handle/issues/12 "> issue #12</ a > .
305
+ </ p >
306
+ </ div >
288
307
< pre class ="idl ">
289
308
partial interface MediaStreamTrack {
290
309
CaptureHandle? getCaptureHandle();
0 commit comments