Say if I am on page 1 , I enter my form data and go to page 2 , But wait I forgot something and I need to go back. FireFox and Safari ask me if I want to resend my form data.
But IE being IE it just goes back and does not show the page.
Is there away around this when I click back it keeps the data and the page appears.
Sorry I cannot give a link but the process for u to go through on my site to get to this part would take you a while.
My suspicion is that your talking about a wizard form. Where each part of the form is a page and you can go backwards and forwards through the pages.
the back button has always caused problems for developers on the web and this is probably the most annoying.
You can stop the IE back button issue by redirecting on the server to the next page when you receive a form post rather than just delivering the form back to the browser. Doing this means that the browser considers each page to have been a get and stops asking you if you want to resubmit the form.
to do this simply make each form post to itself and then return a redirect to the next page of the wizard. I'd give examples but I'm not sure what language you are using on the server.
the other alternative is to use javascript to create a wizard from your form see this jQuery wizard form demo.
create a new back button besides the submit button and when a user clicks on either one you call a javascript function which modifies the form action either to the next page or the previous page.
Related
I faced with a strange problem. I write ASP.NET web application.
I have form tag on the aspx page and submit in the form. When I click on the submit form's data are posted. It is ok. But if I close the page right after submit and then re-open it with Main Menu -> Recent Tabs (I use Google Chrome) the form's submit fires once again and data are posted too. I would like to avoid this behavior because repeated posting data to server is unwelcome and unexpected. It happens after select Recent Tabs only (when I prress Ctrl+Shift+T it does not happen) How could I prevent it? Thanks in advance
Check if it's a PostBack. If it is a PostBack then return.
I need to open several email popups (~30) from Adobe AIR Flex app, I am currently using navigateToURL but I observed that at times some email popups go missing. I have tried callLater as well. WHen I introduce delay between popups it works better but still has a risk of some popup missing. Can anyone advise please? These emails dont have any attachments but have html contents.
I am guessing that you don't want all 25-30 messages to appear at once. If you could try to schedule a better way like the one below, I think that will really help you fix the problem:-
Add references to all the 25-30 objects in an array
Now on click of a button, show the 1st email body. Have a button in the popup which reads something like 'Send and Read next email'. On click event, fire the email to be sent and pop the next object from your array to show contents of the next email.
I have a form on a webpage that submits post information to the server. All is working good except when i submit the form and press back button the data in the form re-appears instead of going to the previous web page. How can I prevent this? Also I want the previous web page to be reloaded again when i press back button.
Thank you.
Im using the jquery event beforeunload $(window).bind('beforeunload') to make an api call after a user closes the browser, or a tab, or hits the back button. It works fine in Firefox, but not completely in Chrome. In Chrome, it works when the user closes the browser or tab, but not when the user hits the back button. The method is supposed to remove the user from a list of "current active users" whenever they close the browser or tab or leave the page. For some reason in Chrome, the history api isn't removing the user whenever they leave the page via the back button. What could be causing this? Thanks.
I am not sure why this happens but, personally, I wouldn't rely on this. What if the users' computer crashes? A browser will not fire that event - it won't have the chance to. Best bet would be to call a page via ajax or something similar, every 5 seconds or so, and that page updates a date related to the user. You then show users where the date is within the last minute, or whatever you decide, in the list of currently active users. If their computer crashes, the date will no longer be updated.
Regards,
Clarkey
So I am running into an issue. I have certain fields that I store within the request from page to page, because each page requires different fields to be populated within a collector that I used cross-page. The problem is the back button.
If I click the link to take my to my login page, the server populates the collector from the request with the appropriate pagename and event name, etc., to allow me to navigate to the login page. (Certain things have to load, so it has to go through a servlet). However, on that page, there are static modules for ads and whatnot, so clicking on one of the ads will take you to a separate, static page that does not require these attributes to access. In Chrome, Safari and FF, if I click the back button after accessing this static page, the browser asks me to reload the request to be able to view the page. In IE8, however, there is no page reload. It just kicks me back to the page, and does not populate the request, and it crashes with my sorry page.
I need to know if there is a way to populate the request on the back button click, and how to do so. Otherwise, my servlet is throwing a null pointer when trying to access the fields because they are all null in the request. Any help would be greatly appreciated. I am not even sure if this is at all possible.
I guess you are using POST requests to navigate to each page. POST should be used only to send some user action different from page view - login, buying something, changing settings, etc. The browsers require the user to confirm that they want to revisit a page using POST, before that implies state change. See What is the difference between POST and GET?
For simple content pages, where the user does not take action, it's better to use GET requests. Also, it is much more common to use request.getSession() to get and store the user fields on the server side. That is, you only send them once, and then look them up for each request. Look up for tutorials on session tracking in java.