edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] edbrowse 3.7.1 is here
Date: Wed, 23 Aug 2017 19:22:09 -0700	[thread overview]
Message-ID: <874lsxpuwe.fsf@the-brannons.com> (raw)

Edbrowse 3.7.1 is here.
The main reason for doing this release so soon after 3.7.0 is
that some important functionality was broken.  If you do not have a ~/.ebrc,
edbrowse will try to create one for you on its first run.  Unfortunately,
instead of creating a config file, edbrowse 3.7.0 will crash.
That bug was introduced by me, Chris Brannon.  So here's my public mea culpa.
Aside from the bugfix, there has been a lot of activity lately.
Edbrowse is really moving forward!  Here's the short summary of
user-visible changes.

Automatically expand a frame when javascript tries to access its objects.
Otherwise it won't expand unti you expand it explicitly.
This saves resources; don't fetch and expand a frame unless it is needed.

^c interrupts javascript, if that javascript calls our native methods. It also interrupts http fetch.
Hit ^c if the browsing is taking too darn long - however - the page may not render properly or completely.
Don't do this if you are using this page for ecommerce or something vital.

Keep edbrowse in 1 process. Don't fork a javascript process to make all the js calls.
There are many technical reasons why 1 process is a better design.

The keyword jspool is no longer used in the .ebrc config file.  This
was needed for Mozilla JS, but it is not needed for Duktape.

Gather keyword value pairs from <style> tags and css files and apply them to the corresponding javascript objects.
Implement getComputedStyle().

You can get edbrowse from the usual place:
https://github.com/CMB/edbrowse/archive/v3.7.1.tar.gz,
or https://github.com/CMB/edbrowse/archive/v3.7.1.zip if you prefer
a zip archive.

-- Chris

                 reply	other threads:[~2017-08-24  2:21 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=874lsxpuwe.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).