W3C home > Mailing lists > Public > www-style@w3.org > April 2009

Re: Tabbed Interfaces in CSS

From: Brad Kemper <brad.kemper@gmail.com>
Date: Mon, 20 Apr 2009 10:31:09 -0700
Cc: Giovanni Campagna <scampa.giovanni@gmail.com>, www-style <www-style@w3.org>
Message-Id: <1C62CCD1-9CB1-4F98-8A98-D2EDEA5F77C0@gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>

On Apr 20, 2009, at 10:19 AM, Tab Atkins Jr. wrote:

> On Mon, Apr 20, 2009 at 12:15 PM, Brad Kemper  
> <brad.kemper@gmail.com> wrote:
>>
>> On Apr 20, 2009, at 9:51 AM, Tab Atkins Jr. wrote:
>>
>>> However, you can only have a
>>> single accordion per page (to be precise, all the accordions will  
>>> act
>>> like one big distributed accordion) and if you try to use a hash- 
>>> link
>>> for anything else on the page it will close the accordion.
>>>
>>> In other words, it suffers from the exact same problems that I
>>> outlined for my pure-CSS tabbed display.
>>
>> With my pure-CSS tabbed display, you could have more than one set  
>> of tabs
>> per page.
>
> Yes, but it suffers from tab display problems.  Unless you can arrange
> your html to alternate tab-card-tab-card (so that a given tab and card
> can both use the same radio element for :checked targeting),

It feels pretty natural to me to have the LABEL surrounding the  
element (like input labels often do), or just inside the element (like  
table captions or fieldset legends), instead of in a separate box. But  
with the "for" attribute of LABEL, it seems like you could have it  
both ways.



> you can't
> style the active tab differently from other tabs.  That's why I mixed
> :checked and :target in my example.
>
> ~TJ
Received on Monday, 20 April 2009 17:31:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 22 May 2012 03:46:58 GMT