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

Make UI responsive for small screens #122

Open
surchs opened this issue Apr 11, 2024 · 2 comments
Open

Make UI responsive for small screens #122

surchs opened this issue Apr 11, 2024 · 2 comments
Labels
feedback:user feedback Feedback from our users. Either direct issue submission or conveyed feedback _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again good first issue Good issue for a new contributor. PR welcome Issue that is not an internal priority, but external PRs to address it are welcome. type:feedback Feedback from users or community members about our services or possible extensions

Comments

@surchs
Copy link
Contributor

surchs commented Apr 11, 2024

Right now the tool works best on desktop screen sizes. On smaller screens it scales down until Ui elements overflow their boxes - and look bad.

Because we use tailwind it should be easy to stack the query form on top of the response container when the screen size is smaller. That should already help.

@surchs surchs added feedback:user feedback Feedback from our users. Either direct issue submission or conveyed feedback good first issue Good issue for a new contributor. PR welcome Issue that is not an internal priority, but external PRs to address it are welcome. type:feedback Feedback from users or community members about our services or possible extensions labels Apr 11, 2024
@surchs
Copy link
Contributor Author

surchs commented Apr 27, 2024

Hey @Sauradip07, cool, thanks. Feel free to open a draft pr where we can look at the changes together!

The main idea here is to have the query form on the left side collapse into a menu or attack on top of the results on smaller screen's.

Copy link

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

  • prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
  • close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
  • archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
    apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
    label in the future. Use sparingly!

@github-actions github-actions bot added the _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again label Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feedback:user feedback Feedback from our users. Either direct issue submission or conveyed feedback _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again good first issue Good issue for a new contributor. PR welcome Issue that is not an internal priority, but external PRs to address it are welcome. type:feedback Feedback from users or community members about our services or possible extensions
Projects
Status: No status
Development

No branches or pull requests

1 participant