🐞Bug: Change in position of navbar elements
Closed this issue · 8 comments
Description
In the navbar when you hover over the signup button you will observer a slight positioning change in the navbar links like home , clubs and other elements. This is affecting the UI experience. Also we instead of adding a border when we hover over the solid color background button we can change the opacity of the color to highlight the active state.
Screenshots
No response
Browser 🥦
Google Chrome
Checklist ✅
- I checked and didn't find similar issue
- I have read the Contributing Guidelines
- I am willing to work on this issue (blank for no).
Hello @dhananjay-Byte, thank you for raising the issue.
Currently, the issue is marked as https://github.com/MilanCommunity/Milan/labels/%F0%9F%91%B7%F0%9F%8F%BB%E2%80%8D%E2%99%82%EF%B8%8F%20status%3A%20awaiting%20triage which means that work for this issue is on hold and we are waiting for the maintainers/owner to review it and provide you with feedback/suggestions to proceed further.
Feel free to reach out to Tamal on Twitter, or drop a mail at tamalcodes@gmail.com if you think that this issue is of critical priority.
Give us a ⭐ to show some support
Happy OpenSource 🚀
Hi can you please show me a demo of what you mean ?
here is the demo:
Intresting, even though the UI was updated. Can you perhaps visit the applications tab > cache storage > clear all the cache ?
There seems to be a problem where the old site is delivered even when the contents were updated.
Even after clearing cache issue is not resolving @tamalCodes
I see, I checked, and looks like this is happening (especially on my screen) when the zoom-in is 100% or more. The issue is where the border is being affected on hover . You can start working on the project.
The CSS property of
border: #e26959 solid 2px;can be changed to the following to fix this issue.
border: #e26959 solid 1px;📑 Checklist in case you missed something
- Local project setup, .env for the frontend.
- Contributing guidelines to be followed.
Please maintain structure, use conventional pull request titles, and avoid spam to avoid closure or bans.
i have solved the issue can i make the PR @tamalCodes
i have solved the issue can i make the PR @tamalCodes
Hi there the assignee has checked on the
I am willing to work on this issue (blank for no). checkbox, so please do not raise PRs for the same.