Hey, I know FF17 is pretty old, but do we care about breakages in it? We noticed some client-side ClassCastExceptions in our logs that are from a user on FF17. The app works fine in FF latest.
The exception is odd, because, according to the de-obfuscated stack trace, given a class hierarchy like: class Base class Foo extends Base class Bar extends Base We are in "new Foo()", from the Foo cstr we call the Base cstr, which calls Base.someMethod(). Base.someMethod() calls Base.anotherMethod(). Now the bizarre thing is that we end up in *Bar*.anotherMethod(), and get a class cast exception. E.g. somehow we jumped subclasses, and went from executing code in Foo/Foo's base class to code that is in Bar. Which seems really odd. Which is why I mention it. If we don't care, that's fine, but it made me scratch my head for awhile. (Our production build is using a GWT snapshot from ~April, but I also reproduced it in our app with a GWT snapshot build from ~last week.) - Stephen -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/20141003135259.76c16354%40sh9. For more options, visit https://groups.google.com/d/optout.
