The time my CSS file decided to take a vacation

I was updating my personal site around 2 AM last Tuesday, and I spent an hour trying to figure out why my header image wouldn't crop right. Turned out I had a missing semicolon in the CSS that was breaking the whole layout for that section. I ended up commenting out half the file line by line until I found it. Has anyone else had a tiny typo eat up way more time than it should have?

2 comments

2 Comments

stone.simon1mo ago

Missing semicolons are like the wild west of debugging, I swear. I once spent a good 45 minutes hunting down a typo where I wrote "display: flex" instead of "display: flex;" on a navbar. It was literally one character - a tiny little bean - that broke the whole menu on mobile. Commenting out line by line is the time-honored ritual we all perform at 2 AM. Your header image probably knew what it was doing, just messing with you for fun.

kelly_miller801mo ago

Honestly, an hour for a missing semicolon? That's not that bad. I've spent whole afternoons chasing stuff like that and just called it part of the job.