On Thursday, July 19, 2012 12:16:26 AM UTC+2, rdayal wrote: > > Hey guys, > > This is my fault. I mis-interpreted the code change. As the change to > "fix" this issue was basically a "revert" of the original commit that was > supposed to add ChromeFrame support, I incorrectly assumed that reverting > the code would prevent special behavior for ChromeFrame (which I figured we > needed in order to make it work). Had I read issue #6665 more carefully, I > would have realized that this fix was to improve support for ChromeFrame, > not remove it entirely. > > I'll be sure to fix this statement in the release notes. >
3 months later, this is unfortunately still there :-( Could anyone fix it please? -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
