|
|
|
While frames provide a useful method of browsing a series of pages (via a contents frame and a document text frame), they also use up real estate, just like scrollbars. Even if the frame decorations were all turned off, the frame containing the majority of the document text now suffers the problems discussed above; the width of the frame is smaller, and the chances of adding a horizontal scrollbar have increased. Additionally, a single line of text will have fewer characters viewable, and the page becomes even more difficult to read and comprehend. Using simple navigation buttons at the top and bottom of the page, or even at the top and bottom of each section should make up for the missing contents frame.
The interaction between frames and scrollbars is another important area of concern. While most browsers manage scrolling within each frame independently, the 4630 Web Access Application only scrolls the entire (single) window. This moves the user's view of the frames as a whole, but it does not scroll any of the data in individual frames. There will likely be data in frames that can never be seen.
The combined problems of minimal screen real estate and the scrolling issues really makes frames something simply to avoid.
|
|
|