TBRW css retrofit

Greg Berge · October 19, 2002, 06:58:39 PM

OK, so I've only been behind the standard for what, 4 years?

Anyway, I'm gradually getting it done (as an excuse to learn HomeSite, Dreamweaver MX, and TopStyle), so you may see some interesting stylistic discrepancies for a while. I expect that. But if your Browser starts being unable to resolve elements at all, or loses pages or links, or anything that far below average, please let me know.

If you're not frame-compliant, you're still screwed. Sorry.

Thanks.

Greg Berge · October 24, 2002, 04:59:38 PM

It's complete. Should be perfect, now.

Edit: ha, ha, ha. "Perfect"? I've already had to break a few hundred bones to reset them, so it will be far from perfect for a while yet. But how much effort can it take when it's still strictly static? (Laughs again, hollowly and somewhat distrurbingly.)

Greg Berge · October 24, 2002, 07:31:25 PM

Q for Age or others who are web-savy. Netscape Communicator 4.76 is not responding to the a:hover tag value from my stylesheet. (IE 6.0 does a fine and wonderful job.) Is there a tweak that allows hover actions on tags?

Also, I have no way to test my pages on Mac or UNIX right now. They ought to be fine -- they have been delinted according to , but if anybody wants to test just the top page of tbrw for disasters I'd appreciate it.

Will · October 24, 2002, 09:08:46 PM

[Q]Q for Age or others who are web-savy. Netscape Communicator 4.76 is not responding to the a:hover tag value from my stylesheet. (IE 6.0 does a fine and wonderful job.) Is there a tweak that allows hover actions on tags?[/Q]

Netscape 4.x is generally a stupid browser because it was never great at supporting web standards. As far as I know, the hover tag has never worked in Netscape 4.x. If there's a tweak for it, I don't know what it is.

jtwcornell91 · October 24, 2002, 11:21:12 PM

Netscape 4's problem was not just that it didn't implement things that were in the spec (although it's true that the contemporary version of Lynx had more support for HTML 4.0), but that its stylesheet implementation in general was so broken as to be occasionally worse than no support at all.

jtwcornell91 · October 24, 2002, 11:27:01 PM

http://validator.w3.org/check?uri=http%3A%2F%2Fspiritone.com%2F%7Ekepler%2Ftbrw.html&charset=%28detect+automatically%29&doctype=Inline

Fails because of no DTD line on the frameset page. You should add a

at the beginning. Compare http://validator.w3.org/check?uri=http%3A%2F%2Fslack.net%2F%7Ewhelan%2Ftbrw.cgi&charset=%28detect+automatically%29&doctype=Inline&ss=

CowbellGuy · October 25, 2002, 09:17:05 AM

Yeah, hover tags won't work in Netscape 4. No workaround either. JS image rollovers will, but that's probably not too useful. I wouldn't worry about it. The sooner the last remaining stragglers switch to a real browser, the better.

Greg Berge · October 25, 2002, 12:46:32 PM

John, thanks for the validator link. Any other useful tools for self-teaching DHTML, JavaScript, web development also appreciated.

Age, etc, thanks for the info on 4.x. I always assume it's me; it's nice to know sometimes it's the product.

I "solved" the problem by moving to 7.0. "Whassa behind me is not important."

jtwcornell91 · October 26, 2002, 12:03:58 PM

I wouldn't sweat fancy widgets not working as designed in some browsers; what you should try to avoid is having content which is only visible under some circumstances. (I could rant more on these issues, but I'm sort of occupied at the moment.)