HTML semantics is a nice idea, but does it really make a difference? There’s a huge gap between HTML spec’s good intentions and what browsers and screen readers are willing to implement.
Hi, my name is
Vadim Makeev
I’m a frontend developer in love with the Web, browsers, bicycles, and podcasting
Here you can find my thoughts on web development, some of my projects, and information about me
Articles 11 in total
View allIf you copy one of my article titles, you’ll probably get “ARTICLE TITLE” in uppercase. Why would I name my article like that? It’s not me, it’s browsers and specs again.
For most developers, HTML is just an artifact, like a binary file, and it often gets wrong and ugly. Fortunately, browsers are smart enough to handle poor markup. But sometimes, they take our mistakes personally, and tags start jumping around.
Remember this old trick that allowed us to load only critical CSS and defer the rest? The one, that used media="print" and onload event. I just realized that sometimes it doesn’t work in Safari.
Recently Sacha Greif challenged his Twitter followers to code a fancy highlighter effect using only CSS. Guess what? I took the bait and started coding!
When building websites on Eleventy, we often have to decide how to deal with the CSS and JavaScript post-processing. Recently I came up with a solution, finally making CSS and JS first-class citizens in Eleventy for me.