[Webkit-unassigned] [Bug 41510] Add Base64DecodePolicy option at base64Decode()

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Aug 2 10:22:13 PDT 2010


--- Comment #16 from Patrick R. Gansterer <paroga at paroga.com>  2010-08-02 10:22:13 PST ---
(In reply to comment #15)
> (From update of attachment 63224 [details])
> > +    // The ascii() function turns any non-ASCII characters into "?" characters,
> > +    // which yields correct behavior because those are illegal in base 64.
> The ascii() function also turns U+0001-U+001F and U+007F into "?" characters. And turns the null string into "(null impl)". Are those behaviors desirable here? Do we have test cases that cover these?
In U+0001-U+001F is not valid base64 charachter; so no problem.
What is the expected behaviour for null-stings? I think like a empty string? Or return false for base64Decode?

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list