Followup for bug 39099