It says this issue should be fixed back in 2015, but it appears it still happens on 4.18.2 (latest as of this time of writing).
It says this issue should be fixed back in 2015, but it appears it still happens on 4.18.2 (latest as of this time of writing).