I think it would be useful to distinguish between a one-off screenshot and screen sharing/streaming here.
On Thu, Oct 23, 2014 at 10:10 PM, Jet Villegas <j...@mozilla.com> wrote: > 1. Web-facing or not? Both. Perhaps with different security models. > 2. Security/Privacy concerns Many. If granting permission to take a screenshot, should it last for the duration of the session, or be something you explicitly ask the user for every time? A security model similar to camera might work for sharing the screen. > 4. Feature requests (eg. blurred or lorem-ipsum text) We could have a hook to the API that allows manipulation of the element before the screenshot is taken, e.g. to transform text into lorem-ipsum or apply some CSS styling that blurs the text. But I'm not sure if there's such a strong use case for this? On Fri, Oct 24, 2014 at 8:48 AM, Anne van Kesteren <ann...@annevk.nl> wrote: > 2) We could perhaps have some concept of taking a snapshot of the > current page or indicated fragment so we can analyze it > asynchronously. Then if a known-bad thing was found, such as a plugin, > native form control, or non-CORS cross-origin image, we would reject. Capturing a fragment, e.g. the bounding box of an element, of the viewport seems useful, but what constitutes as “bad” in this context? It depends a lot on what the user wants to share. On Fri, Oct 24, 2014 at 9:08 AM, Jonas Sicking <jo...@sicking.cc> wrote: > It would also be cool to enable sharing just a particular app, or a > particular browser tab. Making this work on the visible portion of the document root element (viewport) by default of a single browser (content tab) makes a lot of sense, as there there are also privacy concerns with allowing a web-facing API to see the desktop. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
