Web Option

Safari for Windows - F5 Key Behavior

Web Option does not suppress Safari default refresh behavior for F5 key.

During Web Option runtime, if you press the F5 key on the keyboard, a dialog opens with the following message:

“Are you sure you want to send a form again? To reopen this page Safari must resend a form. This might result in duplicate purchases, comments, or other actions.”

We recommend that you do not use the F5 key. However, if it is inadvertently pressed, select the Cancel option in the dialog box.

Internet Explorer, Chrome, Firefox - F5 Key Behavior

Web Option does not suppress the refresh behavior for Internet Explorer (IE), Firefox, and Chrome when your cursor is in the browser address bar and if you press F5 key.

When your cursor is in the browser address bar and if you press F5 key in any of the following browsers, a dialog opens with the following message:

Firefox:: "To display this page, Firefox must send information that will repeat any action (such as a search or order confirmation) that was performed earlier."
Chrome:: "The page that you are looking for used information that you entered. Returning to that page might cause any action that you took to be repeated. Do you want to continue?”
IE:: “To display the webpage again, the web browser needs to resend the information you’ve previously submitted. If you were making a purchase, you should Cancel to avoid a duplicate transaction. Otherwise, click Retry to display the webpage again.”

We recommend that you do not use the F5 key. However, if it is inadvertently pressed, select the Cancel option in the dialog box.

JIT Displayed When Skeleton Exists

A limitation exists with Web Option where it can display a Just-In-Time (JIT) page, even if a skeleton was previously generated for the screen. This limitation only occurs when:

The function is a window function.
The function has a confirm prompt (that normally appears in its own small window).
The function displays with the confirm prompt, but was not displayed immediately before and without the confirm prompt.

For example, if a window function WinFun (with a confirm prompt) displays, and then, as a result of action on the WinFun page, a different function SelFun is displayed. In this case, when the user leaves SelFun, WinFun is immediately redisplayed with the confirm prompt, and the WinFun page displays in JIT mode.

This limitation occurs because although Web Option is able to determine that a confirm prompt (in its own window) is being displayed, it is unable to retrieve required details of the underlying window, such as its original window offset and attributes, which are required to process field offsets.

This limitation does not effect full-screen functions. It does not effect window functions that initially display without the confirm prompt and then redisplay with the confirm prompt when the user presses Enter.

There are two workarounds to this limitation:

Ensure that window functions that have the option to show the confirm prompts always display without the confirm prompt. Require a command key such as Enter to be pressed before the confirm prompt displays. This is essential in situations such as the previous example, where control might have gone to a different function and can then return to the window function.
When window functions do not have the option to display the confirm prompt, consider changing the window function to be a full-screen function.

Note: If a window function displays in JIT mode, this is only while the confirm prompt is displayed.When the window function displays without the confirm prompt, the generated skeleton is used. If the window function displays in JIT mode, normal application functionality is retained. However, functions specific to the generated skeleton, such as drop-down lists, are not available.