Will not fix in 3.0.x. The problem has been there since much earlier releases and we do not have time to fix in 3.0. This will be taken care in 3.1. It's not a critical issue.
Will not fix in 3.0.x. The problem has been there since much earlier releases and we do not have time to fix in 3.0. This will be taken care in 3.1. It's not a critical issue.