🦙 Bug - TinaCMS Dependency - Missing navigation and scroll reset when exiting inline edit form

Requested by: @GordonBeeming via YakShaver.ai 🦬
cc: @GordonBeeming, @Marxoz, @PothieuG, @Freego1783

Hi Team!

  🟥  Watch the video (40 sec)

  Url from screen share: https://www.ssw.com.au/rules/admin#/rules/use-github-copilot-cli-secure-environment

Pain

While editing content in Rules V3 (TinaCMS), clicking an editable field opens a secondary form without any visible UI controls to cancel, go back, or undo. Users must rely on the breadcrumb to exit the form. When using the breadcrumb, the page resets to the top instead of returning the user to their previous scroll position, resulting in a confusing and disruptive editing experience.

Acceptance Criteria

1. When an inline or secondary edit form is opened, a clear and visible action (e.g. Back, Cancel, or Close) is available to exit the form.
2. Exiting the edit form returns the user to the previous context without requiring breadcrumb navigation.
3. If breadcrumb navigation is used, the user is returned to their previous scroll position on the page.
4. The editing flow feels consistent and intuitive, without forcing the user to rediscover how to exit the form.
5. No regression is introduced to existing content editing functionality.

Reproduce Steps

1. Navigate to a content page in Rules V3 (TinaCMS).
2. Scroll down to a section near the bottom of the page.
3. Click on an editable field or box to open the secondary edit form.
4. Observe that no Back, Cancel, or Close UI is visible.
5. Click the breadcrumb at the top to exit the form.
6. Observe that the page reloads at the top instead of returning to the previous scroll position.

Screenshot

Figure: Editing opens a nested form with no clear return path, and using the breadcrumb resets scroll position

Start by reproducing the issue in the Rules V3 TinaCMS editor using the linked Rules admin URL, following the listed steps and observing the nested form and breadcrumb behavior. Done means the inline form has a visible way to exit, returning preserves the previous context and scroll position, and existing content editing still works without regression.