On Mon, Jul 25, 2011 at 5:55 PM, David Chandler <drfibona...@google.com> wrote: > Good luck, Eric :-) It likely requires non-trivial changes (which is > why the GWT team hasn't done it yet).
It's not clear yet what'll be required. It looks like whoever wrote the current plugin did a pretty decent job of separating concerns. I'm currently playing with one of the WebKit example NPAPI plugins (from webkit.org)... and that at least works. I would like to say that it really stinks that nobody from the GWT team warned us that Safari 5.1 + OOPHM doesn't work. It's debatable whether or not it's my responsibility to keep up with this stuff, but it's definitely the GWT team's responsibility to at least communicate such things to their users. Part of me wants to say f*ck it and use FF, but frankly, I don't like FF. Devmode is painfully slow in Chrome, and I'm definitely not switching to Windows. > We're currently evaluating how to handle the recent Firefox as well as > Safari changes going forward. The FF change is especially onerous as > it now requires engineering effort every 6 weeks to stay up to date. Hire somebody. eric -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
