Comment 15 for bug 1759732

If what Jean-Baptiste (and Steve) confirmed is true and the issue is not a regression from .4, I do not feel that we should re-spin just to include this fix. If it was there in the previous point-release and we did not block on it then, not sure we should right now. Not to mention there has been almost 4 months to get this fixed.

What I can propose is that we pull in this fix *if* we re-spin for some other reasons.