Bug 55990
| Summary: | Web Inspector: unknown cursor mime never suggested | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | John A. Bilicki III <jab_creations> |
| Component: | Web Inspector (Deprecated) | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | apavlov, bweinstein, joepeck, keishi, loislo, pfeldman, pmuellr, rik, yurys |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://www.jabcreations.com/ | ||
John A. Bilicki III
When WebKit encounters cursors it spawns a mime/media type error however it does not suggest what the correct mime is. I have not been able to find any mime type that WebKit deems appropriate hence this bug report.
The console error message...
"Resource interpreted as Image but transferred with MIME "...
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
John A. Bilicki III
The following resolves this issue...
.htaccess
AddType image/vnd.microsoft.icon .cur .ico
This should be clarified in the error message, "Resource interpreted as Image but transferred with MIME type application/octet-stream." so people will have some clue as how to resolve the issue.
Alexander Pavlov (apavlov)
(In reply to comment #1)
> The following resolves this issue...
>
> .htaccess
> AddType image/vnd.microsoft.icon .cur .ico
>
> This should be clarified in the error message, "Resource interpreted as Image but transferred with MIME type application/octet-stream." so people will have some clue as how to resolve the issue.
Multiple MIME types can map to a single resource category, so it is impossible for WebKit to figure out which MIME type it should be. Otherwise MIME types would not be necessary.
Alexander Pavlov (apavlov)
Closing as per Comment #2.
John A. Bilicki III
This bug shouldn't be closed, the correct media type/mime should be suggested otherwise it's pointless for the console to mention it.
Alexander Pavlov (apavlov)
(In reply to comment #4)
> This bug shouldn't be closed, the correct media type/mime should be suggested otherwise it's pointless for the console to mention it.
First off, the correct "media type" is already mentioned in the console message ("...interpreted as Image...").
Now, if "foo.js" has been transferred with "application/octet-stream", which mime-type is "correct"? "application/javascript", "application/x-javascript", "text/javascript1.2", "text/javascript1.3", or some other?
WebCore makes a best guess attempt based on the content sniffing, which does not guarantee the correct result (and even could be leveraged to run XSS attacks.)
What kind of mime-type suggestion would you expect for "foo.js" transferred with "application/octet-stream"?
John A. Bilicki III
Unfortunately "interpreted as Image" doesn't help in this case. If guessing specific media types is too excessive then perhaps it would be better idea to have the console link to a page documenting file and media types?