Comment 109 for bug 1690719

Revision history for this message
In , Thomas-godart-gm (thomas-godart-gm) wrote :

With the recent launch of Firefox 57 while I was testing it (both on Ubuntu and Android), I randomly arrived on words by Mozilla which totally correspond to our topic here, as far as I understand Gnome 3 being a web-like css gui compositing tool:

(from https://hacks.mozilla.org/2016/02/smoother-scrolling-in-firefox-46-with-apz/ )

"Browsers traditionally handled user input events on the browser’s main event-handling thread. This meant that it could get blocked by pretty much anything else the browser was doing, including running scripts and painting. In Firefox, the Electrolysis (e10s) project separates the content process from the main browser process. This gives us another path for handling input events. Instead of passing the input events from the parent process to the content process to drive scrolling as usual, the input events are used to drive scrolling in the parent process compositor before they are forwarded to the child process for normal processing and dispatch. This is illustrated in the diagrams below."