If a Posts or Pages column change cannot be saved, the server-backed setting rolls back but the open table and its menu do not. The rejected layout remains on screen until the page is reloaded.
How to reproduce
- Open the native Posts or Pages window.
- Open Window actions → Show columns.
- Take the browser offline.
- Hide a column and wait for the save to fail.
- The authoritative setting returns to its previous value, but the table keeps the column hidden and the menu keeps it unchecked.
What should happen
The table and menu should repaint from the restored saved state, and OpenStation should clearly say that the change could not be saved.
Where I would look
The global failure handler replaces its settings state, but does not notify subscribeOsSettings() listeners after rollback. The native table depends on that subscription to repaint its columns and menu.
src/settings/index.ts
src/settings/state.ts
src/posts-window/index.ts

If a Posts or Pages column change cannot be saved, the server-backed setting rolls back but the open table and its menu do not. The rejected layout remains on screen until the page is reloaded.
How to reproduce
What should happen
The table and menu should repaint from the restored saved state, and OpenStation should clearly say that the change could not be saved.
Where I would look
The global failure handler replaces its settings state, but does not notify
subscribeOsSettings()listeners after rollback. The native table depends on that subscription to repaint its columns and menu.src/settings/index.tssrc/settings/state.tssrc/posts-window/index.ts