Vadim Makeev

I have some news for you: 1. There’s a city somewhere along Elba called Pisselberg. 2. Three days and 350 km later, I finally arrived in Hamburg on my bicycle. 3. My bum hurts. Over and out 😵‍💫

Planning next week the longest bikepacking trip so far: around 650 km from Berlin to Hamburg and back in a week. Two-thirds of the way along the Elba with a few ferry crossings. It looks terrifying, but I’m going to be fine, right? 😬

Ordered a book to learn how to cook, but instead, they sent me “Web Accessibility Cookbook” by Manuel Matuzović 🙄

Your browser is not supported! It’s probably lacking some serious API, and we can’t possibly make it work, sorry * * Just kidding. Spoof the UA string, it’ll work just fine. beta.maps.apple.com

Look what just shipped in Firefox Nightly! You can now double-click any element’s tag name, type space, and add any attributes. Once you press the Enter, the attribute will be added to the end of the tag 😎️️️️️️ Just a week later, after I complained about this behavior, thanks to my colleague Nicolas Chevobbe from DevTools. Now waiting for the Safari Web Inspector to join the club 😉

False alarm! This MathML “bug” is more of a “lack of feature” or rather confusing behavior, if you ask me. It seems like both Firefox and Safari’s DevTools won’t let you add attributes just by typing them next to the tag name. Instead, they parse it as a tag name, and since it’s invalid, they discard it. Safari gives a hint: what you type also goes to the closing tag 😬 I learned this behavior in Chrome DevTools and my code editor, and I find it intuitive. Two more bugs to follow: Firefox and Safari.

This season, I’m working on improving MathML documentation on MDN. It’s still a work in progress, but I also found a bug in the browser DevTools. Apparently, you cannot add attributes to MathML elements in the DOM tree in Firefox and Safari. Fortunately, it works in Chrome 🙄 Bugs filed, of course: Firefox, Safari. But I’m not sure if MathML could get high-priority treatment. But I believe in miracles!

Sometimes, it’s more of a parkour than parking, really.

Added a very subtle scroll-driven animation to pepelsbey.dev (Chrome-only for now), like it was supposed to be in the design. But back then, it was too much of an effort to implement. Now, it’s as simple as it could be 🤓

So, I got a second bike. This one is a 100% city bike. It’s very lightweight and simple, but it has a rather aristocratic name: Viktor Schindelhauer 🧐

Plans for June I’m very much looking forward to: 2–5. Web Engines Hackfest, A Coruña 6–7. CSS Day, Amsterdam 8. Tool, Berlin 22. Smashing Pumpkins, Berlin

Look! The popover is available in all major browsers now, starting from this week’s Firefox 125 release 🥹 This includes HTML attributes, CSS pseudo-classes, and JS API. — Firefox 125 release notes — Popover API on MDN

Gave up waiting for the hausmeister to make a proper sign for me. So I found a round font and used a laser printer on vinyl paper, and the result looks better than some of the proper ones 😎

I might have thrown a housewarming party this weekend just to hang this sign. Sorry for the kerning. The guests left only by 22:30, by the way.

My precious bike is back from the workshop. Now, with the 11-speed geared hub (Shimano Alfine + Microshift drop bars) ready to climb hills and carry some weight. Unlike the previous hub, this one is completely silent 😍

Essentials☝️

Tunnels under the U4 Innsbrucker Platz in Berlin. Kudos to @hello_togo_bot for organizing the visit✌️

Did you know that nesting <h1> in the <article>, <aside>, <nav>, or <section> elements decreases its font-size? Well, not anymore in Firefox Nightly. It’s still an experiment for now, but it’s time for the last remaining of the HTML outline to go 👋 — The death of outline — Firefox bug to follow

I don’t want to hear semantics. You anti-semantic bastard!

Got back from a quick trip to Copenhagen 📷