material-components / material-components/material-web
Request for Missing Navigation Components in Material Web
Nobody has claimed this yet.
- Dominant language
- SCSS
- Stars
- 11.3k
- Forks
- 1.1k
- Avg merge
- 20h 28m
- Merged PRs (30d)
- 13
Description
Description
Hello Google Material Web team,
I’m writing to share appreciation for the work you’ve done on the Material Web (Material Design 3 Web Components) library, and to request consideration for several navigation components that are currently missing from the implementation.
The existing components — such as tabs, buttons, text fields, chips, dialogs, and progress indicators — are excellent and make it possible to build clean, modern MD3 interfaces on the web. However, several key navigation components described in the Material Design 3 guidelines are not yet available in the Material Web library.
Specifically, I would like to request the addition of the following components:
- Navigation bar
- Navigation rail
- Navigation drawer
- Top app bar
- Bottom app bar
These components are essential for building complete MD3 applications that follow the recommended navigation patterns. Their absence makes it difficult to fully adopt MD3 in production interfaces, especially for apps that rely on structured, multi-level navigation.
I appreciate the ongoing work on Material Web and understand that the library is still evolving. I hope these navigation components can be prioritized in future updates.
Thank you for your time and for your continued work on Material Web.
Best regards,
Soph
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Begin by comparing the requested navigation bar, rail, drawer, top app bar, and bottom app bar with the library’s current component set and Material Design 3 guidance; done would require an agreed scope and implementation plan for all five components.
Written by the indexing model from the issue text.
Assessment
- Domain
- design, frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100