edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev]  bad byte in NASA's vendor.js
Date: Fri, 30 Dec 2016 18:13:51 -0500	[thread overview]
Message-ID: <20161130181351.eklhad@comcast.net> (raw)
In-Reply-To: <87wpehuqnj.fsf@the-brannons.com>

My latest push should fix this breakspace bug. It runs for me on jsrt, and the test cases we created.
Kevin, give this a whirl with the nasa page, and march on to the next problem.

Warning - I may have totally broken things if your machine is big endian.
I couldn't really tell if JSEvaluateUCScript always wants little endian,
or if it wants what is native to your machine.
anyone able to test this for me?

Karl Dahlke

  reply	other threads:[~2016-12-30 23:13 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
2016-12-30 23:13           ` Karl Dahlke [this message]
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=20161130181351.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --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).