Here is another patch, I'm not sure we should handle multiple versions
of webkitgtk. But as this bug is corrected in newer (recent, stable)
versions of webkitgtk, should we remove the needless workaround and
assume user has a valid version of webkitgtk ?
Received on Mon Feb 10 2014 - 00:13:18 CET