I agree with Phillip. Mozilla/Netscape 6 will be fairly useless to some corporate users with its lack of live connect. Neither Flash nor Quicktime can be scripted from JavaScript which makes my company refuse to support them.
If live connect is not compatible with the new Java runtime enviornments, then another solution with XPConnect should be offered. Or some serious evangelising of Apple, Macromedia and other plug-in developers needs to take place to support XPConnect. Phillip M. Jones, C.E.T. wrote: > Many plugins That Communicator can use, do not work in netscape 6 or > Mozilla because they use Live Connect. > > My understanding as stated on this very newsgroup is That "liveconnect" > was a proprietary code that "netscape used". As such W3C would not > accept for inclusion in W3C standards because it was proprietary to > Netscape. Netscape has since donated the code. W3C still hasn't seen fit > to ratify the code for inclusion. > Therefore if its isn't ratified, they do not recommended using. > > My take on the subject: If that's the case, if they don't approve it for > use it "must" be considered banned. > > That doesn't mean that some one can't use it. For that matter MS could > use it now if they so chose. since they don't usually adhere to standards. > > Because liveconnect can not be used, most plugins can not be used. > > Christian Biesinger wrote: > >>Phillip M. Jones, C.E.T. wrote: >> >>> That Live connect is a tecnology that Netscape Submitted to >>>W3C which is used by current plugin technology to make them work. >> >>LiveConnect has nothing to do whatsoever with the W3C. It's only used >>for plugins, which have nothing to do with the W3C. >> >>-- >>"They that can give up essential liberty to obtain a little temporary >>safety deserve neither liberty nor safety." >> -- Benjamin Franklin > >
