ISSUE-53: UI Security model for composited drawing models

UI Security model for composited drawing models

UI Security model for composited drawing models

State:
CLOSED
Product:
UI Security
Raised by:
Adam Barth
Opened on:
2013-04-26
Description:
Need to rethink the UI Security model for drawing models that use e.g. a multithreaded or multiprocess compositing model that prevents any single browsing context from having knowledge of the final rendering to the user to "take a screenshot". May be ways around this by if the compositor handles some UI events first, but spec should consider and provide advice on these alternate rendering models.

abarth: could possibly encode protected regions as a plane in the stencil buffer (where the composition is similar to a 3D rendering with multiple surfaces representing different logical parts of the final rendering) for hit testing, could be processed in the compositing thread
Related Actions Items:
No related actions
Related emails:
No related emails

Related notes:

Closed after new spec text added in Oct 31 editor's draft.

Brad Hill, 25 Nov 2013, 22:33:59

Display change log ATOM feed


Daniel Veditz <dveditz@mozilla.com>, Mike West <mkwst@google.com>, Chairs, Wendy Seltzer <wseltzer@w3.org>, Samuel Weiler <weiler@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 53.html,v 1.1 2020/01/17 08:52:36 carcone Exp $