Sometimes pretty simple HTML elements have a lot of things to consider and take care of, from interactivity, styling, accessibility, and more.
Selecting the *next* element in CSS can be done easily with the + combinator. Selecting the *previous* element used to be impossible, but now can be like :has(+ .el), and can be extended in either direction.
TanStack Router is a comprehensive JavaScript framework for client-side applications, emphasizing type-safe routing and navigation. It includes nested layouts and efficient data loading.
The `clip-path` property with the `inset()` shape makes for some cool design opportunities. Here we’ll expand on some existing ideas, improving them by not requiring any content duplication.
Hydration refers to JavaScript frameworks making server-side rendered HTML interactive.
“TypeScript has a steep learning curve, steeper than JavaScript itself. Understanding both of these at the same time can be overwhelming.”
This guide serves as an introduction to learning JavaScript, covering necessary prerequisite knowledge and addressing common obstacles. It highlights JavaScript’s origins, essential concepts, and practical applications across different environments.
It’s a fun idea to do a full-on March-Madness style-playoff bracket for choosing a coding font. Still a Monolisa guy myself.
There are no obvious CSS properties or values for making a @keyframe animation wait between iterations, or have a pause before starting. But Nils Riedmann cooked up a clever way to do it using linear() animation timing. I think this is cleaner than faking it with multiple benign keyframe steps. Remember linear is not the same as linear(). The later is a function that can take any number of points and thus create any sort of easing.
These custom video (and audio) players are very nice. I like how the accommodate narrow/vertical video players and work with any video provider (even YouTube).
We might be shooting for the stars, but we’re also building on top of the magical media chrome ecosystem of player components, which does a few things for us:
- It uses web components which are compatible across web dev frameworks. Yes, even React (which can be grumpy about web components).
- It allows us to separate the player UI from the player streaming technology, so skins can be used across “players” rather than being player-specific.
Sacha Greif introducing the State of CSS 2024 results:
Let me make a prediction: we’ll look back at 2024 as the turning point between “CSS Classic” and “New CSS”.
That feels intuitively true to me, except we won’t use those names. Check out work done on CSS Levels which define CSS4 and CSS5 “eras” (which kicked off in earnest here). Officials names like this have weight and I hope it’s enough that we’ll actually start keeping these terms up to date and using them.
Check out the full survey results as well. Quick thoughts… Interesting to see Lightning CSS so low, I find it pretty sweet. I agree with the masses, anchor positioning is probably the #1 thing I’d love to see get cross-browser supported and mixins is the #1 feature I’d love to see get fully specced out.
Little boosts of front-end development news, information, and advice — right to your feed reader of choice.
RSSHere's our page on guest writing. It's a win-win-win!
Frontend Masters Donates to open source projects. $363,806 contributed to date.
