On 31 Mar 2010, at 18:59, Joel Webber wrote:
John,
Sorry for the slow response -- I've had a browser window open for
several days to respond, but I keep getting pulled off onto other
things.
Ha ha! I know exactly how it is.
It sounds like this is indeed an ordering bug. It's hard to be sure
precisely when IE's going to call onresize() (onmove() and
onresize() are obscure non-standard events that aren't documented
all that well). But what you're saying makes perfect sense, and I'll
try to find a way to get the ordering straight. Would you mind
entering an issue (or pointing me to it if you already have) that
captures this?
Cool I will do. Just thought I would check first that there was
nothing silly I was overlooking.
It may take me a little while to get a test case together and work
out a solution. Please let me know anything you discover that might
help.
Thanks Joel. I have worked around the issue for now by firing a Timer
in onResize() that actually resizes the child 100ms after the last
event. That works a treat for now. But I'll have a look at re-
ordring for the bug report.
Cheers!
John
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
To unsubscribe, reply using "remove me" as the subject.
