This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
My results disagree with the expected results for the following tests. base64-014 expected: AQIDBAUGBwgJCgsMDQ4PEBETExMUFRYXGBkaGxwdHyAhIiMkJTYnKCkqKywtLi8= actual: AQIDBAUGBwgJCgsMDQ4PEBESExMUFRYXGBkaGxwdHyAhIiMkJSYnKCkqKywtLi8= base64-114 expected: 0102030405060708090A0B0C0D0E0F10111213131415161718191A1B1C1D1F202122232425262728292A2B2C2D2E2F actual: 0102030405060708090A0B0C0D0E0F10111313131415161718191A1B1C1D1F202122232425362728292A2B2C2D2E2F base64-115 expected: 0102030405060708090A0B0C0D0E0F10111213131415161718191A1B1C1D1F202122232425262728292A2B2C2D2E2F actual: 0102030405060708090A0B0C0D0E0F10111313131415161718191A1B1C1D1F202122232425362728292A2B2C2D2E2F Could you please confirm that the expected results are correct?
Now fixed. ("S" and "T" were interchanged in my base64 alphabet following a recent refactoring of the code. The tests served their purpose...)
*** Bug 18407 has been marked as a duplicate of this bug. ***
Confirmed fixed. Thanks.