PPAPI/NaCl: Make tests enforce dispatchEvent check

ppapi/tests/test_case.html

Index: ppapi/tests/test_case.html
diff --git a/ppapi/tests/test_case.html b/ppapi/tests/test_case.html
index 1552ae2a5e063026f29d887dd3a24d63229b3d19..12053bce5f19104de6c0ed26b3b4e98c3be34cd2 100644
--- a/ppapi/tests/test_case.html
+++ b/ppapi/tests/test_case.html
@@ -297,14 +297,7 @@ onload = function() {
     // below.
     var original = obj.dispatchEvent;
     obj.dispatchEvent = function() {
-      // TODO(dmichael): NaCl triggers this; take out the special case for NaCl
-      //                 when crbug.com/109775 is fixed.
-      if (mode.indexOf("nacl") !== 0)
-        InternalError("Bad dispatchEvent called!");
-
-      // Pass it on anyways, we need the event to detect load progress and
-      // errors.
-      return original.apply(obj, arguments);
+      InternalError("Bad dispatchEvent called!");
     }
     container.appendChild(obj);
   }
@@ -314,10 +307,9 @@ onload = function() {
 // This part of the script does some nefarious things to make sure that it
 // doesn't affect the behavior of PostMessage (on which all the tests rely). In
 // particular, we replace document.createEvent, MessageEvent.initMessageEvent,
-// and the MessageEvent constructor. Previous versions of the PostMessage
-// implementation made use of these and would fail (http://crbug.com/82604).
-// The NaCl plugin uses dispatchEvent for progress events, hence we are careful
-// to make that still pass for NaCl (see above, and see crbug.com/109775).
+// and the MessageEvent constructor. Previously, the NaCl integration
+// implementation made use of these and would fail (http://crbug.com/82604
+// and http://crbug.com/109775).
 document.createEvent = function() {
   InternalError("Bad document.createEvent called!");
 }