Prototype

Comments and changes to this ticket

• 

  Juriy Zaytsev July 3rd, 2008 @ 07:22 PM

  • → State changed from “new” to “not_for_core”

  So what you're saying is:

  <h2 ontitlechanged="highlight()" id="foo">
    foo bar baz
  </h2>
  

  would translate into:

  $('foo').observe(':titlechanged', highlight);
  

  I'm not exactly sure how custom attributes would translate into appropriate event names. Is "ontitlechanged" becomes "title:changed" or "titlec:hanged" or "tit:lechanged" ?

  I'm closing this as "not-for-core". Please feel free to reopen with a working patch/tests.

• 

  David Fenster July 3rd, 2008 @ 07:59 PM

  That is very close to what I mean. I'm not really sure what the significance of the colon ':' character is, so I would have said it translated into:

  $('foo').observe('titlechanged', function(){ highlight() });

  The reason I wouldn't even bother with the colon is because I already know something like this works:

  $('foo').observe('onclick', function(){ highlight() });

  What is the significance of the colon ':' character? I apologize for asking that here if this is not the correct venue.

• 

  Juriy Zaytsev July 3rd, 2008 @ 09:21 PM

  David,

  1) custom events are required to have colon anywhere in a string.

  2) #observe requires a W3C-compliant event name (i.e. "click" rather than "onclick"), so your example doesn't really work:

  $(foo).observe('onclick', function(){ ... } ) // fails
  $(foo).observe('click', function(){ ... } ) // works
  

• 

  David Fenster July 3rd, 2008 @ 09:50 PM

  Thanks for explaining it to me.

  Is there any purpose to requiring a colon character in custom events?