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 the facility detail page more properly responsive #6621

Closed
3 tasks
nihal467 opened this issue Nov 15, 2023 · 4 comments · Fixed by #6960
Closed
3 tasks

Make the facility detail page more properly responsive #6621

nihal467 opened this issue Nov 15, 2023 · 4 comments · Fixed by #6960

Comments

@nihal467
Copy link
Member

Describe the bug

  • the facility details which can be shown in the same row are been displayed as a different row in the responsive view
  • the buttons are stretched a lot to occupy the entire row, where it can occupy two or three buttons as per the screen size

To Reproduce
Steps to reproduce the behavior:

  1. Go to facility detail page
  2. See error

Expected behavior

  • make the facility detail page, fully responsive properly

Screenshots

image

@kshitijv256
Copy link
Contributor

I would like to work on this issue

@nihal467
Copy link
Member Author

nihal467 commented Nov 15, 2023

@kshitijv256 you already have a issue assigned to yourself, i would recommend post fixing that, only assign yourself with another issue

@rithviknishad rithviknishad moved this from Triage to Up Next in Care Nov 15, 2023
Copy link

Hi, @gigincg, @nihal467, @khavinshankar, @mathew-alex, @aparnacoronasafe, This issue has been automatically marked as stale because it has not had any recent activity.

@github-actions github-actions bot added the stale label Nov 30, 2023
@Ashesh3
Copy link
Member

Ashesh3 commented Dec 26, 2023

I would like to work on this issue

Hey, do you still want to take this up?

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

Successfully merging a pull request may close this issue.

3 participants