Yann 🇫🇷🇺🇦

Plus qu'une semaine pour soumettre ton talk à Sunny Tech !

Tu as une idée de sujet qui te passionne ? Un retour d'expérience à partager ? Une techno que tu veux faire découvrir ? C'est le moment de te lancer

📆 Clôture : 1er mars
👉️ sunny-tech.io/cfp

#SunnyTech #CFP

Yes, easy to get the number up when you pay for overpriced US stuff. Did you see where it got? Do we look safer now as Europeans?

The Epstein Files and Russiagate are the Same Thing For years the culture war has assigned these scandals to opposite teams.

hegemon.substack.com/p/the-epstei...

🦕 Dinosaurs are cool anyway 🦖

The idea is to create one or several custom elements that you can share to use in html. Not necessarily a full app, nor with SDOM. SDOM gives you control as an editor to future evolution. Not using it gives control to the user to make customisation at the risk of your styles conflicting with theirs.

🙌 Today I made my first custom element with manual slot assignment with the help of this article by @knowler.dev. Thanks!

knowler.dev/blog/an-intr...

👀 github.com/orgs/angular...

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!

Hey #WebComponents enthousiasts and #Angular users ! The release of angular 21 with experimental signal Form is close.
I wasn't able to make custom elements work directly with it, so I created this issue.
Could you help me with your feedback ? A thumb up ?

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.

European Tech Alternatives 🇪🇺 · Matthias Ott Matthias Ott is an independent user experience designer and web design engineer from Stuttgart, Germany. He also teaches Interface Prototyping at the Muthesius Academy of Fine Arts and Design.

✍️ New post: Euro­pean Tech Alternatives 🇪🇺

#blogtober #tech #software #europe
matthiasott.com/notes/europe...

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.

Custom Forms with Web Components and "ElementInternals" The ElementInternals API allows us to create form-associated custom elements which we can use to make our own supercharged form fields.

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...

What gif pops up when you type your name?
Third match, but it aligns better with the current state of my vacations 🤪

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.

We ran a randomized controlled trial to see how much AI coding tools speed up experienced open-source developers.

The results surprised us: Developers thought they were 20% faster with AI tools, but they were actually 19% slower when they had access to AI than when they didn't.

two men are standing next to each other in a park . one of the men is wearing a baseball jersey . ALT: two men are standing next to each other in a park . one of the men is wearing a baseball jersey .

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 think I found a bug with WebKit not blocking the click event inside shadow DOM

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 😇