proof of concept: phx-portal #3478
Conversation
This is a proof of concept commit implementing a new phx binding called `phx-portal`. This binding allows to designate an element to be rendered at another location in the DOM, designated by the ID that `phx-portal` points to. This can be useful to render things like dialogs at the top layer, outside any containers that might affect their rendering (e.g. overflow: hidden). Nowadays there is also the Popover API and native `<dialog>` elements, so this might not be that important any more. Because of this, I also don't feel like this is something we really want to support. This commit only shows how it could be implemented.
SteffenDE
force-pushed
the
sd-phx-portal
branch
from
843df76
to
2e49ff4
Compare
|
Hey @SteffenDE, I think this is a worthy addition, even with the upcoming Dialog API. Even though the Dialog API usage is already at 95%, there are use cases where a portal is needed outside of a dialog usage, anything that we need to break out of its container layout. Now, my only doubt is if this should be user-land, but I would be perfectly happy to have it built-in. :) |
|
I would love this to simplify "forms within forms". Say for instance you have a multi-select component in a form and you want to be able to create options from within the component using another predeclared form (which is our use case). Would this work for that? That's at least how we used Vue Teleport before migrating to Live View. |
|
will be great to have this in 1.0 release. This is very necessary feature with which modals can finally will be live! :) |
This is a proof of concept PR implementing a new phx binding called
phx-portal. This binding allows to designate an element to be rendered at another location in the DOM, designated by the ID thatphx-portalpoints to. This can be useful to render things like dialogs at the top layer, outside any containers that might affect their rendering (e.g. overflow: hidden).Nowadays there is also the Popover API and native
<dialog>elements, so this might not be that important any more.Because of this, I also don't feel like this is something we really want to support. This PR only shows how it could be implemented.