- From: Dimitri Glazkov <dimitri.glazkov@gmail.com>
- Date: Mon, 3 Oct 2005 13:20:51 -0500
- To: Andrew Fedoniouk <news@terrainformatica.com>
- Cc: Daniel Glazman <daniel.glazman@disruptive-innovations.com>, W3C CSS <www-style@w3.org>
On 10/3/05, Andrew Fedoniouk <news@terrainformatica.com> wrote: > > ----- Original Message ----- > From: "Daniel Glazman" <daniel.glazman@disruptive-innovations.com> > > > > Dimitri Glazkov wrote: > > > >> There is not question they are both lists. However, the <select> list > >> has inherent input semantics that are not present in a <ul>|<ol>. > > > > No, it has no "input semantics". It has a different input behavior, while > > a <ul> has no input behavior by default. > > > > Agree. Hmm... Maybe I didn't say it right, but what I meant is that "select" communicates to the UA what are expected input choices are for a given POST or GET query parameter. That's not something ordinary lists can do. Is this what you mean by input behavior? I would think that term should refer to how the actual UI element works in the browser. :DG<
Received on Monday, 3 October 2005 18:20:54 UTC