Closed Bug 1276475 Opened 8 years ago Closed 8 years ago

First xhr example reads file, not pixels

Categories

(Developer Documentation Graveyard :: API: Miscellaneous, defect, P5)

Product:
Developer Documentation Graveyard
Component:
API: Miscellaneous
Platform:
All
Other
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: owen, Unassigned)

References

(
URL
)

Details

:: Developer Documentation Request

      Request Type: Correction
     Gecko Version: unspecified
 Technical Contact: 

:: Details

On the Sending and Receiving Binary Data page
https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest/Sending_and_Receiving_Binary_Data
the first example reads a .png as an arraybuffer.

My assumption was that the arraybuffer would be that of the image itself, i.e. the decoded .png data.

Instead, the arraybuffer is the .png file content itself, encoded.

Is this the intent? If so, the page needs to indicate it is the encoded .png file, not the image arraybuffer.

If not, chrome latest has a bug!  :)
The page is about binary data. I have added a sentence that this will not read pixels and a link to a JS png decoder.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Component: JavaScript → API: Miscellaneous
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.