[Webkit-unassigned] [Bug 44519] New: HTMLMediaElement.canPlayType gives wrong results on the iPhone

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Aug 24 06:10:39 PDT 2010


https://bugs.webkit.org/show_bug.cgi?id=44519

           Summary: HTMLMediaElement.canPlayType gives wrong results on
                    the iPhone
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Other
               URL: http://rakaz.nl/2010/06/problems-with-html5-video-code
                    c-detection.html
        OS/Version: Other
            Status: UNCONFIRMED
          Severity: Critical
          Priority: P2
         Component: Media Elements
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: niels.leenheer at gmail.com


The canPlayType() function gives back wrong information on the iPhone and iPad (tested with iOS 3.2 and 4).

Safari for iOS will report back "probably: for containers that it supports when only a MIME type is specified. This is something that is explicitly discouraged by the specification. When no codecs parameter is present, it should report "maybe" at best.

v=document.createElement('video');
v.canPlayType('video/mp4')
-> probably     // incorrect, should be maybe


When a codecs parameter is present, Safari will strangely report back "maybe" for all MIME types it recognized, regardless of the contents of the codecs parameter. The proper response would be to report back "probably" for supported codecs and an empty string for codecs it doesn’t recognize. 

v=document.createElement('video');
v.canPlayType('video/mp4; codecs="avc1.42E01E"')
-> maybe     // incorrect, should be probably

v=document.createElement('video');
v.canPlayType('video/mp4; codecs="foobar"')
-> maybe     // incorrect, should be ""


This bug makes codec detection impossible on the iPhone and needs to be fixed as soon as possible.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the webkit-unassigned mailing list