Skip to content
English
Submit a request
  • There are no suggestions because the search field is empty.

Builder 2.0: Page Persistence on Browser Refresh

Refreshing the browser in Builder now returns the user to their current page, not Page 1

1. Purpose & Scope

This article documents the Builder 2.0 page persistence improvement released in Tiled v59.0.0. Prior to this release, refreshing the browser while working in the Tiled Builder would reset the user's view to Page 1, regardless of which page they were actively editing. This caused loss of working context and required users to manually re-navigate to their intended page after every accidental or intentional refresh.

Scope: All Tiled users with Builder access (Editor role and above) working in Builder 2.0.

2. Control Objective

The control objective is to preserve the user's active working context across browser refresh events within Builder 2.0, ensuring that the editing session resumes at the correct page without requiring manual re-navigation. This supports operational continuity and reduces the risk of users inadvertently editing the wrong page after a refresh.

3. Feature Description

When a user refreshes their browser while working in the Tiled Builder 2.0, the application now restores their session to the page they were editing at the time of refresh. This is achieved by persisting the active page state in the session context so that on reload, the correct page is resolved and rendered automatically.

Note: This behavior applies to Builder 2.0 only. Builder 1.0 behavior is unchanged. Page persistence applies to the active page within the microapp — it does not preserve unsaved edits made before the refresh.

4. Behavior Reference

Before v59.0.0

Browser refresh in Builder always returned the user to Page 1, regardless of the page being edited at time of refresh.

After v59.0.0

Browser refresh returns the user to the page they were actively editing. If on Page 5, refresh reopens on Page 5.

Unsaved Edits

Unsaved changes are not preserved across a browser refresh. Only the active page position is restored.

Builder Version

Applies to Builder 2.0 only. Builder 1.0 behavior is unaffected.

5. Testing Verification Steps

QA Focus: This feature is a primary testing focus for the v59.0.0 release cycle. Testers must verify page persistence from multiple starting pages.
  1. Open a microapp with multiple pages in Builder 2.0.
  2. Navigate to a page other than Page 1 (e.g., Page 3, Page 5).
  3. Refresh the browser using the browser's refresh button or Ctrl+R / Cmd+R.
  4. Verify that the Builder reopens on the same page that was active before the refresh.
  5. Repeat the test from at least three different pages to confirm consistent behavior.
  6. Also test after navigating via the Layers panel and via page thumbnails.

6. Roles & Access Requirements

Editor / Builder User

Any user with Builder access can verify this behavior. No elevated permissions required.

QA Tester

Responsible for executing the verification steps above and recording results in the testing matrix.

Release Owner

Signs off on the testing record as evidence of pre-release validation.

7. Audit Evidence

  •   Testing results recorded in the v59.0.0 QA Testing Matrix (KB-v59-06) constitute evidence of pre-release validation for this control.
  •   SOC 2 CC4.2 (Evaluation of Control Deficiencies): The prior behavior (always reverting to Page 1) is treated as a corrected deficiency. This article and its associated test record serve as evidence that the deficiency was identified and remediated.

8. Change History

v1.0 — April 2025

Initial article. Feature shipped in Tiled v59.0.0 April release.