This bug is also in Radar as <rdar://4213393> Very little shows in Safari. A lot more in FireFox. Side-by-side screenshot attached. ------------------------------------------- <GMT20-Dec-2005 00:02:12GMT> Geoff Garen: JavaScript errors: - Msn.Runtime.Init() is called, but Msn.Runtime is undefined. It looks like Msn.Runtime, Msn.Bindings, and some others declared in msncore.js aren't being evaluated properly. - window.attachEvent is called, but Safari doesn't implement it. (That's not the key to this bug, since the attached event is only a debugging routine, which doesn't impact the layout of the page.)
Created attachment 5744 [details] screenshot
researching a bit further leads to finding: http://start.com//extern/wsfw/compat/0.072605.0/msncompat.js which should provide a mozilla compat layer, unfortunately we aren't seen as mozilla, due to this code used to detect it: "(typeof HTMLDocument!='undefined')" -> false for safari
Filed bug 7838 about supporting window.HTMLDocument and related items.
Darin and Maciej and I talked this over and concluded that adding support for the Mozilla compatibility layer, which uses the DOM, is a better approach than implementing IE's extensions to the DOM. So let's try that approach first.
This appears to at least display now, but some things don't work. For example, entering a city name fails.
(In reply to comment #0) > - window.attachEvent is called, but Safari doesn't implement it. (That's not the key to this bug, since the > attached event is only a debugging routine, which doesn't impact the layout of the page.) Added Bug 6598 to depends-on list for tracking purposes.
(In reply to comment #5) > This appears to at least display now, but some things don't work. For example, > entering a city name fails. Maybe we should retitle this bug then? The thing originally reported here is fixed.
The only failure I could find was that I couldn't set the city -- I think that's a new bug and not this one. Everything else I tried worked.
I am testing <http://www.start.com> now, not <http://www.start.com/3>; everything seems to work fine. I think this should be moving off the hit list, unless someone finds I'm mistaken and reports a specific problem.