Rudder

An error also appears on the eventlog page when clicking on the details, it might be related

This is due to the use of "prop" in place of "attr" in the following JS in SrvGrid.scala:

  def initJsCallBack(tableId:String, callback : (String) => JsCmd) : JsCmd = {
      JsRaw("""$('td[name="serverName"]', #table_var#.fnGetNodes() ).each( function () {
          $(this).click( function () {
              var aPos = #table_var#.fnGetPosition( this );
              var aData = jQuery(#table_var#.fnGetData( aPos[0] ));
              var node = jQuery(aData[aPos[1]]);
              var id = node.prop("serverid");
              var jsid = node.prop("jsuuid");
              var ajaxParam = jsid + "|" + id;
              %s;
          } );
        })
      """.format(....

This is following correction of issue #2036, so now I just don't understand when to use ".attr" and when to use ".prop".

Some information¹ seems to say that "attr is what is defined on HTML, and .prop is for the DOM properties". But I thought that a prop was at least equals to attr, and seems that no.
Perhaps that is true only for specific attributes, like "serverid" or "jsuuid", which are not normalize, see this fiddle (with firebug opened) to see that: http://jsfiddle.net/fDcbS/

Nico, could you please try to understand that ? And perhaps change what have to be change in the commit ce6f985e92e8230ff9d58bbef082fdf47346eb85 ? Moreover, perhaps we should revert that commit ?

[1]
http://api.jquery.com/prop/ and http://api.jquery.com/attr/
http://forum.jquery.com/topic/whats-the-difference-between-jquery-attr-and-jquery-prop

The link from witch I initially read about "prefer .prop to .attr":
http://stackoverflow.com/questions/5874652/prop-vs-attr

This is a very interesting topic :)

From these links :
http://stackoverflow.com/questions/5874652/prop-vs-attr
http://blog.jquery.com/2011/05/10/jquery-1-6-1-rc-1-released/

"The .prop() method should be used for boolean attributes/properties and for properties which do not exist in html (such as window.location). All other attributes (ones you can see in the html) can and should continue to be manipulated with the .attr() method."

• if you can read the attribute in the HTML, and it is unmutable, then it's an attr
• if you cannot read the attribute in the HTML, then it's a prop
• if you can read the attribute in the HTML, but it is mutable, then it has to be verified, but most of the time prop will be what you need (at least for checked, disabled and selected)

Note that if the value doesn't exist in the properties, you can set it with the prop, making it readable with a prop read afterward