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

Cannot edit schema #41

Closed
jdcrecur opened this issue Jan 12, 2019 · 5 comments
Closed

Cannot edit schema #41

jdcrecur opened this issue Jan 12, 2019 · 5 comments
Assignees
Labels

Comments

@jdcrecur
Copy link

jdcrecur commented Jan 12, 2019

Version: latest at time of writing.
Browser: Chrome latest at time of writing.
Screen: 24" screen

Cannot edit a schema unless there are enough schema's already in the list.
Requires a min. of 5 schema before you can edit the contents properly.

screenshot from 2019-01-12 15-19-27
screenshot from 2019-01-12 15-22-37
screenshot from 2019-01-12 15-23-57

Taking the flexbox and overflow hidden off seems to fix it (there is a js error thought too though, don't know if this is related):
screenshot from 2019-01-12 15-30-02

@jdcrecur
Copy link
Author

Actually wait that does not fix it, once the list of attributes gets too long for the modal window it becomes un-usable again :/

@MikeRalphson
Copy link
Contributor

Thanks for the report. Will try and reproduce.

@MikeRalphson MikeRalphson self-assigned this Jan 14, 2019
@MikeRalphson
Copy link
Contributor

MikeRalphson commented Jan 14, 2019

Reproduced in Firefox 64.0 and Chrome 70.0 so I think this is a generic layout/CSS bug. Thanks again for the report. I think the JS error is to do with trying to lock the screen.orientation to landscape which is within a try/catch so should not be relevant to this issue.

MikeRalphson added a commit that referenced this issue Jan 14, 2019
@MikeRalphson
Copy link
Contributor

MikeRalphson commented Jan 14, 2019

Setting position:fixed and a margin-top seems to improve this. Would be grateful if you could re-test.

@jdcrecur
Copy link
Author

Yup this has resolved the bug. Thanks!

MikeRalphson added a commit that referenced this issue Feb 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants