- From: <piranna@gmail.com>
- Date: Thu, 9 Jan 2014 01:04:39 +0100
- To: Alex Gouaillard <alex.gouaillard@temasys.com.sg>
- Cc: Randell Jesup <randell-ietf@jesup.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
> The pledge is no plug in, no download. We believe the > solution implemented right now in chrome for full screen sharing, > which require 1. a flag to be enabled, 2. to connect over https, and > 3. to click on a prompt to provide permission, add some burden but > would be acceptable. > >From my point of view, requesting to the average user to enable a flag on his browser it's equivalent to install a plugin, they will do it without think (continue, next, next, ok) just as it's something to enable new, hidden, power-user functionality, or they will don't do it due to fear to broke their system. I find better to only allow to init the screensharing from the main document and after accepting the prompt for that particular domain, and also incentivate to the developers to share the less screen space as posible: browser tabs (for example, screensharing of an HTML5 videogame on championships) over particular application windows over all windows from an app (showing black areas outside them) over desktop without taskbar (is it possible to detect that use case?) over full screen desktop, maybe lowering the requeriments (and the final user annoyance) for some of them. It's not the same to just ask for share explicitly the "Excel - TAX contability" window to request some help on an account page than to share the full desktop with a luxury cars web page open on the taskbar that you didn't remind you opened it before going to eat... -- "Si quieres viajar alrededor del mundo y ser invitado a hablar en un monton de sitios diferentes, simplemente escribe un sistema operativo Unix." – Linus Tordvals, creador del sistema operativo Linux
Received on Thursday, 9 January 2014 00:05:28 UTC