W3C home > Mailing lists > Public > whatwg@whatwg.org > January 2011

[whatwg] Specs for window.atob() and window.btoa()

From: Aryeh Gregor <Simetrical+w3c@gmail.com>
Date: Sun, 9 Jan 2011 14:08:54 -0500
Message-ID: <AANLkTinvqBmb_ntkN3PVo9HVnh-SWrAhdq=Dkf2eQBFk@mail.gmail.com>
On Fri, Jan 7, 2011 at 12:38 PM, Boris Zbarsky <bzbarsky at mit.edu> wrote:
> In that case, I would prefer that the character and length constraints just
> be explicitly specified. ?Specifying them via an unreadable regexp is
> hostile not just to implementors but to the users of the spec too.

I've updated the spec and tests to define things this way.  I used a
regex originally because I couldn't think of a good way to write it in
prose, but your summary was good, so I more or less used that.

On Fri, Jan 7, 2011 at 1:17 PM, Joshua Bell <josh at lindenlab.com> wrote:
> It might not hurt to include an *informative* note in the specification that
> some base64-encoding tools and APIs by default inject whitespace into any
> base64-encoded data they output; for example, line breaks after 76
> characters.

I've added a note to this effect.
Received on Sunday, 9 January 2011 11:08:54 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:29 UTC