Blog

Fixing the potato

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.

Tags

Let’s start using details more

Earlier I wrote about taking a screenshot of an element with JavaScript, SVG and canvas, and how the experience on an iOS PWA was poor. I decided putting the final image in a popover with a share button would be better than that, but there are performance issues to fix first. Originally the image was generated on page load in the background. Looking in the dev tools performance panel the canvas.

DX In 2016 I was given two days off work to watch the livesteam of the ReactEurope conference from Paris. Speaker after speaker kept saying “DX”, and at first I couldn’t figure it out. What was this DX? After a couple of talks I realised it was developer experience, and also noted throughout the two days nobody mentioned UX. This was shocking to me. I’ve been to a handful of web conferences and watched plenty of recordings of talks, and it’s pretty much a given that “UX” will be in every talk.

Building a progressively enhanced todo with modern web standards Recently I need to use a mutation observer and dutifully searched for “mdn mutation observer”. It led to me this blog post, and it had a demo of a regular list with contenteditable. What I neither knew nor expected was that contenteditable on a list means you can add new items by pressing enter. It started me wondering if I could build a decent todo list—like framework devs used to do and boast about it being only 80 megabytes or whatever.