Rails ujs callback not work about remotipart

[danielgrippi]

We are experiencing the same thing on diaspora with the most recent rails.js and remotipart.

It seems to be related to making handlRemote returning false before it gets bound, and then manually constructing the ajax call

if you were to expose the ajax object here

   // Allow remotipartSubmit to be cancelled if needed
         if ($.rails.fire(form, 'ajax:remotipartSubmit', [xhr, settings])) {
            // Second verse, same as the first
            $.rails.ajax(settings);
         }

we could then use it as a promise.

[danielgrippi]

there seems to be some weirdness where success isn't getting triggered, but complete is, in our app code we are doing this:

$('#new_photo').bind('ajax:complete', function(evt, xhr) {
  console.log(evt, xhr)
});

[JangoSteve]

Perhaps see if you can find a difference between your implementation and the remotipart demo app, as it works fine there.

@JangoSteve , It's working cause there's no callback of ajax:success on form[data-remote]; And it's using the JS on create.js.erb to achieve the .replaceWith().

.delegate('form[data-remote]', 'ajax:aborted:required, ajax:success', function(){
alert('there');

And by adding the ajax:success on the form[data-remote], you can reproduce it's not triggering the callback.

@danielgrippi confirmed that ajax:success not trigger but ajax:complete does. Tested on Demo app:

.delegate('form[data-remote]', 'ajax:aborted:required, ajax:success, ajax:complete', function(){
alert('there');

Same issue rails/jquery-ujs#256 (comment)

Oops, sorry. Not the same issue as this one ajax:success not trigger not just on replaceWith, it's not trigger when upload document...

[jgorset]

I, too, can confirm this behavior.

[mcfilib]

I got around this in our app by listening to ajax:error and setting a specific status code in the controller. Ouch.

[JangoSteve]

This is now fixed in remotipart c1.0.3.

[mcfilib]

👍