(In reply to Michael Catanzaro from comment #34)
> Oh and to complicate matters further, we're switching to a new graphics
> architecture in WebKitGTK+ 2.14.0, which is available now for testing in
> WebKitGTK+ 2.13.4. It might cause this bug to occur all of the time (because
> accelerated compositing mode is now used always), or never (who knows!)
(In reply to Michael Catanzaro from comment #34)
> Oh and to complicate matters further, we're switching to a new graphics
> architecture in WebKitGTK+ 2.14.0, which is available now for testing in
> WebKitGTK+ 2.13.4. It might cause this bug to occur all of the time (because
> accelerated compositing mode is now used always), or never (who knows!)
It now occurs all of the time.