CSS background moves

[sysop9999]

I'm just getting into CSS so I'm sure it's pretty basic stuff.

But I'm getting this effect each time a link is clicked on a page and the page needs to reload (like: ../view.asp?id=20). It looks as the background itself is moving to the left each time - the content stays put on the screen. It's only the background that moves a few pixels each time.
It also effect the scrollbar as it moves along with it to the left - after 10-12 reloads of the page, the page turns all white.

What's causing that?

I use DIV's within DIV's etc. but nothing heavy and it shouldn't effect the background ..... or?

[ADAM Web Design]

URL? Kinda hard to tell without one.

[sysop9999]

I managed to put up a testpage.

http://www.incomm.dk/thetest.asp

[sysop9999]

Now it somehow works. I use it on another domain within a frame. Maybe CSS doesn't like frames?

[ADAM Web Design]

I don't see a background there at all, but I do see a broken image. Does that have something to do with it?

[sysop9999]

nahh ... I just made room for logo-stuff there. So the image is supposed to be broken :-)

It´s working all ok now when I use it on my mainsite. The other site has its DNS pointing to a sub-directory and since I don't have a unique IP address on that one, I had to point it in there using a frame. While I'm working on a site, I just buy the domain name and do it like that until it's finish - I'm cheap, I know :-)

Anyways, it looks as it's that frame there's messing things up. I'll try to put up the testpage on the 'framed' one instead.... then it's easy to see the error

[sysop9999]

try this URL instead....

http://www.modelized.net/

You'll probably already notice that the scrollbar has moved slightly to the left ... and it does so each time a link has been clicked

[Steelchord]

This site is well and truly fubar'd.

First: get rid of frames. If you *must* use a frame for your asp-driven menu, then use an iframe instead. What's happening with the "moving scrollbar" is that you're opening a new frame within the existing newsbox frame (or whatever you're calling it, I forget.) So don't. There's a way to avoid that problem and keep the frames structure intact the way you have it, but it is not worth your time or mine for me to explain it.

The fix: Open the new page in "top" instead, and make sure that each page has the other elements that you want to include--topbar, menu, etc. You can generate them using ssi, asp, javascript, or your favorite other flavor, or just copy and paste the html each time, but you need to have those elements on each page.

Unless, of course, instead of using a pageload within a frame for your content changes, you use an xml parser script, or something equally sensible... That would be faster, less bloated, and the content pages would be easier to write. Just my two cents.

--Geek With A Guitar

[sysop9999]

lol... I had hoped it was some CSS thing I could solve with a simple:

{
frame: freeze-dammit; }

:-)

But thanks for clearing that one out. I never found out anything, so I removed the frame-thingy from the DNS admin, so now it will show the 'true' URL and it works as expected now (not the above example URL though - that one still uses a frame)