Hello

Could you provide some demo on codepen?

Here's the pen:
https://codepen.io/ovictorribeiro/pen/xPZrwo

thanks

ok, so this happens because after deletion you send EXACT same layout of current cluster.
clusterize has additional check to prevent unnecessary updates if layout wasn't changed

the only difference between rows after row number 80 is numbers. but after deletion you restoring numbers of subsequent rows. layout stored in clusterize cache and updated layout for current cluster are equal, that's why this condition fails for your case.

what you can do:

1. dirty but quick workaround.
   after deletion - change your list at least somehow to give a hint for clusterize to update list.
   here I've added data-update attribute, data property increments on every deletion so this should help.
   https://codepen.io/NeXTs/pen/rYxpbm?editors=1010

2. Wait until I publish update for clusterize (day or two) that would allow you to use pure css counters.

Oh thank you very much for the workaround and for the explanation (thanks for the redundance tip too).

I'll implement your solution. I'll wait for the update, though.

Hey @jvribeiro
see demo of "Ordered list" + explanation in FAQ

Cool! That was pretty fast.

case Nothing change, could return something in callback ?