Posted By JerryB on 02/21/2008 3:11 PM
Dwight:
Not to divert from my perception that the 'new' MLS forum software has quite a few problems, but doing a Google search on
Internet Explorer compatibility produces 1,440,000 hits. The same search for
Firefox compatibility produces 738,000 hits. Using your suggested test, should I conclude that Safari has the upper hand (as in lower numbers) when it comes to compatibility issues? LOL!! (I would put some smiley faces in here, but don't know how to access them from 'Quick Reply'.
Not to start an argument here, but the first his listed is,
"Don't lose potential revenue from your site due to incompatibility with the Safari browser."
The second hit is similar.
The third opens with,
"Anonymous Coward writes "It seems that everywhere I turn, I feel unwelcome on the Web as a Safari user. There have always been major sites that I could not use (like OldNavy.com), but I ran across many more while doing some shopping this holiday season. What is worse are the sites and services which used to be compatible, no longer work (for example, Nextel's recent "upgrade" renders their Mobile Locator service unusable in Safari and Bank of America's "upgrade" last July removed support for Macintosh Quicken direct connect). This made me wonder: is there currently or should there be a registry of web sites which are not compatible with Safari? Would making such a list public coax these companies into making their services compatible with Macintosh?"
The fourth is a forum where people are sharing their experiences that their web sites aren't compatible with Safari.
The fifth is a site devoted to helping with Safari compatibility for web developers.
The sixth is dev.FCKeditor.net, and states,
"This milestone will be used to group tickets relative to the compatibility of FCKeditor with Safari. Once we'll announce the compatibility, the milestone will not anymore exist, and all Safari bugs will be moved to the normal tickets system.
We are working together with the developers of Safari's core software, named WebKit, to fix both sides. It means that not only FCKeditor must be fixed, but also Safari needs fixes to be able to work properly." The progress bar is at 81% (81% compatibility?).
While I didn't peruse the remaining 387,994 links, to me the evidence suggests some glaring compatibility issues with major corporate sites (BofA).
I'm not trying to knock the Mac or its browser, and I know most Mac users are
"extremely committed" to their Macs and how simply
fabulous they are (

), but I think laying the blame entirely at the feet of MLS when major corporations have the same problems is entirely unreasonable.
Blame where blame is due, and certainly at least some of it belongs with the Safari core code. /DesktopModules/NTForums/themes/mls/emoticons/shocked.gif The fact that IE, Firefox, and other major browsers work is indicative of a problem with Safari. If it doesn't play nice with the rest of the world when the rest of the world plays together just fine, then it's broken regardless of how "correct" it is concerning W3C.
MHO.