Closed GoogleCodeExporter closed 9 years ago
Can this please be addressed? It is a more generic problem than the summary
suggests. http://code.google.com/p/smartgwt/issues/detail?id=311 has a test
case at the bottom that reproduces the issue even on nightly builds. This
problem has been shrugged off in the forums too. Can we at least have some
disclosure on whether it will ever be fixed?
Original comment by chad.r...@gmail.com
on 14 Dec 2010 at 6:53
As explained on the forums, this second and unrelated problem is an arbitrarily
imposed native stack depth limit in IE - SmartGWT doesn't go into an infinite
loop, but IE stops execution at an arbitrary stack depth like 150. GWT appears
to be exacerbating the issue by burning extra stack frames. It's likely to go
away with future version of IE and/or GWT with no changes to SmartGWT.
It is easily worked around by deferring drawing of interior components of a
page (just use DelayedCommand), which is better user experience anyway, since
they will see the basic page framing (outermost layouts) sooner.
Original comment by smartgwt...@gmail.com
on 14 Dec 2010 at 10:13
See above comment. Use DeferredCommand to workaround the issue.
Original comment by sanjiv.j...@gmail.com
on 20 Dec 2010 at 12:19
Original comment by smartgwt...@gmail.com
on 10 Jan 2011 at 7:18
Issue 562 has been merged into this issue.
Original comment by charles....@gmail.com
on 14 Mar 2011 at 7:44
Original issue reported on code.google.com by
Herist.Z...@gmail.com
on 7 Jul 2010 at 3:20Attachments: