[Bug 23106] Spec should treat content type as an opaque string from bugzilla@jessica.w3.org on 2013-09-03 (public-webapps-bugzilla@w3.org from September 2013)

From: <bugzilla@jessica.w3.org>
Date: Tue, 03 Sep 2013 09:41:27 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-23106-2532-gr3Ma6cGaZ@http.www.w3.org/Bugs/Public/>

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23106

Anne <annevk@annevk.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |annevk@annevk.nl

--- Comment #1 from Anne <annevk@annevk.nl> ---
I'm pretty sure that's because we changed our mind. The question is where we
should put the constraints and what conversion between code units and bytes we
should make. It cannot be a code unit sequence without conversion algorithm to
bytes. Making it a ByteString would make some sense...

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 3 September 2013 09:41:28 UTC