One thing that I think is abused on the internet the most is target=”_blank”. In my experience, most of the time this attribute is used by developers and designers, is when the client “doesn’t want users to leave their website”. Other times it’s likely down to pure naivety.
I created a little Chrome extension called Blanka to help remedy this.
Well, target=”_blank” abuse makes me rage just like one of my favourite Street Fighter characters, Blanka does in the game. I’ve always wanted to incorporate a Street Fighter character in a project, so it seemed perfect.
Why I made a Chrome extension
There’s a number of reasons why I made a Chrome extension. The main one is that I wanted to test the water for a couple of accessibility tools that I’m thinking of making. The experience of making a Chrome extension was much better than I expected it to be too.
Another reason is that where a link opens should be the user’s and only the user’s choice. Even if we as developers and designers think it may enhance the user’s experience, we’re likely to be wrong. This extension should help users take back control from these decisions.
Sometimes there are exceptions
There is a very small handful of situations where target=”_blank” could possibly be useful such as:
- The user is playing audio or video. Chris Coyier has talked about this in the past
- The user is at the checkout/payment stage of an ecommerce site
- The user is filling out a long form
- The user is adding / editing content which hasn’t been saved
Exceptions like these will likely find their way into Blanka behind configurable flags as I want to keep developing it to be as useful to everybody as possible.
For now though, there’s a decent MVP out there ready to be used.