Boris Zbarsky wrote:
On 10/21/12 1:49 AM, Patrick Walton wrote:
I'm not entirely clear on the semantics of adoptNode. Is it possible
that the node could come from a different origin?
On the web, no. As far as what browser UI and extensions can do... up
to us, I guess.
I think the right answer is "no". Between distinct origins, postMessage
or bust.
If the node can't come from a different origin, it's still tricky, but
relatively straightforward: we brain transplant the JS object and
essentially treat the node as deleted on the document it came from as
far as layout is concerned. It's an invariant that layout can't directly
store DOM node handles from layout pass to layout pass, so once layout
is completed it should be OK to move the node over.
Ah, ok. We'd need to find all the places in the old document that
reference the node, but that might be feasible.
By tracking all the time, or scanning only upon an adoptNode? Hrm.
/be
_______________________________________________
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
