-
Notifications
You must be signed in to change notification settings - Fork 344
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
Navigation menubar example: Clicking menu item scrolls page to top in Chrome #1307
Comments
The "scroll to top" sounds like a missing event.preventDefault() on a repurposed anchor element. |
I was able to replicate the "scroll to top" behavior and provide a fix. |
No. Thanks for fixing! I tried it - the problem is solved |
) Issue #1307 reported 2 problems with the navigation menubar example. This commit resolves the scroll to top issue by preventing menuitem anchor elements from jumping to href="#" (i.e. top of page in Chrome) if they have a menu/submenu. Co-authored-by: Matt King <a11yThinker@Gmail.com>
Navigation menubar: Fix scroll-to-top problem for issue 1307 (pull #1308) Issue #1307 reported 2 problems with the navigation menubar example. This commit resolves the scroll to top issue by preventing menuitem anchor elements from jumping to href="#" (i.e. top of page in Chrome) if they have a menu/submenu. Co-authored-by: Matt King <a11yThinker@Gmail.com>
@mcking65 I reviewed the issue and we can close it. |
@a11ydoer
|
Finally, I got an Android phone, Version Android 9, to test the reported problem. Navigation Menubar Test URL since this was merged to Master branch. |
@a11ydoer I believe this issue was fixed along time ago, I don't see the reported behavior in the current example. |
When I click on a main menu item in Chrome, the page is scrolled to the top of the page. Depending on the display size of my device, the menu is no longer visible.
With Chrome on mobile device (Android) there is also the problem that after clicking on a menu item the font size of the menu items changes (they get much bigger).
Both problems do not occur with Safari, IE, Firefox.
Unfortunately I have not been able to find out the cause of the problems.
The text was updated successfully, but these errors were encountered: