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

confusing UX when editing existing source or candidate #502

Closed
tarheel opened this issue Aug 24, 2020 · 1 comment
Closed

confusing UX when editing existing source or candidate #502

tarheel opened this issue Aug 24, 2020 · 1 comment
Assignees
Milestone

Comments

@tarheel
Copy link
Contributor

tarheel commented Aug 24, 2020

If you click on a text box for an existing CVR source or candidate and edit the value, then click outside of the box, it looks like your change has been registered. But it actually hasn't; as the message above the table says, you have to hit Enter to make it stick. Can we change the behavior so that clicking outside of the box either a) updates the underlying config object or b) reverts the rendered string to the existing value in the object?

@tarheel
Copy link
Contributor Author

tarheel commented Oct 1, 2020

No longer relevant because we disabled editing in #519 and #522.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants