That is not quite the same problem. Modern browsers are vastly more standards-compliant than they were in the IE era, and most CSS/JS works across Chrome, Firefox and Safari without browser-specific hacks.

There was a time when we routinely did browser sniffing, maintained IE-specific code paths, used vendor prefixes everywhere, and sometimes shipped completely different fixes depending on the browser. That largely disappeared as browsers converged on standards.

Chrome-first development can still cause bugs elsewhere, but that's usually a "testing/implementation problem" rather than the same compatibility mess we had back then.