{"id":6768,"date":"2016-08-10T14:19:05","date_gmt":"2016-08-10T14:19:05","guid":{"rendered":"http:\/\/www.worldflow.net\/?p=6768"},"modified":"2016-08-10T14:19:05","modified_gmt":"2016-08-10T14:19:05","slug":"safari-new-ie","status":"publish","type":"post","link":"https:\/\/betaworldflownet.local\/safari-new-ie\/","title":{"rendered":"Safari is the new IE\u2026."},"content":{"rendered":"

\"images-9\"<\/a><\/p>\n

It hurts me to complain about an Apple product, as I use my Mac \/ iPad \/ iPhone everyday, and they are the tools on which I run my business, and often my life.<\/p>\n

However, it has got the stage now that as a development shop we struggle to manage the mess that is Safari.<\/p>\n

Back in the day, we built a Research system, that was developed in the Internet Explorer 7 era, where IE7 was just so off the wall, and the client only used IE7 internally. IE7 had to be specially coded for all the time. The system we developed ended up with a full 1\/3 of the code being IE7 specific code.<\/p>\n

Now we have moved on, and IE11 is good and solid, Chrome just works, Firefox has issues that can be overcome, but Safari is now a developers\u2019 nightmare. And I see this consistently in what we build and indeed what I use on the Web.<\/p>\n

Safari on the Mac and iPad has a number of unforgiving issues, in addition to the very slow response times compared to Chrome.<\/p>\n

It has some great features too. The tabbing works well, sync between my platforms is very good, Keychain is a major benefit. Still I end up moving regularly, and soon may move fully to Chrome.<\/p>\n

Simple examples that cause me obscure problems, and force me into Chrome daily now:<\/p>\n