Updates:
Status: Fixed
Owner: m...@chromium.org
Comment #42 on issue 7448 by aba...@chromium.org: CSS and JS files with
MIME Type text/plain should still apply
http://code.google.com/p/chromium/issues/detail?id=7448
The fix is in http://trac.webkit.org/changeset/42322. We can
Comment #41 on issue 7448 by aba...@chromium.org: CSS and JS files with
MIME Type text/plain should still apply
http://code.google.com/p/chromium/issues/detail?id=7448
Getting close upstream. We're talking tests now.
--
You received this message because you are listed in the owner
or CC fiel
Comment #39 on issue 7448 by m...@chromium.org: CSS and JS files with MIME
Type text/plain should still apply
http://code.google.com/p/chromium/issues/detail?id=7448
Issue 6465 has been merged into this issue.
--
You received this message because you are listed in the owner
or CC fields of th
Updates:
Labels: Waiver
Comment #38 on issue 7448 by j...@chromium.org: CSS and JS files with MIME
Type text/plain should still apply
http://code.google.com/p/chromium/issues/detail?id=7448
(No comment was entered for this change.)
--
You received this message because you are listed i
Comment #37 on issue 7448 by aba...@chromium.org: CSS and JS files with
MIME Type text/plain should still apply
http://code.google.com/p/chromium/issues/detail?id=7448
Having trouble coordinating with upstream about how to implement the
WebCore side of
this change. I'll keep this bug update
Comment #36 on issue 7448 by bugdro...@chromium.org: CSS and JS files with
MIME Type text/plain should still apply
http://code.google.com/p/chromium/issues/detail?id=7448
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=12739
Comment #35 on issue 7448 by aba...@chromium.org: CSS and JS files with
MIME Type text/plain should still apply
http://code.google.com/p/chromium/issues/detail?id=7448
Here's the chrome side of the change (doesn't do much until upstream work
is done):
http://codereview.chromium.org/55049
Comment #34 on issue 7448 by aba...@chromium.org: CSS and JS files with
MIME Type text/plain should still apply
http://code.google.com/p/chromium/issues/detail?id=7448
Upstream patch in https://bugs.webkit.org/show_bug.cgi?id=24904
--
You received this message because you are listed in the ow
Updates:
Labels: -Type-Bug -has-regression-info
Comment #30 on issue 7448 by jasn...@chromium.org: CSS and JS files with
MIME Type text/plain should still apply
http://code.google.com/p/chromium/issues/detail?id=7448
(No comment was entered for this change.)
--
You received this messa
Comment #26 on issue 7448 by w...@chromium.org: CSS and JS files with MIME
Type text/plain should still apply
http://code.google.com/p/chromium/issues/detail?id=7448
Unfortunately we download something with application/x-unknown-content-type
in the main frame.
I will build Firefox and inspect
Comment #25 on issue 7448 by aba...@chromium.org: CSS and JS files with
MIME Type text/plain should still apply
http://code.google.com/p/chromium/issues/detail?id=7448
What happens if you load something with application/x-unknown-content-type
in the
main frame? If it's displayed as text, we
Comment #24 on issue 7448 by ero...@chromium.org: 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):
P
Comment #23 on issue 7448 by aba...@chromium.org: CSS and JS files with
MIME Type text/plain should still apply
http://code.google.com/p/chromium/issues/detail?id=7448
Regarding ACID 3: That's unfortunate. I wonder if the authors of that test
evaluated
the Web compatibility impact of this t
Updates:
Status: Assigned
Owner: w...@chromium.org
Comment #16 on issue 7448 by s...@chromium.org: CSS and JS files with MIME
Type text/plain should still apply
http://code.google.com/p/chromium/issues/detail?id=7448
(No comment was entered for this change.)
--
You received th
Updates:
Status: wt
Comment #15 on issue 7448 by s...@chromium.org: CSS and JS files with MIME
Type text/plain should still apply
http://code.google.com/p/chromium/issues/detail?id=7448
(No comment was entered for this change.)
--
You received this message because you are listed in th
Updates:
Labels: -Area-Compat Area-BrowserBackend
Comment #14 on issue 7448 by j...@chromium.org: CSS and JS files with MIME
Type text/plain should still apply
http://code.google.com/p/chromium/issues/detail?id=7448
(No comment was entered for this change.)
--
You received this messag
Updates:
Labels: -Pri-2 Pri-1
Comment #13 on issue 7448 by j...@chromium.org: CSS and JS files with MIME
Type text/plain should still apply
http://code.google.com/p/chromium/issues/detail?id=7448
(No comment was entered for this change.)
--
You received this message because you are li
Comment #12 on issue 7448 by m...@chromium.org: CSS and JS files with MIME
Type text/plain should still apply
http://code.google.com/p/chromium/issues/detail?id=7448
Here is the http response of the problematic css reference:
HTTP/1.1 200 OK
Last-Modified: Fri, 20 Feb 2009 21:23:28 GMT
Accept
Updates:
Summary: CSS and JS files with MIME Type text/plain should still apply
Status: Available
Owner: ---
Comment #11 on issue 7448 by j...@chromium.org: CSS and JS files with MIME
Type text/plain should still apply
http://code.google.com/p/chromium/issues/detail?id=7
19 matches
Mail list logo