[Bug 24560] New: Difference in error handling for video element

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24560

            Bug ID: 24560
           Summary: Difference in error handling for video element
           Product: WHATWG
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML
          Assignee: ian@hixie.ch
          Reporter: simonp@opera.com
        QA Contact: contributor@whatwg.org
                CC: krsacme@gmail.com, mike@w3.org, philipj@opera.com,
                    public-html-admin@w3.org, simonp@opera.com
        Depends on: 24558

+++ This bug was initially created as a clone of Bug #24558 +++

Overview:
Observed a difference in error handling with and without source element for the
video tag. In both the cases, the expectation is that application should know
correct error codes (Network or Decode or Source Not Supported). Video element
with out source is behaving as expected. Want to know why such a difference has
been forced.

Steps To Reproduce:
1. Load "video_error_good.html file"
2. MediaError object in video element is updated with correct error code
3. Load "video_error_bad.html"
4. MediaError object in video element is null

Expected Behavior:
Application should be able to identify the reason for the failure (Network or
Decode or source not supported)

Actual Behavior:
Application does not know what error it is even though source element fires
error handler, type of the error is not known

Posted a query on the public-html5-comments list, haven't received any update.
Link -
http://lists.w3.org/Archives/Public/public-html-comments/2014Jan/0000.html


(also see comments in Bug #24558)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Thursday, 6 February 2014 11:18:15 UTC