W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > January to March 2000

re discussion:[Fwd: Re: Java Access Bridge 1.0 released!]

From: David Poehlman <poehlman@clark.net>
Date: Thu, 13 Jan 2000 18:34:35 -0500
Message-ID: <387E610B.DFF0CD84@clark.net>
To: User Agent Working group list <w3c-wai-ua@w3.org>, Java Accessibility interest mailing list <JAVA-ACCESS@java.sun.com>
we're talking here about the plug in that allows applettes to be
accessible.  is there anything in the ua guidelines that might help
here?

-------- Original Message --------
Subject: Re: Java Access Bridge 1.0 released!
Date: Thu, 13 Jan 2000 09:19:31 -0600
From: pjenkins@US.IBM.COM
Reply-To: Java Accessibility interest mailing
list<JAVA-ACCESS@java.sun.com>
To: JAVA-ACCESS@JAVA.SUN.COM

Peter wrote:
>The issue is that, in order for the browser to invoke the Java Plugin, the
>web page that contains the Java applet(s) must be recoded to invoke it.
This
>is unfortunate, but there is presently no way to get around that.

Why can't we pressure the IE and Netscape developers to allow the JVM
that
the browser's use to be user configurable?  In others words, when the
user
install the JVM, it replaces the one shipped by the browser mfg. if the
users so desires.  It was great that the JVM was shipped by the browser
in
the first place.  Now they seemed to have locked us in to older Java
technology.  Why wasn't it user replaceable in the first place?

If this is an initiative, what's the status?  Please separate the
political
[many] from the technical [if any] issues.

Regards,
Phill Jenkins,

===========================================================================
To unsubscribe, send email to listserv@java.sun.com and include in the
body
of the message "signoff JAVA-ACCESS".  For general help, send email to
listserv@java.sun.com and include in the body of the message "help".
Received on Thursday, 13 January 2000 18:42:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:49:51 GMT