Same issue for bebo webite : http://www.bebo.com/PhotoUpload.jsp

(No comment was entered for this change.)

Not a blocker for mstone-4 moving to mstone-5

F1 live timing uses a java applet... still not available on Chrome on Mac/Linux

http://www.formula1.com/services/live_timing/live_timing.html

(No comment was entered for this change.)

 Issue 25895  has been merged into this issue.

aocampo, it works for me. Is this still reproducible for you?

Java is without a doubt not supported yet on the Mac; if the original test case works now 
it would only be because they stopped using Java.

We can't support Java yet because there is not currently a stable NPAPI Java plugin.

Stuart, thank you for that, saved me going in circles trying to get java working in 
Chrome on my Mac...

Do you know when a stable NPAPI might be available, is someone working on it?
Is there anything we can do to get it progressed faster?

I should add, that I think Chrome works really well on the Mac, I much prefer it to 
Safari and Firefox, but I really do need java plug in to work for my own product.

Would it be possible to add this support using the Java Embedding Plugin: 
http://javaplugin.sourceforge.net/

This is how the Gecko browsers do it.

It would be a good stopgap until there is a stable Java NPAPI plugin.

@19
A development version of an NPAPI Java plugin shipped with Snow Leopard 
(mentioned in the Java for Snow Leopard release notes), but it's not viable for use yet. 
No final release date is listed, so you'd have to ask Apple about that (same goes for 
whether there is anything you could do to make it happen faster, but I would imagine 
not).

@20
No. JEP is not designed for out-of-process use, and would almost certainly be 
infeasible to get working that way.

When Java support is feasible, we'll certainly work on making sure it works correctly; 
for now, just starring the issue so you get updates is the best thing to do.

 Issue 29476  has been merged into this issue.

 Issue 30473  has been merged into this issue.

(No comment was entered for this change.)

 Issue 30574  has been merged into this issue.

 Issue 31839  has been merged into this issue.

(No comment was entered for this change.)

 Issue 33936  has been merged into this issue.

(No comment was entered for this change.)

 Issue 34462  has been merged into this issue.

 Issue 34984  has been merged into this issue.

 Issue 36305  has been merged into this issue.

(No comment was entered for this change.)

 Issue 36900  has been merged into this issue.

 Issue 36908  has been merged into this issue.

Please try the latest developer preview of Java for Mac OS X (10M3044+9M3144) at 
<https://connect.apple.com/cgi-bin/WebObjects/MemberSite.woa/wa/getSoftware?
bundleID=20580>.

Full announcement here: <http://lists.apple.com/archives/java-
dev/2010/Mar/msg00126.html>

I am a little surprised to see a 32bit Chrome Helper start a 64bit Java Applet Host - I 
may be going a little beside the issue now, but might there be a way to start a 32bit 
Java VM rather than a 64bit one?  It appears Chrome (or just the Java Applet 
Bundle/Plugin) goes through a lot of effort to find a JDK (which I believe is only available 
as 64bit at /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0) rather than 
the JRE (at /System/Library/Frameworks/JavaVM.framework/Versions/A), regardless of 
the preference set in Java Preferences.  I merely ask because we need to interact with 
pcscd and this seems to only work when running a 32bit JVM.

I'm puzzled. (Using the developer download suggested above.) Yesterday this just 
brought up a black rectangle, this morning, it seems to bring up my working java 
applet?

There are issues with the operation of the applet, that are not seen on Safari. Should I 
be

1. Waiting a while for later releases of Chrome.
2. Raising the issues I notice on this thread.
3. Raising new Chrome bug reports.

Guidance please.

Reloading the page typically cycles between a black box and a working applet box — in the meantime try 
reloading the page.

This bug may be Chrome, or it could be the developer release of Java…

Re: lhunath @ comment 62:
There is no "JVM" in Versions/A - the "A" directory contains components common to each of the JDK versions, 
and the binaries necessary for a native applications to link against the JavaVM.framework.

Please read the "Known Issues" section of the release notes of the developer preview for more details about the 
version selection logic.

Re: geofftitmuss @ comment 63:
Were you using the "Run applets (*) In their own process" setting in Java Preferences? Also, try running Safari in 
32-bit mode to see if Safari exhibits the same behavior.

If you find that an issue is common to more than one browser, please file it against "Java" at 
<http://bugreporter.apple.com>.

> There are issues with the operation of the applet, that are not seen on Safari.

Just to reinforce what Mike was getting at in comment 66: if you are doing comparative 
testing in order to report bugs, it's critical that you actually use Plugin2 in all the browsers 
you are testing with; comparisons between Plugin2 in Chromium and a different plugin 
(Safari's .webplugin, Firefox/Camino's JEP, etc.) in another browser don't really tell us much.

With that in mind, if a bug is Chromium specific filing a new bug here is definitely the right 
answer. Please don't raise sub-issues in this bug, because it makes them impossible to 
track effectively, and they will almost certainly be lost when I close this bug--which will be 
as soon as basic support is generally available, not when it's bug-free.

I would like to confirm that the Update 2 Developer Preview fixes our applet launching issues as well. 

 Issue 40364  has been merged into this issue.

 Issue 40621  has been merged into this issue.

Using 5.0.375.29 and update 2 developer preview fixed applets from not displaying.

Apple just released "Java for Mac OS X 10.5 Update 7" and Java for Mac OS X 10.6 Update 2
So this is official now.

Indeed, Java is now supported! Congrats and thank you to mike.swingler :)

To prevent this from becoming an attractor for "But I have bug X with Java" comments, I'm going to lock this bug. 
For any remaining issues, read comments 63, 66, and 67, then file a new bug in the appropriate place.

(No comment was entered for this change.)

(No comment was entered for this change.)