[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

RE: [xsl] onChange does not funtioning?


Subject: RE: [xsl] onChange does not funtioning?
From: "W Charlton" <XSLList@xxxxxxxxxx>
Date: Fri, 16 May 2008 09:59:42 +0100

It's a small point but I think Michael meant bgcolor and not bgColor ;)

bgColor will work in HTML but is incorrect in XHTML.


William Charlton
The yMonda team
yMonda Limited
w: www.ymonda.net

-----Original Message-----
From: Michael Kay [mailto:mike@xxxxxxxxxxxx] 
Sent: 2008 May 15 11:56
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: RE: [xsl] onChange does not funtioning?

As far as XSLT is concerned, onChange is just an attribute to be added to
the generated HTML (or ASP) output document. It's no different from
generating an attribute called bgColor or fzSackTheLawyers. If the output
document doesn't behave the way you want, then you need to fix it. That
doesn't require a change in the way the document is generated.

Or perhaps you are imagining that somehow the onChange action should be
activated during the XSLT transformation? If so, you're confused about the
processing model.

Michael Kay
http://www.saxonica.com/ 

> -----Original Message-----
> From: nenad@xxxxxxxxxxxxxxx [mailto:nenad@xxxxxxxxxxxxxxx] 
> Sent: 15 May 2008 11:33
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: [xsl] onChange does not funtioning?
> 
> Hi,
> I have:
> 
>         <form action="Default.aspx"    runat="server">
> 
> 
> <select name="SelectCategories">
>                   <xsl:attribute 
> name="onChange">form.submit()</xsl:attribute>
>                   <xsl:for-each 
> select="document('../content/en//categorycodes.xml')/catcodes/
> category">
>                     <option>
>                       <xsl:attribute name="value">
>                         <xsl:value-of select="@code"/>
>                       </xsl:attribute>
> 
>                       <xsl:value-of select="."/>
>                     </option>
>                   </xsl:for-each>
>                 </select>
> 
> 
> 
> </form>
> 
> onChange is not reacting.
> Should I use javascript instead?
> Thanks
> Nenad


Current Thread
Keywords