Summary: | site displays completely wrong (konq3, firefox, etc work fine) | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | Mihai RUSU <dizzy> |
Component: | general | Assignee: | Konqueror Developers <konq-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | andresbajotierra, maksim |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Mihai RUSU
2008-08-21 10:03:51 UTC
Using KDE 4.1.1 (KDE 4.1.0 (4.1 >= 20080722)) (KDEmod) in ArchLinux i686: I can confirm this. Seems like the CSS isn't loaded. For some reason we get mimetype as ":", which isn't a valid stylesheet mimetype and hence gets it ignored in strict mode. The server doesn't send anything (bad server!) Oh, actually is does: Content-Type: : so KIO is right here. Now I need to figure out whether other browsers are parsing this differently (hmm, may be via XHR?), or if something can override the mimetype check... Thanks for the workaround. So you are saying that tho the css files are php documents (so their contents is probably dynamically generated) they should still come with Content-Type: text/css right? I suppose they need to use header() PHP function or something similar :) You're welcome. And yes, stylesheets served to web pages in strict mode have to have the mimetype text/css, or no mimetype at all. Thing is, the server actually sends a malformed content-type header altogether. That it's PHP on the server end doesn't matter, since content-type describes the type of the data we get / how we should handle it --- it makes no difference to the displaying application if it was hand-coded or generated by PHP or Perl or Rails, or ASP or whatever. |