Home > front end >  Chrome after upgrading, JQuery form subimt a bad way
Chrome after upgrading, JQuery form subimt a bad way

Time:09-16

My code is as follows:
 Save: function () {
$(" # save "). The linkbutton (" disable ");
Var _url="/Request/ashx/ABC ashx? Type=update ";
$(' # form1 '). The form (the 'submit' {
Url: _url,
OnSubmit: function (param) {
Param. Operatestatus=BaseParam. ProOperateStatus;
Var isSubmit=true;
Try {
Var validate=$(" # form1 "). The form (" validate ");
if (! Validate) {
Throw "please fill in all required fields!" ;
}
The else {
BasicFunction. GetEditData (param, true);
}

WebUI. Events. SaveBefore (param);
}
The catch (ex) {
EasyUIBase. EasyuiAlert (ex);
IsSubmit=false;
$(" # save "). The linkbutton (" enable ");
}
Return isSubmit;
},
Success: the function (data) {

},
Error: function (XMLHttpRequest, textStatus errorThrown) {
EasyUIBase. EasyuiAlert (XMLHttpRequest. The responseText);
$(" # save "). The linkbutton (" enable ");
}
});
}


This code has been running a few years there are no more questions, after chrome upgrade this code can not make, $(' # form1 '). The form (the 'submit' {}) according to the result of don't send the request to the server or the server returns is canceled, could you tell me how to handle all this to?

CodePudding user response:

See jq for the first time. The form, thought uncultured, and checked the, by the way, is not it, dare the original poster is this writing your own plugin?

CodePudding user response:

reference 1st floor chinaskysun response:
see jq for the first time. The form, thought uncultured, and checked the, by the way, is not it, dare the original poster is this writing your own plugin?

Of course well, you did not seriously check,

https://blog.csdn.net/weixin_39793752/article/details/80844568

CodePudding user response:

reference 1st floor chinaskysun response:
see jq for the first time. The form, thought uncultured, and checked the, by the way, is not it, dare the original poster is this writing your own plugin?

This is not a Jquery, Jquery EasyUI,

CodePudding user response:

Look at the code should be the ajax functionality, why not $. Ajax ()?
The third-party plug-in error, stick is only dropped with function, at least also stick error code out ah,

CodePudding user response:

reference 4 floor chinaskysun response:
look at code should be ajax functions, why not $. Ajax ()?
The third-party plug-in error, stick is only dropped with function, at least also stick error code out ah,

1st floor is error code, $(' # form1 '). The form (the 'submit' {}) function easyui is closed, I think whether chrome after upgrading, the reason why the high security requirements?

CodePudding user response:

The individual feels should have nothing to do with upgrading, you can try firefox, opera and see if you have any questions,
And you clearly on the first floor is handwritten code, I said that the error code is a developer tool tips above, was not a return code, return code is your server code, so that even gantharambhakatha easyui is going to help you to solve the problem
  • Related