Skip to content

Added clarification to phx-remove to explain a surprising behavior #3800

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
pinetops wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Added clarification to phx-remove to explain a surprising behavior #3800

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions guides/client/bindings.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -353,6 +353,9 @@ may be specified, which can contain a `Phoenix.LiveView.JS` command to execute.
The `phx-remove` command is only executed for the removed parent element.
It does not cascade to children.

Note that it's recommended that for `phx-remove` to work correctly, the parent
element should have a (unique) DOM ID. If it doesn't have one, it may not fire.

To react to elements being updated in the DOM, you'll need to use a
[hook](js-interop.md#client-hooks-via-phx-hook), which gives you full access
to the element life-cycle.
Expand Down