Return to Answer

If you want a request sent after a confirmation dialog is shown it's up to you, via client code, to do that. The browser will not take any initiatives for you there. On its own it only can tell it must send a request when a form is submitted, a link is clicked or a new address or search query is submitted. That's it. Other than that, it never knows.

So the answer to your question really is: Whatever happens when the user clicks OK or Cancel on a message box is on you. It's your code's responsibility to take appropriate action.

Usually your presentation layer will show confirmation dialogs with javascript and wait for input. When the user makes a choice, it gets processed by the code and the next step is executed depending on the choice. Again, remember that whatever happens then is up to you. For all there is, you could very well end up having the "Cancel" button click making a server request. There might be a very good reason for that: rollbacking an on-going transaction, going back to a specific page... it really all depends on your app design and requirements.

Now, on Page.IsValid, if you look at the documentation you'll find out that this tells if the validation server controls are all valid within the page. Depending on what you're trying to do here this might not even be related at all.

I hope you find that information useful.

If you want a request sent after a confirmation dialog is shown it's up to you, via client code, to do that. The browser will not take any initiatives for you there. On its own it only can tell it must send a request when a form is submitted, a link is clicked or a new address or search query is submitted. That's it. Other than that, it never knows.

So the answer to your question really is: Whatever happens after a user makes a choice in a confirmation box is on you. It's your code's responsibility to take appropriate action.

Usually your presentation layer will show confirmation dialogs with javascript and wait for input. When the user makes a choice, it gets processed by the code and the next step is executed depending on the choice. Again, remember that whatever happens then is up to you. For all there is, you could very well end up having the "Cancel" button click making a server request. There might be a very good reason for that: rollbacking an on-going transaction, going back to a specific page, etc...

It really all depends on your app design and requirements. If anything, pressing either OK or Cancel may even not lead to a query being made at all!

Now, on Page.IsValid, if you look at the documentation you'll find out that this tells if the validation server controls are all valid within the page. Depending on what you're trying to do here this might not even be related at all.

I hope you find that information useful.

The short answer is that the client never knows to send request to server unless the client code make that happen. Whatever happens when the user clicks OK or Cancel is up to you, and you alone. It's your responsibility to react on user input and take the appropriate action. The browser will not take any initiatives for you there.

Usually your presentation layer will show confirmation dialogs with javascript and wait for input. When the user makes a choice, it gets processed by the code and the next step is executed depending on the choice. Again, remember that whatever happens then is up to you. For all there is, you could very well end up having the "Cancel" button click making a server request. There might be a very good reason for that: rollbacking an on-going transaction, going back to a specific page... it really all depends on your app design and requirements.

Now, on Page.IsValid, if you look at the documentation you'll find out that this tells if the validation server controls are all valid within the page. Depending on what you're trying to do here this might not even be related at all.

If you want a request sent after a confirmation dialog is shown it's up to you, via client code, to do that. The browser will not take any initiatives for you there. On its own it only can tell it must send a request when a form is submitted, a link is clicked or a new address or search query is submitted. That's it. Other than that, it never knows.

So the answer to your question really is: Whatever happens when the user clicks OK or Cancel on a message box is on you. It's your code's responsibility to take appropriate action.

Usually your presentation layer will show confirmation dialogs with javascript and wait for input. When the user makes a choice, it gets processed by the code and the next step is executed depending on the choice. Again, remember that whatever happens then is up to you. For all there is, you could very well end up having the "Cancel" button click making a server request. There might be a very good reason for that: rollbacking an on-going transaction, going back to a specific page... it really all depends on your app design and requirements.

Now, on Page.IsValid, if you look at the documentation you'll find out that this tells if the validation server controls are all valid within the page. Depending on what you're trying to do here this might not even be related at all.

I hope you find that information useful.

The short answer is that the client never knows to send request to server unless the client code make that happen. Whatever happens when the user clicks OK or Cancel is up to you, and you alone. It's your responsibility to react on user input and take the appropriate action. The browser will not take any initiatives for you there.

Usually your presentation layer will show confirmation dialogs with javascript and wait for input. When the user makes a choice, it gets processed by the code and the next step is executed depending on the choice. Again, remember that whatever happens then is up to you. For all there is, you could very well end up having the "Cancel" button click making a server request. There might be a very good reason for that: rollbacking an on-going transaction, going back to a specific page... it really all depends on your app design and requirements.

The short answer is that the client never knows to send request to server unless the client code make that happen. Whatever happens when the user clicks OK or Cancel is up to you, and you alone. It's your responsibility to react on user input and take the appropriate action. The browser will not take any initiatives for you there.

Usually your presentation layer will show confirmation dialogs with javascript and wait for input. When the user makes a choice, it gets processed by the code and the next step is executed depending on the choice. Again, remember that whatever happens then is up to you. For all there is, you could very well end up having the "Cancel" button click making a server request. There might be a very good reason for that: rollbacking an on-going transaction, going back to a specific page... it really all depends on your app design and requirements.

Now, on Page.IsValid, if you look at the documentation you'll find out that this tells if the validation server controls are all valid within the page. Depending on what you're trying to do here this might not even be related at all.