Why are IE and Safari different than Netscape,Firefox,Camino? Trying to design web sites but keep running into a wall. When previewing in IE or Safari, my mouseovers cause my animated gif on the same page to turn into a blank box with the picture icon in the center. This DOES NOT happen in the aforementioned browsers. Also I have a problem with WindowsXP, it keeps WARNING me that there is active content that could do something to computer. What the heck, is going on? I am new to designing and producing web sites so any information would be welcome. I only use Macs, so this process of making sure it works for the darkside users really bugs me.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Why are IE and Safari different than Netscape,Firefox,Camino?
- Thread starter Dane D.
- Start date
- Sort by reaction score
Some code would be great. I'm going to make a suggestion, even though I think something else is also not right.
For rollovers, they are not generally loaded until the user moves his mouse over them, at which point the browser will ask the server for the file of the rollover image and it will began downloading (time delay). You might try preloading them or at the very least, make sure your rollovers are that big.
As for the windows xp warning, I think that you have included some type of activex control on your page, which might actually explain both errors.
For rollovers, they are not generally loaded until the user moves his mouse over them, at which point the browser will ask the server for the file of the rollover image and it will began downloading (time delay). You might try preloading them or at the very least, make sure your rollovers are that big.
As for the windows xp warning, I think that you have included some type of activex control on your page, which might actually explain both errors.
IE uses the proprietary MSHTML rendering engine.
Safari, Konquerer and others use the KHTML rendering engine.
Mozilla, FireFox, Netscape, and Camino use the Gekko rendering engine.
KHTML and Gekko try to follow the standards so they're similar, but MSHTML is the most messed up usually.
Safari, Konquerer and others use the KHTML rendering engine.
Mozilla, FireFox, Netscape, and Camino use the Gekko rendering engine.
KHTML and Gekko try to follow the standards so they're similar, but MSHTML is the most messed up usually.
IE, Opera, Avant, AOL for Windows and MSN all use the IE (MSHTML) engine. This is the most popular engine and the easiest to code but for advanced coders or professional websites, so much more can go wrong. If your website works in IE, 70% of the computer world will see a perfect website. IE does not display CSS or PNGs correctly. IE 7 will fix these issues.
Mozilla, Netscape, Camino, Firefox, AOL for Mac, and all these "open source-mozilla/netscape browsers" use the Netscape Gecko engine. This is the most advanced engine for websites and little can go wrong with coding because these browsers are smart and can detect what the coding is USUALLY supposed to be. If a website is perfect in the Gecko engine, the MSHTML IE engine may not display the websites properly.
Safari and other "Apple Only" browsers utilize the KHTML engine, an engine which is sometimes critisised by users because it is the least advanced engine. It is better than the MSHTML engine in some ways but overall it is unsuccessful and a lame attempt to fight microsofts browser. However, it is always advancing and currently little behind Microsofts HTML engine. Safari 2.0 MAY have made it better than MSHTML by upgrading KHTML database, etc.
Sites that display a button for "Taking Back The Web" are usually designed for the Gecko engine. Websites that say "Made for Internet Explorer 5.5+" are, well its self-explanatory, and websites that say "Made on a Mac" are USUALLY KTHML compliant.
W3.org has a coding checker which will check the coding of your website and tell you how to fix it so it is a "universal website" for every browser. Life would be easier if everyone used Firefox/Camino.
Mozilla, Netscape, Camino, Firefox, AOL for Mac, and all these "open source-mozilla/netscape browsers" use the Netscape Gecko engine. This is the most advanced engine for websites and little can go wrong with coding because these browsers are smart and can detect what the coding is USUALLY supposed to be. If a website is perfect in the Gecko engine, the MSHTML IE engine may not display the websites properly.
Safari and other "Apple Only" browsers utilize the KHTML engine, an engine which is sometimes critisised by users because it is the least advanced engine. It is better than the MSHTML engine in some ways but overall it is unsuccessful and a lame attempt to fight microsofts browser. However, it is always advancing and currently little behind Microsofts HTML engine. Safari 2.0 MAY have made it better than MSHTML by upgrading KHTML database, etc.
Sites that display a button for "Taking Back The Web" are usually designed for the Gecko engine. Websites that say "Made for Internet Explorer 5.5+" are, well its self-explanatory, and websites that say "Made on a Mac" are USUALLY KTHML compliant.
W3.org has a coding checker which will check the coding of your website and tell you how to fix it so it is a "universal website" for every browser. Life would be easier if everyone used Firefox/Camino.
Mechcozmo said:But you're gonna have to wait a few years for it... and I hear it breaks HTML rendering.
You might not have to wait so long as you think. In response to the success of Firefox Microsoft announced recently that they would be bringing forward the release of IE7 (previously it was going to release along with Longhorn). Beta's should be out this summer.
witness said:
Keyword: "should"
Longhorn was also previously due out in 2003... then 2004... then 2005... and here we are. I don't expect that they'll push the date further, but frankly, I wouldn't be at all surprised if they did.
Some advice here is on spot on while others are a bit off.
Opera does NOT use MSHTML as its rendering engine. It uses it's own in-house built rendering engine and the engine is the same across all platforms Opera is built for.
Internet Explorer (IE) for Windows uses the MSHTML rendering engine.
IE for Mac used a different rendering engine than MSHTML.
Netscape, Mozilla, FireFox, Camino etc. use Gecko
Safari uses a branch of KHTML. Konqueror (linux program) uses KHTML as well but don't expect things to be 100% the same in Safari and Konq. Not all of the changes and enhancements made in one will make it into the other.
Opera does NOT use MSHTML as its rendering engine. It uses it's own in-house built rendering engine and the engine is the same across all platforms Opera is built for.
Internet Explorer (IE) for Windows uses the MSHTML rendering engine.
IE for Mac used a different rendering engine than MSHTML.
Netscape, Mozilla, FireFox, Camino etc. use Gecko
Safari uses a branch of KHTML. Konqueror (linux program) uses KHTML as well but don't expect things to be 100% the same in Safari and Konq. Not all of the changes and enhancements made in one will make it into the other.
Actually, that's not 100% correct. Safari and other "Apple Only" browsers actually use WebCore, which is derived from KHTML, and has some things KHTML doesn't.dotdotdot said:
The only pure KHTML browser I know of is Konqueror. KHTML also has some things that haven't yet made it into WebCore.
Due to Apple's handling of sending WebCore updates to the KHTML developers, changes made in KHTML are FAR more likely to make it into WebCore than WebCore changes are likely to make it into KHTML.