OPFS persistence check¶
Save a small PostgreSQL record on this device, then check it after restarting your browser. This page uses OPFS, independently of the homepage's memory database.
First, write a test record. Then quit your browser, return to this exact address, and verify it.
No saved test yetNot read in this page visitRecovery test and report
Test interrupted write changes the record inside an uncommitted transaction, then reloads without closing the database. Recovery should keep the original committed record.
Use a normal browser window and keep the same website address and browser profile. Clearing site data also deletes this test database. Keep only one copy of this test page open.
Write & verify saves a unique marker, closes the database, and checks the record through a fresh database instance. Verify saved data only opens an existing database: it never recreates the test table or inserts replacement data. The expected marker is kept separately as a small browser-local receipt; the actual marker is always queried from PostgreSQL.
Returning after quitting Safari and verifying the same marker tests persistence on your device. The interrupted-write check tests page interruption and rollback, not hardware power loss. These focused checks do not establish full Safari/iOS release qualification.
The first start downloads the same browser package as the homepage. Static hosts such as GitHub Pages may reload once to prepare the browser; no database server is involved. See the browser guide for SDK usage.
From a source checkout, run this page's automated checks with:
The checks cover Chromium, Firefox and WebKit, with both response-header isolation and a GitHub Pages-style static host. Linux WebKit does not replace testing on an actual Safari device.