Furthermore there's a growing movement to slowly deprecate certain embedding use cases. Embedded sites could always pop themselves out of the current page, but there's now also HTTP headers that let you explicitly forbid embedding on either end. This is actually considered a security best practice[0] as there are crafty XSRF attacks that could be enabled by, say, layering an invisible iframe in front of your cursor that just so happens to be open and scrolled to the "send all my money to someone" button on your bank account. Timing attacks apparently also rely on embedding, so anyone who wants to use, say, shared-memory multithreading for WASM[1] has to also opt out of both being embedded and being allowed to embed other sites.
[0] According to people begging for bug bounty money
[1] i.e. Ruffle
Ultimately though it was the web that implemented the end goal of interactive, linked documents and components though.