Interesting. Another report (bug 1202388) indicated that 5.19.1 still shows the problem, so I don't bet yet :)