Question: material design m3 support

[paulwwisl]

I wonder if material design m3 https://m3.material.io/ support is considered?

Is it correct that currently this project targets m2 https://m2.material.io/ ?

What may work or not work when moving to m3 ?

[paulwwisl]

This depends on https://github.com/material-components/material-web v1 release

[aforemny]

Hi @paulwwisl, thank you for your interest and question.

This library will never support material design m3, unfortunately, as its upstream project material-components-web will not add support for m3.

Google has apparently decided to abandon/ switch to maintenance support on its m2 web library, and start over with a new m3 web library.

While that library material-web certainly has its similarities to material-components-web, I expect it to be significantly different in some regards. For instance, they've added first class support for web components in that library, something which was missing from the m2 library, and which this library used to facilitate the Elm integration.

I am not familiar with material-web at all, but I would expect an Elm integration of that upstream project will be a project on its own, with its own challenges and maybe its own advantages over the integration done here.

As material-web features web components, I personally would go ahead and just use those from within Elm, maybe writing a small wrapper library around the customizing options (attributes, properties).

From what I've learned writing this library, I would expect that to mostly work OK, but would also prepare to expect some potential rough edges around limited Web platform support exposed by Elm, as well as some rough edges in material-web interfacing with a more-than-usual declarative front-end framework.

I would then approach upstream (ie. material-web) with my findings.

But I personally don't have any plans working on a material m3 library for Elm at the current time.