upset: unset;

If CSS were D&D, baseline’s alignment would be chaotic.

New blog post: “Fixing Baselines”. https://blog.kizu.dev/fixing-baselines/ Do you know how to center things in CSS? In year 2025? Easy! You just… align… or justify…, ok, maybe just place? your content… or items? …Forget it, this post is not about alignment. Or is it? This post is about […]

Finishing up a quick-ish blog post, in which I will share a technique that I have used for, like, 12 years, which I never shared before, and did not see many people talk about.

New blog post: “Box-Decoration-Break”. https://blog.kizu.dev/box-decoration-break/ In the last few days, coincidentally, I saw two cases where the obscure `box-decoration-break` #css property could help. This might be a good sign that it is worth it to remind everyone about its existence!

New blog post: “Zombie Styles” https://blog.kizu.dev/zombie-styles/ This is a short post about one thing I encounter a lot with #css but never saw explicitly defined for easy reference.

XSLT, but it is all custom elements like `<xsl-template>` etc.

New blog post: “Renaming Outer Variables in CSS Functions” https://blog.kizu.dev/renaming-outer-variables-in-functions/ In which I continue a series of posts about my initial experiments with custom #css functions. This one is about a not very useful (but fun) nuance about their arguments.

Random thought: maybe for any complex selectors the specificity should've been “scoped” per part. Example: `#foo > *` vs `.bar` matching on the same element: in most cases `> *` would define some _default_ styles, while the `.bar` should be more specific, etc.

New blog post: “Inline Custom Identifiers” https://blog.kizu.dev/inline-custom-identifiers/ This is a quick post about a pattern that I use more and more: a way to connect elements that require named custom or dashed identifiers for various #css features.

New blog post: “Photo Walk in March” https://blog.kizu.dev/walk-march-2025/ Well… It is November, but I am sharing photos from my walk from this March. I already published them on my Pixelfed account almost right after taking them, but I really want to continue posting them here as well.

Didn't plan it this way, but nothing much scarier than talking about getting a job in tech these days 😱 Check out my full convo with @nerdy.dev about his recent experience looking for a new job: 📺 www.youtube.com/watch?v=JLdh... 🎙️ zencastr.com/z/KHLM-Zlu

New blog post: “November, Again” https://blog.kizu.dev/november-again/ For the third time, I am attempting to write a blog post for every day of November. I managed to do it for 2023 and 2024. I won’t promise I’ll manage to post every day this time, but I’ll try. #nablopomo

I am happy that for simple codepens for anchor positioning I no longer need to switch to Chrome and can do them in my Firefox Nightly.

Gecko: Intent to Ship: Scoped Styles (@scope)

Planning to post in my blog every day of this November. As, surely, if I am already burnt out, doing so won't change anything for it, but I'll get thirty sparkling posts as the result in the end, right? RIght?..

Blink: Intent to Ship: CSS anchor positioning with transforms

`display: gritty`

Slowly starting to think about self-hosting various personal stuff like music streaming, file storage, etc. Have no idea what to do, so will need to research a bunch, but pretty sure that's the right direction to go regardless.

`:is()` is nice.

Thinking about intrinsic sizes and calculations.

Blink: Intent to Prototype: The inherit() CSS function

I want to speak with someone about how cascade layers do not work with a component-based approach if we aim to import them in an arbitrary order, with those components depending on each other in some way. It seems that, with the way cascade layers work, every component that depends on two or […]

New blog post: “Fit-to-Width Status Update: Prototype and Issues” https://blog.kizu.dev/text-fit-update/ In which I present the current state of things and share links and descriptions of issues I opened in the CSS Working Group’s GitHub following the Chrome team’s feedback. #accessibility […]

I wish you could do `<template shadowrootmode="open" slot="foo">`

Started playing “Against the Storm” this weekend, and it was mistake: it is too addicting :blobcatmelt:

