I love a side project. A while back I had to figure out how to screenshot a node, and in my most recent side project I’ve got the chance to do some things I knew about but have never used, as well as learning some new things I had never heard of.
Links I found interesting since the last list.
Interesting links I found this week.
Interesting links I found this week.
Interesting links I found this week.
I was working on a page with a link to a document fragment and put an animation on it using the :target pseudo-class. Scrolling back to the anchor and pressing it again skips to the fragment, but the animation does not run again. That’s because it still has the pseudo-class, it doesn’t disappear when scrolling.
In my last post about screenshotting a node with JavaScript I got as far as a fairly low quality image. Since then I’ve figured out how to fix it.
One of my kids wanted a way to record their sports predictions and their notes app system was getting unwieldy, so I built a website for them. It’s on a Netlify subdomain with no search engine indexing as it’s a personal record, not a way to show off how good the predictions are, and they have no interest in monetising it. That means they’d rather not share pages with other fans, but screenshots. If it’s a big event with multiple predictions it extends beyond the viewport, so a regular OS screenshot won’t work.
Usually when I build a navigation it is at the end of the source and a skiplink appears at the top of small viewports linking to it. I then enhance it using CSS and JavaScript so that most devices and browsers get something nicer—an off-canvas interaction perhaps.
The for loop is most commonly used for iterating over an array and performing an action on each item. For example:
