public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Justin Ekis <jekis@ntelos.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: elinks and javascript
Date: Fri, 26 May 2006 16:25:43 -0400	[thread overview]
Message-ID: <20060526201816.GA7219@debian> (raw)
In-Reply-To: <20060526194932.GA20219@localhost.localdomain>

One other thing. Even if the js support is compiled in and working
properly, elinks will still show the content in the <noscript> tags by 
default. I guess the js support isn't quite complete and this let's 
alternate content continue to be shown.
This means if you get a message about not having javascript things may 
still work fine. This is an elinks feature that seems to backfire or 
just be confusing more often than it helps. This line in elinks.conf 
will turn it off.

set ecmascript.ignore_noscript = 1

hth
Justin

On Fri, May 26, 2006 at 12:49:32PM -0700, Gregory Nowak wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1

> In your $HOME/.elinks/elinks.conf you want to put something like:

> set protocol.http.user_agent = "Mozilla/4.0 (compatible; MSIE 6.0;
> Windows NT 5.1; SV1; .NET CLR 1.1.4322)"

> The above line will tell servers that you're using msie6, under
> windows xp.

> Be aware however, that from my experience at least, this doesn't always
> help the js detection situation either.

> Greg


  reply	other threads:[~ UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 randy turner
 ` Michael Whapples
   ` randy turner
     ` Igor Gueths
       ` randy turner
         ` Gregory Nowak
           ` Justin Ekis [this message]
             ` randy turner
           ` randy turner
           ` using git and cg randy turner

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=20060526201816.GA7219@debian \
    --to=jekis@ntelos.net \
    --cc=speakup@braille.uwo.ca \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).