Hi all,
We have a minor problem on one of our web applications regarding the use of the "back" button on the browser. Basically, part of the web app allows the user to open up a printable version of a page and then use the "file" menu to print it out. At this point, the user must press the "back" button on the browser to return to the previous screen and continue using the system. This part all works fine; the user can return to the previous screen and the print-off is ok.
On our web applications, we use WebEventMappings in the forms' load method to map the click action of a button onto a picture object. This means that our buttons can be 'prettier' and therefore more user friendly. Again, this works with no issues.
The problem, is that when the user presses the "back" button from the printable page, it seems to reload the screen from cache, which means the WebEventMappings are not loaded. This, therefore, means that the buttons no longer work so the user has to close the browser and reopen the system. This does not occur when using Internet Explorer, the system in IE simply reloads the screen and allows the user to continue, however, Mozilla Firefox causes the error.
Does anybody know what we can do to stop this from occuring? We could disable the back button and add a new button control to the printable screen, however, this would mean the button is printed out along with the data, and also it would mean a change to the workings of the screen - meaning changes to manuals and informing users.
I have tried to move the mappings into other methods, i.e. the initialPopulate method, but this made no difference. Is there any way, for example, that you can tell the "file -> print" option which frames to print out? Or does it just print everything on the screen?
Any help would be very appreciated.
Cheers,
Rich