From ed74fd67ee8d72e52c4e66ab67edf155948a39f1 Mon Sep 17 00:00:00 2001
From: Michael Bayne <mdb@threerings.net>
Date: Wed, 7 Feb 2007 21:30:13 +0000
Subject: [PATCH] We may be having problems where we know about one JSException
 class and the VM is throwing another and they don't end up matching. Let's
 just catch any exception thrown when trying to propagate status to JavaScript
 and log it.

---
 src/java/com/threerings/getdown/launcher/GetdownApplet.java | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/java/com/threerings/getdown/launcher/GetdownApplet.java b/src/java/com/threerings/getdown/launcher/GetdownApplet.java
index 597d5c7..baa390d 100644
--- a/src/java/com/threerings/getdown/launcher/GetdownApplet.java
+++ b/src/java/com/threerings/getdown/launcher/GetdownApplet.java
@@ -134,8 +134,8 @@ public class GetdownApplet extends JApplet
                     try {
                         JSObject.getWindow(GetdownApplet.this).call(
                             "getdownStatus", new Object[] { message, percent, remaining });
-                    } catch (JSException jse) {
-                        // don't sweat it.
+                    } catch (Throwable t) {
+                        Log.warning("Failed to communicate status to JavaScript: " + t);
                     }
                 }
             };