My client-side application works reliably and as intended in Firefox, but not in IE6. The problem seems to be that I do not have control over the page stack in IE, while I do in Firefox. So far I have not figured out how to use “focus” to assure proper page sequencing.
Here is an overview of my client-side application. There are 6 screens that capture user-entered data. Screen 1 opens 2, which opens 3, which opens 4, which opens 5, which opens 6. Each screen requests the user to enter data before moving to the next screen. Data validation prevents moving to the next screen if errors are found or a required field is skipped. Each screen opens the subsequent screen by pressing the NEXT button. When the NEXT button is pressed, that screen is not closed, but stays open holding the data that was entered.
When screen 6 is reached, there is no NEXT button, because there is no screen following it. In place of a NEXT button, screen 6 shows a SAVE button. After data entry and validation in screen 6, pressing the SAVE button causes screen 6’s data to be passed to its parent (screen 5) and screen 6 is closed. Closing screen 6 leaves screen 5 showing at the top of the stack. Screen 5 now shows only a SAVE button (replacing the previously used NEXT button). Pressing the screen 5 SAVE button passes all data in 5 to 4 and closes 5, leaving 4 showing at the top of the stack. SAVE buttons are used for screens 4, 3, and 2 to move their respective data to screen 1, which at the end of the process is the only one remaining open. At that point a REPORT button appears to initiate reporting based on the data passed to 1 from screens 6, 5, 4, 3, and 2.
The reason that Firefox seems to control the stack properly is that when the NEXT button is pressed, Firefox opens each subsequent screen in a new tab. Thus when pressing the screen 6 SAVE button, 6 is closed and 5 immediately appears from behind it.
In contrast to Firefox, IE6 opens each screen in separate windows, not tabs. When pressing the screen 6 SAVE button, screen 5 is not always the next screen in the stack to appear, or if it is, then its parent (screen 4) is not always behind it in the stack.
What occurs to me are these possibilities:
(a) control the stack order so that it is always 6, 5, 4, 3, 2, 1; control by use of “focus” or some other javascript technique;
(b) make the screens open in IE in tabs so that the desired order is obtained (this assumes IE and Firefox would use tabs in the same manner);
(c) something else someone more experienced would suggest.
TIA for any ideas that work!!
Here is an overview of my client-side application. There are 6 screens that capture user-entered data. Screen 1 opens 2, which opens 3, which opens 4, which opens 5, which opens 6. Each screen requests the user to enter data before moving to the next screen. Data validation prevents moving to the next screen if errors are found or a required field is skipped. Each screen opens the subsequent screen by pressing the NEXT button. When the NEXT button is pressed, that screen is not closed, but stays open holding the data that was entered.
When screen 6 is reached, there is no NEXT button, because there is no screen following it. In place of a NEXT button, screen 6 shows a SAVE button. After data entry and validation in screen 6, pressing the SAVE button causes screen 6’s data to be passed to its parent (screen 5) and screen 6 is closed. Closing screen 6 leaves screen 5 showing at the top of the stack. Screen 5 now shows only a SAVE button (replacing the previously used NEXT button). Pressing the screen 5 SAVE button passes all data in 5 to 4 and closes 5, leaving 4 showing at the top of the stack. SAVE buttons are used for screens 4, 3, and 2 to move their respective data to screen 1, which at the end of the process is the only one remaining open. At that point a REPORT button appears to initiate reporting based on the data passed to 1 from screens 6, 5, 4, 3, and 2.
The reason that Firefox seems to control the stack properly is that when the NEXT button is pressed, Firefox opens each subsequent screen in a new tab. Thus when pressing the screen 6 SAVE button, 6 is closed and 5 immediately appears from behind it.
In contrast to Firefox, IE6 opens each screen in separate windows, not tabs. When pressing the screen 6 SAVE button, screen 5 is not always the next screen in the stack to appear, or if it is, then its parent (screen 4) is not always behind it in the stack.
What occurs to me are these possibilities:
(a) control the stack order so that it is always 6, 5, 4, 3, 2, 1; control by use of “focus” or some other javascript technique;
(b) make the screens open in IE in tabs so that the desired order is obtained (this assumes IE and Firefox would use tabs in the same manner);
(c) something else someone more experienced would suggest.
TIA for any ideas that work!!
Comment