Ubuntu
webkitgtk package

  1. Bug #1615871
  2. Comment #51

Comment 51 for bug 1615871

Revision history for this message
In , Michael Catanzaro (mike-catanzaro) wrote :

(In reply to Michael Catanzaro from comment #31)
> Note that Chrome does not use WebKitGTK+ and has a completely different
> graphics architecture; might be worth reporting a second bug.

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!), but it should definitely no longer occur on a small subset of web pages anymore.