jasonl Posted October 30, 2004 Share Posted October 30, 2004 I am designing my site with Frontpage. Everything seems to be working ok now but my tables are drawing very differently when viewed with Mozilla vs when the site is viewed with IE. Any tips, suggestions on how I might be able to make this pesky problem go away? Thanks ahead of time! Quote Link to comment Share on other sites More sharing options...
borfast Posted October 30, 2004 Share Posted October 30, 2004 Don't use frontpage. FP writes non-standard, IE-only code. That's why it appears OK in IE but breaks on Mozilla - and I bet it will break on other browsers as well. Quote Link to comment Share on other sites More sharing options...
jasonl Posted October 30, 2004 Author Share Posted October 30, 2004 Well, I have most my site constructed in Frontpage at them moment. What would you suggest? Dreamweaver? Quote Link to comment Share on other sites More sharing options...
TCH-Bruce Posted October 31, 2004 Share Posted October 31, 2004 I use a plain text editor and sometimes HTML-kit Quote Link to comment Share on other sites More sharing options...
Deverill Posted October 31, 2004 Share Posted October 31, 2004 It's been a long time since I used FP but there may be some options you can set to make it more compliant. Quote Link to comment Share on other sites More sharing options...
TCH-Rob Posted October 31, 2004 Share Posted October 31, 2004 Well, I have most my site constructed in Frontpage at them moment. What would you suggest? Dreamweaver? The can of worms has now been opened. You have made most of your site in FP? Finish it in FP then. Make it all the same, just remember using a MS product makes it look good in IE (an MS product) but has disadvantages in other browsers. DW, may be the same. No two browsers are going to display the same. If you are almost done then finish it and go back and edit the smaller things with something else. I prefer text editors when fine tuning my site but I often use a HTML editor to start because I cant see it in my head, I need a jump start. You are going to get many replies here because there are as many preferences here as to what to use as there are seconds in a year. Quote Link to comment Share on other sites More sharing options...
TCH-Thomas Posted October 31, 2004 Share Posted October 31, 2004 Sorry Jason, I have nothing to say but CuteSite Builder (read more here). You are going to get many replies here because there are as many preferences here as to what to use as there are seconds in a year. This thread is gonna get 31 556 926 answers then? Quote Link to comment Share on other sites More sharing options...
TCH-Don Posted October 31, 2004 Share Posted October 31, 2004 One thing you might try when designing with tables is to turn on the borders to help see where the tables are and how they are affected by different browsers. Quote Link to comment Share on other sites More sharing options...
Deverill Posted November 1, 2004 Share Posted November 1, 2004 I'm thinking along the same lines as Rob. Finish your site in FrontPage which looks good on IE. Then spend your time learning HTML and what's IE-specific. The knowledge of HTML will prove invaluable to you and you can rather quickly find the key troublespots making it not look right in other browsers. Use a text editor and you'll not only get the most out of the exercise in knowledge but you'll also be able to make precise changes. Just switching to Dreamweaver for an existing site will not "fix" the problems FP caused. Quote Link to comment Share on other sites More sharing options...
TCH-Bruce Posted November 1, 2004 Share Posted November 1, 2004 And you may want to familiarize yourself with validating your web pages. http://validator.w3.org/ The validator can also help spot problems. Quote Link to comment Share on other sites More sharing options...
Deverill Posted November 1, 2004 Share Posted November 1, 2004 And you may want to familiarize yourself with validating your web pages. Excellent point, Bruce. If a website passes the validator it will probably be very close to generic code that everyone understands. The validator should identify all proprietary (IE Only) code too. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.