On 2/25/13 4:51 PM, Brian Smith wrote:
David Bruant wrote:
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).

I thought Rust tasks were supposed to be very lightweight. If so, why not put 
every iframe in a separate task, whether it is same-origin or not?

Because that involves being able to make JS calls directly across tasks. That's a lot of infrastructure to add.

Furthermore, the web relies on event ordering in same-origin iframes, so you can't run them in parallel. Serializing multiple tasks is ... hard, I would assume.

It would be interesting to get the telemetry to see how common the following 
kinds of pages are:

1. Page with no iframes

On today's web, pretty much nonexistent.

2. Page with only same-origin iframes (and how many such iframes)

On today's web, I would expect rare, but worth getting telemetry.

3. Page with only cross-origin but same site (eTLD+1) iframes (and how many)

Again, I would expect rare.

4. Pages with only cross-site iframes (and how many)

I would expect this to be common. For example every single Facebook Like button or Google+ +1 button involves a cross-site iframe.

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

Reply via email to