unwanted horizontal scroll

[mykl]

I have a problem with a horizontal scroll bar appearing that doesn't have the blue scroll tab thingy cos the page isn't wide enough to need horizontal scrolling. It doesn't show up in IE but it does appear in Firefox. How can I get rid of the pesky thing?
If you want to see what I'm talking about go to http://www.mykl.org.uk/ and click on one of the links. Remember, it doesn't appear in IE4.

[alexgeek]

this is a CSS question.
and you use IE4?

[karinne]

Originally Posted by mykl

Remember, it doesn't appear in IE4.

Good Lord ... who still uses IE4 ... I hope that was a typo

I don't see a problem with your site in FF ... can you take a screenshot maybe?

[mykl]

I have no idea how to do screen shots. Do I need a special program? I mostly use FF, the IE4 is a relic! Never got around to upgrading...

[alexgeek]

you really shouldn't be using frames!
Nor tables!
very bad!

[karinne]

Originally Posted by mykl

I have no idea how to do screen shots. Do I need a special program?.

Screengrab is great little extension for FF

[mykl]

I LIKE frames AND tables! They do what I want. CSS means you need to update a million navigation bars if you add a page!

[karinne]

Far from it

Resources for learning how to use CSS for layout

[mykl]

Ok, i've got screengrap and i've saved a screen shot. How do I put it here?

[alexgeek]

I seriously recommend you don't continue with tables and frames.
there are too many bad reasons to list.
Search engines will hate it.
readers will hate it
and you will eventually

but to answer your question
when posting a reply, click add an attachment and browse to the screenshot

[AdRock]

Originally Posted by mykl

I LIKE frames AND tables! They do what I want. CSS means you need to update a million navigation bars if you add a page!

Why don't you create a template for the index page, and use php to include the content. That means you don't have to duplicate page content as the only thing that changes is the content

[alexgeek]

Why not to use frames:

1. Indexing programs (search engines such as AltaVista, Harvest, and
InfoSeek) do not automatically index the content of frames.

2. Bookmarks don't work as expected; you can bookmark the top-level
(frameset) page, but not necessarily what's displayed on your screen.

3. What you see on screen and what gets printed are usually not the
same.

4. Frames are harder to code, with syntax that includes frameset tags
and target windows. Pages with frames are also harder to maintain. For
instance, the number of files to track for each page with frames is the
number of windows plus the frameset page (usually 3-4 pages).

6. A few browsers can't deal with frames (e.g., some AOL versions,
lynx).

7. Netscape 2.x doesn't supply "back" navigation with frames.

8. When frames are nested within frames, text can become unreadable.

9. Frames can be coded to open a new, external window. Most systems take
quite a while to open a new window, and some viewers find this "feature"
annoying.

10. If you want to check the source code of a frame, you have to open at
least two documents.

Why not to use tables:
http://davespicks.com/essays/notables.html