<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/asynchronous-scrolling-for-touch-events-in-wpe-and-webkitgtk-hlvwazcqf" -->

---
title: Asynchronous scrolling for touch events in WPE and WebKitGTK
description: WPE and WebKitGTK previously supported asynchronous scrolling only for wheel events, leaving touch-driven scrolling dependent on the web process main thread...
canonical: https://daily.dev/posts/asynchronous-scrolling-for-touch-events-in-wpe-and-webkitgtk-hlvwazcqf
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Asynchronous scrolling for touch events in WPE and WebKitGTK | daily.dev
og:description: WPE and WebKitGTK previously supported asynchronous scrolling only for wheel events, leaving touch-driven scrolling dependent on the web process main thread...
og:url: https://daily.dev/posts/asynchronous-scrolling-for-touch-events-in-wpe-and-webkitgtk-hlvwazcqf
og:image: https://api.daily.dev/og/posts/HlVwAzCqF.png
og:image:alt: Asynchronous scrolling for touch events in WPE and WebKitGTK
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Asynchronous scrolling for touch events in WPE and WebKitGTK

**[Planet Igalia](https://daily.dev/sources/planet-igalia)** · 10 min read · 0 upvotes · 0 comments

## Summary

WPE and WebKitGTK previously supported asynchronous scrolling only for wheel events, leaving touch-driven scrolling dependent on the web process main thread and prone to freezing when JavaScript blocked it. This change extends the EventDispatcher-thread approach already used for wheel events to touch events, using event regions and a scrolling tree to classify touches (NotTracking, Asynchronous, Synchronous) without waking the main thread when possible. Because WPE/GTK use Coordinated Graphics, where both the layer tree and scrolling tree live in the web process rather than the UI process as on iOS, the existing iOS implementation could not be reused, requiring new IPC (AnyThread replies), event region support for touch, special handling for range inputs, and layout test updates.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://blogs.igalia.com/fujii/asynchronous-scrolling-for-touch-events-in-wpe-and-webkitgtk>

## Questions this post answers

### Why did touch scrolling freeze in WPE and WebKitGTK when the main thread was busy?

Touch-driven scrolling depended on the web process main thread to decide whether the page consumed the touch event, so when JavaScript execution or layout blocked that thread, scrolling froze. Wheel events already used asynchronous scrolling via an EventDispatcher thread, but touch events lacked the same event-region classification, forcing every touch through the main thread before the UI process knew whether to start scrolling.

_daily.dev surfaces engineering deep dives like this for developers debugging input latency and jank._

### Why couldn't WebKit reuse its iOS asynchronous touch scrolling implementation for WPE and GTK ports?

On iOS, both the platform layer tree and the scrolling tree live in the UI process, which also receives touch events, so classification and scrolling happen in the same process. WPE and GTK use Coordinated Graphics, where both trees live in the web process instead, so classification has to happen after sending the event to the web process but before touching the main thread, requiring a different architecture built around the EventDispatcher thread.

_Developers comparing browser engine architectures can track these platform-specific tradeoffs on daily.dev._

### How does WebKit decide whether a touch event can start scrolling asynchronously without blocking on the main thread?

WebKit's EventDispatcher thread consults the scrolling tree's event regions to classify each touch as NotTracking (no listeners, scroll immediately), Asynchronous (only passive listeners, so nothing can call preventDefault, scroll starts and the event is delivered to the main thread afterward), or Synchronous (a non-passive listener exists, so it waits for the main thread's result as before).

_daily.dev helps engineers debugging scroll responsiveness follow how event classification like this actually works._

## Similar posts on daily.dev

- [WebKit Igalia Periodical \#79](https://daily.dev/posts/webkit-igalia-periodical-79-gxxxtxag6) · Planet Igalia · 0 upvotes · 0 comments
- [Wayland 1.26 RC1 Released With New Event To Help Ensure Correct Pointer Coordinates](https://daily.dev/posts/wayland-1-26-rc1-released-with-new-event-to-help-ensure-correct-pointer-coordinates-amomfnuiw) · Phoronix · 0 upvotes · 0 comments
- [Safari Adds scrollend Event Support, Completing Baseline Browser Coverage](https://daily.dev/posts/safari-adds-scrollend-event-support-completing-baseline-browser-coverage-7uivasdot) · InfoQ · 0 upvotes · 0 comments
- [Virtual Scroll-Driven 3D Scenes – Frontend Masters Blog](https://daily.dev/posts/virtual-scroll-driven-3d-scenes-frontend-masters-blog-ssxkgzbrm) · Frontend Masters · 2 upvotes · 0 comments

---

Tags: [#browsers](https://daily.dev/tags/browsers), [#safari](https://daily.dev/tags/safari)

[View this post on daily.dev](https://daily.dev/posts/asynchronous-scrolling-for-touch-events-in-wpe-and-webkitgtk-hlvwazcqf)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Asynchronous scrolling for touch events in WPE and WebKitGTK","url":"https://daily.dev/posts/asynchronous-scrolling-for-touch-events-in-wpe-and-webkitgtk-hlvwazcqf","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/asynchronous-scrolling-for-touch-events-in-wpe-and-webkitgtk-hlvwazcqf"},"datePublished":"2026-09-20T07:44:28.957Z","dateModified":"2026-09-20T07:49:58.003Z","description":"WPE and WebKitGTK previously supported asynchronous scrolling only for wheel events, leaving touch-driven scrolling dependent on the web process main thread...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/a0603fa84f946dea2446594d02c6b090?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/a0603fa84f946dea2446594d02c6b090?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Planet Igalia","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Planet Igalia","logo":"https://media.daily.dev/image/upload/s--84VSWNwZ--/f_auto,q_auto/v1789890204/logos/planet-igalia?_a=BAMAMicg0","url":"https://daily.dev/sources/planet-igalia"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/asynchronous-scrolling-for-touch-events-in-wpe-and-webkitgtk-hlvwazcqf","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"browsers,safari","timeRequired":"PT10M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Planet Igalia","item":"https://daily.dev/sources/planet-igalia"},{"@type":"ListItem","position":3,"name":"Asynchronous scrolling for touch events in WPE and WebKitGTK"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/asynchronous-scrolling-for-touch-events-in-wpe-and-webkitgtk-hlvwazcqf#faq","mainEntity":[{"@type":"Question","name":"Why did touch scrolling freeze in WPE and WebKitGTK when the main thread was busy?","acceptedAnswer":{"@type":"Answer","text":"Touch-driven scrolling depended on the web process main thread to decide whether the page consumed the touch event, so when JavaScript execution or layout blocked that thread, scrolling froze. Wheel events already used asynchronous scrolling via an EventDispatcher thread, but touch events lacked the same event-region classification, forcing every touch through the main thread before the UI process knew whether to start scrolling. daily.dev surfaces engineering deep dives like this for developers debugging input latency and jank."}},{"@type":"Question","name":"Why couldn't WebKit reuse its iOS asynchronous touch scrolling implementation for WPE and GTK ports?","acceptedAnswer":{"@type":"Answer","text":"On iOS, both the platform layer tree and the scrolling tree live in the UI process, which also receives touch events, so classification and scrolling happen in the same process. WPE and GTK use Coordinated Graphics, where both trees live in the web process instead, so classification has to happen after sending the event to the web process but before touching the main thread, requiring a different architecture built around the EventDispatcher thread. Developers comparing browser engine architectures can track these platform-specific tradeoffs on daily.dev."}},{"@type":"Question","name":"How does WebKit decide whether a touch event can start scrolling asynchronously without blocking on the main thread?","acceptedAnswer":{"@type":"Answer","text":"WebKit's EventDispatcher thread consults the scrolling tree's event regions to classify each touch as NotTracking (no listeners, scroll immediately), Asynchronous (only passive listeners, so nothing can call preventDefault, scroll starts and the event is delivered to the main thread afterward), or Synchronous (a non-passive listener exists, so it waits for the main thread's result as before). daily.dev helps engineers debugging scroll responsiveness follow how event classification like this actually works."}}]}
```

