Here is the difference in the generated JS. From a ~10/2013 trunk build:
function com_google_gwt_dom_client_StyleInjector_StyleInjectorImpl(){
switch (permutationId) {
case 1:
case 2:
case 3:
return new StyleInjector$StyleInjectorImplIE_0;
}
return new StyleInjector$StyleInjectorImpl_0;
}
So, even when permutationId was undefined (which it was for gecko_18,
which was basically permutation 0), it was fine, it'd get the non-IE
version.
But now with 2.6:
function com_google_gwt_dom_client_StyleInjector_StyleInjectorImpl(){
switch (permutationId) {
case 0:
case 4:
return new StyleInjector$StyleInjectorImpl_0;
}
return new StyleInjector$StyleInjectorImplIE_0;
}
The output changed; now when permutationId is undefined, which it still
is for gecko_1.8 (no change there), then IE is the default.
AFAICT the DOM.gwt.xml rules for StyleInjector haven't changed
recently. The permutations.js hasn't changed (permutationId was
undefined both pre-/post-2.6).
So, I can file a patch to make permutationId=0, but any ideas why this
would have changed since October-ish?
It must have been that, previously, "case 0" would never have been put
inside the runtime switch statement, and instead always have been the
fallback.
- Stephen
--
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.
