I'm pretty sure that this issue is valid for 6.0, but it's not critical, so, it probably will stuck in "won't fix" state.
However, it could be resolved for 6.1/7.0, and that needs to be checked.
I'm pretty sure that this issue is valid for 6.0, but it's not critical, so, it probably will stuck in "won't fix" state.
However, it could be resolved for 6.1/7.0, and that needs to be checked.