Upcoming stuff and outlook

[wuda-io]

Hi guys!

Thank you for all the effort and strong community. I had to do much restructuring in private and am still not quite sure how everything turns out for me. I hope everthing will be ok and also I hope to spend more time again in developing materialize.

I had the following thoughts:

• Move back to pure JS and use JSDoc
• Split into components or directories (already in dev branch, needs new release)
• Pure color / theme change with raw CSS Vars and functions (now it is calculated with a JS dependency)
• anchor positioning is now supported in all major browsers, so we can make use of it in modals, dropdowns, autocomplete, date-time pickers an more!
• docs as READMEs for each component, must not usw MDX or any React stuff

Thats it for now. I look forward for your opinions and that we will find good solutions together.

I wish you all a happy and peaceful time!

[HIRANO-Satoshi]

Just wanted to say thank you, and Merry Christmas to you and everyone involved 🎄

[tinsever]

Merry christmas, well – rather a happy new year tomorrow evening! :) I was using the old materializecss.com and have just seen it's unmaintained and found this in a PR. Sad, that it's not listed first on Google or somewhere. Anyway: Great work thank y'all!

[ginosanterre]

There are many unresolved issues. I'm still using 2.1.1 because of this one: #576

I've been considering switching to another library, but I might wait a bit longer.

[wuda-io]

There are many unresolved issues. I'm still using 2.1.1 because of this one: #576

I've been considering switching to another library, but I might wait a bit longer.

Yes, this is a tricky one. I think it is now much easier to solve with the new anchor positioning CSS features.
I will take a look soon.

[wuda-io]

Ok. The problem with anchor positioning are the names:
As far as I saw, there is no possibility to do this with anchor names,
because when having multiple inputs, it attaches always to the last anchor name used. And i always use the same anchor name in CSS.

Nevertheless, i merged the commits from the open PR and refactored and improved it for most usecases.
It works with CSS only, but the problem is, that it has to use fieldset html elements. So i would suggest to use new semantics here and keep the old input-fields still useable.

I think this is the easiest way, without breaking too much and also adding it as new featue.