Does anyone know if this is a bug or if there's anyway I could workaround this behavior?
Issue:
What I expected:
What I've found:
Hi Gustavo,
I tried to reproduce this issue, but couldn't. Can you share an OML where the issue happens?
Hi, Aurelio :).
Just managed to isolate the behavior to a single module, which you can find attached.
Steps to reproduce: