Thanks, conceptually it does make sense that bindMethods on a DOM element would do "bad things" as far as security-conscious browsers are concerned. I suppose I was just lazy in using bindMethods instead of explicitly binding only the methods that I created :)
The general pattern that we're using this along with is adding "behaviors" to DOM objects, and having the methods on the DOM objects themselves is pretty darn convenient. Thanks for the suggestion of using bind inline as we're defining the methods - that's a much cleaner way to do it. I appreciate the help. I get the feeling that few people are really using the MochiKit:Base stuff effectively (because few people understand functional programming conceptually), so it's nice to be able to come to this group and get meaningful guidance :) Peter --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~----------~----~----~----~------~----~------~--~---
