W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > March 2011

[Bug 12245] @size on <select> drop-downs is not enough to specify the drop-down maxlength on long options lists with scrollbars

From: <bugzilla@jessica.w3.org>
Date: Tue, 22 Mar 2011 00:24:05 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Q1pOH-0001ua-95@jessica.w3.org>

Jonas Sicking <jonas@sicking.cc> changed:

           What    |Removed                     |Added
                 CC|                            |jonas@sicking.cc

--- Comment #13 from Jonas Sicking <jonas@sicking.cc> 2011-03-22 00:24:03 UTC ---
First off, the way that @size works is how things have worked for ages. Every
time you see a list on a website, such as the cc-list on this very page, it
relies on @size to accomplish this. It sucks, but changing it will break a very
large percentage of sites on the web so it unfortunately that isn't an option.
So whatever solution we'll come up with here will have to involve some other

So, that said, moving on to the actual problem at hand:

Isn't this a quality-of-implementation issue? What you are saying is that in
some browsers, having a <select> with a large number of elements results in
unusable UI. So you are asking for a mechanism to set the size of the dropdown
so that you can take responsibility for keeping it usable.

Rather than adding a mechanism for "Useable UI please!", why not always require
browsers to have usable UI? I.e. is there a use case for showing exactly X
number of items in the dropdown, or do you simply not want it to grow large
enough to become unusable?

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 22 March 2011 00:24:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:44 UTC