Home > Standards > Target the tabs? Please no.

Target the tabs? Please no.

July 2, 2007

In the framework.aspnet newsgroup, there was a question the other day regarding opening windows in tabs with target=”_tab” or something similar.  As far as I know, that’s impossible since tabs are browser-based implementations and not part of the W3C guidelines.

But, the more I think about it, the more of a total nightmare it sound.  We think pop-ups are bad… imagine clicking on a website and 30 tabs opening with all the latest junk you don’t care about.  Yeah, it wouldn’t be opening new windows, it wouldn’t be “in your face,” but it’d sure be annoying!

Also, from a technical standpoint… how would that work on browsers that don’t support tabs?  Would the page just fail?  What kind of hole have we dug ourselves into by creating browsers that continue to do more and more and the W3C not keeping up (or are not being followed)… ?

While most the work I do is in a sterile environment (read: standardized platform, browser, etc), I still fear what this offers for the rest of browsing.  Imagine someone using “tabs” as a menu system… and opening a half-dozen and decorating their page to look up.  How’s that work if your using a browser with tabs on the side?  Etc.

I think we all have enough to deal with—let’s leave tabs alone.🙂

 

Categories: Standards
%d bloggers like this: