Re: SELECT/ OPTION GROUPS with the SIZE attribute

Scott Isaacs wrote:
> There are ambigious cases in the current proposal. When you define a
> size on a select is usually displays constrained to 4 rows at a time:
> eg.
> If optiongroups were introduced, how would it effect the rendering?  I
> doubt the user would expect that they see only 4 rows at each expansion
> level (actually I am unsure what the correct behavior would be).

I'll let Dave, Al, or somebody address that.

> I understand the goal of grouping list items for the purpose of
> accessibility, but the current specification is going way beyond that
> one requirement.

You are welcome to propose something less ambitious.

> I do not believe you can create an interoperable
> implementation based on the spec

That's argument by assertion, and it's not very constructive.
Please present evidence.

> and as I previously said that it fails
> to address many requirements for hierarchical lists.

The proposal does not need to address the requirements for
hierarchical list, but only the stated accessability requirement.

>  That said, I agree
> with the WAI's intent that a grouping mechanism with broader reach than
> accessibility should be defined.  I request that the group work on this
> proposal in a more timely fashion rather than rushing to including this
> in HTML 4.0. I assume a separate working draft can be published as the
> group works through these issues.

That's not how it works. There is no "later." There is
"yes," "yes, but do it this way instead" and "no," but you have
to take your "no" argument to w3c-wai-hc.

I have said this 4 times now. I'm getting tired of it.
Please present novel evidence or stop objecting.

Please read in detail:

Message-ID: <>
Date: Mon, 27 Oct 1997 00:00:15 -0600
From: Dan Connolly <>
Subject: WAI HC/HTML relationship [was: Minutes [was: Agenda for 971023
HTML WG meeting]]

Dan Connolly, W3C HTML Working Group Chair

Received on Monday, 27 October 1997 15:49:47 UTC