Thank you for the notice. It did get fixed for version 2.39 but it wasn’t reported for version 40 but I don’t know if it was already working in version 40 and this bug reappeared?
Yes, same issue that is described in the ticket linked to this topic. 
Thanks!