View Full Version : [FIXED] Buffered view isn't refreshed correctly when store events are queued

22 Jul 2015, 6:43 AM
Steps to reproduce:
1) open fiddle
2) press 'outdent 3 w/o....' -> see node now is sibling to it's parent
3) press 'outdent 5 w/...' -> node 5 is sibling to it's parent, but it's duplicated. refresh view and it's fine again

Reproducible in Ext 6.0, Ext 5.1 is fine, because of extra refresh.


Normally refresh would happen right after node is removed from store, and after that it's added again and 'itemadd' event triggers single node rendering.
When queue is suspended, refresh happen after all changes are made, so no need to append new record, it'll be duplicate.

Gary Schlosberg
22 Jul 2015, 3:19 PM
Thanks for the report! I have opened a bug in our bug tracker.

22 Jul 2015, 7:27 PM
Can you suggest a workaround?

24 Jul 2015, 6:04 AM
Hi there. I've posted a workaround in the fiddle.

But queueing up events during a suspend and then firing them all after a whole bunch of operations have happened cannot be guaranteed to work by us.

At the time each event was fired, the application and its objects were all in a certain state which will be constantly changing.

When events are resumed and flushed, the state is will be different to the state that the event fired on.

The workaround will fix this one particular scenario.

But I do not think this code should go into the mainline.

30 Oct 2015, 5:07 AM
Is this already corrected?