Hi

First, I think this is a fantastic idea! Thanks David for bringing this up.

>> Its also not time-invariant when document.domain is used, correct?
>
> True. I guess the cases of "iframe initially has a different origin than its
> parent, but JS can change that" are more numerous than I originally thought.

Other than document.domain, what changes effective principal without
navigation? If I am not wrong, document.domain changes would mean that
"if you were a cross-origin frame, but changed  document.domain; then
cross-iframe access would be far more slower than if you had started
off being same-origin". I think that's fantastic and should be
considered a feature, not a bug. We want people to stop using
document.domain, right?  (postMessage)

http://research.microsoft.com/en-us/um/people/helenw/papers/incoherencyAndWebAnalyzer.pdf
 suggests that it was already not common to use document.domain in
2009. It is hopefully less common now and will be even  less common by
the time Servo is ready. I just don't think we should consider
document.domain while guiding the design.

Putting iframes from different origins into different tasks might also
help ease moving some critical iframes (like say for *.google.com) to
a new process, which was discussed on this list a fortnight ago.

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

Reply via email to