Pete Home wrote:
>Thanks Francky,
>I saw the first error and didn't look down the email for the fix!
>
>
Hi Pete,
Glad I've send the safety message!
>There is no missing DIV, I ran it through the validator and got the same
>error, but I do not understand why. I move the fieldset in the form and
>validate down to 1 error.
>
This I don't understand. The html-validator as well as html-Tidy report
this 1 error: a missing </div>. They say it is the #container which
isn't closed, but my experience is that the diagnosis of the validators
is not always right: it can be missing also somewhere else...
In fact, I'm pretty sure it is somewhere in the div-mountains of the
#content part, for in my examples I commented these out, and no error is
coming:
* http://home.tiscali.nl/developerscorner/css-discuss/test-o-gazetteer-5.htm
So brute force: I counted the starting <div ...>'s and the closing
</div>'s ... two times ... and the validators are right: really there
are 99 starting div's and 98 ending div's. :-)
>If I add an extra div at the end, I get different
>errors. I'm not sure why this happens.
>
>
You said, adding a fresh </div> in the end is causing fresh errors: I
don't understand that either.
If I make a new testpage, based on your actual page, with the added #99
ending div, it is reporting no error or warning at all, nor in the
html-editor, nor in html-Tidy:
*
http://home.tiscali.nl/developerscorner/css-discuss/test-fresh-o-gazetteer.htm
Maybe it has something to do with testing the html from your local
server, or with a residue in your cache? - Oh, correction, when I read
this again. [1]
>Anyway, I added a 95% width to the bg0 and bg1 (ooops, forgot the .!) which
>stops the scroll h/bar
>
Not yet in IE, which isn't good in computing %'s... Therefore I applied
a straight 458px solution.
>but still does nothing for the background color.
>
>Regards
>Pete
>
In IE the background color is already coming.
In FF not yet, but over there I see a small bar of the bg0
background-color #CAD4E2 above the "Atlas Gallery" line. So you are
close! :-)
I guess the color is in a containing div which is not stretching because
of some floats inside.
Just back in a moment ...
... and see FF is cooperating:
*
http://home.tiscali.nl/developerscorner/css-discuss/test-fresh-o-gazetteer-color.htm
Now only the venuinfo-class has to be adapted:
*
http://home.tiscali.nl/developerscorner/css-discuss/test-fresh-o-gazetteer-color2.htm
or an other fine tuning which you like.
O, almost forgotten: going back to IE and see what it is playing now!
- Thank you MS, indeed correcting to get rid of an IE gap is needed; but
that's another story... [2] ;-)
Success and greetings,
francky
PS:
Adding <meta http-equiv="imagetoolbar" content="no"> in the head will
prohibit that IE-visitors are seeing this annoying toolbar, when
hovering over an image. Not all IE-owners do know how to find the IE
settings to turn it off. We can help them! :-)
[1]
I first thought you mean: new html-errors > that I don't understand. But
if you mean: errors in the design of the page, I can understand. Adding
a </div> in the end (just to make the # of div's complete) can be no
good, as the missing div is probably somewhere in the middle of the
multi-div content. And adding a </div> in an abitrary place can have
inpredictible effects! - So if you want to sort out the missing </div>,
some more bug hunting is needed...
[2]
The vifiller-class is the culprit: empty div without some <!-- comment
to correct IE --> inside is giving the default line-height in IE. But
also in FF this div is making kinda double borderline above the
"Photography" line.
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
IE7 information -- http://css-discuss.incutio.com/?page=IE7
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
