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

Aryeh Gregor Simetrical+w3c at gmail.com
Sun Jan 9 11:08:54 PST 2011

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.

More information about the whatwg mailing list