Le 06/08/2013 16:26, Jack Moffitt a écrit :
The main issue with those is they tend to have not much layout stuff
inside but lots of script.  :(

We should think about putting cross-origin iframes on a separate script
task, for now, hopefully in a separate process later...
There wouldn't be much point to the suggested benchmark if this
weren't the case. We now have cross origin iframes on separate tasks
(they have their own pipeline -- layout, script, render, and pipelines
for any sub-iframes, etc). This was the work of Tim Kuehn and the main
subject of his talk last week:
https://air.mozilla.org/2013-intern-kuehn/
<3
To partially answer Dave Herman's question on same-origin iframes, the @sandbox attribute can be such an API (making same-origin iframes parallel without changing their DNS-domain).

Besides a maybe inaccurate test (documented by the TODO), the implementation Josh linked to doesn't seem to account for when the origin of a page can be changed using document.domain. We've also been discussing how an iframe could both have @sandbox="allow-same-origin" and run in parallel of the page (poison document.domain setter) [1]. The standard needs to be changed a bit. It'd be nice if someone from the Servo project could come weigh in the thread to ask for that change :-)

I believe most ads also use iframes, which means they are also in
their own pipelines.

The last piece of this puzzle is layered compositing, which we have a
PR for as of last night. Once that lands, you'll be able to see these
parallel iframes.
Love it! This is a game changer for web development. I mean it.

David

[1] http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2013-August/040356.html
_______________________________________________
dev-servo mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-servo

Reply via email to