Hi All
I am building a website that consists of multiple steps, all liked by forms. Each step has its own web page. Values are passed to each web page using POST, then with hidden form elements. This method is quite effective because the user may click the back button to modify the form before they submit it to us. They can back up to various different steps.
When I incorporated FCKeditor into the application, it worked fine in IE. However, you could not hit the back button to get to the step before the FCK one. You have to click the little dropdown thing next to the back button, and six pages down the history list is the last step.
Any ideas on how I can get it functioning properly? If you need clarifications let me know.
I am building a website that consists of multiple steps, all liked by forms. Each step has its own web page. Values are passed to each web page using POST, then with hidden form elements. This method is quite effective because the user may click the back button to modify the form before they submit it to us. They can back up to various different steps.
When I incorporated FCKeditor into the application, it worked fine in IE. However, you could not hit the back button to get to the step before the FCK one. You have to click the little dropdown thing next to the back button, and six pages down the history list is the last step.
Any ideas on how I can get it functioning properly? If you need clarifications let me know.
RE: Back Button Problems
From time to time, you'll see the form itself listed in the history.
RE: Back Button Problems
It's the only thing that prevents us to use it in our elearning application.
RE: Back Button Problems
This is a critical issue.
Certain items in the toolbar (dropdown menus, popup color selectors) produce an additional entry in history when loaded. In the default configuration, there are 4 dropdowns and 2 color selectors, resulting in 6 extra history entries.
With these items disabled, the back button works normally (and the editor loads much faster).
The common thread is that each of these items is an IFRAME. So mozilla puts iframes in history, IE does not? Or IE provides a workaround that moz does not?
A solution would seem to involve reworking these items so that they don't produce an extra history entry. I'm definitely not a dhtml guru.
http://alex.netwindows.org/2005/03/in-d ... tton.shtml
This page indicates that IFRAMEs which are created after onLoad() is called will not be included in history. Would it be possible to load the guilty IFRAMEs after the page loads?