- From: <bugzilla@jessica.w3.org>
- Date: Thu, 06 Feb 2014 09:18:51 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24558 Bug ID: 24558 Summary: Difference in error handling for video element Product: HTML WG Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P2 Component: CR HTML5 spec Assignee: robin@w3.org Reporter: krsacme@gmail.com QA Contact: public-html-bugzilla@w3.org CC: public-html-admin@w3.org Created attachment 1438 --> https://www.w3.org/Bugs/Public/attachment.cgi?id=1438&action=edit Samples to demonstrate the problem 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 -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 6 February 2014 09:18:53 UTC