In T181801#2629271, @hacost1809 wrote: Issue still exists in stable 1.2.0.70
Issue still exists in stable 1.2.0.70