W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2010

[Bug 11074] New: Why does this need to be a specific codec? Why couldn't developers have the option to specify the type of the stream, similar to the way a MIME type can be specified in the canvas's toDataURL method?

From: <bugzilla@jessica.w3.org>
Date: Sat, 16 Oct 2010 19:26:27 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-11074-2486@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11074

           Summary: Why does this need to be a specific codec? Why
                    couldn't developers have the option to specify the
                    type of the stream, similar to the way a MIME type can
                    be specified in the canvas's toDataURL method?
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#str
                    eam-api
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: other Hixie drafts (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org


Section:
http://www.whatwg.org/specs/web-apps/current-work/complete.html#stream-api

Comment:
Why does this need to be a specific codec? Why couldn't developers have the
option to specify the type of the stream, similar to the way a MIME type can
be specified in the canvas's toDataURL method?

Posted from: 65.185.149.158

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Saturday, 16 October 2010 19:26:29 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:31 UTC