Lack of persistence in editing apps is an accessibility fail

[Myndex]

Select Topic Area

Product Feedback
Bug

Lack of Persistence

I am asking that all editing web apps in GitHub's web presence have persistence, so that if something happens, either a crash or an accidental navigation to another page, that what was being worked on is not lost. Right now, all work is lost.

Right now, using any of the editing web apps anywhere on GitHub, with any browser, if something happens on that webpage be at a crash or an accidental navigation or an accidental window close, everything is lost.

This is in part because GitHub takes over JavaScript and bypasses any protections that the browser may actually incorporate. This means that it is GitHub's responsibility to make sure that content entered is persistent.

Accessibility

I am blind/low vision. As a result, it is very easy to accidentially close a window or hit a navigation element. This should not post a problem, except that GitHub has no protection when editing a file or text.

To be clear, what I'm asking for is persistence. There is no excuse to have a web app for editing a file or text that is so volatile that all work is lost when any of the following occur:

• Crash
• Window close
• Nav to new page
• Nav back
• Page refresh
• Browser quit

At the VERY least, the GitHub web app should have protection from accidental window close or nav when editing a file or text.

Orthagonal persistence is common today. This is 2023, and it is the expected behavior. But GitHub's editing web apps (all of them) fail here completely, as if it was 1997. There is no persistence, there is no safety when editing any file in the GitHub web apps.

Thank you for reading.

Andy

[ghostinhershell]

Hey there @Myndex 👋🏾

Thanks so much for providing this feedback. I'll file this with our Accessibility team so that it can be reviewed and will follow-up here with any additional questions or updates.

Thanks again!