Update on what happened in WebKit in the week from August 31 to September 7.
This was another week focused on ironing out graphics issues in preparation for the upcoming 2.54.x release series. Did we say release? Here we have another set of packaged release candidates as well!
Cross-Port 🐱
The “paint flushing” feature of the Web Inspector that shows the areas of the
layers that were painted is now
available. On the other hand, setting
WEBKIT_SHOW_DAMAGE=1 in the environment will show the areas of the window
that were rendered. For example, if the page is scrolled a little, the whole
window is rendered, but no layer has to be repainted.
Graphics 🖼️
Fixed visible pixel snapping in the GTK and WPE ports' Skia compositor by choosing linear instead of nearest-neighbor sampling for backing store tiles whenever a layer's transform no longer maps tile pixels onto screen pixels 1:1, matching what the Texture Mapper backend already got from its always-linear OpenGL code path.
Fixed a clipping bug in the
Skia-based compositor that caused layers with overflow: hidden set to
not clip blur and box-shadow filter outsets.
Fixed a repaint bug where content
changing behind an element with a software-rendered filter such as blur()
could leave stale pixels on screen, as with the glow effect that YouTube draws
around videos in dark/ambient mode. The fix restores proper tracking of which
layers act as the repaint container for a pixel-moving filter, so the repaint
area is expanded correctly again on WPE, GTK and macOS.
Releases 📦️
Release candidates WebKitGTK 2.53.92 and WPE WebKit 2.53.92 have been published, and they include polishing and a number of fixes that ensure that there will not be noticeable regressions brought in by the new Skia-based compositor and the damage tracking support—two of the main features of the upcoming stable release series. As the stable release dates approaches, we encourage people who try these preview versions to report issues in Bugzilla.
That’s all for this week!