Pixel art, but all colors in the palette are out-of-gamut and are <del>clipped</del> gamut-mapped to the best of your display's ability.

The older I get, the more ideas I come up with and collect, and the fewer spoons I have available at any given time. Surely, these 5 game ideas from 15 years ago will one day materialize into something :blobcatreading:

A Small Beach A photo from a walk on 15 June, 2024. 📷 OM-D E-M5 & 45 mm ƒ1.8, shot at ƒ7.1.

Once again, a project to which I wanted to maybe contribute some CSS/design, but which uses tailwind, so I'm out before starting anything. Good part: checking the source code before actually trying to do anything just to check if the code is contributable.

A bench. A photo from a walk on 15 June, 2024. 📷 OM-D E-M5 & 45 mm ƒ1.8, shot at ƒ8.

A pine. A photo from a walk on 15 June, 2024. 📷 OM-D E-M5 & 45 mm ƒ1.8, shot at ƒ8.

Hills, Goats, Ocean. A photo from a walk on 15 June, 2024. 📷 OM-D E-M5 & 45 mm ƒ1.8, shot at ƒ8.

Random landscape from around A Coruña. A photo from a walk on 15 June, 2024. 📷 OM-D E-M5 & 45 mm ƒ1.8, shot at ƒ5.6.

That feeling when publishing 45 photos, where you write descriptions and alts for all of them, alongside editing and optimizing for publishing, haha, oof. :blobcatfearful: Anyways! I just published photos I took a bit more than a year ago in A Coruña, during our #CssWg F2F outing […]

gradient.style has finally - come out of beta - offers multiple background editing - is open source 🎉 https://nerdy.dev/gradient.style-is-out-of-beta

I'll declare a holiday when WebKit rewrites their fragmentation layout engine. I wanted the block-level multicol overflow since 100 years ago, alongside many other things that improved fragmentation can bring, like the `box-decoration-break: clone` for columns etc etc etc :blobcatsadreach:

Once `reading-flow` is in all browsers, it would be interesting to look deeper into the `order` property and what we could do with it without the current drawbacks. For example, with it and `sibling-index()` we could achieve the “insert at an arbitrary index” use case: first, assign the `order […]

You give me custom functions in CSS — I am starting to think about callback arguments (including for regular properties), arrow functions, IIFE, polymorphism, recursion, and more. Unlikely we will get any of this lol, but I'll never stop dreaming big.

Would you rather write one longhand-sized shorthand or 100 shorthand-sized longhands?

Was thinking about masonry, and ended up wanting CSS Regions once again, as it goes.

A thought: it should be possible to use CSS mixins inside CSS functions, as you could want a mixin to return multiple custom properties that you could then use for some calculation inside a function.

That feeling when

Recently followed @outofprintarchive, and now my favorite thing is to look at some of those wacky print layouts of old game magazines and think through how you could replicate them with #css. I wish designers took more inspiration from print today — this is one of the things we lost as more and […]

There is currently a hot topic in WHATWG issues about how we can introduce a better, more flexible way to associate things. I am not yet sure about what could be the best solution there, but I thought about one thing that we could want to do alongside regardless of the chosen method (and maybe […]

Everyone needs more fragmentainers in their lives.

Playing with floats, found two bugs.

Opened a new CSSWG issue with a proposal for `container-var()`: https://github.com/w3c/csswg-drafts/issues/12604 — an ability to get values of custom properties from named containers. Mentioned in the issue: - article by Zell Liew - Issue about `inherit()` function by @leaverou - Issue about […]

It should be possible to combine multiple #css layouts on the same element. Define multiple grids on an element, and then reconcile their definitions. Define a grid area, and then say that this area is another grid, or a flex container, or a multicol content. And so on, and so on. All without […]

Do want: Web Preferences API, AND browsers with it telling me if some page is using any of the corresponding media queries. Like, if I choose to prefer reduced motion, then I want to know that page contained some motion that I'd want to re-enable to opt-in. Same with reduced transparency […]