I spent 6 hours on a CSS animation that broke because of one missing comma

Was working on a ripple effect for a button in my living room in Nashville, and the whole thing just froze on mobile. Turns out I had a trailing comma in the keyframe array that Chrome ignored but Safari choked on. Anyone else find browser quirks that make you want to throw your laptop out the window?

2 comments

2 Comments

lucaslane13d ago

Oh man, Safari is the worst for catching stuff like that.

paul_burns13d ago

Yeah, I've had Safari miss so many trackers on my end too. Last week I counted 47 different scripts running on a news site alone, and uBlock Origin caught most of them but Safari let like 12 slip through. It's kind of wild how Chrome and Firefox at least let you install real extensions that can handle the heavy lifting, but Safari's content blocker system is so limited. Maybe it's just me but I feel like Apple half-ases the privacy stuff on purpose, like they want you to think it's secure without actually giving you the tools to lock it down.