Géry Debongnie f18c73e59f [FIX] component: solve a tricky concurrency rendering issue ...

When components were initially rendered more than once, in consecutive
microtask ticks, the order of two actions was reversed: the assignation
of the vnode to the __owl__.vnode property, and the assignation of
__owl__.vnode to the final rendered vdom of the component.

As a result, the widget was rendered as null (so, not present).

The reason for this issue was that the renderPromise key was reassigned
at some point.

2019-07-30 08:54:55 +02:00

..

__snapshots__

[REF] owl: reorganize src code in sub files

2019-07-16 13:12:08 +02:00

component.test.ts

[FIX] component: solve a tricky concurrency rendering issue

2019-07-30 08:54:55 +02:00

props_validation.test.ts

[REF] owl: reorganize src code in sub files

2019-07-16 13:12:08 +02:00