Would it be good to make this configurable as a number of seconds rather than days? Looking at other configuration variables there seem to be both approaches used (e.g. $wgRCMaxAge defaults to 90 days, in seconds) and seconds seem more common. People can then do e.g. $wgEditRecoveryDeleteAfter = 30 * 24 * 3600; to get the default, or $wgEditRecoveryDeleteAfter = 60 * 5; for five minutes for easier local testing.

I wondered about calling it $wgEditRecoveryMaxAge but entries could end up being older than that if the user doesn't interact with the site, so it's not strictly a maximum.

Change 965179 had a related patch set uploaded (by Samtar; author: Samtar):

[mediawiki/core@master] EditRecovery: Add $wgEditRecoveryDeleteAfter config var

https://gerrit.wikimedia.org/r/965179

Change 965179 merged by jenkins-bot:

[mediawiki/core@master] EditRecovery: Add $wgEditRecoveryExpiry config var

https://gerrit.wikimedia.org/r/965179

nb. for QA, the config variable to set in LocalSettings.php is $wgEditRecoveryExpiry, defaulting to 2592000 seconds (30 days)

@Samwilson & @TheresNoTime I updated to core and added $wgEditRecoveryExpiry = 120; in my LocalSettings.php which should be two minutes but after 15 minutes, it's still showing even when going in and out of pages and browsers as seen in the screenshots below. Am I missing anything else? Also, Storage is now showing expiry compared to expiryDate like before.

Status: ❓NMI
Environment: Local: 1.42.0-alpha (7eb8efa) 16:46, 23 October 2023
OS: macOS Sonoma 14.0
Browser: Chrome 117
Skins. n/a
Device: MBA M2
Emulated Device:: n/a
Test Links:
http://localhost:8080/w/index.php?title=Harry_potter&action=edit
http://localhost:8080/w/index.php?title=Beer&action=edit

❓AC1: https://phabricator.wikimedia.org/T348593

Latest Patch- Edit Recovery	Latest Patch- expiryDate	Previous Patch

Also if you do two separate edits on the same article, should it show more than once in the Edit Storage? Since it's within the 120 seconds, shouldn't I see the edit saved on Safari too besides just Chrome since I'm under the same login?
Chrome & Firefox

Finally got somewhere with figuring out why this was working for me and not you — some recent changes have maybe caused:

:8080/w/load.php?lan…&version=5695o:1125 Uncaught (in promise) DOMException: Failed to execute 'transaction' on 'IDBDatabase': The database connection is closing.
    at http://localhost:8080/w/load.php?lang=en&modules=ext.CodeMirror.lib%7Cext.wikiEditor.realtimepreview%7Cjquery%2Coojs-ui-core%2Coojs-ui-toolbars%2Coojs-ui-widgets%2Coojs-ui-windows%7Cjquery.makeCollapsible%2Cui%7Cmediawiki.base%2Cnotification%2Cpulsatingdot%2Cwidgets%7Cmediawiki.diff.styles%7Cmediawiki.editRecovery.edit%7Coojs-ui.styles.icons-content&skin=vector&version=5695o:1125:716
    at new Promise (<anonymous>)
    at Object.deleteData (http://localhost:8080/w/load.php?lang=en&modules=ext.CodeMirror.lib%7Cext.wikiEditor.realtimepreview%7Cjquery%2Coojs-ui-core%2Coojs-ui-toolbars%2Coojs-ui-widgets%2Coojs-ui-windows%7Cjquery.makeCollapsible%2Cui%7Cmediawiki.base%2Cnotification%2Cpulsatingdot%2Cwidgets%7Cmediawiki.diff.styles%7Cmediawiki.editRecovery.edit%7Coojs-ui.styles.icons-content&skin=vector&version=5695o:1125:625)
    at saveFormData (http://localhost:8080/w/load.php?lang=en&modules=ext.CodeMirror.lib%7Cext.wikiEditor.realtimepreview%7Cjquery%2Coojs-ui-core%2Coojs-ui-toolbars%2Coojs-ui-widgets%2Coojs-ui-windows%7Cjquery.makeCollapsible%2Cui%7Cmediawiki.base%2Cnotification%2Cpulsatingdot%2Cwidgets%7Cmediawiki.diff.styles%7Cmediawiki.editRecovery.edit%7Coojs-ui.styles.icons-content&skin=vector&version=5695o:1122:220)

Change 982782 had a related patch set uploaded (by Samtar; author: Samtar):

[mediawiki/core@master] EditRecovery: Use ResourceLoader dynamic config

https://gerrit.wikimedia.org/r/982782

Change 982782 merged by jenkins-bot:

[mediawiki/core@master] EditRecovery: Use ResourceLoader dynamic config

https://gerrit.wikimedia.org/r/982782

Testing locally, I have been able to set $wgEditRecoveryExpiry in LocalSettings.php to a number of seconds. The expiration date added to the Edit Recovery entry in IndexedDB is the current date plus that number of seconds. This expiration date appears to be updated everytime Edit Recovery is triggered (e.g. 5 seconds after you type something or switch tabs).

I couldn't really test this on beta as I cannot change the configs there. But, I see that when an Edit Recovery entry is stored on beta the expiration date is roughly 2592000 seconds in the future, which is the default value of $wgEditRecoveryExpiry.