@@ -33,21 +33,11 @@ If you'd like to contribute, please follow our [contributing guidelines][contrib
33
33
our [ ` help wanted ` ] [ help-wanted ] label for a list of issues with good opportunities for
34
34
contribution.
35
35
36
- ## What we're working on now (Q4 2021):
37
- * Continuing to create new, API-compatible versions of the Angular Material components backed by
38
- [ MDC Web] [ ] ([ see @jelbourn 's ng-conf talk] ( https://youtu.be/4EXQKP-Sihw?t=891 ) ). Much of our effort
39
- is dedicated towards rolling out these new versions of the components across Angular apps
40
- inside Google. This work will pay off with the following benefits:
41
- * Dramatically improve consistency with the Material Design spec, which has changed significantly
42
- since Angular Material's 2016 inception. This also makes future versions of Material Design
43
- significantly easier to adopt.
44
- * Introduce a new theming API for component density, a top feature request.
45
- * Fix a number of longstanding accessibility bugs.
46
- * Increase number of people working to continuously improve the components on an ongoing basis
47
- (both the Angular team and the Material Design team).
48
- * Accessibility - we'll be focusing on improving the accessibility of ` MatDatepicker ` as well as
49
- evaluating accessibility bugs for mobile web platforms.
50
-
36
+ ## What we're working on now (Q4 2022):
37
+ * Investigating and fixing reported regressions for the new components launched in v15
38
+ * Creating a new more flexible theming API in collaboration with [ MDC Web] ( https://github.com/material-components/material-components-web/ )
39
+ * Designing and Implementing a CDK combobox component
40
+ * Continuing to focus on improving the accessibility of Angular Material components
51
41
52
42
## About the team
53
43
The Angular Components team is part of the Angular team at Google. The team includes both Google
0 commit comments