Open pySilver opened 1 year ago
Interesting enough typical replace
action does not have such side effects.
Hey @pySilver, thanks for opening this issue. This is definitely an interesting use-case!
Usually I would say, if the replace/update
action serves your needs just use them over morph
.
Though I still want to also make this work for the morph action as well. Or - at least - explain why it doesn't work.
I will take a look and come back to you with my results.
Not sure if it's a bug or expected behaviour but having this markup initially on page:
We cannot issue the following morph:
The following happens: