UVE enters infinite loop in Firefox when running headless Next.js example

Problem Statement

When running the headless Next.js example application inside the Universal Visual Editor (UVE) using Firefox, the page enters an infinite loop. The loop manifests as an endless stream of logs printed in the Next.js dev console/terminal, and as a result the page becomes unresponsive/unavailable to edit inside UVE.

The Angular example does not exhibit this problem when tested in Firefox — the issue appears specific to the Next.js example (or to how it interacts with UVE in Firefox specifically). It is still pending to verify whether the Vue example, or other example apps, are also affected.

Browser: Firefox (latest stable)
Not affected: Chrome/Chromium-based browsers, Angular example

Steps to Reproduce

https://github.com/user-attachments/assets/3658f179-fa73-4c78-8a81-15277bdc1bbb

Or detailed steps:

1. Open the headless Next.js example application.
2. Load the example inside UVE (Universal Visual Editor).
3. Use Firefox (latest stable) as the browser.
4. Observe the Next.js dev server terminal/console.

Expected: UVE loads and allows editing the page normally, as it does with the Angular example.

Actual: The page enters an infinite loop; the Next.js terminal/console fills with an endless stream of logs, and the page becomes unavailable to edit within UVE.

Acceptance Criteria

• Loading the headless Next.js example inside UVE in Firefox (latest stable) does not trigger an infinite loop
• The Next.js dev server/terminal does not produce a continuous, unbounded stream of logs when the example is loaded in UVE under Firefox
• The page is fully editable within UVE when using the Next.js example in Firefox (matching the existing behavior of the Angular example)
• Existing Firefox behavior for the Angular example remains unaffected (no regression)
• Existing behavior for the Next.js example in other browsers (e.g., Chrome) remains unaffected (no regression)

dotCMS Version

Latest from main branch

Severity

High - Major functionality broken

Links

NA

Start by running the headless Next.js example inside UVE with Firefox and watch the Next.js dev server terminal for the repeating logs. Compare the behavior with Chrome and the Angular example, then trace the interaction that repeats during loading. Done means the page loads and remains editable in Firefox without unbounded logging, while Angular and other-browser behavior stay unchanged.