A few days ago there was a lot of chatter about a 'keylogger' built in CSS, but the real problem is thinking that third party content is 'safe'.
Array.isArray works, and how we can use symbols to create our own type-matching functions.
When writing async functions, there are differences between
return await, and picking the right one is important.
createImageBitmap to make SVG render off the main thread.
"HTTP/2 push will solve that" is something I've heard a lot when it comes to page load performance problems, but I didn't know much about it, so I decided to dig in.
HTTP/2 push is more complicated and low-level than I initially thought, but what really caught me off-guard is how inconsistent it is between browsers – I'd assumed it was a done deal & totally ready for production.
There's a proposal for adding a new
<h> element to the HTML spec, but can we solve the problem in a way that benefits the existing web?