Java Not Working in Safari, Works in WebKit, Firefox, etc.

What makes you believe Java is working in WebKit and Firefox, but not Safari? What web sites have you visited that use Java to confirm this (provide specific URLs)? There's not enough information here to reproduce the problem or offer a possible solution.

Post back with details.

Mulder

Hi Moptop

do you see the same problem in a new user account?

Hey Moptop!

I tried going to the link and I didn't even get the Java 'coffee cup' stage. It never loaded for me on Firefox.

We need to figure this out because I have the same issue!! I see the coffee cup in both links you gave.

hmm, that's an odd one- although firefox can show java w/o the plugins in Library/Internet plugins, webkit still requires them.... and another account is the same, so forget user prefs etc.

also forget java prefs since webkit works...

to be honest I can only wonder if one of the frameworks is err hosed, and since webkit brings in it's own later ones, that's why it behaves when safari doesn't

it's possible to use pacifist to reinstall the various frameworks ( webkit, webcore, javascriptcore etc ) , or even copy the ones from inside webkit; but first I wonder, does your Console app show anything when you see the coffee cup?

if you say which safari version you use, it may be possible to check modified date/exact size of the various files - a bit long-winded tho... 🙂

HI again

I did play with various ideas offline before- & couldn't find a way to cause the issue with plugins etc; so I'd have to assume something's up with the frameworks I previously mentioned ( b/c webkit brings its own ones in ) yet something that isn't fixed via repair permissions & isn't a problem when run as root....

of course, permissions being 'right' depends on the correct info being available in ( is it the same in Leopard ??) HD/LIbrary/Receipts/ - so make sure the relevant receipts are there ( long shot, but hey! )

'fraid I can't dig up much on the com.apple.Safari.ServiceProvider error.

-----

I guess if you just want it working, I'd try either running the huge 10.5.3 combo update, or pulling the frameworks via Pacifist from either the combo update of the safari 3.1.1 update ( some info on that here . On the face of things, your safari app shouldn't be suspect since webkit uses it mostly, but the app can be extracted as per the link too.

In other words.... the non-tech " who cares why? - just fix it! " route is 1: the combo update, 2: reinstall etc