If Chrome’s your default browser then you’re fine. Albeit, you’re running Chrome on a Mac which isn’t fine at all if you value speed and power efficiency above Chrome’s incredible, multi-platform extensibility.

Actual Safari window failing with t.co

The exasperating 4-month-old bug appears to have been introduced with the general release of OS X El Capitan on September 30th of last year. It seems limited to HTTPS links that have been contracted by Twitter’s link shortening service t.co. The issue’s been roundly discussed on Twitter and Apple’s own forums with several people — not Apple — posting what they claim are fixes.

Making Chrome my default browser until Apple fixes Safari’s stupid https://t.co/bEKIq9M3TK issue — Cool Brand Luke (@jephjacques) January 20, 2016

Apple is apparently aware of the issue and a fix has been identified. This, according to Timothy Hatcher, WebKit Developer Experience Manager at Apple, who noted that the issue "is lower level than Webkit," the engine that powers Safari. When that’ll see a release is unknown.

I’ve tried a few workarounds over the last few months to no avail. This morning I started testing a new "fix" du jour to bypass t.co link shortening. So far, so good, in Tweetbot at least — t.co links in TweetDeck, however, still fail in Safari.

What about you, fellow Safari users?