edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] noscript
Date: Fri, 21 Feb 2014 18:59:13 +0000	[thread overview]
Message-ID: <20140221185913.GX28870@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <20140121074647.eklhad@comcast.net>

On Fri, Feb 21, 2014 at 07:46:47AM -0500, Karl Dahlke wrote:
> Ok - the noscript tags become active when js is not.

Thanks.  Pulled, built and working well.
> We can talk about features to turn them off in the nojs directive in the
> config file later.

Yeah, not sure of the best way of doing this.

> 
> Yes I too have run into some sites where it claims js is off, but
> it is really on.
> My objects are not complete enough for it to recognize that it is on,
> so it prints those warning messages.
> These are the sites that lead us to the objects
> or methods that we are missing.
> But that's another story.

Yeah, I think a complete dom is a way off yet,
but we're certainly making large improvements.
So much so that I think that we should probably be aiming at a release around
the start of April. What do other people think?

> 
> My jsrt file includes some noscript tags for testing.
> Browse it with js off and you'll see what I mean.
> I put in some tags, not just text, to make sure the html runs
> inside noscript, as it should.

Thanks, works well.

Cheers,
Adam.

  reply	other threads:[~2014-02-21 19:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-21 12:46 Karl Dahlke
2014-02-21 18:59 ` Adam Thompson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-02-21  9:41 Karl Dahlke
2014-02-21 12:05 ` 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=20140221185913.GX28870@toaster.adamthompson.me.uk \
    --to=arthompson1990@gmail.com \
    --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).