Comment 2 for bug 1541999

@kalikiana thanks for pointing this out, the previous change request was actually incorrect. I've marked that previous bug accordingly, and set it as a dupe of this bug to avoid confusion. Thanks!