Comment 9 for bug 927662

Has this behavior changed in unity 5.6? The version I'm running currently doesn't seem to experience this problem but I'm not sure if there's an actual fix or whether it's a quirk of my current (new) monitor configuration.