[Webkit-unassigned] [Bug 154189] New: Adaptive Stream Video Throws DOM Exception 18 When Uploaded to a Texture

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Feb 12 13:04:45 PST 2016


            Bug ID: 154189
           Summary: Adaptive Stream Video Throws DOM Exception 18 When
                    Uploaded to a Texture
    Classification: Unclassified
           Product: WebKit
           Version: Safari 9
          Hardware: Macintosh
                OS: OS X 10.11
            Status: NEW
          Severity: Critical
          Priority: P2
         Component: Canvas
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: jonobrandel at gmail.com
                CC: dino at apple.com

Created attachment 271208
  --> https://bugs.webkit.org/attachment.cgi?id=271208&action=review
Screenshot of Chrome (left) and Safari (right) behavior.

It's really common practice to use a <video /> element to play some content. Less frequent, but still very useful is to take that elements content and put it in a canvas. In this example I'm using the <video /> element, but pointing it to a stream via the library Shaka Player (https://github.com/google/shaka-player). I expect to be able to take the pixel information of the <video /> element at a given time and reproduce it / manipulate it on a canvas element. However, in Safari 9 this is not the case. When implementing with WebGL I get a DOM Exception 18 error. When implementing with canvas I get no error, but also no image. The assets are same domain, so I don't think there are CORS issues present. Below are links that reproduce this behavior:

1) Go to either:

Example using canvas via texImage2D in WebGL (with Three.js):

Example using canvas via drawImage directly:

2) Click the "Play Button" on the <video /> element.
3) The video starts playing

When going through these steps in Google Chrome when I hit play I see 2 videos on the page. One that is the <video /> element and one that is the <canvas /> element that reproduces the pixel information of the source <video /> element. I expect Safari to behave similarly.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160212/d205e3a4/attachment.html>

More information about the webkit-unassigned mailing list