Mat Kelly

Hex 89 is becoming hex EFBFBD. This sounds waaay too familiar, like a BOM issue.

Part of the problem is that the call to fetch the image data via Ajax has required synchronicity for string building. Otherwise an arraybuffer or a Blob (see https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest/Sending_and_Receiving_Binary_Data )...

See http://stackoverflow.com/questions/21708000/acquring-raw-image-data-when-fetching-image-using-ajax

An alternative might be to try to capture the image data using the Chrome facilities when it first comes in but the response handlers don't seem to have access to...

Woo, created a basis solution! Now, to scale it. var hexValue = 0x89; var png = "PNG"; var hexValueArrayBuffer = new ArrayBuffer(1); var hexValueInt8Ary = new Int8Array(hexValueArrayBuffer); hexValueInt8Ary[0] = hexValue;...

Content length is now correct for simple case (mkdc) but not for large cases (e.g., CNN.com, FB)

@eligrey , thank you for chiming in. Is there an explanation of why this limit is the case?

See also: https://github.com/jimmywarting/StreamSaver.js

@N0taN3rd Very large payloads, as described in this ticket (and potentially generated per #66), should be a test case in WARCreate. We currently have no test suite integration but need...

@N0taN3rd Those stats seem believable. At some point, we ought to convert to WebExtensions if, for nothing else, to document the process of going from a Chrome Extension to Web...