Mat Kelly

Results 844 comments of Mat Kelly

Might be due to the characters being turned into an Int8ArrayBuffer wherein → requires more bits. e.g., "3".charCodeAt(0) --> 51 "3".charCodeAt(1) --> NaN "→‎".charCodeAt(0) --> 8594 "→‎".charCodeAt(1) --> 8206 I'm...

No dice on simply changing var buf = new ArrayBuffer(str.length) to var buf = new ArrayBuffer(lengthInUtf8Bytes(str)) in str2ab(), ~ line 8 warcgenerator.js. A single 8-byte character is still produced for...

What might be the case is that the content sent to warcgenerator.js as o_request.docHtml is already mangled due to encoding issues of the string...

Alternate approach, convert the characters to something encoded, e.g., → to → This is probably the wrong way to go about it, as it's modifying the content and will likely...

console before send shows correct → character. After send, the character is still preserved as well, so this might come down to the Uint8 issue afterall.

The same applies post-concatenation with HTTP headers, so it's not a string concat issue.

Test http://warcreate.com/tests/bug50.html Main contents (3 arrows): Bug 50 Test → → → In WARCreate WARC: Bug 50 Test →→→

There might be hope in the [chrome.devtools](https://developer.chrome.com/extensions/devtools) extension API.

"the APIs are available only through the lifetime of the DevTools window." Thus, the info cannot be extracted unless the devtools window is open. Back to the drawing board.