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

Avoid second click after changing the content of a metadata field #6100

Open
andre-hohmann opened this issue Jun 5, 2024 · 1 comment
Open
Assignees
Labels
feature metadata editor scheduled issues already planned/"ordered" for implementation

Comments

@andre-hohmann
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
If in the metadata editor the content of a metadata field is changed (add, delete, ...) it is not possible to choose directly another structure element or to apply the buttons "Validate", "Save", ...
A similar behavior occurs during the creation of newspaper processes wit the calendar.

Probably this is necessary to avoid the loss of the changes of the content of the metadata.

For users, this is annoying and in a few cases it lead to loss of data, because the buttons "Save" and "Exit" has been applied too quickly. It hasn't been regarded, that the "Save"-function was not been triggered and the metadata editor was closed without saving the changes in the metadata field.

Describe the solution you'd like
After changing the content in a metadata field, it should be possible to select directly other structure elements or the buttons "Validate", "Save", ...

Describe alternatives you've considered
If the implementation of the requirement causes too far-reaching adjustments to the software, the current status should be retained.

The users can get into the habit of clicking on somewhere in the “Metadata” frame after changing the content in a metadata field and before before clicking on an object outside of the metadata frame.

@solth
Copy link
Member

solth commented Jun 6, 2024

I think this is a description of the effects of #3472, which also causes #3346

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature metadata editor scheduled issues already planned/"ordered" for implementation
Development

No branches or pull requests

3 participants