In most cases that is true, but CssResource is an interesting exception. The fallback rules work by looking to see if there is no implementation for a particular value, and if not, looking to see if there *is* an implementation for some other value. In the case of ClientBundle and CssResource, they are generated at compile time - when you refer to @if user.agent ie9, that will be compiled *only* into the ie9 build, and not into any ie10 build, which will only contain non-qualified code or statements that actually evaluate to true for ie10.
But yes, otherwise it should behave as you've described.
On Monday, April 22, 2013 5:01:56 AM UTC-5, Honza Rames wrote:
It does but out of curiosity, if I add IE10 permutation/browser detection to UserAgent.gwt.xml to which value should I set the property-fallback? I mean is property fallback-recursive (I would assume it is) so setting it to IE9 should work? In case IE9 rule isn't specified it will recursively fallback to IE8 (and generate a compiler warning) right?--
On Wednesday, April 17, 2013 12:40:04 AM UTC+2, Thomas Broyer wrote:
On Tuesday, April 16, 2013 2:07:34 PM UTC+2, Mariusz Magdziarz wrote:When you add support for IE10??AFAIK, IE10 works OK with the ie9 permutation.Vaadin has started working on bringing MSPointerEvents to support touch-enabled (and touch-only) devices.
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
To post to this group, send email to firstname.lastname@example.org.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.