Stephen Haberman
unread,Oct 3, 2014, 2:53:05 PM10/3/14Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to google-web-toolkit-contributors
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