Skip to content
Component infrastructure and Material Design components for Angular
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci build: add job to run tests with ivy May 15, 2019
.github chore: update github issue templates; add docs/troubleshooting (#16077) May 22, 2019
.vscode chore: disable vscode autoformat settings (#15406) Mar 7, 2019
e2e build: update bazel nodejs rules to v0.29.0 (#16063) May 20, 2019
guides chore: update "material2" to "components" (#15905) Apr 25, 2019
scripts build: add job to run tests with ivy May 15, 2019
src build: fill in missing MATERIAL_EXPERIMENTAL_PACKAGES (#16113) May 24, 2019
test build: source maps for some dependencies not exposed during unit tests ( May 24, 2019
tools build: no longer use deprecated api in sass_bundle rule (#16064) May 20, 2019
.bazelignore build: update to Angular 7.0.1 http_archive & @angular/bazel package (#… Oct 29, 2018
.bazelrc build: publish docs-content bazel artifacts (#14634) Jan 16, 2019
.clang-format chore: add `yarn format` command and pre-commit hook to ensure code i… Feb 9, 2019
.editorconfig chore: add editorconfig (#16042) May 18, 2019
.firebaserc feat(table): support sticky headers, footers, and columns (#11483) Jun 7, 2018
.gitignore build: remove example-module from gitignore May 16, 2019
BUILD.bazel build: test cdk with bazel (#13575) Oct 15, 2018
CHANGELOG.md chore: bump version to 8.0.0-rc.2 w/ changelog (#16116) May 24, 2019
CODE_REVIEWS.md build: restructure demo-app in favor of bazel (#13965) Nov 15, 2018
CODING_STANDARDS.md chore: remove noRxjsPatchImportsRule (#10765) Apr 10, 2018
CONTRIBUTING.md chore: update "material2" to "components" (#15905) Apr 25, 2019
DEV_ENVIRONMENT.md chore: update "material2" to "components" (#15905) Apr 25, 2019
LICENSE chore: bump year (#14688) Jan 3, 2019
README.md chore: update "material2" to "components" (#15905) Apr 25, 2019
WORKSPACE build: update bazel nodejs rules to v0.29.0 (#16063) May 20, 2019
angular-tsconfig.json chore(e2e): re-enable e2e tests for some components (#15615) Mar 26, 2019
build-config.js prototype(checkbox): create prototype checkbox based on MDC Web (#15782) Apr 16, 2019
firebase.json build: fix dev-app deployment to firebase (#14529) Dec 18, 2018
gulpfile.js build: throw when running build tasks inside of a directory with spac… Nov 14, 2018
package.json chore: bump version to 8.0.0-rc.2 w/ changelog (#16116) May 24, 2019
packages.bzl build: fill in missing MATERIAL_EXPERIMENTAL_PACKAGES (#16113) May 24, 2019
stylelint-config.json prototype(checkbox): create prototype checkbox based on MDC Web (#15782) Apr 16, 2019
tsconfig.json build: fix tslint being unable to type check cross-package references May 23, 2019
tslint.json build: add linting for class member naming (#15812) May 13, 2019
yarn.lock chore: bump to Angular 8.0.0-rc.5 (#16106) May 24, 2019

README.md

Components and Material Design for Angular

npm version Build status Gitter

This is the home for the Angular team's UI components built for and with Angular. These include Material Design components and the Angular Component Development Kit (CDK).

Quick links

Documentation, demos, and guides | Google group | Contributing | StackBlitz Template

Getting started

See our Getting Started Guide if you're building your first project with Angular Material.

Check out our directory of design documents for more insight into our process.

If you'd like to contribute, you must follow our contributing guidelines. You can look through the GitHub issues (which should be up-to-date on who is working on which features and which pieces are blocked) and make a comment.

Please see our help wanted label for a list of issues where we could use help from the community.

High level stuff planned for Q1 → Q2 2019 (January - June):

  • Most of the Angular Components team is on loan to the framework team helping with Ivy. We've been using the Angular CDK and Angular Material tests to validate code paths as well as helping debug issues in switching Google applications to the new rendering pipeline.
  • We're also working with the Material Design team on a strategy to collaborate more deeply. We'll have more to share on this once our plans are further along.
  • Assorted bugfixes and minor feature improvements.
  • Design for API enhancements to the tree component to improve ergonomics.

Available features

Feature Notes Docs
autocomplete Docs
badge Docs
bottom-sheet Docs
button Docs
button-toggle Docs
cards Docs
checkbox Docs
chips Docs
data-table Docs
datepicker Docs
dialog Docs
divider Docs
drag-drop Docs
expansion-panel Docs
grid-list Docs
icon Docs
input Docs
list Docs
menu Docs
paginator Docs
progress-bar Docs
progress-spinner Docs
radio Docs
ripples Docs
select Docs
sidenav Docs
slide-toggle Docs
slider Docs
snackbar / toast Docs
sort-header Docs
stepper Docs
tabs Docs
textarea Docs
toolbar Docs
tooltip Docs
tree Docs
virtual-scroll Docs
---------------- ------------------------------------------------------ ------------
theming Guide
typography Guide
layout See CDK Layout or @angular/flex-layout -
cdk Docs

The goal of Angular Material and the CDK

Our goal is to build a set of high-quality UI components built with Angular and TypeScript. These include foundational components and services, found in the CDK, and components that follow the Material Design spec. These components serve as an example of how to build Angular UI components that follow best practices.

What do we mean by "high-quality"?

  • Internationalized and accessible so that all users can use them.
  • Straightforward APIs that don't confuse developers.
  • Behave as expected across a wide variety of use-cases without bugs.
  • Behavior is well-tested with both unit and integration tests.
  • Customizable within the bounds of the Material Design specification.
  • Performance cost is minimized.
  • Code is clean and well-documented to serve as an example for Angular developers.

Browser and screen reader support

Angular Material supports the most recent two versions of all major browsers: Chrome (including Android), Firefox, Safari (including iOS), and IE11 / Edge.

We aim for great user experience with the following screen readers:

  • Windows: NVDA and JAWS with IE11 / FF / Chrome.
  • macOS: VoiceOver with Safari / Chrome.
  • iOS: VoiceOver with Safari
  • Android: Android Accessibility Suite (formerly TalkBack) with Chrome.
  • Chrome OS: ChromeVox with Chrome.
You can’t perform that action at this time.