Hi there,
I see there is a patch for IE9, but also wondering if Chrome 6.x is being looked at. I have some very basic XSLT work which has been working fine, and certainly not an issue in firefox, so just wondering if someone could shed some light on this. I have the code as follows:
XSLT
[code]<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet version=“1.0” xmlns:xsl=“XSLT Namespace”>
<xsl:template match=“/”>
<xsl:for-each select="data/item">
<xsl:value-of select="notificationsDate"/>
<a href="showprofile.html?id={fromMemberID}">
<xsl:value-of select="FromMember"/>
</a>
has created a new <xsl:value-of select="notificationsType"/>
<a href="{notificationsURL}">
<xsl:value-of select="notificationsDesc" />
</a>
</xsl:for-each>
</xsl:template>
</xsl:stylesheet>[/code]
EXAMPLE XML
<?xml version="1.0" encoding="utf-8" ?>
<data>
<item id="9">
<fromMemberID>7</fromMemberID>
<FromMember>david</FromMember>
<notificationsType>event</notificationsType>
<notificationsDesc>A new event (Test Event Tuesday, 21 September 2010) has been created.</notificationsDesc>
<notificationsDate>21 Sep 2010</notificationsDate>
<notificationsTime>17:46:07</notificationsTime>
<notificationsURL>/memberEventDetail.html?id=7</notificationsURL>
</item>
<item id="10">
<fromMemberID>7</fromMemberID>
<FromMember>david</FromMember>
<notificationsType>event</notificationsType>
<notificationsDesc>A new event (Test Event Saturday, 25 September 2010) has been created.</notificationsDesc>
<notificationsDate>25 Sep 2010</notificationsDate>
<notificationsTime>17:56:54</notificationsTime>
<notificationsURL>/memberEventDetail.html?id=8</notificationsURL>
</item>
</data>
… and of course the JS/DHX Ajax bit…
dhtmlxAjax.get('/PageTemplates/membernotifications_template.xsl', function (xslLoader) {
//var xmlLoader = dhtmlxAjax.getSync('/ajaxget/getmembernotifications.ashx');
var xmlLoader = dhtmlxAjax.getSync('/PageTemplates/test.xml');
$('#notifications').html(xmlLoader.doXSLTransToString(xslLoader.xmlDoc.responseXML));
});
Any ideas much appreciated… I have attached an image of the error produced in Chrome 6.0.472.63