There will be a workaround for this issue in the upcoming WebKitGTK+ 2.12.4 release (which should occur within the next few days).
There will be a workaround for this issue in the upcoming WebKitGTK+ 2.12.4 release (which should occur within the next few days).