No. That choice is SUPPOSED to either:
1. CHECKED: scroll the background image with the text.
2. UNCHECKED: Fix the background image where it is and allow text to scroll over it. This gives a different feeling to your web page. Looks like text is on a transparent piece of glass, sliding OVER the background image that never changes.
BUT....That check box only fixes the background image in Internet Explorer!
To make it work in Firefox, you need to do two things:
1. You will use the COLOR and the IMAGE NAME already being used by CSB for your webpage. Publish your page, go to VIEW SOURCE from the top menu on your Internet Explorer Menu. Look for the section that says
<BODY BGCOLOR="#000000" TEXT="#F7F7FF" bgproperties="fixed" background="2f500bb3.jpg" LINK="#CC99CC" ALINK="#E6769A" VLINK="#FFCCCC">
Grab the bgcolor and the background image name.
2. Add a piece of code to the top of your webpage (in an INSERT HTML box) or to your page layout:
<style type="text/css">
body
{
background: #000000 url('2f500bb3.jpg') repeat-y fixed top left;
}
</style> This code will cause a plain color to appear first, then your background image in a FIXED position. It is set to repeat only vertically (repeat-y). If you want your image to repeat going horizontally too, then just make the code say repeat.
Please visit
this page in both Internet Explorer and in Foxfire.
- Internet Explorer shows that this page has a FIXED background, the background ivy along the left side and rose stone stays EXACTLY where it is while the TEXT moves over the background on a sheer pane
- FoxFire does not show a fixed background because the extra coding I mention above is NOT included on the page. Firefox treats it as a normlly scrolling background. In this case, the ivy and stone moves WITH the text.
All web pages have a background, even if just plain white, it is still a background. So having the choice HOW your background looks is not a frame issue, only a design decision for that individual page.
===========================================
Frames are literally separate HMTL pages that come together to structure a single page.
For example,
this page about a neat Thumbnail viewer script from Dynamic Drive is on a framed page. It is one page when you visit it but it is constructed by sticking 2 individual pages together into one.
The page you visit is id141.htm, which has code in it to load two separate pages into the window. A FRAME, fixed borders, are assigned at the top of the source code, describing how many pieces and what the names are of each piece.
In this example, there are only 2 pieces:
<FRAMESET FRAMEBORDER=0 FRAMESPACING=0 BORDER=0 ROWS=" 50,*">
<FRAME NAME="TRLX_Top" SRC="id141_t.htm" FRAMEBORDER=0 FRAMESPACING=0 MARGINHEIGHT=0 MARGINWIDTH=0 SCROLLING="NO">
<FRAME NAME="TRLX_Middle" SRC="id141_m.htm" FRAMEBORDER=0 FRAMESPACING=0 MARGINHEIGHT=0 MARGINWIDTH=0>top border:TRLX_Top actually takes up the first 50 rows of the page, stays fixed on the page and the CONTENTS of that is found in a page called id141_t.htm.
page body:TRLX_Middle is the rest of the page, beginning on line 51. The CONTENTS for that page body is found in a page called id141_m.htm
CSB is smart. You can not visit the PIECES of that page, even though a full webpage is generated for each frame (TOP and MIDDLE). There is a tiny piece of code in the page body file id141_m.htm that FORCES you to reload the whole combined page (a redirect script).
<SCRIPT language="JavaScript">
var n4p = (self.innerHeight != null && self.innerHeight == 0);
if ((parent.TlxPgNm==null || parent.TlxPgNm!='id141') && !n4p){
location.replace('id141.htm');
}
</SCRIPT>
