You, is that the current duilib Newwindow3 side do before integration WebBrowser control processing is the default browser, because involves session, will open a browser to login interface, side to opened the client internal demand, in a certain piece of jump and in the browser is not the same as a result, I developer tools to debug and find the new page is launched a post request, is preliminarily concluded that because of less post information
PDisp void NewWindow3 (IDispatch * * and VARIANT_BOOL * & amp; Cancel, dwords dwFlags, BSTR bstrUrlContext, BSTR bstrUrl); Here to find a can post information field
Also the information
https://docs.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/platform-apis/aa768283 (v=vs. 85)
May I ask you the next post information on how to get to the
Sorry, no points

CodePudding user response:

Sorry, it's supposed to get, is but A page open B page, the request object is C page, if it is B page refresh, that is A post request

CodePudding user response:

 function batDel () {
Document. ExpenseForm. Target="_blank"; 
Var name=encodeURI (encodeURI ($(" # name "). Val ())); 
Var url="XXXXXX. Do? Method=XXXXX& Name="+ name; 
Document. ExpenseForm. Action=url; 
Document. ExpenseForm. Submit (); 
location.reload(); 
} 

Saw is the problem, he submitted a form after a new page, not my side js level difference, there are bosses know whether this is a new page to do the form submission form submission or the original page?
The individual feels side problems appeared in the form is submitted, as a new page with the original