Roma Komarov / is on Nostr

Inventing weird CSS things.

Frontend engineer working on Datadog's design system.

CSSWG Member (previously: an invited expert).

Ask me about: #CSS, #Frontend, #DesignSystems

Located in France. He/him.

Articles and Experiments: https://kizu.dev
Less polished blog: https://blog.kizu.dev
GitHub: https://github.com/kizu
Current Mood: Sleepy, thinking about a new article to write 🍵:blobcatmelt:

Last Notes

2024-07-21 10:32:10

Do you have any unsolved #CSS problems that you want to be eventually solved?
And what do you think is impossible, and we probably will never get?

2024-06-19 10:16:41

New post: “Custom Properties and CSS-Wide Keywords”.
https://blog.kizu.dev/variables-and-css-wide-keywords/
I did some tests with custom properties in #CSS, and how they work (or don’t) with the CSS-Wide Keywords (`initial`, `inherit`, `unset`, `revert` and `revert-layer`).
As the result, I did create a PR adding a few Web Platform Tests, and opened two bugs in Safari and Firefox.

2024-06-19 10:16:41

2024-05-09 13:42:59

- reply

Think of the JSX ability to pass any callback to a component via a prop — what I want is something like that. If such a script is static, without any server-side interpolations, then I don't see an issue?

2024-05-09 13:42:59

- reply

2024-05-09 13:03:52

Let's say I want to have a web component.
Whenever I use it, I would like to provide a custom callback to run in its context, defining it in HTML.
Is there an idiomatic way to do so? The way I'm thinking of is to use `currentScript`:
<my-element>
<script> document.currentScript.myCallback = () => console.log('Hey!');</script>
</my-element>
And then call this `myCallback` from inside the `connectedCallback`.
Is there anything better (apart from using a unique `id` for this)?

2024-05-09 13:03:52