public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Andor Demarteau <ademarte@students.cs.uu.nl>
To: blinux-list@redhat.com
Subject: Re: dealing with javascript
Date: Mon, 27 May 2002 13:21:27 +0200 (MET DST)	[thread overview]
Message-ID: <Pine.GSO.4.21.0205271320250.2225-100000@abeel.students.cs.uu.nl> (raw)
In-Reply-To: <20020527002632.GB7221@debian>

On Mon, 27 May 2002, Peter Durieux wrote:

 > Hi, I know there is a project on sourforge.
 > Netrik is a text browser that may support js, c http://netrik.sourceforge.net.
last time I checked it didn't even support forsm yet.
And I tested it on a heavily js-infected site, still no text was showing.
Wheilst their idea's seem okay, I've not yet seen any practical outcome of
it.
 > I haven't tested the last versions.
 > 
 > grtz 
 > 
 > -Peter
 > 
 > On Thu, May 23, 2002 at 03:20:47PM +1000, RAYNER Peter wrote:
 > > I guess we're all running into problems with javascript more and more
 > > often.  I'm wondering if it's time to put some collective effort into
 > > a solution and, if so, what it might be.  
 > > The last time this topic turned up on the emacs-w3 list, Bill Perry's
 > > suggestion was for some kind of external parser, rather than extending
 > > the capabilities of emacs-w3 itself.  
 > > The other alternatives I see are to wait and hope the netscape
 > > accessibility efforts make the problem go away or to extend the
 > > capabilities of some other access tool.  
 > > Does anyone have any suggestions for which alternative might be
 > > preferable?  If we do decide on an external filter what kinds of
 > > capabilities must it have?  The few times I've looked inside
 > > inaccessible pages the JS seems to be doing uninteresting things like
 > > drop-down lists which could easily be handled other ways.  But I don't
 > > know enough about the capabilities of javascript to know what other
 > > kinds of events we might have to deal with.  I'm happy to try and hack
 > > something together to do this provided there's a reasonable chance of
 > > success; it's about time I brushed up my perl anyway.    There  also
 > > look to be some open-source implementations of interpretters out there
 > > we could possibly modify for the task.  
 > > So do people have a view of whether and how to go forward with this?
 > > Any currently active projects?  Other comments
 > > cheers
 > > Peter Rayner
 > > 
 > > 
 > > 
 > > _______________________________________________
 > > Blinux-list mailing list
 > > Blinux-list@redhat.com
 > > https://listman.redhat.com/mailman/listinfo/blinux-list
 > 
 > 
 > 
 > _______________________________________________
 > Blinux-list mailing list
 > Blinux-list@redhat.com
 > https://listman.redhat.com/mailman/listinfo/blinux-list
 > 

-- 
slainte mhaith (good health), slainte (cheers)
Uisce Beatha (water of live/health)
-----------
Andor Demarteau                 E-mail: ademarte@students.cs.uu.nl
student computer science        www: http://www.students.cs.uu.nl/~ademarte/
Utrecht University              irc: see webpage for details
-----------
Believe in yourself, know what you want, and make it happen!




      reply	other threads:[~ UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 RAYNER Peter
 ` Shaun Oliver
 ` Dave Mielke
   ` Cheryl Homiak
 ` T. V. Raman
   ` Cheryl Homiak
   ` Reformatting websites " Mario Lang
   ` Andor Demarteau
 ` Peter Durieux
   ` Andor Demarteau [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=Pine.GSO.4.21.0205271320250.2225-100000@abeel.students.cs.uu.nl \
    --to=ademarte@students.cs.uu.nl \
    --cc=blinux-list@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).