Thanks for the report, this is fixed at revision#66940.