8000 Accidental navigation back (backspace) too easy - none of the entered text is remembered neither · Issue #563 · prose/prose · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Accidental navigation back (backspace) too easy - none of the entered text is remembered neither #563

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
antitoxic opened this issue Aug 3, 2013 · 9 comments
Open

Accidental navigation back (backspace) too easy - none of the entered text is remembered neither #563

antitoxic opened this issue Aug 3, 2013 · 9 comments
Labels
enhancement

Comments

@antitoxic
Copy link

I use http://prose.io as an editor and the i love the interface.

One thing however is a big issue for a editor application.

Having the website is js powered (all urls and nav), when a user looses focus on textarea and presses backspace the browser Back navigation is triggered

When I try going forward (after a dose of doh!) my texteditor is empty or have discarded any changes that i havent saved.

Textarea looses focus most often on navigating back and forward from metadata to text editing and other panels.

I can think of 2 solutions:

  • Simple autofocus on the textarea after going back to "Edit"
  • Keep the id and contents from last edited file in js and just revert back to that remembered contents when the same file is opened again
@mikemorris
Copy link
Contributor

Your second proposed solution should already be implemented, sounds like something might have broken it?

@antitoxic
Copy link
Author

When editing an already existing file that is tru but when creating a new one it's not.

That issue is regarding the New File use case . I noticed it as I often post to jekyll blogs through prose.

@antitoxic
Copy link
Author

May be (if not already used) : https://github.com/simsalabim/sisyphus

@mikemorris
Copy link
Contributor

@antitoxic We've already implemented localStorage for saving content for existing files, this is something we could potentially add for new files as well.

@joewiz
Copy link
joewiz commented Aug 20, 2013

I just got bit by the new file problem. Steps to reproduce:

  1. Select New File to start a new file.
  2. Enter text into the editor; the disk icon indicates there are changes to save.
  3. Hover the mouse over the prose.io icon in the top-left corner, and select About from the dropdown menu that appears. Boom, your changes are lost.

I had hoped the changes would be recoverable, but couldn't find a way to recover what I had typed.

@mikemorris mikemorris mentioned this issue Aug 28, 2013
Closed
@bruth
Copy link
bruth commented Oct 25, 2013

Another recommendation is adding a window.onbeforeunload handler to catch when leaving the page. The user will have to confirm if they want to leave their unsaved changes.

@bruth
Copy link
bruth commented Oct 25, 2013

I don't actually know if onbeforeunload gets triggered on push/popState, so that will have to be emulated for those cases.

@mikemorris mikemorris mentioned this issue Nov 25, 2014
Closed
@davidkalosi
Copy link

+1 on this. happened to me today

@fulldecent
Copy link

Hello and thank you for this issue report. There have been several point releases in Prose since this issue was opened and there has not been much discussion here. I wanted to ask if you could please assist in confirming this is still an issue in the latest version of the product. If it is fixed, please close this issue :-)

Also, if possible could you please

  • Find out if this only affects certain browsers
  • Create a test case -- a list of steps we can perform to reproduce the problem
  • Enable web developer extensions and report the Javascript error message. And when in doubt, be over-descriptive of the bug and how you discovered it.

Since this project is looking for new maintainers (#743), it will be helpful if users can double check the old issues and delete ones that are fixed. This will be super helpful for the new team that works on moving this project forward.

I'm sorry this message is impersonal. And thanks for your help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@joewiz @antitoxic @fulldecent @bruth @mikemorris @davidkalosi
0