Closed
Bug 1566327
Opened 6 years ago
Closed 5 years ago
Mobile navigation experience is poor
Categories
(developer.mozilla.org Graveyard :: General, defect, P1)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: info, Assigned: espressive)
References
Details
(Keywords: in-triage, Whiteboard: [specification][type:bug])
What did you do?
I'm trying out the beta version of the MDN web docs, which has apparently been rebuilt with React. It seems like the mobile experience hasn't had much attention. Here's just things I noticed about the navigation experience which doesn't work well on my phone.
What happened?
- The yellow beta corner is obstructing the beta intro text and URL
- Pressing the navigation link text actually goes to that page. You have to press on the triangle, which has a tiny hit area, to open up the sub items.
- No space between the logo and search input in the header
- The sign in text link also has a very small hit area
- When you're signed in, the user menu is a small Mozilla (dino?) Logo. I would not have expected this to be a user menu at all.
What should have happened?
- The yellow corner shouldn't cover text. Also consider not using the full URL as the link's text, because it's a lot for screenreader users to listen to.
- The hit area on interactive elements should be at least a fingertip size on mobile.
- Space between elements could be reviewed throughout.
- Change the dino image to a user profile image or something else more intuitive.
Is there anything else we should know?
| Assignee | ||
Updated•6 years ago
|
Assignee: nobody → schalk.neethling.bugs
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Comment 2•5 years ago
|
||
MDN Web Docs' bug reporting has now moved to GitHub. From now on, please file content bugs at https://github.com/mdn/sprints/issues/ and platform bugs at https://github.com/mdn/kuma/issues/.
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
Updated•5 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•