W3C home > Mailing lists > Public > public-media-capture@w3.org > January 2014

Re: MediaError object (Re: New Editor's draft v20131225)

From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Date: Thu, 23 Jan 2014 15:20:50 +0000
To: Jan-Ivar Bruaroey <jib@mozilla.com>, Harald Alvestrand <harald@alvestrand.no>, "public-media-capture@w3.org" <public-media-capture@w3.org>
Message-ID: <1447FA0C20ED5147A1AA0EF02890A64B1CF3374E@ESESSMB209.ericsson.se>
On 09/01/14 18:22, Jan-Ivar Bruaroey wrote:
> On 1/9/14 10:11 AM, Harald Alvestrand wrote:
>> On 01/09/2014 04:04 PM, Jan-Ivar Bruaroey wrote:
>>> It's not needed by programs, except programs that would need to do
>>> this anyway IMHO. I think we let this cat out of the bag when we said
>>> "SDP parsing" was an API. It's not. It's an emergency access panel to
>>> the implementation.
>>
>> To which viewpoint I agree.....
>>
>>> My point was quite specific: Line-number isn't enough to cover
>>> Sylvia's rather ambitious code anyway, which likely would look like
>>> this already to parse the error messages for clues, not to mention
>>> browser-specific SDP tricks that might need to be dealt with, so this
>>> seems par for the course. Who needs a silver spoon to eat out of
>>> trashcans?
>>
>> But SDP, for all its faults, has a specified grammar. So an SDP parser
>> can parse any compliant SDP, and "line number" has a specific meaning.
>> No browser implementor governs the syntax of SDP.

I noted that reporting line number in errors is also done for Workers 
(http://www.w3.org/TR/workers/#runtime-script-errors) - so there is some 
precedence.


Received on Thursday, 23 January 2014 15:21:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:26:23 UTC