This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 14953 - [Explainer]: Explain how confinement could be achieved using existing primitives
Summary: [Explainer]: Explain how confinement could be achieved using existing primitives
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 14949
  Show dependency tree / graph
 
Reported: 2011-11-28 19:21 UTC by Dimitri Glazkov
Modified: 2011-11-28 20:55 UTC (History)
0 users

See Also:

Attachments

Description Dimitri Glazkov 2011-11-28 19:21:01 UTC 
"Component confinement is much trickier. Perhaps it needs to be tackled as a separate effort."

Using a pair of corruptible/incorruptible objects, one being a worker/iframe.
Comment 1 Dimitri Glazkov 2011-11-28 20:55:36 UTC 
http://dvcs.w3.org/hg/webcomponents/rev/71369e6512bf