Good day, just to confirm; is this issue solved until 6.0.0? It keeps presenting on 5.0.7. I thought it was resolved since 19/Mar/2014.