We can now confirm that the issue does not happen with 4.0.9. This leads to the assumption that the problem has either been fixed between 4.0 and 4.0.9, or, and I consider this much more likely, the problem was introduced between 4.0 and 4.1 on the main branch.
We can now confirm that the issue does not happen with 4.0.9. This leads to the assumption that the problem has either been fixed between 4.0 and 4.0.9, or, and I consider this much more likely, the problem was introduced between 4.0 and 4.1 on the main branch.