From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] from the Skunkworks department
Date: Fri, 29 Dec 2017 01:56:38 -0500 [thread overview]
Message-ID: <20171129015638.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.LRH.2.03.1712282015210.24564@carhart.net>
[-- Attachment #1: Type: text/plain, Size: 456 bytes --]
Well I wonder if the interpreter can understand our side effects, like setters and such, like setting form.whatever.value calls a c function that does something etc.
If it can't incorporate that then I don't think it would be very useful.
We do need something like that though; there are some sites that just hang in js, we don't know why and we don't have an error to go on.
I'll post a url the next time I run into one of these sites.
Karl Dahlke
prev parent reply other threads:[~2017-12-29 6:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 4:48 Kevin Carhart
2017-12-29 6:56 ` Karl Dahlke [this message]
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=20171129015638.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).