-
-
Notifications
You must be signed in to change notification settings - Fork 836
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
Search bar issue when u open search bar in mobile its not responsive #1495
Labels
💻 aspect: code
Concerns the software code in the repository
bug
Something isn't working
🛠 goal: fix
Bug fix
🏁 status: ready for dev
Ready for work
Comments
RanaZaeem0
added
bug
Something isn't working
💻 aspect: code
Concerns the software code in the repository
🚦status: awaiting triage
Has not been triaged & therefore, not ready for work
🛠 goal: fix
Bug fix
labels
Jun 8, 2024
To reduce notifications, issues are locked. Your issue will be unlocked when we add the label |
priyankarpal
added
🏁 status: ready for dev
Ready for work
and removed
🚦status: awaiting triage
Has not been triaged & therefore, not ready for work
labels
Jun 8, 2024
assigned |
thank you i alredy started working |
ok |
priyankarpal
pushed a commit
that referenced
this issue
Jun 11, 2024
hi by adding some css properties the search filter is became responsive on all device Signed-off-by: Rana Zaeem <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
💻 aspect: code
Concerns the software code in the repository
bug
Something isn't working
🛠 goal: fix
Bug fix
🏁 status: ready for dev
Ready for work
Descrcibe the bug?
when the user try to input any detail in mobile is not responsive
Steps to reproduce the bug?
Expected behavior
with the help of tailwind css we can solved this issue
Desktop (Please provide your system information)
chrome
Mobile (Please provide your device information)
mobile pixel 1
Screenshot / Screenshare
Relevant log output
No response
Record
Code of Conduct
The text was updated successfully, but these errors were encountered: