Be more explicit when defining the elements that are tabs.

Hello,

We're working on a site for a client that has a small featurette on the homepage that we want to use quicktabs for. There are basically three views feeding in content, and associated tabs to toggle that content into view, however the tabs call for more than simply text entry. That issue, in and of itself, is not what I want to propose here, because, through the use of hooks, we are able to render anything we want within our tab.

However, that's where the issue comes into play. Say the tabs exist, we're injecting some basic content into them, but we want to offer the users a link that doesn't make use of the tab, but is supposed to direct users to a new page. The current quicktabs setup is too generic when it comes to defining what a 'tab' is in terms of html... basically, any <a> element that is a descendant of the tab <li> is counted as a new index, thus, three tabs quickly becomes six when additional markup is injected into the tab. We still want users to be able to use the tab portion of the quicktabs, but there are other interface elements we want to mix in.

The solution is relatively simple and I have a proposed patch forthcoming.

Thanks!
-Kai