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

    isc.ListGrid's body.isFocused is not a function

    SmartClient Version: v9.1p_2016-04-15/Pro Development Only (built 2016-04-15)
    All browsers

    When calling isc.ListGrid's focusInRow method, an error appears saying that this.body.isFocused() is not a method. Is this a bug? Previously, SmartClient 9.1 API did not have this function but the docs now mention it.

    This was added as part of a bug fix because it was necessary in order to allow a certain obscure use case to be achieved (which the docs implied could be achieved, hence its a bug).

    Although way too light on details, your report of an issue already appears impossible (there would be no way for this method to be absent). The only thing we can guess is that you are somehow mixing files from two different versions, possibly due to not clearing your browser cache.


      We have tried the possibility of clearing the browser cache but no good result. It seems that the documentation link I sent you was for SmartClient 10.0 (even though URL says smartclient-9.1). After going to the correct documentation:, it is indicated that the function isFocused does not exist in SmartClient 9.1.

      I was able to replicate this behaviour on SmartClient's Feature Explorer in 9.1 and 10.0 by calling focusInRow. The line of code was ran in the web console. In 9.1, it is expected to return an error. In 10.0, it is expected to run successfully.

      Therefore, the issue seems to persist on the latest SmartClient 9.1. Is this a bug where isFocused is accidentally being used internally in SmartClient 9.1?


        Hi Isomorphic, how is the investigation coming along (if any)?


          We've found and fixed the culprit. Sorry for the inconvenience.

          Please try the next nightly build, dated Aug 16 or above

          Isomorphic Software


            Hi Isomorphic,

            Where is the nightly build for August 16 or above? I cannot find it at:



              The August 16 build is up now at the URL you linked. There was a deployment issue that's now been resolved. Apologies.