Hey guys.

As we dropped IE6/7 permutation, we started to see more incidents related
to unsupported browsers.

Currently, when a browser is unsupported (incl IE compatibility modes), GWT
falls back to gecko1_8. The problem is Firefox itself has its own bugs and
we have workarounds for those that will usually break the app in an other
browser.

Instead of relying gecko1_8 as the fallback permutation, perhaps we can
provide a specific permutation for unsupported browsers. With this
permutation, most of the we can provide the standard implementation in
deferred bindings. The biggest advantage of this is, the app can handle it
in a way they see appropriate; e.g. provide an early shortcut to show a
warning page.

Also another thing we might want to do is to make sure that an IE
permutation is used for the legacy browsers; IE8 would be a much better
match than gecko for IE6/7 and any compatibility mode.

Anyway, I would love to hear your input on this.

 - Goktug

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
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].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to