On Wednesday, November 27, 2013 1:13:30 AM UTC+1, Jens wrote:
>
> 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.
>>
>
> Are you sure? In our app we have removed the ie6/7 user.agent value and
> when visiting our app with IE6/7 or IE compatibility mode no permutation is
> selected. Thats why we configured a redirect to a static site in your load
> balancers. Is it possible that we have somehow accidentally disabled this
> gecko1_8 fallback mechanism?
>
I agree, I don't recall seeing anything related to falling back to
gecko1_8, and UserAgentPropertyGenerator has a "return 'unknown'" as a
fallback when no predicate matches.
Goktug, are you sure it's not an issue with your Server-Side
Selection-Script?
>
>
>> 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.
>>
>
> Falling back to a standards based permutation will be nice for new/unusual
> browsers that might work with GWT but are not detected by GWT. Falling back
> to an IE8 permutation for IE6/7 might work now but in a year IE8 is
> probably gone anyways so I am not sure if its worth it. Also although the
> JS code might work then, the UI is likely to not work very well if IE6/7
> specific UI code has been deleted.
>
> What I like to see is something like:
>
> 1.) A way to ask GWT at runtime if it runs in a fallback permutation
> because it has failed to detect the browser (may it be a standards based
> permutation or for IE a specific IE fallback permutation). This would allow
> an app to provide a warning message. This is kind of an optimistic approach
> as it could also happen that the app does not load at all.
> 2.) A way to configure a redirect URL if GWT can not detect the browser
> (or the browser is unsupported). That would be the pessimistic approach.
>
There's "gwt:onPropertyErrorFn" and "gwt:onLoadErrorFn" hooks (set the name
of a JS func in a <meta> with that name; e.g. <meta
name="gwt:onPropertyErrorFn" value="gwtErrFns.prop">, and var gwtErrFns = {
prop: function(propName, allowedValuesList, value) {
window.location.replace("static/error.html"); } })
> 3.) A configuration property for developers to tell GWT if it should
> choose approach 1.) or 2.)
>
>
> -- J.
>
>>
--
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.
