Creating Alternative Content
Frames are a fairly old technology (they were introduced in Netscape 2.0) and are supported in all modern browsers. However, frames are one of the few HTML techniques that have no graceful fallback. When browsers encounter a tag they don't understand, they simply ignore the tag. In most cases, that doesn't present much of a problem, but in the case of frames, the page containing the frame tags doesn't contain any content. It only contains tags that define the frames. For that reason, when a browser that doesn't understand frames loads that page, it simply won't display anything at all.
Fortunately, there is a way to specify alternative content for browsers that don't understand frames. By using the No Frames view, as shown in Figure 6.7, you can specify content to be displayed for browsers that don't support frames.
Figure 6.7 The No Frames view allows you to enter content to be displayed when a browser doesn't support frames.
The default message provided by Expression Web (shown in Figure 6.7) isn't very useful, so you'll likely want to add your own content. Therein lies one of the problems with frames. If you're going to create content in the No Frames view that emulates your frames content, you may as well carefully evaluate whether the frameless content is suitable for everyone as a substitute for frames.