This issue has been confirmed as fixed in our development code: leaving it open as confirmed for 2.0.
This issue has been confirmed as fixed in our development code: leaving it open as confirmed for 2.0.