Elad Alon
@jan-ivar: > 1. it assumes order doesn't matter First, if we think it's important to support order, it's trivial to specify that. [Sequences](https://webidl.spec.whatwg.org/#idl-sequence) are ordered. (And let UX worry about...
@jan-ivar: My previous comment dealt with the technical details raised in your previous comment. I'm posting a separate comment here to address what I see as a **severe methodological issue**,...
We're proceeding in the WICG for the time being. (https://github.com/WICG/multicapture) I'm hoping to see this go back to the W3C.
> My ... lack of implementer interest (at this point) remain You raise an interesting topic - the appropriateness of the W3C as a spec-hosting venue for specs which only...
To clarify the tone of this message - I think we're on a similar page overall. I am supportive of the controller approach as a good compromise, I want to...
> 1. focus() is a one time thing. > This option is more capturer saying "I made a decision to focus or not to focus". > In that case, I...
> Can you elaborate on the risks? Please see the text beginning with "tricking the user to double-click..." and ending with "...of the captured surface" in [this message](https://github.com/w3c/mediacapture-screen-share/issues/230#issuecomment-1235415996). > Could...
> Your past message says that tricking a user to click will allow the web page to focus to the capturee page. > My question is what are the scenarios...
> Do we agree that supporting screen recording by letting users pick a displaySurface that isn't brought to front, is a requirement? If we don't have our requirements down, it's...
@jan-ivar, I'm assuming your last comment pertains only to the lines it quoted. So wrt to this part: > I see points 1-8 in [my message](https://github.com/w3c/mediacapture-screen-share/issues/230#issuecomment-1235415996) as sufficient for an...