You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a user is writing a changeset comment on a changeset page https://www.openstreetmap.org/changeset/:id: and they accidentally close the browser tab, the in-progress comment is lost upon restoring the tab.
It would be preferable for the in-progress comment to be restored in the input text area upon restoring the tab.
For example this happens here in GitHub, if you're entering a comment, writing an issue description and close the tab, then restore that tab, the in-progress text is restored.
In my case this happens because in Vim Ctrl+W deletes the last word, but in Chrome it closes the tab and sometimes they can be mixed up.
An alternative would be to popup that their message will be lost and if they should continue, but I see this as a worse UX.
The text was updated successfully, but these errors were encountered:
I'm running Google Chrome, latest version, on Debian but from Google's repository, with no extensions enabled for openstreetmap.org, and yes it doesn't seem to restore by itself. GitHub does, OSM doesn't.
If a user is writing a changeset comment on a changeset page
https://www.openstreetmap.org/changeset/:id:
and they accidentally close the browser tab, the in-progress comment is lost upon restoring the tab.It would be preferable for the in-progress comment to be restored in the input text area upon restoring the tab.
For example this happens here in GitHub, if you're entering a comment, writing an issue description and close the tab, then restore that tab, the in-progress text is restored.
In my case this happens because in Vim Ctrl+W deletes the last word, but in Chrome it closes the tab and sometimes they can be mixed up.
An alternative would be to popup that their message will be lost and if they should continue, but I see this as a worse UX.
The text was updated successfully, but these errors were encountered: