Eli Zaretskii writes: > The below seems to fix the problem, but I hope you also have a more > complex real-life use case, because I'm not really sure this solution > has no adverse effects elsewhere. My use case was like this: