I know that Apple is working on implementing the newer Mozilla
Javascript NSAPI,
I'd like to correct a misconception. The Safari team at Apple developed
and implemented the initial version of this API. We worked with people
from Mozilla, Opera, Macromedia, Sun, and others who helped us refine
it, and Mozilla implemented it as well.
which is great, but my client is not really interested in waiting on
Apple to handle this, nor are they interested in having to tell the
user to get the latest Safari, (which may/may not require a newer
version of OSX,) in order to use this product. My own inclination
is to not try anything tricky and just to implement this using the new
NPAPI instead. This would mean that the product would only work in
Mozilla/Firefox.
Assuming for the sake of argument that the new version of Safari didn't
require a new version of OS X, is there a reason your client would be
willing to require the latest Firefox which adds support for this new
plug-in scripting API, but not willing to require the latest Safari
which also adds such support?
-- Darin
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webcore-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webcore-dev/email@hidden
