[jaredm]

We can't really look into an issue that existed in builds 2 months ago, especially when we don't see it against more recent builds. You'll need to re-test the IE11 case against the latest build from smartclient.com/builds.

However, if you wait until tomorrow's build, you can also test the fix we just applied to deal with the Chrome bug, which we *were* able to reproduce.

Hi Isomorphic,

With regards to the Chrome fix, I look forward to it and will test the next nightly - thank you for trying to address this.

For IE11, I reported that I tested it with the current hands on demo dated today (17 Feb 2016) and observed the same issue - and included a screenshot of what I observed when running the provided sample code in your Showcase environment. Can you confirm that when you test the issue in IE11 you see the tabset appear when expanding the last row?

[Isomorphic]

The Showcase is a specialized environment. Do you see the issue outside of the Showcase?

[jaredm]

The Showcase is a specialized environment. Do you see the issue outside of the Showcase?

I have just downloaded the latest Pro: "v10.1p_2016-02-17/Pro Development Only" and continue to see the the reported issue with IE11.

[Isomorphic]

Did you still paste your code into the Feature Explorer? If so, you need to run it outside of that environment.

If not, please post the entire bootstrap file for your test-case.

[jaredm]

Did you still paste your code into the Feature Explorer? If so, you need to run it outside of that environment.

If not, please post the entire bootstrap file for your test-case.

Hi, I didn't paste it into the Feature Explorer, I used the same stand-alone sample that I provided in Post #6 - nothing has changed: http://forums.smartclient.com/forum/...960#post231960

Thanks

[Isomorphic]

Ah, ok - we see the issue in IE11 now also - the difference was the row-count - our sample code had 25000 rows, a value you'd noted earlier in the thread, but your code has 40000.

Hang fire on updating to test the Chrome fix while we retest.

[jaredm]

Ah, ok - we see the issue in IE11 now also - the difference was the row-count - our sample code had 25000 rows, a value you'd noted earlier in the thread, but your code has 40000.

Hang fire on updating to test the Chrome fix while he retest.

Ok, thanks - you guys are great! I will wait for your update and will be ready to retest

[Isomorphic]

By way of an update: we have a couple of ways to fix this issue as it appears in Chrome, where the cause of the misbehavior is well understood. The fix we're considering would fix Chrome permanently in this regard, and would also apply a general optimization to Canvas.get[Left/Top]() calls. But it's a change to low-level Canvas code and requires deep testing before it hits builds.

As regards the issue in IE11 - we see this misbehavior also, but it's not the same cause as in Chrome. The cut-off value in this browser (where widget misplacement begins) is about 1.5 million pixels, and we've yet to find a sensible workaround.

We'll update later, when we have more information.