From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] jex mode and rerender
Date: Sat, 17 Oct 2015 14:43:20 -0700 (PDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1510171440580.28208@carhart.net> (raw)
In-Reply-To: <20150917044047.eklhad@comcast.net>
That's awesome!
Very helpful for following the side effects to
their resolution.
Any abbreviation is fine - I used to have it on 'y'
and 'z'!
Kevin
On Sat, 17 Oct 2015, Karl Dahlke wrote:
> Our javascript debugger,
> which we enter by jex for javascript execution for historical reasons,
> but looking at it now I think jdb for javascript debugger
> would make more sense, what do you think?
>
> Anyways when you enter that mode and make some changes and then leave,
> edbrowse did not go down the same pathways as say running some onclick code.
> You could set innerHTML, or add some options to an option list,
> or createTextNode and appendChild to paste text into the document,
> and none of that was reflected in the buffer.
> I have fixed this.
> As of the latest commit, side effects are processed,
> and the buffer rerendered, as though you had pushed a button
> to run onclick js code or some such.
> This makes it easier to test our dom functions like create and append
> and innerHTML and the like, and see the results rendered in the buffer.
>
> Karl Dahlke
> _______________________________________________
> Edbrowse-dev mailing list
> Edbrowse-dev@lists.the-brannons.com
> http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
>
--------
Kevin Carhart * 415 225 5306 * The Ten Ninety Nihilists
prev parent reply other threads:[~2015-10-17 21:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-17 8:40 Karl Dahlke
2015-10-17 21:43 ` Kevin Carhart [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=alpine.LRH.2.03.1510171440580.28208@carhart.net \
--to=kevin@carhart.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.net \
/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).