It has been fixed post rev#74255.
Thank you for reporting.