Bug 13546

Summary: MSDN left column never loads. Just says "Loading..."
Product: WebKit Reporter: Robbie Foust <rfoust>
Component: EvangelismAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: ddkilzer, just1gb, markmalone
Priority: P2    
Version: 419.x   
Hardware: Mac (Intel)   
OS: OS X 10.4   
URL: http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqlcommand.aspx

Description Robbie Foust 2007-04-29 18:27:39 PDT
The left column on the msdn library site says "Loading..." and it never actually loads.  Also the resize bar starts on the very left side, but I can easily drag it to resize with no problems.

Example:  http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqlcommand.aspx
Comment 1 Alexey Proskuryakov 2007-04-30 01:37:32 PDT
This works for me in both shipping Safari and TOT when spoofing UA as IE 6 or Mozilla. Apparently, MSDN is sending us broken content; moving to Evangelism.
Comment 2 Alexey Proskuryakov 2007-07-06 13:33:44 PDT
*** Bug 14543 has been marked as a duplicate of this bug. ***
Comment 3 David Kilzer (:ddkilzer) 2007-11-26 13:54:16 PST
This is still an issue.

Comment 4 David Kilzer (:ddkilzer) 2007-11-26 15:37:31 PST
Mark:

In <http://msdn2.microsoft.com/App_scripts/ssmoz.js>, the following piece of JavaScript code appears at the very end of the script (cleaned up for style):

if ( ! document.all ) {
    __loadCompat(window);
    if (window.navigator.userAgent.indexOf('Safari')>=0) {
        _loadSafariCompat(window);
    } else {
        _loadMozillaCompat(window);
    }
}

The 'Safari' code path is basically broken on both Safari 2 (I just tested it) and Safari 3, so it should be removed in favor of the Mozilla code path (which works on both Safari 2 and Safari 3 while spoofing as Mozilla 1.1 and Firefox 2.0.0.2, respectively).

I should note that this works for this particular page on the MSDN site.  Not sure if ssmoz.js is only used for displaying the collapsable tree nav area or whether it's used for other things as well.

Comment 5 David Kilzer (:ddkilzer) 2008-05-16 09:57:47 PDT
This appears to be fixed now.  Tested with Safari 3.1.1 on Mac OS X 10.5.x Leopard.