Paul Straw

I'll need to see your custom CSS in order to help with this.

I'm not seeing anything offhand. If you comment out your custom CSS, do you still see the issue?

@dahliacreative, 23c58063ac61d080ffe4852a8a0287401a992fac actually has invalid Coffee on line 151 (no `===` in CoffeeScript). This whole conditional can also be simplified down to `trigger.toggleClass 'selected', clicked.data('raw-value') != ''`. I'll be happy...

The CoffeeScript looks right, but I'm not totally sure what's going on with the JS. How did you recompile that?

Presumably this is happening because of these lines: https://github.com/octopuscreative/FancySelect/blob/master/fancySelect.coffee#L184-L186 Would someone mind checking if `opt.val().toString()` fixes the issue? I'd gladly accept a PR if that does the trick.

Yeah, this would probably be a nice thing to have. Will try to get to it as soon as I've got some time for OSS stuff.

@erik5388: I'm in the middle of a move and job change right now. I'm hoping to do a FancySelect revamp at some point, but can't _quite_ yet!

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.

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

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...