I cut the follwoing snippet of code from an xsl that I use to format test data for presentation. The second line of code declares the onclick method as an xsl attribute. The sixth line of code includes the declaration of the onclick inline with the html. What's the difference? I eventually want my user to click the href tag and use the ID associated with that row (in this case the name of the test data) to be sent to a javascript method that will set a parameter in the xsl and will allow me to access a specific node in the xml tree. Is that logical?

    <TR id="trnode">
    <xsl:attribute name="onclick">selectRow(this)</xsl:attribute>
    <xsl:attribute name="ondblclick">selectRow(this);selectTestCurren tRow()</xsl:attribute>
    <TD id="idCol" width="200">
        <a href="{./ID/@value}testreport.htm" onClick="alert('Hello from JavaScript!')"><xsl:value-of select="./ID"/></a>
    </TD>

Regarding your XSLT there is no difference in your case between constructing an attribute using the xsl:atribute element and writing it to an element literal as you have done with the 'a' element. The first method gives you more control over namespaces and dynamic control of the attribute name but you do not need that.

As to your JavaScript I'm not sure what you want but what you have looks a little odd. When you click on the 'a' element you will receive an alert and the selectRow will be fired passing the 'TR' object as its only argument. Unless you return false from this method then the href in the 'a' element will also be navigated to.



--

Joe (Co-author Beginning XML, 3rd edition)