material-web VS felte

For example, all the following design systems can be used without tooling (some of them provide ready-to-use bundles, others can be used through import maps): Google's Material Web, Microsoft's Fluent UI, IBM's Carbon, Adobe's Spectrum, Nordhealth's Nord, Shoelace, etc.

Guess there was a 1.0 3 weeks ago: https://github.com/material-components/material-web/discussi...

There is a new “official” one in the works here [1] that uses lots of the “latest and greatest stuff” and should be very fast when it’s finished (later this year). As far as I know it’s set to become the new default company wide implementation of Material on web.

[1] https://github.com/material-components/material-web

I'm using material-web web components inside a form with felte.dev

If you're going for full SSR and don't want to have to worry about JavaScript, I'd just grab the MDC web components library from Google. That's going to be the easiest time you'll have without implementing a front end framework.

Ultimately, I'd like to be able to write reasonably complex client/server web apps in Rust, so the next medium term thing on my list is web components (as a consumer). That'll allow a lot of existing Javascript components to be reused. For example: Microsoft Fast, Material Web Components and UI5.

Material Design (Google)

How does it compare to Felte?

Don’t know if it can help, but I discovered this only recently, which was really missing for me with svelte: https://felte.dev/

I’ve been experimenting with web components in order to build a wrapper for Felte that can easily be used with vanilla JS. One of Felte’s features is the ability to use custom field components that are not based on the browser’s native inputs (input, textarea, select). The example I show is a div with an attribute [contenteditable=“true”]. While testing this experiment I found some weird behaviour coming from Firefox: while I could perfectly click each field and type of it, if I tried to use the form only using the keyboard (tabbing to each field) the focus moved but trying to type would always result in the text being added to the first field I focused.

There’s an example on Felte’s repo setting this up!

Ah. Of course 😅. mwc-textfield is not a native input. Felte relies on native inputs. You can use createField (by creating your own "wrapper" Svelte component that will render your ) or... better yet... you can experiment with what I've been working for the past weeks.

For the past few weeks I’ve taken the (arguably pointless) work of migrating Felte from using Jest to uvu. This is a really tedious work by itself, but one of details that would have made this work even more tedious is that Jest prefers assertions to the style of expect(…).toBe* while uvu gives you freedom to choose any assertion library, although there’s an official uvu/assert module that comes with assertions to the style of assert.is(value, expected).

After more than a year of work, I am proud to announce the release of version 1.0.0 of Felte!