Kim,

Do you understand that some of us do not speak a foreign language? I don’t want to claim ignorance _ but when I browse it is the only time I can recollect being a browser. :)

Seems like a non-issue to me. The Church sites have always worked well with Microsoft IE as well as Netscape, Opera and Foxfire/Mozella. A few tweaks might be needed to the settings page of some browsers; e.g., Opera’s “Server Settings”, etc. (I have not tried Netscape’s recent versions.)

I’ve used several browsers with the ward sites, lds.org, ldscatalog.com, familysearch.com, etc. All with success.

You’ll never find “the universal browser” that works with every site in the WWW world. A nice idea, but an idea that is will always be just that…a good idea that is always a few revisions away. The same is true of web sites. No site can be coded to insure it will work with every browser and every browser’s settings

Roger

“The Church sites have always worked well with Microsoft IE as well as Netscape, Opera and Foxfire/Mozella (sic)”

Except, at least, for the first four months of this year when anyone using a non-IE browser could not place an order on ldscatalog.com.

“No site can be coded to insure it will work with every browser and every browser’s settings”

Depends on what you mean by ‘work’. Every site I build works in every browser in every situation (even cellphones) in that the content is made available and the site is easily navigable. Do they look the same in every browser in every situation? No. But I do not consider aesthetics to be exclusively dependent on how something functions.