Re: [mediacapture-screen-share] A CaptureController object for getDisplayMedia() (#230)

> - controller should be non-transferable

I'm happy to start with that. (I imagine you might wish to revise that in the future for Capture Actions. I think we'll be able to.)

> - I'm ok with sync for now

Awesome, agreement there too.

> - I still prefer `focus()` over `setFocusBehavior("focus-captured-surface")`
> 
> Browsers' behavior today assumes a specific task. It is taking automatic action toward that task. I think if you attach a controller then it's like turning off autopilot and taking over control, and the assumption flips. You are more likely to remote control the capture in some way, so not losing focus seems like a logical starting point.

Please see my point in the first paragraph of [this message](https://github.com/w3c/mediacapture-screen-share/issues/230#issuecomment-1238184221). Namely, your requirement of `same unspecified default behavior with/without controller` is mutually exclusive with `our new func() can only focus, not prevent focus`. Please choose one. My own preference is to retain `same unspecified default behavior`.

>  Do we have TPAC time for this? If so it is probably more urgent to make slides than a PR. We could present both options even.

Yes, I intend to use the time set for me to present Conditional Focus. Naturally this will touch on the controller. Do you want to pull our slots together or reorder them so that you may present your wider vision for the controller in conjunction with its first use of Conditional Focus?


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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 8 September 2022 07:41:01 UTC