[whatwg] Suggestion: Implementation of Tabbed Forms

Ian Hickson ian at hixie.ch
Wed Aug 11 06:05:29 PDT 2004

On Sat, 3 Jul 2004, Matthew Raymond wrote:
> Lachlan Hunt wrote:
> >   Maybe something like <exclusive> and <mxsection> (Mutually eXclusive
> > section).  I think we actually need two elements: One as a container for all
> > the sections, and another to represent 1 section. eg. in this format (not
> > necessarily with these element names):
> > <mxsection>
> >     <exclusive><label>Exclusive Section 1</label>...</exclusive>
> >     <exclusive><label>Exclusive Section 2</label>...</exclusive>
> > </mxsection>
>    I think the following would be a little bit better:
> <mxsections>
>   <mxsection><label>Exclusive Section 1</label>...</mxsection>
>   <mxsection><label>Exclusive Section 2</label>...</mxsection>
> </mxsections>
>    Each element you had labeled "exclusive" is really a mutually exclusive
> section in and of itself, where as <mxsection> in your example was a section
> that CONTAINED mutually exclusive section.

At the moment the spec says it would be:

       <h1>Exclusive Section 1</h1>
       <h1>Exclusive Section 2</h1>

I don't really like the name "switch", but it is what SVG and XForms have 
and it seems better than the alternatives I've considered (thanks to 
everyone who suggested these, by the way):


The second choice after <switch> is currently <stateset>, but both
seem a bit geeky.

Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

More information about the whatwg mailing list