After Latest Update JS Function Not Working about fancyselect

[paulstraw]

The events were namespaced in he last update. So, if you were triggering "update" before, you'd want to trigger "update.fs" now. Give that a shot and let me know.

[hudsonperalta]

I am calling the function on change similar to the below js.

$('select').on("change", function() {
    if (this.val() == "NEW") {
      $('#newAcct').slideDown("fast");
    }
});

[paulstraw]

Did you try changing to change.fs as described above?

[hudsonperalta]

I will try it in the morning. I just feel that if you want this amazing tool to replace all select boxes on a site you shouldn’t have to change how they typically function.

[seanwash]

Hello @hudsonperalta,

It's not that we're changing how something would typically function just because, it's that we don't want our plugin to conflict with any other plugins that you might include in a site as well. By namespacing events we can ensure that when you want to fire something like .change on FancySelect, it affects only FancySelect and not any other elements that might have .change bound to them.

Here are a few good reads on the subject:

• http://css-tricks.com/namespaced-events-jquery/
• http://www.learningjquery.com/2007/09/namespace-your-events/
• http://api.jquery.com/event.namespace/

Hope that helps!

[hudsonperalta]

First of all I want to make clear that I my intentions are not to bash your hard work and your amazing tool. I think you did an amazing job and I am a big fan of FancySelect and it's developers. But as a big fan I feel it's my duty to offer suggestions. I understand the need for namespacing events in most cases; especially on a .click event that is used throughout a site but FancySelect is specific to select boxes and I feel should function just like all select boxes. My plan was to use it on a pretty big site and I would hate to have to weed through others code to change .change to .change.fs.

Again, thanks for your hard work!

[seanwash]

No worries @hudsonperalta! Thank you for the kind words :)

[paulstraw]

Hey @hudsonperalta. After thinking about this a bit more, we might have a future solution. We're a bit busy to make OSS improvements at the moment, but I'm going to leave this issue open while we think about it and such.

[hudsonperalta]

Any updates on this? We are interested in using FancySelect on a big mortgage site but we really want it to use it to replace all select boxes on the site