The Canary version of React has a special component for ViewTransitions. Does it help?
You should know that in-app browser can and do literally inject JavaScript into the websites you visit with them with tracking scripts from the app you’re inside of. And that’s just one thing that sucks about them.
Danila Fedorin’s article about unique UX features in blogs is fun. Here’s some extra thoughts, resources, and opinions.
Having a named block of styles to apply in CSS can be useful, and newfangled Style Queries are pretty close to that. We look at one use case here, how Sass did mixins better, and hope for a native solution.
CSS allows setting different overflow behaviors for x and y directions. It doesn’t actually work with the `hidden` value, but it does with `clip`!
The navigation in this game works with the arrow keys, which is made possible with scroll driven animations, faked collision detection, and maintaining state with CSS custom properties.
Polyfill.io recently served malicious code, redirecting users to inappropriate sites. Subresource Integrity (SRI) can help prevent such issues by verifying script integrity.
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.
Developer 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 through thanks.dev and Open Collective, as well as donates to non-profits like The Last Mile, Annie Canons, and Vets Who Code.
