Now that 4.14 has reached testing, I can confirm that the bug persists under 
4.14.

Reply via email to