You may want to execute some JavaScript when an inline form is added or removed\nin the admin change form. The formset:added and formset:removed events\nallow this. event.detail.formsetName is the formset the row belongs to.\nFor the formset:added event, event.target is the newly added row.
In your custom change_form.html template, extend the\nadmin_change_form_document_ready block and add the event listener code:
{% extends 'admin/change_form.html' %}\n{% load static %}\n\n{% block admin_change_form_document_ready %}\n{{ block.super }}\n<script src="{% static 'app/formset_handlers.js' %}"></script>\n{% endblock %}\napp/static/app/formset_handlers.jsdocument.addEventListener('formset:added', (event) => {\n if (event.detail.formsetName == 'author_set') {\n // Do something\n }\n});\ndocument.addEventListener('formset:removed', (event) => {\n // Row removed\n});\nTwo points to keep in mind:
\nThe JavaScript code must go in a template block if you are inheriting\nadmin/change_form.html or it won’t be rendered in the final HTML.
{{ block.super }} is added because Django’s\nadmin_change_form_document_ready block contains JavaScript code to handle\nvarious operations in the change form and we need that to be rendered too.
If your event listener still has to support older versions of Django you have\nto use jQuery to register your event listener. jQuery handles JavaScript events\nbut the reverse isn’t true.
\nYou could check for the presence of event.detail.formsetName and fall back\nto the old listener signature as follows:
function handleFormsetAdded(row, formsetName) {\n // Do something\n}\n\n$(document).on('formset:added', (event, $row, formsetName) => {\n if (event.detail && event.detail.formsetName) {\n // Django >= 4.1\n handleFormsetAdded(event.target, event.detail.formsetName)\n } else {\n // Django < 4.1, use $row and formsetName\n handleFormsetAdded($row.get(0), formsetName)\n }\n})\n