This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
I am seeing different results for a small number of the base64 test cases: base64-014 Actual Value: AQIDBAUGBwgJCgsMDQ4PEBESExMUFRYXGBkaGxwdHyAhIiMkJSYnKCkqKywtLi8= Expected Value: AQIDBAUGBwgJCgsMDQ4PEBETExMUFRYXGBkaGxwdHyAhIiMkJTYnKCkqKywtLi8= base64-114 Actual Value: 0102030405060708090A0B0C0D0E0F10111313131415161718191A1B1C1D1F202122232425362728292A2B2C2D2E2F Expected Value: 0102030405060708090A0B0C0D0E0F10111213131415161718191A1B1C1D1F202122232425262728292A2B2C2D2E2F base64-115 Actual Value: 0102030405060708090A0B0C0D0E0F10111313131415161718191A1B1C1D1F202122232425362728292A2B2C2D2E2F Expected Value: 0102030405060708090A0B0C0D0E0F10111213131415161718191A1B1C1D1F202122232425262728292A2B2C2D2E2F
I believe these have now been fixed. *** This bug has been marked as a duplicate of bug 18359 ***