-
-
Notifications
You must be signed in to change notification settings - Fork 41
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
Mobile bottom menu toggle not working well #375
Comments
This WFM (Safari and Firefox on iOS). @flora8984461 What mobile OS and browser are you using? |
@brianking Please find the attached video for reference: open-vsx-toggle-issue.mp4I clicked in bottom toggle, it opens the bottom menu the first time, then cannot be toggled back. Thanks! |
Actually, I just noticed that I need to click outside of the menu to invoke the toggle function of the bottom menu. This is not a big issue anymore, might be a little bit confusing. |
I tried this and I can reproduce it, but doesn't seem like a big deal. @chrisguindon your thoughts? |
@kineticsquid I would argue that the severity level is medium for this. The reason I consider the severity level to be medium rather than low is that we have important links in the footer such as our privacy policy, terms of use, publisher agreement, copyright agent, and legal resources. Many of these links are required in our Eclipse Foundation Hosted Services Privacy and Acceptable Usage Policy: https://www.eclipse.org/org/documents/eclipse-foundation-hosted-services-privacy-and-acceptable-usage-policy.pdf However, I wouldn't consider it to be a critical or high level of severity since these links only become inaccessible after interacting with the main-menu on mobile. There is a workaround which is not to use the main menu but it's not ideal in my opinion. |
This is for the website's mobile view, I tried to click on the bottom nav toggle arrow, it shows the bottom menu the first time, and it cannot take the menu back. And after toggling the top menu, the bottom menu does not work anymore.
The text was updated successfully, but these errors were encountered: