Comment 7 for bug 1484105

@Junien

This is against 1.25 which is in Critical-bug-fixes only mode. From reading comment#5, this bug was fixed by another. Are you seeing the problem with 1.25.6? The last communication here was back in June. If this bug is Critical, please comment why, for example lack of workaround, etc. We'll be happy to raise it higher \o/

Our current focus in on 2.0. Is this still happening with 2.0-beta16?