Skip to content
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.

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

Invalid field content lost when selecting different entry #1866

Closed
lenhard opened this issue Aug 26, 2016 · 3 comments
Closed

Invalid field content lost when selecting different entry #1866

lenhard opened this issue Aug 26, 2016 · 3 comments
Labels
bug Confirmed bugs or reports that are very likely to be bugs ui

Comments

@lenhard
Copy link
Member

lenhard commented Aug 26, 2016

JabRef version 3.5 onwards.

As first mentioned in #1863 (comment)

Steps to reproduce:

  1. Insert {a in article's title field
  2. Select different bib entry
  3. Return to first entry, field is reset to prior value

Although the field value is invalid. It should not simply be deleted without a message. Instead, it should still be present and, possibly, the field should be colored red. Alternatively, an error message could pop up, forcing the user to return to the corrupt field.

@lenhard lenhard added bug Confirmed bugs or reports that are very likely to be bugs ui labels Aug 26, 2016
@stefan-kolb stefan-kolb added this to the v3.7 milestone Aug 26, 2016
@lenhard
Copy link
Member Author

lenhard commented Sep 13, 2016

Fixed by #1893

@lenhard lenhard closed this as completed Sep 13, 2016
@lenhard
Copy link
Member Author

lenhard commented Sep 13, 2016

Correcting: Though indicated by the PRs, the issue is not really solved.

@lenhard
Copy link
Member Author

lenhard commented Jul 18, 2017

This seems to be solved in current master.

@lenhard lenhard closed this as completed Jul 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bugs or reports that are very likely to be bugs ui
Projects
None yet
Development

No branches or pull requests

4 participants