Also, structured serialization/deserialization had been implemented in Chromium for long, since it's what powers e.g. `worker.postMessage()`. Making `structuredClone()` work literally took me less than a day, and this was before I worked at Igalia, so I had to wait hours for a local Chromium build.

This also goes towards people who might need to cross the US border – for example to attend conferences or business meetings, as is common in my line of work; and as is the case for this friend I was mentioning – even if they think they might not be at risk in the parts of the US they are visiting.

Obviously only do this if it's safe for you! In fascistic regimes, or countries moving towards fascism, "antifa" is obviously politically charged, and it might get you discriminated against, or even facing state violence. And your personal safety is more important.

I don't own a Framework, although I *had* been thinking of getting one before all of this came out to the surface. But over the weekend I was hanging out with a friend who does own one, and thinking that if the logo is becoming a fascistic icon, anyone who disagrees should explicitly counteract it.

web standards keep evolving so we need ever more tests; I talked to @littledan.dev, @technosophos.bsky.social, @andreubotella.com & @joyeecheung.bsky.social about processes: standards written in code > written in words. I also touch on the question of funding and who contributes to WPT and how

Stop making the US the center of the world. And maybe we can also make sure it doesn't go back to being the center even after it stops being an authoritarian regime.

It did feel right when I wrote the bio, even though "non-binary" was also in that list then. But feelings on your own gender identity can evolve over time. So it's "Linux person" now.

I do have a "g(r)ay asexual" bit in that same bullet point list, and I'm *not* changing that 😁

#gender #non-binary

This percent syntax was never implemented in other browsers, and it was even removed from Chromium many years ago.

If you want something better, in the CSS Working Group we're working on letting you clamp by a height (`line-clamp: auto; max-height: 300px`), and hopefully will ship soonish in Chrome

The behavior I would have expected would be something like this: 0% means 1 line, 100% means the full number of lines, and everything is evenly spaced.

So clamping by `floor(1 + (percentage / 100) * (numLines - 1))`.

This is the smallest values that trigger clamping by that many lines, on a test with 5 lines. From what I can tell, it behaves like clamping by `max(1, floor((percentage / 100) * (numLines + 1)))` lines.

The `numLines + 1` multiplier means you can clamp by the full number of lines (5 here) with 84%

I thought it could be a way to clamp based on a height, since percentages are used for heights elsewhere in CSS, and so it could be precedent for the work on clamping by height that I'm working on on Chromium.

Nope, it's a percentage of the total number of lines. And the way it works is wonky.