Comment 2 for bug 1667509

Revision history for this message
Thomas Preud'homme (thomas-preudhomme) wrote :

Hi,

I could reproduce this with our 5-2016Q3 release but it seems fixed from 6-2016Q4 onwards. I suggest that you move to our most recent 6-2017Q1 release that was released yesterday.

Best regards.