Material Design Lite

google

Material Design Components in HTML/CSS/JS

Developed by Organization:google

Used languages: HTML(284.72 kB), CSS(266.68 kB), JavaScript(226.32 kB)


Written Sass Less JS
Templates
Documents
Framework design material
Feature type full

Current version

v1.3.0

Last release

Dec 21, 2016

Created at Jan 15, 2015

Last commit

Jun 28, 2017


Open Issues

352

Forks

5,296

Star

30,811

Watchers

1,342



Release Notes on December 21, 2016 for v1.3.0

MDL v1.3 adds some fixes that have been committed since 1.2.1, as well as a new feature.

New: prevent automatic upgrading

@AlexanderOtavka added the ability to disable auto-upgrading! This is useful if you want to manage the component lifecycle yourself, such as if you're integrating with a framework.

In order to do this, register an event listener for the mdl-componentupgrading event. Once you receive an event, you can choose whether or not to cancel it, giving you control on a per-component basis.

Bug fixes and improvements

  • @chajath added an option to disable JS layout switching
  • @MitchLillie improved tab handling to allow more types of links
  • @leocaseiro added the mdl-card--border option to mdl-card__supporting-text(https://github.com/google/material-design-lite/commit/4ee5202c6c934096ad8edfe7eb94fc29f133e42d)
  • @enniel fixed a bug with spinners and some documentation typos
  • @pndewit fixed a bug with vertical alignment in radios
  • @ko22009 fixed several unit tests
  • @hanyuzhou2006 fixed a bug in ripples
  • @Abradoks improved support for older browsers in radios

Thank you to all the contributors, and sorry if I missed anyone above!

MDC-Web and plans for the future

As you may have noticed, an alpha for Material Components for the web (MDC-Web) was recently released.

MDC-Web started life as version 2 of Material Design Lite, but has since evolved into a project of its own, with a broader team and a strong focus on providing a high-quality Material Design implementation for all of the web.

Here are some of the highlights of what you can expect:

  • Modular components, served as independent NPM packages (as well as a large all-in-one meta-package)
  • Manual lifecycle control, with an opt-in auto-init option
  • Stronger focus on progressive enhancement, performance, and accessibility
  • Internals built with low-level architecture to facilitate integration into frameworks
  • Still fully vanilla: no polyfills or frameworks needed

The project is still in its alpha stage, so expect to find a lot of missing components, and to see significant churn as we make changes based on your feedback!

What happens to Material Design Lite?

Material Design Lite (v1) will remain available, with limited support. We don’t have the resources to fully maintain both projects, so we won’t be doing any further development on MDL ourselves.

That said, we’ll do our best to be around to fix critical bugs and accept PRs from the community, as well as release those in new versions. This model has worked well ever since we started the v2 work that eventually resulted in MDC-Web, with new components, new features, and many bugfixes contributed since then.

With this approach, we plan to give developers time to migrate to MDC-Web as the project matures and the community grows.

Full 1.3.0 changelist.

Downloads:

material-design-lite-1.3.0.zip MD5: c6ec30e0470491e58ad2c69aefcbfce9 SHA1: 123dd0c30b2aa03fc37ae8216276547461dd115c SHA256: ce746c6483c357da5642915c38b01b03d124c37565855b6f60b7d87e74228fea

material-design-lite-1.3.0.tar.gz MD5: 18201311fc4c71b581ca717f4ead3992 SHA1: 3aff5e0ec9e31ad1a8e57e9365c7ac113f1d6def SHA256: 4b4ab9845dba0e6a6fda172d69aff6da72c3e429dc1f3d30fa0935d315f40cb6

In this page, you can compare and find Frontend framework for your development in the following categories. Best CSS frameworks to use 2017(based on current maintenance), skeleton framework to start the project immediately, grid support frameworks, material design framework, AngularJS 1 supported frontend framework, Angular 2 supported CSS framework, ReactJs supported frontend framework, metro design framework, etc...

Frameworks can compare based on filesize, currently maintained by contributors, documentation supports and etc...