W3C home > Mailing lists > Public > www-html@w3.org > April 1999

Re: Form "select" suggestion

From: Ian Hickson <py8ieh@bath.ac.uk>
Date: Tue, 20 Apr 1999 23:50:19 +0100 (BST)
To: "L. David Baron" <dbaron@fas.harvard.edu>
cc: www-html@w3.org, www-style <www-style@w3.org>
Message-ID: <Pine.GSO.4.04.9904202342310.10408-100000@midge.bath.ac.uk>
On Thu, 8 Apr 1999, L. David Baron wrote:
> On Thu, 8 Apr 1999 21:24:35 +0100, George Lund wrote:
>>> [giving icons to HTML drop down box items]
>> Perhaps SELECT boxes could be counted as lists so that the
>> 'list-style-image' property would apply.
> In theory, this *may* already be possible in CSS, using the
> ":before" pseudo-element for generated content. However, I don't
> know if anyone understands how generated content works on elements
> that don't take arbitrary inline (or inline and block) elements as
> children (such as SELECT, IMG, OPTION, etc.).

On IMG, or any of the form elements, there is no particular problem
with generated content AFAIK. On elements _inside_ replaced elements,
such as SELECT, well...

The problem here is that the rendering of SELECT is not yet mentioned
in any specs. It may be covered by CSS3, and maybe one of the XML
behaviour proposals (brothers of XLink) will cover it.

For now it seems that SELECT is pretty much out of scope of CSS.

However, is we simply treat each SELECT element as its own document,
then we could say that all properties that apply to root elements
apply to SELECT. There is no particular problem with this, except that
SELECTs are usually rendered by deferring to the OS's UI code.

> It certainly isn't implemented anywhere.


Ian Hickson 
U+2642 U+2651
U+262E U+2603 U+263A
Received on Tuesday, 20 April 1999 18:50:25 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:50 UTC