- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Tue, 01 Jun 2021 13:52:37 +0000
- To: public-webrtc-logs@w3.org
> > At the moment we're having trouble reaching consensus over something far more modest > > As I said in the past, I am fine with having something very modest like exposing a static piece of information which always contain an origin (or expose nothing). > But it seems your usecase is much more advanced than that and requires tracking navigation, change of origins and so on. **On the one hand:** You suggested exposing the origin back on the original thread. It seems like you're still fine with it, and even ask for it to be done by default, with no way for the captured app to opt-out of that part. **On the other hand:** You list change of origins (e.g. when the captured tab experiences navigation) as an unexpected (?) complicating factor. Please help me understand. Has new information come to light, or have the goalposts moved? -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/166#issuecomment-852143245 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 1 June 2021 13:53:13 UTC