W3C home > Mailing lists > Public > public-html-media@w3.org > August 2012

[Bug 18660] New: Run endOfStream("decode") instead of "the media element's error handling code"

From: <bugzilla@jessica.w3.org>
Date: Thu, 23 Aug 2012 08:35:41 +0000
To: public-html-media@w3.org
Message-ID: <bug-18660-5436@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18660

           Summary: Run endOfStream("decode") instead of "the media
                    element's error handling code"
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Media Source Extensions
        AssignedTo: adrianba@microsoft.com
        ReportedBy: philipj@opera.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-media@w3.org


http://dvcs.w3.org/hg/html-media/raw-file/tip/media-source/media-source.html#dom-append

The phrasing "run the media element's error handling code to signal a
MediaError.MEDIA_ERR_DECODE error" is used in a few places.

The intention must be to treat this as a decode error in any other kind of
resource, but this doesn't point out the section in HTML that actually does
this.

Suggestion: Define that the equivalent of endOfStream("decode") be run.

This will also set readyState to "ended", which seems desirable to cause any
further call to append() to fail. Possibly, the call where the decode error is
caught should also throw, but a caller could tell that an error occurred by
checking readyState, so it's not strictly necessary.

-- 
Configure bugmail: https://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 Thursday, 23 August 2012 08:35:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 15:48:25 UTC