Edit Content page auto-scrolls to JSON field instead of staying at top

Problem Statement

While doing QA for #36318, we found that the Edit Content page automatically scrolls down to the JSON field when creating or re-opening a contentlet of the test Content Type from that ticket's sample bundle. The page should always default to the top of the scroll position — it should never auto-scroll to any field, including JSON.

This is a UX/UI regression in the new Edit Content mode. It doesn't cause data loss, but it disrupts the editing flow and can mislead the user into thinking they landed on the wrong field or that content is missing above the fold.

Steps to Reproduce

Content Type: Use the sample Content Type bundle attached to #36318 (contains a JSON field among others). Import it via Site → Publishing Queue → Bundles before following these steps.

1. Go to Content → New Content and select the test Content Type.
2. Add dummy values to the fields.
3. Click Publish.
4. Re-open the published contentlet for editing.
5. Observed: The page scroll automatically moves down to the JSON field.
6. Expected: The page scroll stays at the very top by default, regardless of field types present.

Acceptance Criteria

• When creating a new contentlet of the test Content Type, the Edit Content page loads with the scroll position at the top.
• When publishing the contentlet and re-opening it for edit, the Edit Content page loads with the scroll position at the top — it does not auto-scroll to the JSON field or any other field.
• The behavior is verified for a contentlet that has values in the JSON field (not just an empty one).
• No regression in normal manual scrolling — users can still scroll to and interact with the JSON field as expected.
• The original bug scenario (scroll auto-jumping to JSON field on reopen) no longer reproduces.

dotCMS Version

Latest from main branch

Severity

Low - Minor issue or cosmetic

Links

• Related: #36318 (New Edit mode has problems with specific field types) — found while doing QA for this ticket

Start at the Content → New Content and Edit Content flows using the sample Content Type bundle from #36318, then reproduce the scroll jump with a populated JSON field. Verify that both new and reopened contentlets load at the top, while manual scrolling and JSON-field interaction still work normally.