Thanks for sharing. I think it will be fixed on Discourse, in the meantime it’s a functional workaround.
Something important to mention is that the component uses MutationObserver and it is a practice that is suggested to avoid.
1 Like