- From: <bugzilla@jessica.w3.org>
- Date: Sat, 17 Sep 2011 06:02:07 +0000
- To: public-html@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14186
Summary: Proposed additional information for <video> Error
events
Product: HTML WG
Version: unspecified
Platform: PC
OS/Version: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: HTML5 spec (editor: Ian Hickson)
AssignedTo: ian@hixie.ch
ReportedBy: offbeatmammal@gmail.com
QAContact: public-html-bugzilla@w3.org
CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
public-html@w3.org
while the Error event on the <video> (and <audio>) elements is useful (or will
be when https://bugs.webkit.org/show_bug.cgi?id=68308 /
http://code.google.com/p/chromium/issues/detail?id=96871 are resolved) the
diagnostic information returned is rather limited...
While there is information about the network conditions there is no easy way to
determine if the request failed because the asset was not found, or the user
was not authorized to access it.
My suggestion would be to add support for an additional attribute on error to
supplement error.code with an error.httpresponse that would give developers the
ability to test and act on a 404 or 403 or 500 etc
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Saturday, 17 September 2011 06:02:13 UTC