On 3/9/11 7:30 PM, Dimitri Glazkov wrote:
From the perspective of the component, the isolation is unfairly
punishing -- you can't use the outside DOM or even DOM element on
which you're hoisted, you can't add methods to it, and you have to
always imagine the membrane in order to build a proper mental model of
what the heck you're trying to accomplish.
This is sort of a requirement for being able to use components that you
don't trust to arbitrarily mess with your DOM though, no?
Also, the component wants to keep the document from poking at its
internals except via the APIs the component exposes, I would think.
From the perspective of the document, the isolation is too fiddly:
it's rare that the level of isolation at the _individual_ component
level is what's actually necessary.
I'm not sure what the "fiddly" issue is here... From the perspective of
the document isolation should mean two things:
1) Cross-site components are safe to use.
2) You can't screw up and depend on implementation details of a
component, because if you're calling something the component
provides then you're using APIs the component explicitly exposed.
Is there something I'm missing?
Or are those things that fall under "modularity" or "encapsulation" in
your message? If so, what are you thinking of in terms of "isolation"?
-Boris
