Not really, I was talking about a PR to add the changed needed for the OP library to be inside LV itself. The PR doesn’t exists yet.
But, either way, nice to know that we could possibly get portal functionality in LV, looking forward to it 
1 Like
live_view_portal the npm package contains the client side code for LiveView with some modifications to make it work in third-party pages.
When you install phoenix_live_view from hex.pm you get both the server and the client side code. Each live_view_portal version is fixed to a phoenix_live_view version, becuase the server and client code should be able to “talk” to each other.
So to answer your question, it is not related to iframe. It is an inherent problem of the library. When we get this merged to LiveView this problem will of course be gone 
(I’m trying to find the time to make this happen).
1 Like
I completely understand! I was wondering if you had tested it in any project, not necessarily production. As I just said in another reply, I’m trying to find some time to get at least a draft for the PR to LiveView.
