At 11:51 AM -0500 3/3/04, [EMAIL PROTECTED] supposedly scribed:
There is no support for 1.4 java in Mozilla. Some stuff ( maybe a lot maybe
few need to be rewritten to use Cocoa instead of Carbon).
So this is definitely a case of the browser specifying what Java the OS has to use? There was an implication that the OS was restricting what Java a browser could use to favor safari; it seemed logical to me that the browser would simply ask the OS to deliver Java and that it was up to the OS as to which to send. My logic goes that as Java is an OS service (of a sort) that the browser would only ask to use it, not specify a version for it to use.
It's more subtle than that. With the release of 1.4, Apple has changed the API that non-webcore browsers use for java embedding on the mac, and failed to port oji from sun. Browsers (including Camino) that depend on that get the most recent 1.3.x vm available. Worse, they don't appear to have documented the new one. The basic thrust as far as I can tell is that browsers which want to use 1.4 applets should "use webcore" :-P... obviously not a workable strategy for all.
So no, this is definitely *not* a case of the browser specifying the VM. It's a case of a documented API being removed in favor of an undocumented one that (currently) is only accessible via WebCore. The implication you read is closer to the truth IMO, though you did not supply a URL for the posting that has you all worked up, so no one can evaluate its accuracy.
Regards,
Geoff _______________________________________________ Camino mailing list [EMAIL PROTECTED] http://mozdev.org/mailman/listinfo/camino
