Website works in Firefox not in IE...

[dmmitchell]

Hello, all -

I am making a website for a group I am involved in. I designed it with
Dreamweaver, and tested it in Firefox. Unfortunately, though, I
discovered upon showing other people that it does not appear in IE.

The website address, temporarily, is:

www.umit.maine.edu/~derek.mitchell/index.htm

Please let me know what might fix this. I've been learning as I go,
and cannot figure this one out.

Thank you,
Derek

[Chris F.A. Johnson]

On 2007-10-02, dm********@gmai l.com wrote:

Hello, all -

I am making a website for a group I am involved in. I designed it with
Dreamweaver, and tested it in Firefox. Unfortunately, though, I
discovered upon showing other people that it does not appear in IE.

The website address, temporarily, is:

www.umit.maine.edu/~derek.mitchell/index.htm

Besides following John's advice, remove all the <BR>s, and use <P>
instead. Get rid of fixed widths, too.

<http://cfaj.freeshell. org/testing/umsg.jpg>

--
Chris F.A. Johnson <http://cfaj.freeshell. org>
=============== =============== =============== =============== =======
Author:
Shell Scripting Recipes: A Problem-Solution Approach (2005, Apress)

[David Stone]

In article <47**********@n ews.bluewin.ch> ,
John Hosking <Jo**@DELETE.Ho sking.name.INVA LIDwrote:

dm********@gmai l.com wrote:

I am making a website for a group I am involved in. I designed it with
Dreamweaver, and tested it in Firefox. Unfortunately, though, I
discovered upon showing other people that it does not appear in IE.

Dreamweaver can be a useful tool, but mostly for those who already have
good knowledge of HTML (and CSS). The generation of class names like
.style5 is a sign of some cluelessness. They don't say anything about
the function or meaning of the element they're identifying.

As you have probably learned, testing in only one browser in
insufficient. Test at least in Firefox, IE7, IE6, and Safari. You must
know what platforms or standard software is recommended or required by
UMaine for its students and provided to its employees; make sure those
are covered, too, if different from the above.

The website address, temporarily, is:

www.umit.maine.edu/~derek.mitchell/index.htm

Please let me know what might fix this. I've been learning as I go,
and cannot figure this one out.

Without looking at it too long, my first suggestion is to fix the syntax
errors. Run your page(s) through the W3C's validator at
http://validator.w3.org/ and after you've corrected the errors it finds
the problem may go away "on its own".

Since you are using Dreamweaver, you might as well use some of its
features like page validation and browser compatability checking.
These are accessible through the menus as well as one of the
default toolbars.

I would still suggest using the W3 validators - both the html
and css ones - but the built-in DW tools will catch a lot of stuff
for you first.

I configure my pages in DW to use an external style sheet, so I
don't have to keep re-inventing the wheel. Whenever I create a
style, I give it a meaningful class name, which makes it easier
to access and use elsewhere within the page/site.

[Bergamot]

dm********@gmai l.com wrote:

>
www.umit.maine.edu/~derek.mitchell/index.htm

Besides the advise others have given, learn some more about optimizing
graphics, including when to use jpg vs png (or gif).

12KB for a small picture of text and a line drawing is way too big. It
should be about a 1-2KB png instead of a 12KB jpg.

--
Berg

[John Hosking]

David Stone wrote:

In article <47**********@n ews.bluewin.ch> , John Hosking wrote:

>dm********@gmai l.com wrote:

>>I am making a website for a group I am involved in. I designed it with
Dreamweaver , and tested it in Firefox.

>Without looking at it too long, my first suggestion is to fix the syntax
errors. Run your page(s) through the W3C's validator at
http://validator.w3.org/ and after you've corrected the errors it finds
the problem may go away "on its own".

Since you are using Dreamweaver, you might as well use some of its
features like page validation and browser compatability checking.

I didn't say I was using Dreamweaver. The OP said he is. I think you
replied to the wrong post. Anyway, I wouldn't trust Macromedia or Adobe
to provide a current, correct, and complete validator. Not when I can
get to the W3C's so fast from my browser.

>
I would still suggest using the W3 validators - both the html
and css ones - but the built-in DW tools will catch a lot of stuff
for you first.

Okay, that might be so. My brief experience with Dreamweaver's validator
(in DW MX, I think) led me to think it wasn't as complete as the W3C's,
so I just dropped the attempt to use it. Now I view my page in FF
(anyway) and validate at W3C via the Web Developer toolbar I've added to it.

--
John
Pondering the value of the UIP: http://improve-usenet.org/