|
| |
|
|
gorilla
Posts: 2974
From: Denmark
Status: offline
 |
RE: More on invalid code . . . - 6/12/2001 20:43:00
Gil - many thanks for spotting my mistake - have edited accordingly.Crispy - I'd love to be able to use just css and when I get my head around the hacks I probably will but until then I'm with crispy on this one - tables still rule for some things. I like Brian's approach - gawd bless server logs where would we be without 'em? ------------------
Hope this helps :-)
Gorilla
aka Mark Saunders
http://www.computerdriving.com marksaunders@techie.com
|
|
|
|
Crispy
Posts: 59
From: Tampa, FL USA
Status: offline
|
RE: More on invalid code . . . - 6/12/2001 20:51:00
You have to make the break somewhere. In my case, I stopped designing for version 3.0 browsers when they dropped below 3% in the server log. I still get occasional complaints from them because I went to CSS and em units for sizing my fonts.Have you ever seen text sized with ems on a version 3.0 browser? <gag> Break out your maginifying glasses kids, some older buggy browsers interpret ems as pixels, so if you have your body text sized at .8 em, guess what your user sees? Crispy
| |
|
|
|
Crispy
Posts: 59
From: Tampa, FL USA
Status: offline
|
RE: More on invalid code . . . - 6/14/2001 20:24:00
And one more follow up to this topic of FrontPage generating invalid code, Thomas Brunt pointed out to me in another thread that if FrontPage insists on inserting or re-inserting invalid code after you delete it, you can always use:Insert > Advanced > HTML This, in affect, hard codes the HTML you enter and FrontPage won't screw with it. This can be a very valuable feature if you are trying to eliminate code that doesn't validate W3C. Crispy
| |
|
|
|
Crispy
Posts: 59
From: Tampa, FL USA
Status: offline
|
RE: More on invalid code . . . - 6/29/2001 20:40:00
In my continuing quest to write valid HTML while still using FrontPage, I have recently incorporated HomeSite as my secondary page editor. I now have a system worked out pretty well. I go ahead and create the page in FrontPage as usual, then as a last step I will do an "open with" and select HomeSite. At this time I work all the kinks out of the code with HomeSite's built in validator and HTML Tidy, which is built in. Yes I know I'm being picky and am going to a lot of trouble that may or may not mean anything in the long run, but HTML Tidy cleans up FrontPage's droppings very nicely and the end result is a W3C compliant web page, which can't be a bad thing, can it? Great! Now I only have about 900 more pages to go. sigh... Anyway, just wanted to share. Crispy
| |
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
 Locked w/ New Messages |
 Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts
|
|
|
Printable Version 
