This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 8531 - Add specification of atob and btoa
Summary: Add specification of atob and btoa
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
: 8559 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-12-21 11:08 UTC by James Graham
Modified: 2010-10-04 14:56 UTC (History)
6 users (show)

See Also:


Attachments

Description James Graham 2009-12-21 11:08:44 UTC
Base64 encoding/decoding methods window.atob and window.btoa should be specified. They are already supported in major engines except Trident and are convenient for working with base64 encoded data e.g. in data urls.
Comment 1 Maciej Stachowiak 2010-01-05 03:55:01 UTC
*** Bug 8559 has been marked as a duplicate of this bug. ***
Comment 2 Maciej Stachowiak 2010-01-05 03:56:50 UTC
Perhaps these should be defined at the ECMAScript level, since they are not Web-dependent.
Comment 3 Ian 'Hixie' Hickson 2010-01-06 12:13:23 UTC
Are they willing to spec it? If not, I'm happy to add them here.
Comment 4 Ian 'Hixie' Hickson 2010-01-07 06:32:14 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: This only seems to exist in Gecko and Webkit, and best belongs in the JS spec anyway, so I'm going to punt on this.