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

Unsaved card edits no longer persist in front-end #10027

Closed
SDScandrettKint opened this issue Sep 11, 2023 · 2 comments · Fixed by #10642
Closed

Unsaved card edits no longer persist in front-end #10027

SDScandrettKint opened this issue Sep 11, 2023 · 2 comments · Fixed by #10642
Assignees

Comments

@SDScandrettKint
Copy link
Member

In Arches V6.2, entering data into a resource card and navigating away to another card would result in the initial inputted data being in an "unsaved edits" state. The UI would represent this with yellow highlighting and navigating back would return the original inputted data:
unsaved_edits_v6 2_cropped

In V7, this feature doesn't appear to be working as the yellow highlighting is missing and the data entered doesn't show up:
unsaved_edits_v7_cropped

@SDScandrettKint
Copy link
Member Author

Update: The highlighting doesn't appear for all datatypes because of the missing CSS found here from V6, but the issue of data not persisting is only for the string and URL datatypes.

@SDScandrettKint
Copy link
Member Author

Update:

This bug occurs for three datatypes:

  • String
  • URL
  • Node Value

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
2 participants