Lack of persistence in editing apps is an accessibility fail #75440
Replies: 3 comments
-
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! |
Beta Was this translation helpful? Give feedback.
-
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
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:
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
Beta Was this translation helpful? Give feedback.
All reactions