Each pseudo element plays a distinct role in how the view transition animates. The browser does most of the heavy lifting though, which makes it a little hard to see what’s actually happening under the hood.
A single button, but it has two different behaviors in JavaScript depending on how far you’ve scrolled in an element (as determined by CSS!)
A look at what happens when you add a whole list of transforms to an element, and how that interacts with `animation-composition`.
The last part of this series is taking our site that we’ve got in GitHub and addng an Astro build process to it, then mapping a domain we own to the Netlify-hosted site.
It’s pretty straightforward to animate list items into new positions, but there is a few tricks when the specific one you’ve chosen to move needs a *different* transition.
The `satisfies` keyword allows you to assert that a certain value “satisfies” a given type, while preventing a wider type from being inferred.
You’ve got A LOT of control over the design of select menus now, and it can be done as a progressive enhancement.
A little reminder from Matt Smith that getting the last item in an Array is easier now:
const fruits = ["apple", "banana", "cherry"];
/* newer, easier */
console.log(fruits.at(-1));
/* older, harder */
console.log(fruits[fruits.length - 1]);
Code language: JavaScript (javascript)Josh Comeau does a great job with beginner-friendly explanations of important concepts, and Promises From The Ground Up is no exception. In a nutshell, we have Promises because we need callbacks. We need callbacks because JavaScript is single-threaded and can’t wait around for things. And so we dance. These days, you’ll see more async and await, but it’s just what they call “syntactic sugar” over Promises, which is to say, a cleaner way to write the same code.
Will Sentance goes deep into Promises in JavaScript: The Hard Parts when you’re ready.
I know that you can “chain” the CSS property filter, like:
.element {
filter: blur(2px) grayscale(80%) contrast(200%);
}Code language: CSS (css)All three of those filters will apply. But somehow I never thought about applying the same filter more than once. That also works, and they don’t override each other, they “stack” (or whatever you want to call it).
So here’s some useless bar trivia for you. What is blurrier, filter: blur(2px) or filter: blur(1px) blur(1px)? Answer.
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.