ansaurus

Question

Javascript better way to identify node of callback than XSLT generate-id() on another attribute.

Answer 1

+1 A:

This is pretty strange looking, but if I understand correctly, you'd like to be able to write your custom event handlers such that they can easily obtain a reference to the element they're attached to. This shouldn't be hard; after all, you're calling the custom handler yourself, so you already know what element it's attached to - you just need to pass that along to the handler itself:

function init(aThis) {
  var result = document.evaluate("//@testd_on_load",
    aThis.document, null, XPathResult.UNORDERED_NODE_SNAPSHOT_TYPE, null);

  for (var i=0; i<result.snapshotLength; i++) {
    var n = result.snapshotItem(i); // attribute node
    var s = n.nodeValue; // script to run
    var e = n.ownerElement; // element for context

    (new Function(s)).call(e); // run script with `this` set to the context node
  }
}

Now you can simplify your event code:

<xsl:attribute name="testd_on_load">testdOnChange(this);</xsl:attribute>

Shog9 2009-08-29 06:05:08

In the for loop the nodeValue is the script so change to: var n = result.snapshotItem(i); var s = n.nodeValue; var e = n.ownerElement; Would you modify your answer since I cannot edit it.

C.W.Holeman II 2009-08-29 13:49:34

Good catch - I've updated the answer.

Shog9 2009-08-29 19:45:53

ansaurus

tags:

views:

answers:

Javascript better way to identify node of callback than XSLT generate-id() on another attribute.

related questions