Summary: | HTML5 Conformance Test failure: approved/video/video_003.htm | ||
---|---|---|---|
Product: | WebKit | Reporter: | David Kilzer (:ddkilzer) <ddkilzer> |
Component: | Media | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED WORKSFORME | ||
Severity: | Normal | CC: | abarth, eric.carlson, simon.fraser |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://test.w3.org/html/tests/approved/video/video_003.htm | ||
Bug Depends on: | |||
Bug Blocks: | 48575 |
Description
David Kilzer (:ddkilzer)
2010-10-28 16:43:26 PDT
@abarth: Does browser mime type sniffing behavior come into play here? Just wondering if the test is expecting the application/octet-stream MIME type to be sniffed, or whether it's testing whether the browser will dump off bytes to the "media engine" with a MIME type of application/octet-stream. Video media type handling is a train wreck. It's unclear what the best behavior is. http://test.w3.org/html/tests/approved/video/video_003.htm is a bogus test. The spec says: The canPlayType(type) method must return the empty string if type is a type that the user agent knows it cannot render or is the type "application/octet-stream" In other words if MUST return "" if the type is "application/octet-stream". The test, however, *fails* if it returns "" : if (vid.canPlayType("application/octet-stream") != "") { passTest(); } WebKit returns "" for "application/octet-stream": > vid.canPlayType("application/octet-stream") "" If there's a bug in the test, this should be reported against the test suite. This test has been removed from the test suite. |