On 1/15/13 11:42 AM, Brendan Eich wrote:
Cool, I'm with you -- this has been a gleam in various eyes for a while.
It turns out (I'm told) that IE9 and up (possibly IE8) process-isolate
such that window.open returns a DCOM proxy, sometimes!
Right. Not sure we want to go there, but...
For finer-grained arrangements such as cross-site <script src=> evolved
to use a subordinate label for the ad code (to subject it to stricter
CSP)
Have we been thinking about this? If so, I suggest getting abarth on
board. He seemed pretty dubious about such setups.
I don't propose inversion of control flow, however.
Not sure what you mean.
Alex Russell zeroed in on this in the Q&A for my AppSecUSA talk where I
proposed the cross-site script sub-label, perhaps in order to see
whether process or finer isolation was in the cards. I don't think it is
a "compatible-enough" change from today's script inclusion execution model.
We could make it opt-in (on the part of the site or script or both) if
needed, if we do it at all.
But this does not mean we should keep to the original
synchronous-calling (with async-loading) design of windows and frames.
That seems to be something that broke without "breaking the web".
Yes, exactly. I think same-origin it needs to be sync still. But
cross-origin is a different ballgame.
There's a race to get advertizers to use iframes. I still see tons of
cross-site script inclusion, CSS flyovers, etc. Nuking those via the
sub-label idea has appeal. Tell me if you think
no-iframe/cross-site-script ads are a dying technique, though.
No idea. The problems seem somewhat orthogonal to me...
We do have the inverted control flow issue on some parts of the DOM,
though. How much of that can we break?
Again, not sure what you mean.
I think the point is that if we ever want WebKit to actually implement
our b2g stuff, we should ensure that any non-same-origin communication
is async in our designs.
I don't agree for cross-site scripts. Those are labeled with the
includers origin, depriving us of an important policy knob. Yet their
code must have synchronous DOM access. Either they become a non-issue,
or we do sub-labels without inverted control flow.
I'd like to understand what you mean about inverted control flow.
Anda again, if we want to do something like this and expect WebKit to
follow, we either need to make it _really_ compelling or get them on
board now.
-Boris
_______________________________________________
dev-servo mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-servo