anssik: when there's enough
momentum. when we have a better idea of what work we have to
do, and we get enough support

richt: which WG?

anssik: any group with good
participation

dino: what is a "good level of
support"?

anssik: we need interoperable
implementations for instance

@@@: are you assuming a single second
screen?

anssik: right now it's a
simplified API
... but it's possible to perform the same API twice and
eventually get a second second screen (pun intended)

jcverdie: i am concerned by the
fact you say now you are considering the case of two UA, while
you said in the mailing list initially you didn't
... you need to clarify which goal you are pursuing, I am
afraid of potential overlap

dominik: i agree we need to
clarify

giuseppe: may be it is worth
exploring, but you need to clarify

jcverdie: to be clear, i'm just
asking for clarification, i'm not saying i'm against it

dino: sometimes your second
screen has more power and it makes sense it opens a UA
... also you need to poll for new displays, detect if some new
display goes online or offline, if there's delay in the display
on 2nd screen, ...

dominik: we'll need additional
events yes

dino: likely a big use case will
be to display a video

<israelh> q

dino: may be just ask for a
specific object to go to the second screen

giuseppe: it would be like a
"requestSecondScreen" similar to request Fullscreen

israelh: what about the UI of the
user agent (such as geolocation popup, ...)
... where would the question go?

dominik: at this point we don't
expect any interaction on the second screen, everything would
need to be covered on 1st screen but no use case so far