关于Angular及Angular Dart组件适配2018版Material Design的疑问

Great question—let’s break this down clearly to address all your points:

Angular Web Components & 2018 MDC #

Angular’s web-based Material components do fully align with the 2018 Material Design Components (MDC) system, not just iterate on older versions. The team intentionally adopted the MDC foundations and adapters architecture you mentioned:

• Foundations handle the core Material Design logic (like animation timing, state management)
• Adapters bridge that logic to Angular’s component system
  This setup lets them directly sync with updates to the native web MDC library, ensuring they stay current with modern Material Design specs.

Angular Dart Components & MDC 2018 Updates #

You’re not missing anything here—Angular Dart components have not been updated to support the 2018 MDC system, and there’s no public roadmap indicating this will happen soon. The main reasons boil down to:

• Resource priorities: The Angular Dart team focuses on core framework functionality and integration with the Dart ecosystem, rather than full MDC 2018 migration (which would require a full rewrite of many components)
• Independent implementation: Unlike the web version, Angular Dart’s Material components were built from scratch without tying into the native MDC library, making updates to new MDC specs much more labor-intensive.

Does the Angular Dart Team Use Foundations/Adapters? #

No, currently the Angular Dart component library does not use the MDC foundations and adapters pattern. Its components are implemented independently, which means they can’t leverage the pre-built logic from the native MDC library. This is a key reason it hasn’t kept up with the 2018 MDC updates.

内容的提问来源于stack exchange，提问作者Mina Atef