From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] bad byte in NASA's vendor.js
Date: Fri, 30 Dec 2016 12:07:44 -0800 [thread overview]
Message-ID: <87wpehuqnj.fsf@the-brannons.com> (raw)
In-Reply-To: <20161130145852.eklhad@comcast.net> (Karl Dahlke's message of "Fri, 30 Dec 2016 14:58:52 -0500")
Karl Dahlke <eklhad@comcast.net> writes:
> It doesn't seem to handle breakspace as whitespace however, and yet it should, and apparently does in other browsers.
I don't know if you have the JavaScript shell that comes with
Spidermonkey installed, but it handles it as whitespace just fine there
too. Test case: http://the-brannons.com/test.js.txt
So why not in JS_EvaluateScript? I added some debugging statements on
the JS side to print the bytes that were coming through, and they did in
fact come through as they should.
-- Chris
next prev parent reply other threads:[~2016-12-30 20:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-30 1:30 Kevin Carhart
2016-12-30 2:11 ` Chris Brannon
2016-12-30 3:24 ` Karl Dahlke
2016-12-30 18:52 ` Chris Brannon
2016-12-30 19:58 ` Karl Dahlke
2016-12-30 20:07 ` Chris Brannon [this message]
2016-12-30 23:13 ` Karl Dahlke
2016-12-31 5:28 ` Kevin Carhart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wpehuqnj.fsf@the-brannons.com \
--to=chris@the-brannons.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).