Bug 8197 - REGRESSION: Realm status is not displayed at worldofwarcraft.com
Summary: REGRESSION: Realm status is not displayed at worldofwarcraft.com
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: XML (show other bugs)
Version: 420+
Hardware: Mac OS X 10.4
: P1 Normal
Assignee: Nobody
URL: http://www.worldofwarcraft.com/realms...
Keywords: Regression
Depends on: 7838
Blocks:
  Show dependency treegraph
 
Reported: 2006-04-05 10:20 PDT by Edward Keech
Modified: 2006-05-11 10:10 PDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Edward Keech 2006-04-05 10:20:57 PDT
Doesn't display the table where the server's are. Safari works fine.
Comment 1 Darin Adler 2006-05-07 20:00:47 PDT
Alexey changed the component to XML, because the error that prevents the page from working is "xslDoc.load" not working. I believe that this worked before because we didn't have XSLTProcessor, and it's failing now because the document returned by XSLTProcessor.getDomDocument does not have a load function. Here's the code:

        tableProcessor = new XSLTProcessor();
        var xslDoc = Sarissa.getDomDocument();
        xslDoc.async = false;
        xslDoc.load('/realmstatus/realmstatus.xsl');
        tableProcessor.importStylesheet(xslDoc);
Comment 2 Dave Hyatt 2006-05-07 20:08:39 PDT
Isn't the load method from DOM 3 Load and Save?  I don't think we've ever supported it.
Comment 3 Dave Hyatt 2006-05-07 20:09:17 PDT
Or is this their own JS document wrapper and not a real DOM document?
Comment 4 Alexey Proskuryakov 2006-05-08 02:59:48 PDT
Sarissa provides its own load(), but only if window.XMLDocument is defined, see bug 7838.

else{ /* end IE initialization, try to deal with real browsers now ;-) */
   if(_SARISSA_HAS_DOM_CREATE_DOCUMENT){
        if(window.XMLDocument){
...
            XMLDocument.prototype.load = function(sURI) {
Comment 5 Alexey Proskuryakov 2006-05-11 10:04:04 PDT
The patch in bug 7838 did fix this. The page is still not 100% OK, though, see bug 8852.