Bug 9017 – Weather2.css incorrectly treated as JavaScript file @ www.live.com

• Status: RESOLVED
• Resolution: FIXED
• Component: Page Loading

[Geoffrey Garen]

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.

[Geoffrey Garen]

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]

Anders mentioned on IRC that the script gets confused because we lack support for namespace attributes.

[Anders Carlsson]

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 on attachment 8482 [details]
Patch

r=me

[Anders Carlsson]

*** Bug 7677 has been marked as a duplicate of this bug. ***