What should a vector editor remember after you hide its panels?
A familiar editor layout has to do more than resemble its reference. In Si, our browser-based vector editor, the workspace must distinguish a persistent preference from a temporary interaction. This is the second development entry, following a study of request-time document snapshots. Three meanings of “hidden” The current workspace source has three separate fields: allHidden , sideHidden , and…
In the Si browser-based vector editor, three levels of hiding the workspace interface exist: allHidden, sideHidden, and collapsed. These fields describe hiding the entire interface, only the side area, and maintaining a compact panel arrangement, respectively. The reducer toggles these fields independently, and an explicit panel selection clears the hiding flags, allowing the previous layout to be restored.
The layout and selected panel preferences are essential for retaining user experience, so a temporary hide command should not permanently erase these settings. The writeWorkspace function persists the layout by storing three fields (allHidden, sideHidden, and tool) in the browser's local storage. The read path initializes from default values, checks the storage version, accepts recognized panel names and units, and limits the width to 220-420 pixels.
If invalid JSON or storage failures occur, the system defaults to the preset preferences. The keyboard boundaries also play a role in preserving the workspace state. Shift+Equal could sometimes be interpreted as = instead of +, but the current keyboard normalizer resolves these inputs to the Plus symbol, mapping it to the tool.addAnchor command.
Ten isolated source checks, including keyboard routing, composition rejection, reducer transitions, transient reset, width bound, and malformed JSON fallback, all passed successfully. These tests validate that normalized input changes explicit state, persistent preferences survive reload, and temporary interactions do not become permanent preferences.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
