The features Safari has not implemented are generally not dangerous - the clear majority are widely accepted standards. The “Safari is the next IE” argument is well supported by Safari’s many showstopping bugs and the extra workarounds required for developers - it’s not a misunderstanding of Safari’s battle to protect privacy & security. Safari and others can’t simply ignore serious proposals for popular features that Chrome wants to implement. They need to engage and offer alternatives, or the problem will only get worse. It’s not accurate to describe Safari’s approach as protecting the web, and right now it looks more likely that it is making the web worse for everybody.
After analyzing CSS and its weaknesses, and management giving a green light to the refactoring project, it’s time to get to work. A team needs to agree on the internal code standards and best practices, plan out the refactoring strategy, and outline individual tasks. We need to set up a visual regression testing suite, and a maintenance plan to enforce the new standards and best practices in the future.
Open Graph images. Those little images that show up when your site is shared on social media. The ones for my site were… bad. My default was to use one, huge, boring branded image for everything—which provided no extra value and just cluttered up y’alls feeds (sorry!). I wanted to make them better and here’s what I did.