We're working on a UI at work and people want to have the number of tabs in a certain area be flexible width so that in certain situations depending on the title length and the number of tabs, the tab row might end up filling 2 or even 3 lines.
I'm wondering if it's ever ok to have multiple rows of tabs; to me it seems like it breaks the tab metaphor and then you have to worry about tabs changing locations.
At the same time, though, I'm not sure of a good alternative other than a list or accordion.
Answer
It definetly breaks the tab metaphor.
Yahoo's Design Pattern Library explicitly states they should be single-lined:
Present a single-line row of tabs in a horizontal bar under the site branding and header
And there are some pretty nasty examples in a 1999 information architecture company's page.
Another article on using the tab pattern in web applications discourages its use for various reasons:
Multiple rows of tabs are confusing and intimidating, particularly to new users who find it difficult to locate the desired tab. In addition, screen real estate is compromised, and the repositioning of tabs to the front row causes tremendous confusion and complexity.
That said, we have seen it in MS Office... so it shouldn't be that bad, right. Right?
UPDATE: other approaches are: vertical tabs, grouping tabs by categories, or a previous screen with icons.
No comments:
Post a Comment