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

[Bug 18589] New: Unclear behavior when failing to attach to a media element

From: <bugzilla@jessica.w3.org>
Date: Thu, 16 Aug 2012 12:32:20 +0000
To: public-html-media@w3.org
Message-ID: <bug-18589-5436@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18589

           Summary: Unclear behavior when failing to attach to a media
                    element
           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#mediasource-attach

"Abort media element's resource fetch algorithm and run the steps to report a
MEDIA_ERR_SRC_NOT_SUPPORTED error."

The way this is phrased is a bit strange. In HTML, there are two ways in which
the resource fetch algorithm can end:

1. "Abort this subalgorithm, returning to the resource selection algorithm."

2. "Abort the overall resource selection algorithm." This is always preceded by
setting error/readyState/networkState.

As phrased, it looks like MSE requires new code paths, which is probably not
intentional.

Treating failure to attach as any (early) network error, like a failure to
resolve the URL or a DNS error would do the right thing here, it will return to
the resource selection algorithm and end up with MEDIA_ERR_SRC_NOT_SUPPORTED
without further intervention.

In short, I think this should be spec'd as running the steps for "If the media
data cannot be fetched at all, due to network errors, causing the user agent to
give up trying to fetch the resource."

-- 
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, 16 August 2012 12:32:22 UTC

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