What happens if you leave the protocol (http:// or https://) off email links completely? It’s complicated
Outlook does the right thing sometimes, while everyone else is wrong. Crazy, I know! →
Never, ever (ever) use the HTML 3.2 ˂center˃ tag in emails
I know what you’re gonna say: you never use that tag and/or you never heard of it! But a search of my Inbox (and Spam folder) shows examples every single day. →
No, Marketo tracked links are not “invalid HTML”
It’s Marketo vs. a venerable ISP with an ancient-seeming webmail UI. Don’t trust either party’s word — trust the HTML standard. →
Don’t (yes, *don’t!*) worry about “garbled” characters when opening JS files directly in your browser
Being paranoid about encoding helps avoid uncomfortable post-mortems. But here’s one type of apparent encoding bug that’s actually a false alarm. →
Sure, multiple query params with the same name are allowed, and Auto-Fill acts accordingly... but what does “accordingly” mean?
A subtle mistake in a link sent to 100,000 people was about to wreak havoc on attribution. Here’s how we avoided that with an emergency JS intervention. →
So You Think You Can Unicode, Quiz #2
> Update 2022-03-18: The prize goes to Shivam, who DM’d me the correct answer: 31 bytes. I’ll explain in the next post! Another encoding-related quiz, →
Sure, spaces in an ˂a href˃ or ˂img src˃ make it invalid — but “invalid” doesn’t mean what you think it means!
Retracing how a web standard got rumor-milled into incorrect, anxiety-producing conventional wisdom. →
Transforming a Marketo ˂select˃ into a so-called “image dropdown” using ddSlick
Non-standard form elements add visual panache. But familiarity, accessibility and (especially) mobility remain concerns, so tread carefully. →