Description

reports that #10537 has reappeared in 1.1 rc1. I do not have time to investigate right now but from a brief look it appears the test added for #10537 might not notice the nature of the change reported in that comment, and that it could be a side-effect of the fix for #10061.