No announcement yet.
  • Filter
  • Time
Clear All
new posts

    We're saying that your code runs as expected for us against the latest framework code in all recent branches, without any crashes or warnings, as far as we can see.

    We don't see any fixes having been made specifically for this issue you mention, but several sort bugs have been fixed in the last two weeks, including two yesterday, so a retest seems like the best way forward.

    We're not sure why you'd want to know whether there was a temporary regression in a particular build from several weeks ago - you did say that it has since been fixed, right?

    Anyway, we've also just added a null check to the code you showed in your stack-trace, just in case. That won't be available until June 12 builds.

    Let us know how you get on.


      Hi Isomorphic

      the regression stuff in the beginning was an assumption from what I was seeing when I did not know the root cause (prior to post #8). I'll just retest and let you know.

      Best regards


        Hi Isomorphic,

        the bug does not occur for me using v10.0p_2015-06-11 in FF26 (and, like before, also not in GC43, IE11).

        Thank you & Best regards