This "bug" is purely symptomatic and people with totally different prerequisites claim to see the "same" issue. You can literally see a person commenting after me saying the exact opposite of my testing:
> Apparently GTK+ 3.2.3 WebKitGTK+ 1.6.3 doesn't have the bug.
> This issue is not fixed in GTK+ 3.2.3[introspection xinerama] with WebKitGTK+ 1.6.3
There is nothing wrong with Midori, WebKit or GTK+. Whatever the problem is, it's evidently something else.
This "bug" is purely symptomatic and people with totally different prerequisites claim to see the "same" issue. You can literally see a person commenting after me saying the exact opposite of my testing:
> Apparently GTK+ 3.2.3 WebKitGTK+ 1.6.3 doesn't have the bug.
> This issue is not fixed in GTK+ 3.2.3[introspection xinerama] with WebKitGTK+ 1.6.3
There is nothing wrong with Midori, WebKit or GTK+. Whatever the problem is, it's evidently something else.