On 2/25/13 2:33 PM, David Bruant wrote:
2) different-origin iframe. JS from the parent can only interact with it
through message passing via postMessage.

Note that whether an iframe is same-origin or not is not time-invariant across navigations.

It seems like in theory, it could be possible to handle the content of a
cross-origin iframe in a specific Rust task (or bunch of tasks). The few
allowed communications (postMessage, iframe size in the parent, etc.)
would "just" be handled by cross-task communication.

Yes, as long as you handled navigations possibly moving the iframe to a new task.

* when the iframe@src changes, all the memory that's specific to the
task can be released directly without waiting for GC graph traversals or
refcounting

That may or may not be true depending on how session history works.

-Boris
_______________________________________________
dev-servo mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-servo

Reply via email to