[whatwg] [WA1] <sl> - The Selection List element

James Graham jg307 at cam.ac.uk
Thu Jun 2 10:01:25 PDT 2005

Matthew Raymond wrote:

> R.J.Koppes wrote:
>> I don't really see the advantage above using ordinary lists or form 
>> controls
>> and css pseudoclasses like :target ,:focus and :active
>    Let's look at these pseudoclasses one at a time...
>    The :target pseudoclass only applies to an element that has its 
> |id| attribute as part of the URL. If it isn't in the URL, or the URL 
> changes so that the |id| is no longer in the URL, then the styling is 
> not applied.

So your example:
| <sl>
|   <li><a href="#s1">Section 1</a></li>
|   <li><a href="#s2">Section 2</a></li>
|   <li><a href="#s3">Section 3</a></li>
| </sl>

You click a link, the URL changes as required and the section in 
question matches the :target selector, no? Or are you suggesting messing 
with the semantics of <a> when an ancestor is a <sl>? If so, that seems 
like a bad idea (does the spec do this already in places? can we avoid it?)

> | <sl multiple="multiple">
> |   <li>Name 1</li>
> |   <li>Name 2</li>
> |   <li>Name 3</li>
> | </sl>
>    If multiple items are selected, and the user performs a drag
> operation on a list item, the drag would automatically be performed on
> all list items selected rather than just the list item being dragged. 

This seems like a very specific construct that doesn't solve the general 
problem - allowing the author to specify groups of items that can be 
manipulated in certain ways (e.g. mutually exclusive selection, dragging 
of a set of items).

"But if science you say still sounds too deep,
Just do what Beaker does, just shrug and 'Meep!'"

-- Dr. Bunsen Honeydew & Beaker of Muppet Labs

More information about the whatwg mailing list