You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I searched through the existing issues and PRs but did not find any that address the problem with the mobile navbar covering the logo.
What is the current behavior?
Currently, when accessing DripUI on a mobile device, the mobile navbar expands over the website's logo, partially covering it. This obscures the visibility of the logo and affects the site's navigational aesthetics and usability.
Steps to Reproduce
Open the DripUI website on a mobile device or use a web browser's developer tools to simulate a mobile viewport.
Click/tap on the hamburger menu icon to expand the mobile navbar.
Observe that the expanded navbar overlays part of the logo at the top of the page.
What is the expected behavior?
The expected behavior is for the mobile navbar to expand without covering or obscuring the logo. Ideally, the navbar should appear below the logo to ensure the logo remains fully visible and unobstructed.
Environment Details
Browser: This issue was observed on Chrome, indicating it's browser-specific.
The text was updated successfully, but these errors were encountered:
Prior Issues
I searched through the existing issues and PRs but did not find any that address the problem with the mobile navbar covering the logo.
What is the current behavior?
Currently, when accessing DripUI on a mobile device, the mobile navbar expands over the website's logo, partially covering it. This obscures the visibility of the logo and affects the site's navigational aesthetics and usability.
Steps to Reproduce
What is the expected behavior?
The expected behavior is for the mobile navbar to expand without covering or obscuring the logo. Ideally, the navbar should appear below the logo to ensure the logo remains fully visible and unobstructed.
Environment Details
Browser: This issue was observed on Chrome, indicating it's browser-specific.
The text was updated successfully, but these errors were encountered: