W3C home > Mailing lists > Public > www-html@w3.org > June 2005

Re: [XHTML2] exclude switch and case as presentational

From: ACJ <ego@acjs.net>
Date: Sat, 11 Jun 2005 21:22:59 +0200
Message-ID: <42AB3A13.1080608@acjs.net>
To: Laurens Holst <lholst@students.cs.uu.nl>
CC: David Woolley <david@djwhome.demon.co.uk>, www-html-editor@w3.org, www-html@w3.org
Tab, and tabgroup seem more like roles than anything else to me. A 
section or a div (or what ever) could function as a tab, and one could 
define this by adding role="tab". From there one could apply style and 
scripting (presentation and behavior) accordingly.

<musing>
  section[role="tab"] { appearance: tab }
</musing>

My 2cents,

ACJ

Laurens Holst wrote:

>
> David Woolley wrote:
>
>> The XHTML2 Forms module includes switch and case elements, but it is
>> pretty clear from the XFORMS 1 specfication that these are 
>> presentational/
>> hehavioural elements and therefore shouldn't be in a structural 
>> language.
>>
>> The give away that they are presentational is the statement that they
>> are there to control whether or not parts of the document are 
>> *rendered*.
>>  
>>
> What else do you expect when you want to create something with 
> specific behavioral and visual representation (such as the request for 
> tab boxes)?
>
> The alternative is to just script it using Javascript. Not that 
> difficult, and perfect separation of content, behaviour and style.
>
> From experience with an XForms-like language I can say that it’t 
> really hard to avoid having presentational markup, and the best way to 
> do that is to just use presentational elements for the navigation, and 
> have separate documents for the content, which are then included.
>
>
> ~Grauw
>

Received on Saturday, 11 June 2005 19:21:45 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:19:03 UTC