Good To know ! Waiting 5.3.0 then !
But anyone know if this is fixed in 5.2 ? (If not, we can maybe except the fix incoming in 5.3.0 to be moved in 5.2.X, no ?)
Good To know ! Waiting 5.3.0 then !
But anyone know if this is fixed in 5.2 ? (If not, we can maybe except the fix incoming in 5.3.0 to be moved in 5.2.X, no ?)