From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] realloc 0 fixed
Date: Sun, 04 Jan 2015 12:29:11 -0500 [thread overview]
Message-ID: <20150004122911.eklhad@comcast.net> (raw)
Ok I fixed that bug. See the log.
Still wondering if we should force
a stack trace on some of the null pointer checks.
I'm back on track pursuing my innerHTML stuff.
I didn't answer Adam's questions because I'm not sure yet.
Probably what I'm doing now will still not be the final answer.
But it should help in the short run, and maybe bring us closer in the long run.
It's really a zoo.
html can run javascript wich can crank out more html,
through document.write or through innerHTML, or,
javascript can create html like elements using createElement(),
and those should be rendered as though they were html.
Not easy to come up with a design that handles all these possibilities,
then code, then execute, then test.
I do agree jsrt has to run many more tests.
We've added functionality already, and jsrt is not always
kept up to date. Kinda like documentation.
Karl Dahlke
reply other threads:[~2015-01-04 17:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150004122911.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).