Comment #24 on issue 7448 by [email protected]: CSS and JS files with
MIME Type text/plain should still apply
http://code.google.com/p/chromium/issues/detail?id=7448
For what its worth, Firefox and WebKit apply the exact same content-type
restrictions to CSS:
Firefox (nsCSSLoader.cpp):
PRBool validType = contentType.EqualsLiteral("text/css") ||
contentType.EqualsLiteral(UNKNOWN_CONTENT_TYPE) ||
contentType.IsEmpty();
WebKit (CachedCSSStyleSheet.cpp):
return mimeType.isEmpty() || equalIgnoringCase(mimeType, "text/css") ||
equalIgnoringCase(mimeType, "application/x-unknown-
content-type");
So it really seems we should just update our content-sniffing layer to pass
back the same data.
In the case of Safari we are seeing it pass "text/css" (which abarth
suggests could be a sniff by extension), it should be seen
what Firefox is doing.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
