Schema-specific web state (browser data) causes trouble in two cases:
- When switching between schema. Selection that only that are not relevant to the schema selected can cause issues.
- For developers working on the schema for similar reasons.
The net effect is that information can become mysteriously hidden.
One or both of the following solutions should be considered.
Solution 1: expire schema-specific settings
If possible, expire schema-specific settings after a period of inactivity such as 12 hours or a day.
The top-level settings should not be effected. These settings are:
- Dark mode
- Compact view
- Show deprecated
Solution 2: explicit cache clearing control
We should add button or similar to clear locally stored cookies and web data.
Sometimes as the implementation evolves, or switching between schema versions, the stored web data causes weird behavior in the UI. This feature will allow clearing all locally stored browser data so the UI operates in a clean state.
Apropos, consider scoping state by schema version to avoid state for one version causing trouble in another.
With this button, we should consider if the top-level settings should be affected. Perhaps clearing these top-level settings should be an option.
Schema-specific web state (browser data) causes trouble in two cases:
The net effect is that information can become mysteriously hidden.
One or both of the following solutions should be considered.
Solution 1: expire schema-specific settings
If possible, expire schema-specific settings after a period of inactivity such as 12 hours or a day.
The top-level settings should not be effected. These settings are:
Solution 2: explicit cache clearing control
We should add button or similar to clear locally stored cookies and web data.
Sometimes as the implementation evolves, or switching between schema versions, the stored web data causes weird behavior in the UI. This feature will allow clearing all locally stored browser data so the UI operates in a clean state.
Apropos, consider scoping state by schema version to avoid state for one version causing trouble in another.
With this button, we should consider if the top-level settings should be affected. Perhaps clearing these top-level settings should be an option.