Limitations of non-scrolling headers
If you intend to use non-scrolling header style in your Web function applications, you should be aware of some of the limitations of this style.
- If you use the Back button of your browser to display previous pages, this causes problems. The non-scrolling header style uses framesets and each frame is a self-contained page. The browser remembers the sequencing of the pages in its memory cache. It does not know the relationship of the frames.
- On a page request, LANSA for the Web will display the body of the function initially. It will then determine if the header needs to be refreshed. If it does, it sends a new header page to the header frame. This means that the last frame to be refreshed is the header frame. When you select the Back button of your browser, it will load the previous page of the header frame, without refreshing the body of the function. This may cause the header and the function to be out of synchronization.
- If you select the 'Refresh' or 'Reload' command in your browser, only the body of the function is loaded. The request to refresh does not reload the frameset definition.
- It is recommended that this header style is not used for WEBEVENT functions.
It is recommended that the non-scrolling header style be used only with Intranet or Extranet applications, where you can provide instructions to your users, and can control the type of browsers they use.