Wow, that's great! I noticed yesterday that Firefox finally added support for stuff like clientX and pageX too. For years, they refused to implement stuff like that.
Oh, mighty Apple web developers! Your absolute refusal to test your code on anything except Safari has finally felled even the mighty Mozilla! Despite its limited market share, Safari truly is the new IE6 of Internet. Nevertheless, having easy knockouts of API functionality would be nice. In fact, my dream API would be to have something like @Deprecated. There would be annotations on the APIs with the browser compliance level of each method. Then, you could get the compiler to automatically analyze your code and issue warnings about what browsers your code works on. Of course, then you would need additional annotations to suppress some of those warnings. And then there would be another layer to detect when your warning suppression annotation is, itself, no longer valid. Something like that is probably beyond the scope of Elemental though. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/522eac8b-51d8-4782-bf74-198bfb952fc0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
