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

[Chrome] [Suggestion] - Have the edit window match the width of the column you're editing #848

Closed
3 tasks done
JacobJT opened this issue Mar 20, 2018 · 1 comment
Closed
3 tasks done
Labels
state:wont-fix Won’t be fixed with a clearly stated reason

Comments

@JacobJT
Copy link

JacobJT commented Mar 20, 2018

Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Dashboard!

  • You're running version >=1.0.23 of Parse Dashboard.

  • You're running version >=2.3.2 of Parse Server.

  • You've searched through existing issues. Chances are that your issue has been reported or resolved before.

Environment Setup

Chrome Version 65.0.3325.162 (Official Build) (64-bit)
MacOS Version 10.12.6 (16G1212)

Steps to reproduce

  • Have a long string or array field
  • View in dashboard, expanding the column in question
  • Double click to enter edit mode
  • The Edit field is very thing, which makes it hard to read the existing data

In my particular case, I was using this to be able to view the data, as it's an array with maybe a dozen or so elements. Expanding the column width isn't a feasible option to view all the data, though I did expand it a generous amount so one of my contained objects would be visible in the preview. My only option was to double click into the field to view the entirety of the data from there. However, with the tiny width box, I couldn't read it properly and had to expand the width by using the drag corner. On several instances I mis-clicked ever so slightly, and it decided to save the object, which changed updatedAt so it's now not a reference for the last time the user had edited the object themselves.

@stale
Copy link

stale bot commented Jan 10, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:wont-fix Won’t be fixed with a clearly stated reason
Projects
None yet
Development

No branches or pull requests

1 participant