Comment 2 for bug 1808884

Revision history for this message
Marc Singer (eleventen) wrote :

I believe I have a test case for this issue. I've run it through the three releases from 2017 and on the one release in 2018. All of them produce the same erroneous code.