Not switched on
Useful2 Signal3
Unsaved artifact edits could survive a reload with Save and Discard buttons, but the skill is off.
Session-storage stashing of unsaved edits exists, but the artifact editing skill's registration check is false.
What's wrong with this entry?
Anonymous. No account, no email.
What
In the artifact editing skill, edits you have not saved are stashed in the browser's session storage and offered back after a reload. The skill's registration check is false in this build, so nothing reaches it.
Details
- The copy is written on a 1 second throttle while the page is dirty and again on
pagehide, under a key built from'kit:unsaved:'plus the page host, with a 24 hour expiry. - A page that loads with a stashed copy shows it in place of the served article, held read-only, with two new toolbar buttons: a second Save (
data-restore) and a Discard (data-discard) that drops the copy and reloads the served version. - Cursor block index and scroll position ride a separate 2 minute stash keyed
'kit:restore:'plus host, so a save-triggered reload lands where you were. - The status text distinguishes a copy taken over the same version from one taken over a newer one.
Evidence
Showing recovered edits over a newer version. Saving replaces it.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.