This causes problems:
users of alternate devices may find a frame-based site hard to navigate; all users may come
across orphaned pages (pages outside of their framesets); bookmarking saves the frameset,
not its pages; and design across frames isn??™t possible. Also, because of the increase in
usage of design applications with templating features, and of PHP and server-side includes,
the ease-of-development aspect of frames is no longer relevant. Because of these issues,
the rest of this subsection is primarily here for the sake of completeness.
Although a frameset is still an HTML page, it requires a specific frameset DTD, which looks
like this:
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-frameset.dtd">
The frameset page lacks a body element (although it still requires head and title elements,
along with defining the character set) and instead uses a frameset element, which
sets the attributes for how the frames are positioned. The frameset element houses frame
elements, which define the location and attribute of each frame. Note that this DTD
should only be used for the frameset and not for the individual pages that will be loaded
into the frameset??”they should use whatever DTD is relevant to their content.
A basic two-column frameset may use a code block like the following one, the cols attribute
defining the width of each frame (values can be numerals for a pixel value, a percentage,
or a wildcard *, which sets the dimension to whatever space remains).
Pages:
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401