From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by listman.redhat.com (Postfix) with ESMTP id 4FDEC3F7D4 for ; Thu, 23 May 2002 11:11:49 -0400 (EDT) Received: (from mail@localhost) by int-mx1.corp.redhat.com (8.11.6/8.11.6) id g4NFBnR02687 for blinux-list@listman.redhat.com; Thu, 23 May 2002 11:11:49 -0400 Received: from mx1.redhat.com (mx1.redhat.com [172.16.48.31]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with SMTP id g4NFBnl02683 for ; Thu, 23 May 2002 11:11:49 -0400 Received: from mailhub1.almaden.ibm.com (mailhub1.almaden.ibm.com [198.4.83.44]) by mx1.redhat.com (8.11.6/8.11.6) with SMTP id g4NF55M21387 for ; Thu, 23 May 2002 11:05:05 -0400 Received: from aster.almaden.ibm.com (aster.almaden.ibm.com [9.1.175.3]) by mailhub1.almaden.ibm.com (8.8.8/8.8.8) with ESMTP id IAA14900 for ; Thu, 23 May 2002 08:11:36 -0700 Received: (from raman@localhost) by aster.almaden.ibm.com (8.9.3/8.9.3) id IAA05503; Thu, 23 May 2002 08:11:38 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15597.1705.864789.104855@gargle.gargle.HOWL> Date: Thu, 23 May 2002 08:11:37 -0700 To: blinux-list@redhat.com Subject: dealing with javascript In-Reply-To: <15596.31791.84467.201839@pjrnb-as.dar.csiro.au> References: <15596.31791.84467.201839@pjrnb-as.dar.csiro.au> X-Mailer: VM 6.84 under Emacs 20.6.1 From: "T. V. Raman" X-Loop: blinux-list@redhat.com Sender: blinux-list-admin@redhat.com Errors-To: blinux-list-admin@redhat.com X-BeenThere: blinux-list@redhat.com X-Mailman-Version: 2.0.1 Precedence: bulk Reply-To: blinux-list@redhat.com X-Reply-To: raman@cs.cornell.edu List-Help: List-Post: List-Subscribe: , List-Id: Linux for blind general discussion List-Unsubscribe: , List-Archive: If you want to write some code, here is an approach that will work: Basically Javascript of interest does one of 3 things: 0) generate content (document.write ) 1) Provides an event handler e.g. for mouse rollovers etc --the only handler that is really of interest is the one on form submit and anchor clicks (href="javascript:") 2) These handlers typically show up as JS functions written by the site author -- and eventually end up calling window.open or something equivalent like document.location="url" You can handle all of these by essentially running the HTML page through a JS interpreter and telling the interpreter to produce HTML with the JS code evaluated and results spliced back in as HTML. Look at rhino.jar for a full JS implementation in Java --take rhino.jar and write yourself the above interpreter --if you dont like Java pick your favorite language. Finally hook the "interpreter" above into a proxy server and test it. the proxy server should run JS enabled WWW pages through your interpreter. If you build this it will work for all browsers. >>>>> "RAYNER" == RAYNER Peter writes: RAYNER> I guess we're all running into problems with RAYNER> javascript more and more often. I'm wondering RAYNER> if it's time to put some collective effort into RAYNER> a solution and, if so, what it might be. The RAYNER> last time this topic turned up on the emacs-w3 RAYNER> list, Bill Perry's suggestion was for some kind RAYNER> of external parser, rather than extending the RAYNER> capabilities of emacs-w3 itself. The other RAYNER> alternatives I see are to wait and hope the RAYNER> netscape accessibility efforts make the problem RAYNER> go away or to extend the capabilities of some RAYNER> other access tool. Does anyone have any RAYNER> suggestions for which alternative might be RAYNER> preferable? If we do decide on an external RAYNER> filter what kinds of capabilities must it have? RAYNER> The few times I've looked inside inaccessible RAYNER> pages the JS seems to be doing uninteresting RAYNER> things like drop-down lists which could easily RAYNER> be handled other ways. But I don't know enough RAYNER> about the capabilities of javascript to know RAYNER> what other kinds of events we might have to deal RAYNER> with. I'm happy to try and hack something RAYNER> together to do this provided there's a RAYNER> reasonable chance of success; it's about time I RAYNER> brushed up my perl anyway. There also look to RAYNER> be some open-source implementations of RAYNER> interpretters out there we could possibly modify RAYNER> for the task. So do people have a view of RAYNER> whether and how to go forward with this? Any RAYNER> currently active projects? Other comments RAYNER> cheers Peter Rayner RAYNER> _______________________________________________ RAYNER> Blinux-list mailing list Blinux-list@redhat.com RAYNER> https://listman.redhat.com/mailman/listinfo/blinux-list -- Best Regards, --raman Email: raman@cs.cornell.edu WWW: http://www.cs.cornell.edu/home/raman/ AIM: TVRaman PGP: http://www.cs.cornell.edu/home/raman/raman.asc