I have big hopes that they tell me it's already feasible while calling me stupid 🤞
If so, it's a big win. The experience will be better than with previous form control 😎

In this context, the parent form is an angular object, not the native element.

They added support for the controlValueAccessor for retro compatibility and it allows to transmit the value. But the error management is different ; NG _VALIDATE provider which was allowing to add custom validators (or transmit the CE validity) isn't supported no more. Parent form has full control!

You could cite also #angular that have its reactive form, soon re-written with signals.
Another thing that makes the "control" idea feel wrong is the a11y handling. Implementing it correctly and it feels more obvious that the form fields should be given the validation logic.

But I was disappointed to not be able to use light-dark() as it doesn't have the support we need and I didn't find a satisfying fallback behaviour for progressive enhancement 🥲

You would be pleased to learn that I was in the process of refactoring our code as suggested in the blog post 😌
That was funny!

I thought that Justin Fagnani started working on a Lit lab mixin for form control but I did not manage to find it again.

I got it messy at first too. But the better I understood it the cleaner it got.
If you didn't find it already, this fine article from @stuffbreaker.bsky.social should help you
dev.to/stuffbreaker...

La mise en place un design system, c'est la partie la plus intéressante mais pas la plus pénible, ni d'ailleurs la plus importante.

I still need a ticket about that to clarify it in the documentation. I expect the user to wrap the button with an `all: unset` anchor tag.
I consider that link and routing is a project concern with a possible SEO/SSR complication that is too hard for a DS to universally tackle.

The problem

It might rather be a lit.dev issue… I will let you know when I discover that the issue is sitting on my chair 😄

I tried them a bit to do some responsiveness at the component level but ended up removing them. It felt off because it was perceived as non predictable.
I think I would rather use style queries expecting the users to control the behaviour from their styles.

Also, I would love the experimental Navigation API to be embedded 😎

I see it as a very useful to build API to control from the outside shadow DOM styles with media queries without needing JavaScript.

CSS container style queries would be really nice to see shipped on Firefox ! It's the only one not supporting the CSS properties part.

Ce n'est rien. Au plaisir de re-échanger une future fois sur les webco 😌

If we count me and a few of the devs of my company it adds something like 200 people 😇