Actually the problem I was mentioning in my original message
was not so much related to the content of the <option> tag but
rather to a fairly standard way of building the test pattern.

The only way I manage to make the <xsl:when> below work with
IE5 is by having something like:
  <xsl:when test=".[.='VALUE1']">blah blah</xsl:when>
whereas the other parsers seem to work fine with simply:
  <xsl:when test=".='VALUE1'">blah blah</xsl:when>
which you mention in your reply.

Any information or pointer on some clarification pertaining to
those test patterns, and a way to have the same working from
IE5 to the parsers implementing the XSLT proposed recommandation?

Olivier.

>
>From: "Nikita Ogievetsky" <nogievet@xxxxxxxxxxxx>
>Date: Tue, 26 Oct 1999 00:41:03 +0100
>Organization: Offsight Arts, Inc
>
>Oliver,
>what you are writing should not work in any parser:
>select is an attribute with a single value.
>This means that both <option selected="true"/> and <option
>selected="false"/> will make option selected.
>Parsers conformant with the latest WD will change <option
>selected="selected"/> into <option selected/>
>One way to solve your problem is the following:>
>
>          <select>
>            <option value="VALUE1">
>                <xsl:choose>
>                  <xsl:when test=".='VALUE1'"><xsl:attribute
>name="selected">selected</xsl:attribute></xsl:when>
>                </xsl:choose>
>              THE VALUE 1
>            </option>
>            <option value="VALUE2">
>                <xsl:choose>
>                  <xsl:when test=".='VALUE2'"><xsl:attribute
>name="selected">selected</xsl:attribute></xsl:when>
>                </xsl:choose>
>              THE VALUE 2
>            </option>
>           </select>
>
>Nikita Ogievetsky
>http://www.cogx.com
>


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list