Maintain angular bindings on cloned frozen columns

Maintain angular bindings on cloned frozen columns

Posted by: matt_baker on 11 April 2018, 9:49 am EST

• 

  matt_baker

  • Post Options:
  • Link
    Copy

  Posted 11 April 2018, 9:49 am EST

  I have grid with 30 or so columns and 500+ grouped rows, with the first 6 or 7 columns frozen. In these frozen columns, I have celltemplates with buttons with ng-click enabled. As I scroll horizontally, the frozen columns “flicker”, as if theyre unable to keep up with the scrolling (this is not an issue in Chrome).

  I noticed that setting cloneFrozenCells to true eliminates the flicker, however the angular bindings no longer work (the ngclicks are never fired).

  Is there a way to fix the bindings, or a fix for Safari’s flicker behavior on horizontal scrolling?

• 

  matt_baker

  • Post Options:
  • Link
    Copy

  Posted 11 April 2018, 10:20 am EST

  See fiddle http://jsfiddle.net/fjo2Leq7/. Using Safari 11.1 in macOS 10.12.6.

  Setting “s.cloneFrozenCells = false;” enabled the ng-click call, setting it to true kills it.

  The only workaround I see is to use plain JS in my frozen columns, however in my app the columns are user-determined, which means I’d have to revert all my angular-specific templating to JS, which is not desirable.

• 

  grapecity

  • Post Options:
  • Link
    Copy

  Posted 12 April 2018, 10:19 am EST

  Hi,

  We were able to replicate the issue at our end and reported it to the concerned team.
  
  Till then you can use the following workaround to capture click event when cloneFrozenCells is set to true:- http://jsfiddle.net/ahwmcj0e/

  ~nilay

  (Internal Use Only)
  
  Bug 317454
  
  Bug 317455