Fixes StackTraceNativeTest failing on lastest Chrome

Latest Chrome added "new" prefix to constructor function
frame and this patch updates the test to handle and ignore
the new prefix from test frames while asserting.

Change-Id: I8db8a26f4a0fe6bd9fe5d7aaef9e92593c0d2647
Review-Link: https://gwt-review.googlesource.com/#/c/19980/
diff --git a/user/test/com/google/gwt/core/client/impl/StackTraceTestBase.java b/user/test/com/google/gwt/core/client/impl/StackTraceTestBase.java
index c33d57a..ec447c1 100644
--- a/user/test/com/google/gwt/core/client/impl/StackTraceTestBase.java
+++ b/user/test/com/google/gwt/core/client/impl/StackTraceTestBase.java
@@ -77,6 +77,13 @@
       }
       StackTraceElement actualElement = trace[i];
       String methodName = actualElement == null ? "!MISSING!" : actualElement.getMethodName();
+
+      // Some new browsers (e.g. Chrome) adds "new" to frame if it was constructor call
+      String ctorFramePrefix = "new ";
+      if (methodName.startsWith(ctorFramePrefix)) {
+        methodName = methodName.substring(ctorFramePrefix.length());
+      }
+
       if (expectedMethodName.equals(methodName)) {
         i++;
         continue;