- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Tue, 6 Aug 2013 11:09:35 +0100
- To: Kenneth Russell <kbr@google.com>, Joshua Bell <jsbell@chromium.org>
- Cc: WHAT Working Group <whatwg@lists.whatwg.org>, Chang Shu <cshu01@gmail.com>, Simon Pieters <simonp@opera.com>
On Tue, Aug 6, 2013 at 1:41 AM, Kenneth Russell <kbr@google.com> wrote: > The Encoding spec at http://encoding.spec.whatwg.org/ seems to have > handled issues like these. Perhaps a better route would be to fold > this functionality into that spec. Yeah, I think my preference would be at this point to expose API-only encodings there. One of those could be base64. Labels for those encodings would simply not be recognized for <form> and URL. We could even give them labels that suggest that, e.g. "api-base64". Another one I've heard requests for is true latin1 which we also use in XMLHttpRequest for various HTTP-related things. -- http://annevankesteren.nl/
Received on Tuesday, 6 August 2013 10:10:01 UTC