Manuel Strehl 🫏

Jack of all trades. Mostly interested in languages, philosophy, the web, science, helping people, and minimizing my personal Dunning-Kruger effect.

Volunteer firefighter. He/him.

Previously @m_strehl on Twitter.

Homepage: https://manuel-strehl.de
Interested in Unicode?: Codepoints.net (npub1gpm…emmp)
...or form validation?: https://hyperform.js.org
Github Profile: https://github.com/Boldewyn

Last Notes

2025-10-19 10:49:30 UTC

- reply

quick caveat (if you want to use it in your beginners’ series): This diagram is only valid for elements with
direction: ltr;
writing-mode: horizontal-tb;
flex-direction: row;
(or writing-mode: vertical-*; flex-direction: column;)
In the corresponding other cases it must be rotated/mirrored accordingly.
I find that this creates a bit of a mental load to get justify/align right all the times, especially when I switch flex-direction on breakpoints.

2024-12-15 18:08:37 UTC

- reply

funnily, old HTML had this feature for table cells (not-standardized, though, but Chromium-based browsers support it):
<td align=char char=".">

2024-12-15 12:11:37 UTC

- reply

I ticked “nuanced”. The problem is that on face value the collected data is trivial. But given the huge amount of possible data to collect and aggregate we need to factor in the aim of collecting the data.
We implicitly assume that the supermarket is in the business of providing goods for its customers, having the well-being of them at least somewhere in the mind of the deciders.
1/2

2024-12-13 09:40:00 UTC

- reply

yes, that is the reason why I virtually never use <input type=color>. RGB hex is OK for a simple color picker (think “what’s your profile color?”), but in other contexts it fails miserably:
- no transparency support
- no empty value, default is black
- no wide gamut colors
This makes it the wrong tool, when it can be expected that the field will also be filled by professionals with higher requirements.

2024-12-13 09:05:11 UTC

If you allow user input for #CSS colors, e.g. for a CMS theme, how would you validate the input?
In the Olden Days ™️ it was easy:
/#[0-9A-F]{6}$/
But now, a valid CSS color can look like this:
hsl(from var(--custom-color) h s clamp(var(--min-lightness), l, var(--max-lightness)))
(from @npub1st5…78sq’s great post at https://angelika.me/2024/12/01/how-to-clamp-relative-color-lightness/. Go read it!)
I assume we only have two options now, „Write a full CSS parser“ and „forgo validation“?

2024-10-23 09:41:12 UTC

- reply

I’d say @‍layer, because this gives you a single point to re-shuffle layers later. Or put another way, it makes the order of layers explicit.
Using it after the imports has no effect (apart from specifying additional layers that come afterwards).