mirror of
https://github.com/odoo/owl.git
synced 2025-10-06 19:59:41 +07:00
Géry Debongnie
2529aa3ef2
Here is a situation that can happen in some complicated case: 1. a parent component is rendered, which includes some children 2. it is then willPatched 3. the sub components are then mounted/willUnmounted 4. because of complicated business logic, this causes the parent component to be rerendered (before parent "patched" method is called) 5. owl will internally reset its currentfiber to null (but there is a pending rendering!) 6. subsequent rendering will ignore pending rendering 7. havoc ensues This is actually one of the reason why modifying a component state in a willPatch component is actually not a good idea. However, the good news is that this specific situation can be properly handled: we can simply make sure that we do not reset currentFiber to null if there is a new pending rendering. closes #728