Bug 15593
| Summary: | "CMSCreateDataProviderOrGetInfo : Invalid colorspace type" on www.whatwg.org | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | David Kilzer (:ddkilzer) <ddkilzer> |
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | esprehn, ian |
| Priority: | P2 | Keywords: | NeedsReduction |
| Version: | 523.x (Safari 3) | ||
| Hardware: | Mac | ||
| OS: | OS X 10.4 | ||
| URL: | http://www.whatwg.org/specs/web-apps/current-work/multipage/section-sql.html#sql | ||
David Kilzer (:ddkilzer)
* SUMMARY
I see the following error message on the console when loading the URL above from the www.whatwg.org web site:
CMSCreateDataProviderOrGetInfo : Invalid colorspace type
Not sure whether this is a WebKit issue or invalid CSS/HTML on the whatwg.org site.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
David Kilzer (:ddkilzer)
According to this Google hit, it's coming from an internal Mac OS X framework:
http://lists.apple.com/archives/cocoa-dev/2006/Nov/msg00261.html
I can't figure out which image is causing the issue, though, since loading images individually that are used on the page produces no such warning message:
http://www.whatwg.org/images/logo
http://www.whatwg.org/images/WD
Ian 'Hixie' Hickson
Is it one of the images in the stylesheet, or maybe the favicon?
David Kilzer (:ddkilzer)
(In reply to comment #2)
> Is it one of the images in the stylesheet, or maybe the favicon?
Heh. It's the favicon. I placed it in /Library/WebServer/Documents/favicon.ico and started Apache on my Tiger installation, and I got the same console message. (Loading a page locally before copying the favicon there did not produce the console message.) Note that clicking on the URL will download the file instead of opening it in Safari/WebKit (Bug 15640):
http://www.whatwg.org/images/icon
David Kilzer (:ddkilzer)
Once Bug 15640 is fixed, it would be nice to know if loading the WhatWG favicon in the browser as an image document produces the same console message.
Elliott Sprehn
The referenced bug has long since been fixed and this issue doesn't reproduce anymore.