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: Re: [Edbrowse-dev] Render
Date: Fri, 28 Feb 2014 11:16:40 -0800	[thread overview]
Message-ID: <87iorzyrmv.fsf@mushroom.PK5001Z> (raw)
In-Reply-To: <20140228174401.GD19851@toaster.adamthompson.me.uk> (Adam Thompson's message of "Fri, 28 Feb 2014 17:44:01 +0000")

Adam Thompson <arthompson1990@gmail.com> writes:

> However, the more I think about it the more I think it's potentially not the
> best direction for edbrowse since it places a lot of dependancy on something
> beyond our control, i.e. the stability or otherwise of a js library.

True, they're all moving targets.  On the other hand, we're pretty much
tied to a JS library, so we're going to have to deal with its possible
instability anyway.
To me, the render-in-JS idea does seem pretty slick.

> I also wonder if this'd work in terms of browsing a web page without
> js,

In the non-JS case, the only thing we ever call is render.  We don't
evaluate scripts or call form handlers from the page.

> or one which defines its own render function.

That's easy.  Just call it edbrowse_render, to prevent namespace
conflicts.  Still, we have to make sure that this function can't be
overwritten by some script.

-- Chris

  reply	other threads:[~2014-02-28 19:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-28 16:43 Karl Dahlke
2014-02-28 17:44 ` Adam Thompson
2014-02-28 19:16   ` Chris Brannon [this message]
2014-02-28 20:01 Karl Dahlke
2014-02-28 22:04 ` Adam Thompson
2014-02-28 23:32 Karl Dahlke
2014-03-01 13:35 ` Adam Thompson
2014-03-12 16:57   ` Chris Brannon
2014-03-13 10:45     ` Adam Thompson

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=87iorzyrmv.fsf@mushroom.PK5001Z \
    --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).