It must be said that this is a bit of a gotcha - it's got me twice, far enough apart that I forgot what the fix was and I had to figure it out again.
Perhaps can we have two modules - a default one that defines user agent, etc, and a fancy one that doesn't, so for more special needs such as yours you could depend on the fancy one? (the "default" one would simply depend on the fancy one and then add the definitions) Dan Στις 8 Ιουνίου 2011 8:08 μ.μ., ο χρήστης Thomas Broyer <[email protected]> έγραψε: > 2011/6/8 Daniel Danilatos <[email protected]>: >> You need to restrict the properties e.g. >> >> <set-property name="user.agent" value="safari,gecko1_8,ie6,ie8"/> >> <set-property name="mobile.user.agent" value="not_mobile" /> >> >> Perhaps something like that should be in the actual user agent module > > As we discussed earlier, I believe it shouldn't (at least the > user.agent one, because it's a "standard" property). > That would prevent anyone from integrating parts of Wave in an > application, where they make sure the Wave code is not used for > unsupported permutations (for instance, giving a server-rendered > read-only view for Opera users with an "Opera is not supported for > editing, please use Chrome, Firefox, Internet Explorer or Safari, and > preferably a recent version" warning). > > Those "constraints" should probably be documented somewhere though. > > (that makes me think we should some day upgrade to GWT 2.3 and support IE9) >
