View Full Version : Couple of small problems...

02-15-2008, 06:31 AM
http://codingforums.com/showthread.php?p=654969 is my original topic.. I fixed the padding by switching over.. (it was an interesting experience!)

now i have a few problems... (and ill add more here later if i run into any)

Ok, When I go to http://cait.netdojo.com/jcs/ in Opera, Go to another tab... or just click around for awhile, it completely disregards the margins.. meaning.. the text in the left column, overflows into the scroll bar.

I Cant seen to reproduce the results in IE.. so is this just an Opera thing?

Also in Opera.. using a widescreen resolution, the left column overlaps the main column.. but using 1024x768 or 800x600, it doesnt. (in IE it doesnt either way)

#2 when i try to to validate the HTML with http://validator.w3.org/, it comes up with..

Line 27, Column 101: there is no attribute "ALLOWTRANSPARENCY".
…%" frameborder="0" allowtransparency="true"></IFRAME>

Well, if i take it out, in IE the transparency goes away.. is this something new that W3 just doesnt have in the checker yet or...?

#3: In IE6, The picture's transparency doesnt work, it just shows a colored background... Should I sacrifice some quality and go with GIF so that IE6 users get something decent, or just make it high quality for IE7?

#4 - Fixed: With the main body, in widescreen it appears to have no margin, it lines right up with the scrollbar on the left section. In anything but widescreen there is a large gap between the guy's picture and the scrollbar..

If i decrease the.....
#centreposition {
position: absolute;
margin-left: 200px;
width: 77%;
height: 78%;
top: 130px;
padding: 0px 0px 0px 0px;
..........margin-left, it gets rid of the gap (in 800x600) but then it overlaps in every other resolution.
If it's at 200px, it looks good in 1024x768, but overlaps in every other (both IE and opera)

Edit: fixed this one by changing it to a %. Thank God for %ages.

#5: I have this code...

body.A { color: #ffffff; background-color: #ffffff; font-size: 12px; font-family: tahoma; text-align: justify; margin:10px; background: url("buttons/bg.jpg"); background-repeat: repeat-x; }

bg.jpg is the black-orange-white gradient... OKay, and on index.html i have <body bgcolor="#ffffff"> in IE, it shows the background as being white (below the gradient). In Opera, it shows it being the default color (grey) why is this?

and this is just a little tidbit of side info, you might find interesting..

When i was doing this, in IE7 (which i got for the first time) everything was looking bold.. I kept trying all these font weight tags and stuff, until after a bit of research, i found out it was ClearType's fault.. hahaha..

Thanks ^^

02-15-2008, 10:18 AM
For a start, you have an incomplete doctype.

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

is not a valid doctype and so would mean that browsers will be rendering the page in quirks mode. I'd suggest you read about doctypes at the top of this forum and get the correct one in there. If you are using frames then you will need a frameset doctype, not an html one.

I'd suggest steering clear of frames. You don't need them, they are nasty and horrible in my opinion (unless used in a clever way), and your frame has a few validation errors anyways!

I'd also look into NOT using absolute positioning for your elements, again, unless you can use it in a clever way that works well and for a specific purpose. The point of CSS is to work with the document flow, and when using absolute positioning you take things out of that flow. You really should be using floats, margins and padding to position things.

Sort the doctype first!

02-15-2008, 01:28 PM
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN"

would... that be right?


I dont like absolute positioning either, but I dont know like, anything about sustituting tables for divs.. I just tried it cuz the person in the other topic told me to.

Now im being told to not use frames.

Why cant i get answers to my questions and not "use this cuz its better!" ?? XD

The only way i can get what i want.. ...NOT using iframes is by usuing PHP's include thing, and i REALLY REALLY hate php, because i CANT use notepad and Browser for testing it.

...and im not rewriting the site... again.

02-15-2008, 02:47 PM
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN"

No, I think you haven't followed the link posted in the comment your first post(mentioned above).

For layouts, have a look at http://bonrouge.com/2c-hf-fluid.php and various other links in this page.

02-18-2008, 04:08 AM
I did look at why tables are stupid. Then i switched from tables to div..

As far as doctype.. On the w3 site, this is what they say


So what DOCTYPEs should we use? Glad you asked. The following complete DOCTYPEs are the ones we need:
HTML 4.01 Strict, Transitional, Frameset

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN"
XHTML 1.0 Strict, Transitional, Frameset
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Frameset//EN"

as far as I know, <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN"
"http://www.w3.org/TR/html4/frameset.dtd"> would be the one to use, seeing as how im using HTML and frames...

02-18-2008, 07:19 AM
There are some issues with using frames, have a look at Why are frames so evil? (http://www.html-faq.com/htmlframes/?framesareevil). BTW why did you choose frames for your layout?

02-19-2008, 10:28 PM
as i said before, "The only way i can get what i want.. ...NOT using iframes is by usuing PHP's include thing, and i REALLY REALLY hate php, because i CANT use notepad and Browser for testing it."

If the menu changes constantly, insted of updating EVERY SINGLE PAGE, use iframes and that way you update ONE file insted of many.

and with why frames are evil...
Bookmarking - it's not that many pages in, to get to, say, high school lunch menu. Just 2 clicks.
Search engines - If someone were to go to body.html and not see the navigation, i used a code that in the event this happens, it redirects to index.
Printing - There's nothing to print at the moment, and if there is something to print, I can have it open in a new window for printing purposes.
Usability- there shouldnt be any scroll bars at the moment, as the content fits on the screen.