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 15536 - [Explainer]: Clarify more how isolation will work
Summary: [Explainer]: Clarify more how isolation will work
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: 2012-01-12 19:43 UTC by Dimitri Glazkov
Modified: 2013-05-29 02:03 UTC (History)
1 user (show)

See Also:

Attachments

Description Dimitri Glazkov 2012-01-12 19:43:18 UTC 
"var service = new Worker("http://example.com/adorable/service/worker.js");"

Olli points out that this will either throw an exception or will need to run in the context of http://example.com, which is not what we expect.
Comment 1 Dominic Cooney 2013-05-28 08:11:11 UTC 
It looks like the way to do this is with an IFRAME. But if you want encapsulation, you need two nested IFRAMEs. Time to buy more RAM.
Comment 2 Dimitri Glazkov 2013-05-28 16:11:57 UTC 
(In reply to comment #1)
> It looks like the way to do this is with an IFRAME. But if you want
> encapsulation, you need two nested IFRAMEs. Time to buy more RAM.

Perhaps we should just nix this section from explainer? We'll work through this via WebAppSec+WebApps group collaboration and then add to explainer when there's something to report.
Comment 3 Dominic Cooney 2013-05-29 02:03:08 UTC 
Nixed in https://dvcs.w3.org/hg/webcomponents/rev/00f6b281ba9b