Composition modes and fix for fixed elements flickering #32
Conversation
* It is pretty clever, but doesn't work that well with fixed elements. * This should fix jerking of fixed elements at the top of the screen, for example on our forums. * The downside is that regular content scrolling has visible artifacts near the top, but it's not as bad as with fixed elements.
| rectAtSrc = rectAtSrc & rectAtDst; | ||
| rectAtDst.OffsetBy(xOffset, yOffset); | ||
|
|
||
| offscreenView->CopyBits(rectAtSrc, rectAtDst); |
There was a problem hiding this comment.
Removing this means the whole webpage is always redrawn everytime one scrolls, instead of just the newly exposed part. Is that ok? Wouldn't it make scrolling on slow to draw webpages even worse?
There was a problem hiding this comment.
Yes, this is a trade-off. Tiled backing store could probably solve both issues, but I'm reluctant to put more work into WebKitLegacy API.
There was a problem hiding this comment.
Fair point.
I had TiledBackingStore working at some point but it tends to create huge bitmaps (2048x2048) and several of them, if we would go in that direction we should at least remove the current offscreen buffer.
Well, I guess that's good enough for WebKitLegacy and start to see about moving things to WebKit2 indeed.
No description provided.