Originally posted by joe.parks@hyperproductive.com
View Post
Announcement
Collapse
No announcement yet.
X
-
A quick follow up on this thread. We have now found a way to reliably reproduce this native browser problem in some situations, and have made a framework change to basically touch the affected DOM element in a trivial way which causes the browser to clean up these artifacts.
This change has been made to both the 5.0d and 4.1p branches and is present in the most recent nightly builds.
Regards
Isomorphic Software
Comment
Comment