We discussed this proposal in an API Owners meeting last week, and then foolip@ and I met with Elad and Björn to discuss it in greater detail.
Jumping over to blink-api-owners-discuss for a higher level question.On Mon, 07 May 2018 19:24:46 +0200, Rick Byers <rby...@chromium.org> wrote:We discussed this proposal in an API Owners meeting last week, and then foolip@ and I met with Elad and Björn to discuss it in greater detail.Did you also discuss the bigger question: How to solve the use cases that have forced hangouts/meet to build an extension? Is there something that the web platform should get that would make that extension unnecessary?
On Tue, May 8, 2018 at 4:24 PM Daniel Bratell <bra...@opera.com> wrote:Jumping over to blink-api-owners-discuss for a higher level question.On Mon, 07 May 2018 19:24:46 +0200, Rick Byers <rby...@chromium.org> wrote:We discussed this proposal in an API Owners meeting last week, and then foolip@ and I met with Elad and Björn to discuss it in greater detail.Did you also discuss the bigger question: How to solve the use cases that have forced hangouts/meet to build an extension? Is there something that the web platform should get that would make that extension unnecessary?We didn't spend too much time on that higher level question, because we'd need more stakeholders involved to really get anywhere.In that area, however, I did take a look at thunk.js earlier today, pasting for your information. Quoting:From skimming https://chromium.googlesource.com/chromium/src/+/cdb8e9984e33e2a59d3c5e80e8b80bc9a2ec7b5f/chrome/browser/resources/hangout_services/thunk.js#64:- Using https://developer.chrome.com/apps/system_cpu to get more information about the CPU than with web-exposed APIs
- Many bits related to logging
- Use of chrome.webrtcAudioPrivate.getSinks and getAssociatedSink. Ends up AudioSystem::GetDeviceDescriptions which presumably provides different information than navigator.mediaDevices.enumerateDevices(). (Not tested.)
- Something called "getNaclArchitecture", so there's NaCL being used for something somewhere (or it's dead code)
- setAudioExperiments, presumably for experiments within libwebrtc
- Screen sharing
- CPU, memory and network usage monitoring
It would require a lot more investigation/discussion to work out a concrete plan to make the extension unnecessary.
--
You received this message because you are subscribed to the Google Groups "blink-api-owners-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-api-owners-d...@chromium.org.
To post to this group, send email to blink-api-ow...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/op.ziq7iwkorbppqq%40cicero2.linkoping.osa.
> Screen sharing seems to be the big one and I can imagine that part never being possible through standard web platform APIs. (for some value of "never")Available in Edge now. navigator.getDisplayMedia. Chrome is simply late to the game.
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALjhuieCdtTaN1YaVDCwfDhOcsDG%3DU%3DL7WDNypmL33o2NJ_Erg%40mail.gmail.com.
On Wed, May 9, 2018 at 7:40 PM PhistucK <phis...@gmail.com> wrote:> Screen sharing seems to be the big one and I can imagine that part never being possible through standard web platform APIs. (for some value of "never")Available in Edge now. navigator.getDisplayMedia. Chrome is simply late to the game.The challenge is that this is a huge cross-origin leak (potentially), but probably hard to convey to the user: if you share your screen, the site might read confidential information from whatever other site you have open or might open while sharing your screen.I guess one way to address this would be to only allow sharing same origin tabs (good enough for presenting a doc), or otherwise filter out cross origin pixels. Or have a CORS like mechanism (again, a presentation website could probably be convinced to send an appropriate CORS response).
Chrome also has it, behind a command line flag for web content (except Hangouts which got it despite the fact that no command line flag was specified, or it least so it was at some point if I understand correctly) and behind an extension API for extensions (Hangouts could have asked the users to install an extension, it was a poor design choice and some abuse of power, in my opinion).☆PhistucK
On Wed, May 9, 2018 at 6:48 PM Daniel Bratell <bra...@opera.com> wrote:
To unsubscribe from this group and stop receiving emails from it, send an email to blink-api-owners-discuss+unsub...@chromium.org.
To post to this group, send email to blink-api-owners-discuss@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/op.ziq7iwkorbppqq%40cicero2.linkoping.osa.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALjhuieCdtTaN1YaVDCwfDhOcsDG%3DU%3DL7WDNypmL33o2NJ_Erg%40mail.gmail.com.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-api-owners-d...@chromium.org.
To post to this group, send email to blink-api-ow...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/op.ziq7iwkorbppqq%40cicero2.linkoping.osa.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/CAARdPYew2shxAQD2gaDh0uM0HHG5sNGQmcVpZY%3D93uyr_WcO1Q%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/CAARdPYetdUxqnoRiYASbAjFh%3DFZ0tXC-G_JBE%3DUTAJn6P7Oatw%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY-rVru3_LfiyJZZKJnTw2MBGmG%3Dbz7U5QwX0T9i2vgJQg%40mail.gmail.com.
I assert that for the average person, their person, conversations and surroundings are much more privacy-sensitive than their device screen
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAMO6jDMp8VURkDUWEbNUj7Brmn6%3DmDtrgwWFzkQ9mQA3414Bvw%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALekkJchupAQoqpN-n60gu4RDN-Q66DZUnLLQBpjv4%2BgdVmYBA%40mail.gmail.com.
send an email to blink-api-owners-discuss+unsub...@chromium.org.
>>>>>>>>> To post to this group, send email to
>>>>>>>>> To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/op.ziq7iwkorbppqq%40cicero2.linkoping.osa
.
>>>>>>> --
>>>>>>> You received this message because you are subscribed to the Google
Groups "blink-dev" group.
>>>>>>> To unsubscribe from this group and stop receiving emails from it,
send an email to blink-dev+unsubscribe@chromium.org.
>>>>>>> To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALjhuieCdtTaN1YaVDCwfDhOcsDG%3DU%3DL7WDNypmL33o2NJ_Erg%40mail.gmail.com
.
> --
> You received this message because you are subscribed to the Google Groups
"blink-dev" group.
> To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAARdPYdwckTBp%3DacQ3CCNdOzOoO5b-TJrHgeDhCXPw3StvjajA%40mail.gmail.com
.
--
You received this message because you are subscribed to the Google Groups "blink-api-owners-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-api-owners-discuss+unsub...@chromium.org.
To post to this group, send email to blink-api-owners-discuss@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/CAARdPYew2shxAQD2gaDh0uM0HHG5sNGQmcVpZY%3D93uyr_WcO1Q%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "blink-api-owners-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-api-owners-discuss+unsub...@chromium.org.
To post to this group, send email to blink-api-owners-discuss@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/CAARdPYetdUxqnoRiYASbAjFh%3DFZ0tXC-G_JBE%3DUTAJn6P7Oatw%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAMO6jDMp8VURkDUWEbNUj7Brmn6%3DmDtrgwWFzkQ9mQA3414Bvw%40mail.gmail.com.
send an email to blink-api-owners-d...@chromium.org.
>>>>>>>>> To post to this group, send email to
>>>>>>>>> To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/op.ziq7iwkorbppqq%40cicero2.linkoping.osa
.
>>>>>>> --
>>>>>>> You received this message because you are subscribed to the Google
Groups "blink-dev" group.
>>>>>>> To unsubscribe from this group and stop receiving emails from it,
send an email to blink-dev+...@chromium.org.
>>>>>>> To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALjhuieCdtTaN1YaVDCwfDhOcsDG%3DU%3DL7WDNypmL33o2NJ_Erg%40mail.gmail.com
.
> --
> You received this message because you are subscribed to the Google Groups
"blink-dev" group.
> To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAARdPYdwckTBp%3DacQ3CCNdOzOoO5b-TJrHgeDhCXPw3StvjajA%40mail.gmail.com
.
--
You received this message because you are subscribed to the Google Groups "blink-api-owners-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-api-owners-d...@chromium.org.
To post to this group, send email to blink-api-ow...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/CAARdPYew2shxAQD2gaDh0uM0HHG5sNGQmcVpZY%3D93uyr_WcO1Q%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "blink-api-owners-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-api-owners-d...@chromium.org.
To post to this group, send email to blink-api-ow...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/CAARdPYetdUxqnoRiYASbAjFh%3DFZ0tXC-G_JBE%3DUTAJn6P7Oatw%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAMO6jDMp8VURkDUWEbNUj7Brmn6%3DmDtrgwWFzkQ9mQA3414Bvw%40mail.gmail.com.