Brandon Oto wrote:
> This isn't so much a finalized make-sure-it's-okay check, as I know there
> are bugs... it's a let-me-know-what's-wrong check, as I haven't a clue
> what's going on outside of my personal browser.
> http://berkeleyhigh.org/design/cb.html (CSS at:
> http://berkeleyhigh.org/design/style.css )
> And take a gander, I'd be glad. Two things: (1) That entire design was
> concocted and coded within about six hours, all after midnight; and (2) It's
> not done. So there's some weird stuff, and you don't need to point out the
> really glaring problems like missing alt attributes or the lack of a title.
> However, any other problems I WOULD like to know about.
Post-midnight coding is always the most interesting kind. ;-|
The bottom bar problem is easily fixed; just move #foot down out of
#content, to the end of #wrapper. Than looks fine in the Win browsers.
(don't forget to rewrite the selector, like I did)
The #header problem is probably mostly bad css syntax. You have
constructions like 'a:visited.nav' and '#first:hover', which are
not kosher. The first should be 'a.nav:visited', and the second,
I'm not as sure of. I do know that IE/win only obeys pseudo-elements
directly on links, at present.
"What the world needs is a good bug ring"--Big John
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.