[naasking]

> Layout-isolated component - A component that is unaffected by the parent it is placed within, and does not itself affect the size and position of its siblings.

I'm honestly still surprised that this isn't the default. Beyond maintainability, it's an obvious security problem, which clickjacking made apparent years ago.

The security implications of user interface API apparently isn't well understood outside the capability security community though:

Design of the EROS Trusted Window System, http://srl.cs.jhu.edu/courses/600.439/shap04windowsystem.pdf

> Remember when we were building our apps as a set of screens and pages instead of thinking in components?

If pages were components in the browser, there wouldn't be any difference. Xanadu had something like this way back in the early 90s, ie. page transclusion.