␡
- CHANGING LAYER STACKING ORDER
- DRAWING MULTIPLE CONSECUTIVE LAYERS
- LAYERS LIKE YOU LIKE 'EM
- TAKING PREVENTATIVE MEASURES
- MOVIN' AND GROOVIN' AND LAYIN' TO THE BEAT NOW
- NO SPECIAL MAGIC REQUIRED
- PUT THOSE LAYERS IN THEIR PLACE
- SUPER SIZING LAYERS
- NO TRESPASSING
- NESTING URGES
- THE OBVIOUS ESCAPES US SOMETIMES
- CHANGE LAYER CONTENTS
- INSERT DIV TAG
- FRAMESETS-A-PALOOZA
- SPLITS ARE ALL RELATIVE
- QUICK DRAW FRAMESETS
- WHY SO BLUE?
- GETTING IN TOUCH WITH YOUR INNER FRAMESET
- PLAYING THE FRAME NAME GAME
- A FRAMESET BY ANY OTHER NAMESET
- KEEPING FRAMES IN THEIR PLACE
- HELP, I'VE BEEN FRAMED, AGAIN!
- TARGETING MULTIPLE FRAMES
- OODLES OF UNDO-ODLES
- CREATING ACCESSIBLE FRAMES
- DÉJÀ VU FRAMES
- THE GUIDING LIGHT
This chapter is from the book
This chapter is from the book
This chapter is from the book
This chapter is from the book
KEEPING FRAMES IN THEIR PLACE
Because framesets are comprised of separate pages, it's entirely possible for a user to browse directly to a page—from a search engine, for example—and have no idea it's supposed to be part of a frameset. One way to handle this problem is to put this code in the <head> of every file in the frameset:
<script language="JavaScript"> if (top == self) self.location.href = "FramesetFileName"; </script>
In this code, FramesetFileName is the name of the frameset the file is part of. This code looks to see whether the page is within a frameset and if not, puts it in its intended place. Notice that this code is triggered only if the page is not in a frameset; it doesn't determine whether or not it is in the correct frameset.