> I'm not sure what it is you want.
> You want to have
[quoted text clipped - 10 lines]
> Any reason you don't want to specify the styles for the class as usual
> in CSS?
> Assume in the style sheet we may have
>
[quoted text clipped - 14 lines]
>
> <SELECT NAME="p1_val" class="list-element-2,list-element">
almost:
<SELECT NAME="p1_val" class="list-element-2 list-element">
The order of the two class names doesn't matter btw. Both styles will
be applied, and in case of any collision, the style that is later in
the stylesheet will prevail.
Alternatively, you can just set the 'fallback styles' for 'select'.
(assuming it's okay to apply those styles to all <select> elements on
the page)
> It's a database app, like to give the users the opportunity to update
> their style sheets (held outside of the app) to specify attributes for
> the new class, but if not yet defined, fallback to the one which we know
> is defined.... not ideal but if it is possible it woul dbe useful.
Sounds like two classes would do the job, as long as the client
understands that they should write styles specifically to overrule the
default ones if needed :-)

Signature
Els http://locusmeus.com/
Sonhos vem. Sonhos vão. O resto é imperfeito.
- Renato Russo -
Now playing: Skunk Anansie - Charity
Jeremy - 29 Jun 2005 10:24 GMT
> almost:
> <SELECT NAME="p1_val" class="list-element-2 list-element">
>
> The order of the two class names doesn't matter btw. Both styles will
> be applied, and in case of any collision, the style that is later in
> the stylesheet will prevail.
Sounds perfect - many thanks for your help.

Signature
jeremy