Issue Bug Under Review

#111476Inline relation container leaves rejected requests and icon loads unhandled

Benjamin Kott 11/17/26, 15:59 updated 11/18/26, 21:08

Description

Problem

When a request of an inline relation fails, AjaxDispatcher::send() shows an error notification and returns the rejected promise. Several callers in InlineControlContainer only chain .then() on it, so every such failure also leaves an unhandled rejection in the browser console:

  • the button for a new record, the selector of an existing record, the selector of a preset and a record inserted from the element browser (importRecord());
  • the button to localize or synchronize the children.

The same happens when an icon fails to load: the visibility toggle and the sort buttons call Icons.getIcon() without handling its rejection.

Steps to reproduce

  1. Open a record with an inline relation in the backend.
  2. Make the request of the button for a new child fail, for example by stopping the web server or blocking the request in the developer tools.
  3. Click the button: the error notification appears, and the browser console reports an uncaught rejection as well.

Cause

Build/Sources/TypeScript/backend/form-engine/container/inline-control-container.ts: the callers of importRecord(), the synchronize and localize request and the three Icons.getIcon() calls (visibility toggle, sort up, sort down) have no catch. importRecord() has to keep rejecting, so that the element browser is not told about an insert that failed.

Reviews 1

History 02