Hmm, I have MATE 1.14 and GTK+ 3.22 on Debian Testing/Unstable, and I can't reproduce the issue. Could it be that this is specific to GTK+ 3.20 and fixed later on?
Hmm, I have MATE 1.14 and GTK+ 3.22 on Debian Testing/Unstable, and I can't reproduce the issue. Could it be that this is specific to GTK+ 3.20 and fixed later on?