Bug 9017

Summary: Weather2.css incorrectly treated as JavaScript file @ www.live.com
Product: WebKit Reporter: Geoffrey Garen <ggaren>
Component: Page LoadingAssignee: Anders Carlsson <andersca>
Status: RESOLVED FIXED    
Severity: Normal CC: sjoerdmulder
Priority: P2    
Version: 420+   
Hardware: Mac   
OS: OS X 10.4   
URL: http://www.live.com
Bug Depends on:    
Bug Blocks: 6628, 7788    
Attachments:
Description Flags
Patch mjs: review+

Geoffrey Garen
Reported 2006-05-20 14:18:58 PDT
1. Navigate to www.live.com 2. --> JS Console: SyntaxError: Parse error for Weather2.css gdb confirms that the file is treated as a CachedScript instead of a CachedCSSStyleSheet.
Attachments
Patch (17.81 KB, patch)
2006-05-23 08:49 PDT, Anders Carlsson 		mjs: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Geoffrey Garen
Comment 1 2006-05-20 14:59:41 PDT
Strangely, it looks like the JS code creates a script element to load the CSS file: URL: "http://www.live.com/1.0.7.122/gadgets/Weather/Weather2.css" (gdb) p this->Node::toString(exec).ascii() $44 = 0x138d9c00 "\n{\n el = document.createElement(\"script\");\n el.onreadystatechange = doCallback;\n el.src = o.url;\n if (!Web.Browser.isIE())\n {\n el.readyState = \"loaded\";\n doCallback();\n }\n}" So the question is, why does the JS code take this path in Safari but not FF? Or does FF just know that CSS is CSS, even if it's loaded into a script element? (Seems unlikely.)
Geoffrey Garen
Comment 2 2006-05-22 22:31:20 PDT
Anders mentioned on IRC that the script gets confused because we lack support for namespace attributes.
Anders Carlsson
Comment 3 2006-05-23 08:49:43 PDT
Created attachment 8482 [details] Patch This patch makes us match Firefox in terms of how getAttribute/setAttribute etc work with attributes that have prefixes
Maciej Stachowiak
Comment 4 2006-05-23 09:12:48 PDT
Comment on attachment 8482 [details] Patch r=me
Anders Carlsson
Comment 5 2006-05-28 00:47:06 PDT
*** Bug 7677 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.