After investigation, it seems it works for some spinners and not for others.
This bug is in fact due to an ambiguity in some models. The CDK timeout element is described twice: one for providers and one for consumers. Sometimes, the data-binding finds the provides first while it has a consumes in the model. And vice-versa.
A solution would consist in factorizing the common elements. But this has an impact on the elements insertion order.
Another solution is to check the parent (provides or consumes) in the intialization command.
After investigation, it seems it works for some spinners and not for others.
This bug is in fact due to an ambiguity in some models. The CDK timeout element is described twice: one for providers and one for consumers. Sometimes, the data-binding finds the provides first while it has a consumes in the model. And vice-versa.
A solution would consist in factorizing the common elements. But this has an impact on the elements insertion order.
Another solution is to check the parent (provides or consumes) in the intialization command.